LVB

If you expand your career scope to hardware and embedded software, your odds of having to be at a facility, or some customer site, and thus be by other people, rise substantially. I've had a number of jobs where it'd be quite impractical to be remote. e.g. actually building equipment in labs and installing it in machines, aircraft, etc. There are tons of examples. The obvious downside is that the options need to be near your home, or you move. Hence the various "hubs" that pop up for various expertise (SV obviously, but e.g. if you like aviation, Wichita is a good choice)

Will look back fondly to that period of short, ed25519 sigs…

Nothing to see here IMO. A large amount of code piled together in a month.

The push here is “zero deps”, though at that point I might as well have Claude do it like they’ve presumable done. FWIW I’m quite ok with bringing in a well-tested/maintained dep. Hand-rolling everything down to crypto primitives like is done here isn’t an advantage.

And this highlights my frustration. I don’t want to have this debate. The tool should allow its operator to set whatever level of strictness or purity they want for their project. Fossil already offers a million settings. Add another and make me turn on “dangerously-unsafe-rebase” to get the feature if need be.

Though I just vented in another comment about fossil, I'll admit that all of my experience was in the pre-agentic era. Since an agent won't be as easily annoyed (heck, it happily belts out sqlite's tedious schema alternation dance without pause), I'm curious to try pointing it fossil as the scm for a project.

Fossil is extremely frustrating to me. There are so many parts that I'm drawn to, but then are there showstoppers that prevent real adoption (by me). I've used it in earnest a number of times. Their immutability stance is at the root of the problems. Lack of rebase is most infamous, but you can't even edit a ticket description! Make a typo or error in the description, and you're expected to append more notes, or delete and recreate the ticket.

I really love the idea of a powerful, shrink-wrapped scm + ticketing etc. system, and I'm a sqlite fan, but fossil hasn't worked out for me.

For me, I know backend development really well, and HTML/CSS passably. HTMX has been much lower friction for me than learning JS frameworks, which tbh I didn't really enjoy, and they were constantly changing. But now, I had mostly leave the JS to Claude, and the HTMX draw has diminished a bit.

Seam

I don’t feel like the learning curve has shifted dramatically for mainstream development. Besides generics—which tend to not show up that often in app code even now—I can’t think of any substantial language change since I Iearned it in 2014. (Well, modules, but that’s more tooling.) Where I do see the shock is jumping to def of a std lib function and landing in indecipherable type soup.

Use 'e' in -p mode and you can edit the hunks as you wish, choose lines, etc.

I've lapsed my subscription because it has, in my opinion, gotten a bit too clickbait-y and many of the articles are sort of thin rehashes of already covered material. It is still better than most, but also fairly pricy.

Swag looks interesting and I'm definitely gonna give it a try!