Karmic Rule Three
If you want to get a complex process right, template it. Karmic Rules for Writing Pretty Good Code
You may also enjoy
Showing My Code: An Open Response to Elon
Elon Musk recently put out a call for coders: “Just show us your code!” Here’s mine.
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.
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.
Anatomy of a Next.js Application
Here’s a useful way to think about a Next.js app that will be built by a team.
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
Karmic Rule Zero
Minimize external dependencies and try not to use shitty libraries. – Karmic Rules for Writing Pretty Good Code
Leave a comment