According to a 2018 poll by @stripe, $85 billion per year are spent on dealing with "bad code".
Bad quality incurs a technical debt every time the code is altered. And this debt does not stay intangible for long.
Here are 5 things about code quality that you should know!
🧵
1️⃣ Expressing empathy to the reader.
Writing high-quality code is expressing empathy to the readers.
Thinking about how our code affects humans is a powerful form of empathy in practice, one that no organization can afford to ignore.
2️⃣ Software Quality Attributes
⭐ External: such as UI
⭐ Internal: architecture
External quality enhances user experience.
Internal quality enhances the software.
3️⃣ Low internal quality
Low internal quality can start with high productivity but eventually slow it down.
4️⃣ High Internal Quality
High internal quality poses an initial cost but accelerates productivity moving forward.
5️⃣ Cruft
Cruft is the difference between the current code and how it would ideally be.
More cruft 🡪 Less productivity.
Less cruft 🡪 More productivity.
This thread is highly inspired by below articles:
• martinfowler.com/articles/is-quality-worth-cost.html
• stackoverflow.blog/2021/10/18/code-quality-a-concern-for-businesses-bottom-lines-and-empathetic-programmers/
You can read the unrolled version of this thread here:
typefully.com/u/itsadityagupta/t/T76R7A8N57Kd
➼ TL;DR
1️⃣ High code quality shows empathy for the reader.
2️⃣ Software Quality Attributes
3️⃣ Low Internal Quality means low productivity.
4️⃣ High Internal quality means high productivity but comes with an initial cost.
5️⃣ Cruft: Diff. b/w the ideal code and current code.