Karmic Rule Two
Nothing raises issues like contact with reality. Karmic Rules for Writing Pretty Good Code
You may also enjoy
Turning the Crank: Design as a Mechanical Process
What a good design artifact looks like, what they’re actually for, and how to use them efficiently to achieve a better outcome for your project.
Git Flow By Example: Writing Down Your Version Control Process
If you haven’t written down your project’s version control process in all its unique glory, then you don’t have one!
Design as Code: A Frictionless Low-Level Design Pipeline
A frictionless low-level design process that integrates with your dev cycle and puts design artifacts at a peer level with the rest of your codebase.
A Modern Agile Project Manifesto
A battle-tested, all-inclusive starting point for a modern Agile project.
Project Governance Toolkit
Running a software development project is hard, but it’s way easier if you have a plan!
Composition in Action: Finishing the Swing
In software engineering, what look to be the easy parts often turn out to be the hard parts. If you’re lucky, the reverse is also true, but don’t count on it.
Mixin It Up: Picking The Right Problem to Solve
Sometimes, when you’re tangled up in a thorny problem, solving it is exactly the wrong answer.
Karmic Rule Five
generic logic + custom config ≫ custom logic – Karmic Rules for Writing Pretty Good Code
Leave a comment