Behind WorkLens

Every week, technical leaders are making high-stakes calls about AI, team structure, and how work actually gets built. The advice floating around is either hype from people who have never shipped, or theory from people watching from the outside.

When I was running teams and putting AI into production, I kept hitting the same wall. Teams were shipping faster than they could vouch for it. AI was multiplying broken processes instead of fixing them. Senior engineers were burning out on review work nobody had budgeted for. And almost nobody making the big calls had honest signal to go on.

I have spent 14 years building and shipping production systems. I founded Interns School, a platform that grew past 100,000 users. I now run Rewired, where I put AI into real technical operations for founders and teams — and have worked with organizations including General Motors, SAP, Novartis, Telenor, L'Oreal, and Garnier.

And so, WorkLens was born.

I created WorkLens as the newsletter I wanted back when I was making those calls myself. A way to turn field notes from real production work into something you can read in ten minutes and still be thinking about on Friday — not stored in a feed you scroll past, but sitting with you when the next hard decision lands.

With one sharp idea per edition, first-person research, and no hype, every Tuesday covers what technical leaders are actually facing: AI in production, engineering judgment, org design, evaluating tools, and the real cost of systems that need to hold up under load.

WorkLens isn't another feed of hot takes — it's clear thinking from someone doing the work.

Get the next edition in your inbox every Tuesday. Free, forever.