The hottest Software Quality Substack posts right now

And their main takeaways
Category
Top Technology Topics

Genie: Death of the Iron Triangle?

Software Design: Tidy First? • 243 implied HN points • 02 Mar 26
🕹 Technology Software Quality
  1. The old Iron Triangle idea—pick any two of better, sooner, or cheaper—doesn't fit software development.
  2. If you fix quality high and let scope vary (an idea from XP), teams can actually deliver sooner and for less cost.
  3. Faster, cheaper, and sooner are connected, and achieving them is a deliberate trade-off of scope rather than a bit of magic.

Software's Iron Triangle: Cheap, Fast and Good - Pick Two

Resilient Cyber • 39 implied HN points • 14 Aug 24
🕹 Technology Software Quality
  1. Balancing quality in software is tough. You can have it cheap, fast, or good, but you can only pick two options.
  2. There's a big gap in information between software makers and users. Many users don’t really know what's in the software they use or how secure it is.
  3. The security of software often takes a back seat to speed and cost. This leads to issues where security measures are seen as extra costs, not necessities.

What we don't talk about when we talk about quality...

The faintest idea • 319 implied HN points • 24 Dec 23
🪑 Design Software Quality
  1. Quality really matters in software because it makes products more valuable and worth paying for. Just like with clothes or furniture, better quality provides a better experience.
  2. Software isn't always compared just by quality since functionality plays a big role too. It's important to fix the small details that make a big difference for users.
  3. People will feel the difference in quality when using software, even if it doesn't show up in simple success metrics. That feeling can influence their choices and how much they are willing to pay.

In Quality, the secret sauce is feedback!

Wisdom over Waves • 79 implied HN points • 11 Jan 24
🕹 Technology Software Quality
  1. Quality in software is about fast and fabulous delivery without compromising on quality.
  2. Defining quality can be subjective, meeting customer needs they may not even know they have.
  3. Feedback is the secret sauce to understanding customer needs, with practical tips like frequent releases, attentive listening, and exploring multiple feedback layers.

How bad is Architectural Complexity [System Design Sundays]

Technology Made Simple • 79 implied HN points • 06 Mar 23
🕹 Technology Software Quality
  1. Complex architectures can significantly impact developer productivity, software quality, and turnover, with potential for 50% drops in productivity and significant increases in defect density and staff turnover.
  2. Architectural complexity can lead to increased defect density in codebases, higher time consumption, and a higher probability of developers leaving the firm.
  3. Complexity can breed more complexity, creating a cycle that hampers future system developments.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Software Quality

Engineering Enablement • 37 implied HN points • 05 Jan 24
🕹 Technology Software Quality
  1. Software quality encompasses four types: process, code, system, and product quality.
  2. Process quality sets the foundation for overall software quality by having a strong development process.
  3. Code quality is crucial for system quality and product quality, focusing on maintainability and reducing defects.

An Interview with Matthew Bischoff

Syntopikon • 0 implied HN points • 14 Jul 23
🕹 Technology Software Quality
  1. Matthew Bischoff started and runs Lickability, a software design & development studio, creating apps for known companies.
  2. Resources to learn software development include online courses, tutorials, and hands-on practice, emphasizing the importance of learning by doing.
  3. Well-designed apps are fast, easy to use, accessible, and solve real problems visibly crafted by a caring team.