272 karma · joined January 26, 2021
Uncaught (in promise) Error: Unable to preload CSS for https://ocelot.lol/_app/immutable/assets/1.n1T2vemw.css Immutable 6 async* https://ocelot.lol/blog/2026/08/07/site-making-of:42 promise callback* https://ocelot.lol/blog/2026/08/07/site-making-of:41 HclGiUj8.js:1:921
Apart from the paywalling, the stupid site has decided that I'm a bot - but I can load pages in a private window. I've tried clearing all storage for the site, but no-go.
So I'll apply the logic I do everywhere: if you're going to block me from reading it, it's not important, and I don't care.
I'm so tired (so incredibly tired) of all the ai slop I've seen, just in my company, and the ai-bros frothing at the mouth about the next terminal to run their agents and how it's making them "so much faster"; even a comment yesterday (with supporting sentiment) that having to do something without ai was tediously slow. The problem is that the _generation_ part is fast. So people only remember that. They don't remember the time taken to craft a good prompt that gets to a reasonable output. They don't remember the time wasted in PR over swathes of comments. They don't remember the days I spent having to unfuck the project from aigen code that literally broke checkout. They got their little dopamine hit, and moved on.
I use ai - claude, to be specific - as an "interactive stack-overflow", to ask questions about the code, and to help me learn how to be better. I still firmly believe that the biggest problem with ai-gen adoption is that the people who think they're getting the most out of it are the same people who don't understand what it output, so are unable to push back when it does something stupid.
I have to push back _regularly_. Like at least 30-50% of the time.
The tools are only useful (imo) when an expert can verify the results - even in cases where I wasn't sure of the actual workings of the code (eg getting Claude to use the typescript ast to do clever linting or type-file generation), I can verify via tests - the box can remain black if I can verify the output. The average vibe-coder verifies nothing directly - it launches, so it's good, right? Oh, how did our checkout screen end up infinitely putting-and-polling at two endpoints? No problem - give it to a real engineer to solve it.
I'm with Linus on this - ai is a _tool_. And much like how we wouldn't allow shit code from any other tool (ide, compiler, linter, whatever) to sift into prod, we should be on top of what we're using this tool for - not putting the onus on someone else to clean up the garbage. AI codegen is most dangerous in the hands of people who have no idea what it's doing - they're firmly stuck in the initial Dunning-Krueger peak, unaware of just what a mess they've made.
Not to mention duplication - literally just had to ask someone to refactor so that we're not sending two components which are 90% the same to the client, but rather pulling out the 90% core into a mixin. Code is so over-commented, it simply _has_ to be ai-gen. But I also can't call it out, because now it's dev egos in the mix too.
The one golden hope I'm leaning on is that eventually everything will implode, people will see the light, and go back to using a tool as a tool, instead of just trusting the bag of words to do it right. In particular, I've learned that ai is to be incorporated in some ingestion pipeline where the final result has financial implications. That's going to be hilarious when it makes a proper goof.
But when I have to work in an area, the first thing I look for is coverage, and if it's not there, I add "fixing tests" to enforce the existing behavior before making changes so I'll know when I broke something.
the other point is that "more data" doesn't necessarily mean "more better" - I'd rather have 1 well-thought-out, curated article on something that matters than 10 insipid pieces compiled by ai from links.
In much the same vein, I rarely actually watch stuff _on_ netflix, through a browser - I watch sped up, and the quality just degrades. Since I pay for it, I feel nothing for downloading a ripped copy to watch it locally :D
concurrency _is_ parallelism, but for I/O. People often think of parallelism for the case of making something go faster - eg placing two computations in parallel (the definition posed in the video), OR placing two I/O operations in parallel - so this is the keyboard-vs-mouse in the OS, even when you're on one core only; this is multiple web requests in JavaScript, which does not support multi-threading, but 100% does support concurrency for I/O operations - that... badum-tiss! RUN IN PARALLEL.
I get the point of the talk, and it's well interesting, but I think it depends on how one views things.
yep, follow the yellow road of mcdonalds wrappers to find the worst president probably ever.
PS: please get rid of your president - the whole world, which didn't think much of you before, thinks even less of you now, because you elected a trouble-maker racist moron who is so thirsty for attention he'll literally fuck the entire world to get it.
First, we money is a delusion we all agree to share - it has no intrinsic value whatsoever
Second, stock is an even more-removed delusion based on what people _think_ a company might be worth to buy - a value that changes at the drop of a hat (look at the recent massive dips, eg nvidia)
Third, and this is probably the real bummer - all this delusion is just going to make Smelly Tusk even more insufferable. Yay.
Yes, people are more lonely, but I'd counter with my experience over the last 5 years or so: people at work are simply NOT your friend. End of story. They never were, they never will be. You MIGHT find A friend at work. You might even be lucky enough to move into a company where you already have a friend or two. But the realisation has hit hard over the last few years that 99% of interactions within a work sphere are not genuine human connection. Most are simply data flow to support the business. Some parts are masking fluff that people put up to appear friendly. But with less time spent dazzled by people's social skills, their true intentions come through plainly in their work outputs and reciprocity - most especially the latter is telling: I've stopped being such an eager volunteer to help people (at least, most people) simply because I know I can't expect the same back - and my salary is paid based on _my_ outputs, not those of co-workers, so if they're not going to co-operate, there's little incentive for me to do so.
Company leaders also seem to be even more out of touch with their people as they are no longer forced to fraternise, but can instead remain atop their hills, barking orders and peering out their their foggy scopes at the terrain below. What a wonderful time to be alive - when the socially malleable have their substrate taken away to expose exactly how shallow they are.