🛬Back from Spain. Vermouth de grifo, Hieronymus Bosch and Matisse, old buildings, and public green spaces are pretty great.
📚Still at it with Power Broker and the first six Dune novels. Larry McMurtry essays are making me a little nostalgic for the idea of Texas (but not contemporary Texas itself). Contemplating adding the giant book of all the Montaigne essays to this list.😎
🎥 Hoppers was fun and feels like possibly a return to form for Pixar. Mandolorian and Grogu isn’t the best or worst Star Wars, but it is fun and hits all the expectations.
📺 Rooster is great if you’ve ever fancied becoming a sharp-witted author and visiting professor in New England. Widow’s Bay is great if ever you’ve wondered what being the mayor of an obscure but definitely cursed island in the northeast might look like.
⭐I should call out Hacks here. That is how you end a series, a comedy in particular. I will now enthusiastically recommend this show to everyone as The Ideal Comedy television series. If you haven’t, go watch it. Five seasons, no skips or lulls.
Fits on a floppy, great idea:
Software has lost its way. Apps that once shipped on a single floppy disk now demand gigabytes of your storage, minutes of your time, and far too much of your patience. We accepted this gradual bloat, but that’s not progress.
Software should be as small as it can be. Not as a gimmick, but as a discipline. The floppy disk is the measuring stick: 1.44 MB. If the software that ran entire businesses could fit in that space, then a modern, focused, single-purpose tool certainly can.
Yep, these criteria make the good stuff:
Launches instantly. Faster startup, nothing unnecessary to load.
Does one thing well. Focused features, fewer bugs, software that lasts.
But, I disagree on some details:
Native only. No dependency bloat, every line of code earns its place.
I usually don’t feel like “native” is crucial these days. Whatever your definition of native is, it’s not a prerequisite for building great software. Even for desktop/mobile platform development using the vendor-intended language and frameworks, the downsides are…a lot, lately.
You can create software that is fast and focused with any language or stack if you’re careful. So, I might replace this one with something about attention to details and care for the craft.
Runs on older systems. Older devices deserve love too.
I love it when this happens. It’s easier to make it work outside native environments, too!
I think the applications are less important than the data. I’d change this one to something about the ability to store one’s own data on a floppy-sized local file instead of in an opaque cloud or a row in a SaaS database somewhere.
Maybe the big idea is that the application and data should fit on the floppy. 🤔
Soundgarden’s Badmotorfinger is underrated. Twenty five years later, still no skips.
Previously in tech, the joke was that Microsoft’s org chart was a bunch of divisions in a Mexican standoff.
Fast-forward to now, instead of pointing guns at each other, every division at Microsoft is yoked to the other via KPIs and bonus allocations. None can maneuver freely enough to ship excellent software. They all have to prioritize “synergy” (Copilot everything!) and integration instead.
In retrospect, at least the drama of a standoff yielded the turnarounds of distributed systems and open source work in the 2010s.
Madrid–Barajas and Heathrow, day 10.
Madrid, day 6.
Madrid, day 4. Museo Prado not pictured at the request of the Museo Prado.
Madrid, day 3. Sometimes, you gotta sleep in and take a short bus tour.
Madrid, day 1
Examples of The Eponymous Trifecta:
Hopefully you’re starting to see the pattern. (There’s way more of these out there. Let me know your favorite!)
Let me throw some variety in:
Ergo: You’re not metal if you don’t have a trifecta. Metallica is not metal. This is probably some kind of paperwork mistake.
But, Bo Diddley is metal. Just listen to the music, I think you’ll agree.
git-spice – stacked diffs, but without another (SaaS) tool to provision and pay for. Excellent ergonomics, if you’re comfortable with the git CLI as-is. I’ve tried this for one project so far, things went as hoped. Moving between commit ‘stacks’ is easy, and rebasing changes from the main branch is straightforward. This is the quality of tool I’d hope to see in git in the first place. But maybe that’s a 2026 expectation. 😇
When you’re stuck or uninspired, reach for your spark file:
This is why for the past eight years or so I’ve been maintaining a single document where I keep all my hunches: ideas for articles, speeches, software features, startups, ways of framing a chapter I know I’m going to write, even whole books. I now keep it as a Google document so I can update it from wherever I happen to be. There’s no organizing principle to it, no taxonomy–just a chronological list of semi-random ideas that I’ve managed to capture before I forgot them. I call it the spark file.
Steven Johnson, The Spark File
It’s a productive trick that doesn’t have an ecosystem of applications, courseware, and influencers wrapped around it. I dig that.
Adjacent: swipe files and commonplace books.
If you were wondering, “could anyone make OAuth2 an even more involved, jargon-filled process?”, the answer is yes. AT Protocol and Bluesky sure did. 🙃
I bet a lot of the grumbling about coding agents is really about losing out on the joy of moving quickly through code via a deeply learned text editor. I’m feeling it too, but I’m not so great at vim that my whole coding identity is wrapped up in it.
As goes the complaint about the decline of manual transmissions, even in sports cars, so goes the decline of emacs/vi/etc. “No connection”, “not enough focus”. Not wrong, but the toothpaste is out of the tube here.
That said, there’s a legitimate complaint to make here about software slowing down! We were almost getting to the point that raw latency was a virtue in software. And then we got uncanny, but not fast, intelligence. 🤷
It strikes me that my text editor is now, effectively, a quasi-natural language interface onto bulk and sometimes quite intelligent text operations. Well, sometimes entirely not what I want. But still, bulk and natural language.
Lately, I try Cursor every several weeks. Mostly to see if the grass is greener. But it’s not for me. Jetbrains-flavored tools are more holistic and more right for me. Regardless of the grass.
I think Cursor is an intriguing team and a good product. The best version of VS Code you could possibly use, the easiest possible onramp to coding with agents. Nonetheless, I want to be using Zed for everything. However, I think the writing is on the wall for pure, even principled, text editors. Typing in code is no longer the bottleneck. Memorizing keystroke optimizations is doubling down on a sunk cost.
Looking at the functionality of an integrated environment like RubyMine or PyCharm, I think the value of its git integration has gone up by a lot. This is essentially why I went back to PyCharm from Cursor. I can’t be bothered with simplistic, non-excellent git interfaces. (I wonder if Sublime Merge sales will start to exceed Sublime Text sales. 🤔)
VS Code, and Cursor by literal extension, seem like the keybindings were invented by 3 different people ten years apart. Which they probably were, literally. I can’t abide this.
The other thing that brought me back to PyCharm is browsing/discovering data alongside code alongside revision changes. It stands to reason that if writing code is less critical in the future, understanding the data will grow in importance. Even better, understanding your code and data in the same tool, with sensible affordances to jump between the two. This is why I’m betting on IDEs gaining ground.
Let’s not mention the part where now we’re paying for code, from our new-found editors, by the line. I’m surprised I’m not more salty about this.😬
The future of code is understanding the whole system, not constructing each part in exquisite detail. The IDE of the future probably looks more like code review alongside a debugger, than a code editor with version control and data management attached as sidecars. A bunch of Slacks and GitHubs mashed together.
Yeah, I’ve locked in to a few writing and coding sessions with The Social Network soundtrack. But, have you ever tried locking in to something you can move your hips to?
Related: currently compiling a list of Soundtracks That Didn’t Have To Go So Hard, and Prince’s Batman is way up there.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。