200 Followers
73 Following
711 Posts

's the name, refactoring's the game. Software Developer & Technical Coach.

🇵🇸✡️🌈🇦🇹🏴󠁧󠁢󠁥󠁮󠁧󠁿

crack down on ebikes that can do over the speed limit. thats great.

lets do cars next

New unit testing rule just dropped:

Any two adjacent lines of code shall be verified by the exact same tests.

This 👇🏼
Thanks to everyone here who suggested lists of desirable test properties. I wrote up my findings so far in a blog: https://coding-is-like-cooking.info/2025/12/test-desiderata-2-0/
Test Desiderata 2.0 - Coding Is Like Cooking

Kent Beck is one of the original authors of JUnit, an open source tool that kick-started a huge shift in programmer behaviour that I and others have found immensely valuable. In 2019 he published his “Test Desiderata” with advice about the properties he values in tests. I have found this list useful, but at the […]

Coding Is Like Cooking

Most NFL teams are named for a city, e.g.: Seahawks, Browns, Cowboys, Bay Buccaneers.

Some are named after states: Titans, Vikings, Cardinals, Panthers, Jets, Giants, Commanders, City Chiefs.

Patriots are named after a country that doesn't exist. Ironic.

Micro USB in 2025 is a misdemeanor.

USB-C that requires a USB-A charger is a felony.

For a source code repo, how would you organize internal (dev-facing) and external (user-facing) documents?
/docs/how-to-use-this.md and /docs/_internal/ho
0%
/docs/external/how-to-use-this.md and /docs/intern
0%
/docs/how-to-use-this.md and /internal_docs/how-to
0%
Poll ended at .

DAE mix coffee grounds with Nutella and spread it on bread?

Kinda like chocolate-covered coffee beans in a different shape.

Another refactoring technique demo video out today: https://youtu.be/EMzOb-WcUwQ
Legacy Code Refactoring for Testability: Replace Supplier with Supplies

YouTube

The top reasons that software project fail:

1. Build the wrong thing
2. Can't explain the value to buyers
3. Unable to adapt to changing conditions

Software organizations behavior does not align with this list of risks.