Ideas
worth keeping.

Key ideas

Ten takeaways worth keeping.

1. 01

   Learning-to-learn is the only durable skill in tech. Tools cycle every few years. The transferable asset is the method of attaining functional proficiency fast, not the tool itself.

   learning-velocitymeta-skill
2. 02

   Words vs. meanings is the core engineering translation problem. Clients ask for "AI" and mean random forests, image recognition, speech synthesis, or 3D generation. The irreducible job is figuring out what they actually need, not transcribing their words.

   stakeholder-empathyconsulting
3. 03

   "If they understood the problem, they wouldn't be hiring you. They'd have fixed it themselves." The diagnostic gap is the entire engagement. Receiving orders and delivering to spec is the part that gets outsourced and automated.

   consultingdiagnostic-first
4. 04

   Architects should make others smarter, not be the smartest in the room. Act as an amplifier — absorb context, uncover blind spots, distill trade-offs the team is implicitly making. The oracle posture is a tell of weakness, not strength.

   architectureleadership
5. 05

   Boring technology principle: adopt new tech only when it's a clear improvement. Refusing to jump on bandwagons keeps engineering cultures uniform and avoids dozens of stacks nobody knows how to operate.

   boring-techarchitecture
6. 06

   Vertical scaling carries you much further than people think. Single VMs can run 120 CPU cores and terabytes of memory. Don't shard or go horizontal until you're at ~80% of vertical limits.

   scaleboring-tech
7. 07

   "Simple is complicated enough, especially at scale." Clean-code dogma swung into over-abstraction that takes decades to become proficient at just reading. At scale, write code in the dumbest most straightforward way possible.

   simple-designcode-quality
8. 08

   Architects are scouts, not cartographers. Snapshotting a giant IT landscape no longer works — by the time the map is done, it's stale. Deliver purpose-driven, situational, timely maps that depict only what's relevant to the move you're trying to make.

   architecturedecision-making
9. 09

   The $50,000-per-hour stakeholder empathy rule. A container terminal generated $50k/hour at 12% capacity. The engineer literally sat in trucks in scorching heat to understand what operators experience before designing anything.

   stakeholder-empathyconsulting
10. 10

    Use AI to validate your understanding, not generate your output. If you can't explain why the code is there, you'll have a rough time maintaining and extending it. Generate a few things, then check whether you actually understand them.

    ai-toolingcraft