2026W33
- Software Engineering fundamentals matter more than ever — The welding analogy is the part I keep coming back to, he learned to build things in his 20s that he couldn’t lift or get out the door of the shop, and the lesson was that how something goes together is the whole game. That maps cleanly onto agents crossing the “can it be done” line, because “can it be done” turns out to be the small part of the job. The seams, the API boundaries, the choices about what should stay stable and what should flex, that’s still the work, and it’s where the reasoning has to be real. His framing that LLMs echo compressed human reasoning rather than doing it themselves is a useful way to set expectations without either the hype or the doom. Where I land with him is that debuggable and maintainable code is exactly the thing the models are worst at, so the fundamentals get more valuable, not less.
- Why Tiny JPEGs Look Different in Chrome — What I liked here is how a “thinner logo in Chrome” bug turns out to be a deliberate optimization, not a defect. Chrome doesn’t fully decode a JPEG it’s about to shrink, it decodes only the low-frequency coefficients it needs, because fully decompressing a 2000x2000 image to render it at 20x20 would burn 12MB to produce 1.2KB of pixels. libjpeg-turbo picks the closest scale with a denominator of 8 and throws away the high-frequency detail, which is fine for a photo and ruins the crisp edges on an icon. The practical takeaway is small but the kind I’ll actually remember, stop shipping icons as JPEG, because the format’s cleverness is tuned for photographs and works against you on graphics.