software architecture
Programming Pearls
The text compiles programming advice and principles, offering memorable rules and insights from various experts in software development, coding, debugging, performance optimization, user interfaces, and documentation.
moss.cs.iit.eduCoding with AI takes (and enables) more discipline.
I need more tests, more checks and constraints. This takes more scaffolding, which is now fast to create.
More “how will I know this works?” and less “how will I implement this?”
I need to learn how to influence the AI, and channel frustration into guidance.
More high-level thinking about what the sof... See more
I need more tests, more checks and constraints. This takes more scaffolding, which is now fast to create.
More “how will I know this works?” and less “how will I implement this?”
I need to learn how to influence the AI, and channel frustration into guidance.
More high-level thinking about what the sof... See more
Jessitron • Augmented Coding: an Experience Report
When production code is important, then it is a minority: most project code is scaffolding. Tests, deployments, linting, verification, utilities for local development, handy admin interfaces–scaffolding is code that helps us safely and efficiently change production code.
Augmented Coding: an Experience Report
Dan Hockenmaier on Substack
substack.com
Org debt is just as dangerous as tech debt but is talked about much less
Org debt builds up every time a company operates without discipline:
- Inconsistent principles for promotions and comp
- Hiring without a clear scope for the new role
- Trying new operating models but not sticking to them
- Allowing meeting creep
In the short term, it's always easier to just let this stuff happen. But in the long term, org debt will destroy a company. Execution will slow down, people will get frustrated, and the best ones will leave.
If you're considering joining a company, assess org discipline in the same way you'd assess their metrics and team.
The benefits of incremental development include a reduction of the potential risk in the project. If the architecture is for a family of related systems, the infrastructure can be reused across the family, lowering the per-system cost of each.
Rick Kazman • Software Architecture in Practice, 4th Edition
enabling incremental development
This practice gained attention in the early 2000s through the ideas of Alistair Cockburn and his notion of a “walking skeleton.” More recently, it has been adopted by those employing MVP (minimum viable product) as a strategy for risk reduction.
Paul Clements • Software Architecture in Practice, 4th Edition
enabling incremental development
The fidelity of the system increases as extensions are added, or early versions are replaced by more complete versions of these parts of the software. In some cases, the parts may be low-fidelity versions or prototypes of the final functionality; in other cases, they may be surrogates that consume and produce data at the appropriate rates but do li... See more
Paul Clements • Software Architecture in Practice, 4th Edition
enabling incremental development