drums8787

The only one that matters, Emacs in evil mode.

The never ending gate bites.

How I have come to detest certain phrases.

It boggles the mind when you hear people defend the US healthcare system in terms of efficiency (OK, granted, maybe people have long stopped doing that).

It has to be one of the most bureaucratic and paperwork overloaded systems of all time. It's hard to imagine somebody who've had an actual health crisis would think otherwise, unless they can afford people who can shield them from the BS.

Even-engineering?

Our week of discontent.

We use WASM DuckDB as the target for an in-browser agentic feature. Generated SQL runs against the user's individual tables that then feed in-browser dashboards.

Excellent performance.

Enter the long tail of caveats

I feel like I finally get to feel the designer’s pain when people arrive with their vibe-coded pile of garbage and I have to explain why it can’t just slide into the product.

It does something and it’s what the business wants. So what’s my problem?

I particularly love when the “CTO” is also the main offender.

No. The means can spoil the end.

Dehomag.

What has been will be again, what has been done will be done again; there is nothing new under the sun.

I often hear comparisons to Web 1.0 (the bubble aspect, potential for change, etc).

As someone who lived and worked during that era, I don’t remember thinking “holy shit, if this ever gets released on the world at scale we’ll have serious problems”.

Maybe that was a lack of imagination and not thinking through what would actually happen to brick and mortar, the job market and so on. But it feels like this time is different. Or I’m just that much older.

This is a big piece of what drove me out of corp jobs.

With a sufficient hourly rate people are less likely to have you waste time in meetings.

Or maybe I’ve just been lucky. Prob doesn’t work everywhere.

My experience is the opposite I guess. I am having a great time using claude to quickly implement little "filler features" that require a good amount of typing and pulling from/editing different sources. Nothing that requires much brainpower beyond remembering the details of some sub system, finding the right files, and typing.

Once the code is written, review, test and done. And on to more fun things.

Maybe what has made it work is that these tasks have all fit comfortably within existing code patterns.

My next step is to break down bigger & more complex changes into claude friendly bites to save me more grunt work.

I make a living writing software that's hosted on Windows. I've never felt as comfortable with the command line options on Windows as I do with macos/Linux. Git bash with vim was such a relief.

It's an idiosyncratic mix of ergonomics and habit probably. I don't really care since I get the job done efficiently (more so than a lot of "Windows natives" I observe).