
A Philosophy of Software Design Summary: Deep Modules Beat Small Ones
John Ousterhout's book in one sitting: complexity is the enemy, deep modules fight it, and 10–20% of your time should go to design. Five ideas to use on Monday.
Tag archive

John Ousterhout's book in one sitting: complexity is the enemy, deep modules fight it, and 10–20% of your time should go to design. Five ideas to use on Monday.

A practical Android guide to let, run, with, apply, and also, with real-world failure modes that quietly break production code.
The Problem Every HR system has a leave request, and every leave request has a...

The Art of Naming Things in Code: Ditch Single-Letter Variables and utils Classes While finding...
Uma jornada prática de estudos que transformou rotinas utilitárias do dia a dia em micro-pacotes com...
We learn DRY early: do not repeat yourself. So we extract, generalize, and parameterize. And...

Clean code is code that a developer other than its author can read, change and extend without fear....
Refactoring is making codes more elastic while not breaking

Clean code is about the reader, not cleverness. This post covers naming, guard clauses, pure functions, refactoring with a safety net, SOLID in plain English, and patterns like strategy, adapter, and wrappers, then builds a provider-agnostic summarizer.

In Java date formatting, uppercase YYYY represents the week-based year, while lowercase yyyy...
How to decouple presentation, domain invariants, and data sources in high-throughput mobile...
Every software engineer has faced it: the pull toward complexity. A new abstraction layer here, a...