
Software Developer @EYCanada. Previously @filamentlab, @86interactive, @teehanlax. Drummer @theflyingmuseum. @MapleLeafs, @BlueJays fan.
Toronto ON Canada
Joined May 2009
- Tweets15.5K
- Following1.7K
- Followers594
- Likes20.2K
Mike Lynch retweeted
Italian graphic design in the ’50s and ’60s was on another level. A selection of Olivetti advertisements.
Mike Lynch retweeted
I've been reviewing a lot of code written by Opus 5.5, and it still seems to make a lot of bad software engineering decisions. The kind that will accumulate/calcify into unmaintainable software over time. IMO even the agents will struggle to maintain vibecoded software.
Mike Lynch retweeted
I'm an avid user of coding agents, but there's something I've been struggling to put into words which I think is encapsulated well by these screenshots. these are two PRs to fix the same bug: the first is a +627 / -291 line change, from Claude, the second is a +3 / -2 line change, from Matt, a human (we closed the former and merged the latter).
there's a certain coherence in a human's mental model of the codebase which makes some bugs trivial for humans and still really difficult (or token-expensive) for agents. this goes beyond just better memory of the codebase. humans will build a mental map and a probability matrix for which parts of the codebase are most likely to surface a particular bug, given the codebase's coherence, and start by tackling those before going another layer deeper.
without matt's contribution we might well have merged the +627 / -291 PR, in turn losing coherence, and becoming more token-dependent as a result. after you lose coherence it's game over.
i've found myself pair programming with agents on tiny PRs after a huge amount of independent research / agent swarms to tackle a given problem, and I think this is pretty effective; you can combine the things that agents are naturally good at (parallelization, verifiable problems) with your human coherence. often this results in 15-20 PRs, not all of which get merged.
I find it interesting that high token usage is seen as a sign of command, a KPI even. Don't get me wrong, all developers should be using AI. But it's so easy to blow through tokens using a frontier model. Shouldn't we be striving for token efficiency at this point?
It feels a bit like we’re entering an era of the “0 → 0 paradox”
Jumping straight into code can feel like you’re pushing from 0 → 1 faster, but the lack of design thinking can set you further back than where you started
Modals everywhere, complex flows, overly/under branded
I'm only about 35 mins into "The End of Oak St." and it might be the best movie I've seen this decade. Feels very Spielberg in the best way possible.
I'm still reviewing code on my personal projects but I no longer care if I understand every line of it. But at work, I'm responsible for client code, so I'm still reviewing every line. Hell, I'm commenting nits on my colleagues' (AI generated) code. That's where I'm at.
Mike Lynch retweeted
ironically, the best way to learn how to use agents is watching how other humans use agents.




























