Niceties
Concise observations, nuanced technical specialties, code and design insights, and occasional humor—short-form notes on engineering patterns, best practices, and lessons learned from real life. Shorter than Writings, more detached than Deliverables, but still sharp and valuable.
-
Architecture, Design.
This is just the short clarification for those hesitant about the subjects
-
Export Members from a TypeScript NPM Package
The short memo on how to conveniently export members of a TypeScript NPM package.
-
Scrum at a Glance
A quick grasp of Scrum and a handy reference based on the latest Scrum Guide.
-
Multiple Conditionals Clean Way
Make conditionals of any size readable and manageable.
-
Technical Debt in the Eye of the Beholder
Humor. Or is it?
If a tree falls in a forest and no one is around to hear it, does it make a sound?. Yet another metaphor—perhaps useful—seeding the ever-growing silo of software analogies.
-
Monolith, Not Ball of Mud
See Big Ball of Mud pattern.
My answer for this StackOverflow question, explaining "modular monolith" term introduction redundancy.
-
Design is Inevitable
-
The Death of Agile (Allen Holub)
Who is Allen Holub, his books.
The YouTube video transcript summary by DeepSeek discussing Agile and Scrum.
See also Martin Fowler's (one of Agile Manifesto's creators) The State of Agile Software in 2018 article.
-
When Bother with Events
When "you aren't gonna need it" (YAGNI) and when you do actually need events.
-
How Good Are Bad Software Engineers (Stan)
Talking 10x programmers? What about "minus 1"? "minus 5"? Paired reading with the one from Nasir Afaf.
-
Software Engineer Toolbox Granularity
My personal approach here is that software creation tooling—both managerial and engineering—is often presented in books and media as monolithic. In reality, these are composites of dozens to hundreds of smaller, independent tools that each bring their own value.
-
Old Programming Joke
still actual as ever...
-
Code-and-Fix Development
McConnell's original definition from his Professional Software Development (2003) book, p. 50.