Section

Articles

Longer pieces, each with an argument and a date. Every one is here to change what you do on Monday, and says so in its first paragraph.

  1. Technical ownership Code is not the advantage Code stopped being the advantage. It did not stop being the constraint. Software is written faster than it has ever been, so the scarce thing moved. What an owner runs short of now is not engineering hours but a dependable answer to how their own system works. What that shortage costs, and how to end it.

How these are written

  • One transition per piece. Each article takes a reader from "this is probably a problem for somebody" to "this is a problem for me and here is the first thing I will do about it". If it cannot name that move, it does not get written.
  • The cost of waiting is made explicit, and only with things that can be checked: what accumulates, what it looks like in three months, what the next big change will make of it.
  • Every article ends in your hands, not in a warning. A sequence, a checklist or a way to test your own position, and a first step small enough to take today.
  • Every invented example says so. There are no customer stories here, because there are no customers to write about yet.
  • A date on every piece. An argument about a moving subject is read differently when you can see how old it is.

Find out what you actually own.

No repository access. No source-code upload. No card.

Build your project map — free