Member-only story
We Keep Rewriting the Same Software
The stack changes. The shape of the problems is often embarrassingly familiar.
Every now and then, I read a new product pitch or internal platform proposal that feels revolutionary for about three minutes.
Then the boxes on the page settle into focus, and I realize I have seen this software before. Not the exact implementation. The shape. A workflow. A dashboard. Permissions. Search. Notifications. Some approvals. Some integrations. A UI that promises to make an old problem feel modern again.
I do not say that cynically. I say it with a kind of tired respect.
We keep rewriting the same software because the same problems keep mattering.
New Tools Change The Wrapping, Not The Core Problem
I think this is why so many technology debates get weirdly dramatic.
People argue as if the new tool invented a new category of work, when in reality it often changed the wrapping more than the core need. Teams still need systems of record, task flows, access boundaries, reporting, and coordination. The frontend gets a facelift. The backend gets more distributed. The business problem quietly remains.
