It’s gonna be a living breathing world, you see. You’re going to be like “omg, this game even accurately captured the blog posts, woah”.
Edit:
This whole blogging-about-cloud-AI genre is just weird and irresponsible now)
I sincerely never considered it was a whole genre.
Something about this idea really resonates with certain personality types. I equate it to the Zettelkasten hype phase from several years ago. People (...like me..) got really wrapped up in the belief that the process was more important that the content. "Linking" was an "activity." Something good will happen as long as you (a) take notes on stuff and (b) link them to other notes on stuff.
You see the same thing with the session transcripts people. They're building ever more sophisticated setups of indexing and storing and cross referencing every conversation they've ever had on the (I would argue) mistaken belief that the transcripts are the valuable part, rather than the uncomfortable part where you go do something. A lot of it, I say from falling in the trap, is fancy procrastination.
(Although, I have found myself jealous on many occasions where their fancy system retrieves something they vaguely recall from a conversation they had 3 months ago. So, who knows.)
Like ancient people? Because "new oil" whilst I get what it might imply sounds bad to me. Oil has been superseded in many places so "new oil" is like going backwards still.
Reference: data is the new oil is a term coined in 2006.
We're in 2026. See what I mean.
I think you may just misunderstand the point of having / writing a personal blog. I write because it's fun! Whether the reader gets any value out of reading it is almost entirely beside the point.
(Also several comments here directly post a fix to the problem stated in the blog post, so readers can and do often help)
I used to blog, as it goes, and I have supported and enabled many more, so no, not really.
I'm trying to rebuild my life so I am in an experimenting and learning phase rather than a massive coding phase, and most of my code work is maintenance of things I have built. That which I do code, I am still coding by hand, though I am dealing with other people's Claude output and I am really unimpressed by it. It's often rather crass.
But I would say to you that if you personally don't write code now but you do have a dependency on one of two presumably unprofitable cloud AI providers, aren't you in trouble? How is this not a three-alarm fire for you?
Unfortunately the point of code is rarely to impress people (certainly not other engineers) or to avoid being "crass." 99.99% of code exists to achieve business outcomes, and velocity matters a lot in many contexts. A lot more than elegance or impressiveness.
The platform risk is a valid concern but alleviated by China's theft and redistribution of open models.
We used to be concerned about code quality. Are we not anymore?
Crassness was a signal. Still is, to me — in a human I find that people who write crass code are going to cause me trouble.
They only care about the things which you can only get with good code quality like reliability and speed of development.
Now do the same exercise for "impressiveness" and "crassness."
Here, I'll do it for you:
> Nobody cares about code quality /s
> They only care about the things which you can only get with good code quality like impressiveness and lack of crassness.
Sounds silly doesn't it?
Of course the house must pass safety inspections and stuff, but the materials and techniques don’t matter one bit for that. All that matters is you achieve the desired outcome, and I will ignore the glaring fact that you achieve the desired outcome by using the right materials and techniques. The materials and techniques don’t matter, just the outcome.
This analogy is more true than you think. This is why modern homes/appartments are trash. You can pass safety inspections using subpar materials and the house will fall apart after a few years, but who cares right? At least you achieved the business outcome!
This mentality is so infuriating. This is why I need to buy new shoes every year. Or why my washer/dryer motherboard craps out in 2 years instead of 10. Nobody gives a shit about quality anymore, this is why society is crumbling around us. Profit driven incentive for fast/cheap over everything else. And now I need to spend my day prompting an AI to fix AI slop code to keep the business hobbling along another day. What a fucking joke.
Where do you live? Because where I live, new houses and apartments are superb. But I'm guessing we don't use two by fours and plaster walls to erect whole structures.
e.g. the bill is definitely coming true for a lot of "non-traditional construction" materials and methods in immediately post-war properties in the UK. There are many unmortgageable properties using Mundic Block in Cornwall and to some extend Devon, in the heavily bombed south east there was a lot of pre-stressed concrete with catastrophic rebar failure, not to mention Orlit construction, and all across the country a lot of RAAC. Almost all of it for good, necessary, upbeat reasons.
It feels a bit like this kind of crisis from AI generated code could hit in ten, fifteen years time; people often fail to understand how long a bit of website code can last.
Costs of those things have gone down over time. The high end still exists, you just don't actually care about quality as much as you think you do.
And yes, for capital-intensive things like real estate development, fast/cheap matters a lot because otherwise there would be no capital available to build any of it at any reasonable scale.
GP said Claude's code "doesn't impress" them and that it's "crass."
Do you think a valid "long term strategy" is to create code that impresses GP and is not crass, but doesn't achieve the business outcomes it's meant to?
Inversely, do you think one can achieve business outcomes if "quality" is so abysmal that the code doesn't work or is unmaintainable?
Is it possible to write perfectly good, maintainable, performant, legible code that "doesn't impress" GP, or feels "crass" to them? Well gee, probably! Because "impressiveness" and "crassness" are literally meaningless.
I will accept "of fully subjective value". But not "literally meaningless".
It's insane to me that you're implying we could build houses with pre-fabricated materials or pneumatic nail guns and still somehow "have houses?" No sticks/jute cord and special symbols, then no house.
What you saw in this thread was someone arguing against the dimensions of "impressiveness" and "crassness" as valid things to care about when it comes to code.
It's your mistake to assume that those are related to any meaningful concept of actual quality.
I clearly said elsewhere that I think they are predictive of problems with the person who writes it, and I fear I can generalise that to LLM tooling that generates it.
Are you not, by developing this way, making yourself more interchangeable, less indispensable, than ever before?
I hate to say this tbh, I loved hand-writing code. I made a great living for 20 years, and I absolutely loved it and was quite good at it.
Hand-typing code is just slower now; there’s no two-ways about it. You are either going to be slow and a bad hire for businesses, or you figure out how to adopt AI into your workflow to speed up.
One thing I think people don't realize is that deep knowledge of programming, performance, architectural, and domain specific trade-offs makes a skilled engineer about 1000X faster than someone without those skills -with AI. But yes, now unskilled people can actually make apps/software. They just tend to be slow, and their products are full of bugs, security flaws, and abysmal performance.
So we went from: Skills = can or cannot ship any software at all. Now we are at: Skills = can ship better software much faster than unskilled people.
I was actually faced with this recently. I decided to learn Rust and port one of my side projects to it. Initially, I moved extremely slowly, and the AI made truly horrific architectural decisions because I didn't have the knowledge of how to direct it, especially compared to my primary languages.
However, once I gained a firm grasp of Rust, I was better able to properly direct the AI to fix fundamental issues and architect things properly. My speed increase multiplier proved to be directly proportional to my growing knowledge of both the language and the domain.
Skill and knowledge combined with AI, when used appropriately, absolutely multiply your speed and quality. I really think once you understand what AI can do, and how to utilize it to produce better code, faster than before, there truly is no going back.
I'm finding a path forward that I actually enjoy now and don't really see losing my value (no telling how things will change in the future), I can have more time to focus on really quality/solid/performant and useful systems with less time just typing one character out at a time.
You could have talked to me 3 months ago and I'd never imagine I'd say the above btw. I REALLY enjoyed code writing and earlier AI models without harnesses were pretty useless for anyone skilled at development. Now with stuff like deepseek Flash I feel like I have a happy medium of 100% directed/fast code turnaround, less typing, more deep focus on architecture, systems, and the actual end product.
I am not convinced it isn't vulnerable to the same problems but the whole tenor of the community around open source/open weights models just doesn't have the same YOLO madness to it.
Sometimes it takes me a day or more to find the one line fix or abstraction necessary, while claude can hammer through a hundred line fix in under an hour.
Quick and cheap are two of the three fabled: "Fast, cheap, and good: choose two"
Or are you saying the industry is (because it is)
I reject your correction: I present the options as nouns, not modifiers to the work. Maybe I should say "Cheap, Fast, or Good" as a compromise.
Same thing with hobby projects - I might ask ChatGPT or Gemini some questions about best practices in Swift for example, but writing code is done by hand.
As others said - if you don't use it, you'll lose it. And I'd rather keep my skills up to date.
Right now I am lucky that I have the time to recover and learn.
And I don't think I'm unique. I see enough posts like https://news.ycombinator.com/item?id=48777257 pop up that I'm reasonably confident all the hype around LLMs saving so much time and increasing productivity so much is, well, just that: hype.
Sure, if you can't code at all and want to build something, an LLM is going to be great for you, even if you can't evaluate the code quality or determine if there are bugs just by looking at the code. But I've been coding professionally for 25 years, and as a hobby since I was like 8 years old. I like to code! It's a passion of mine. If the LLM isn't doing it faster or better (and most of the time it isn't), why wouldn't I write code myself?
I'll have the LLM write boilerplate stuff or do tedious refactoring, because I just don't feel like it (even if it does take longer). But for the real work? Of course I do most of it myself.
One area where the LLM shines for me is finding the root causes of bugs. It can generally do that much faster than I do. Often orders of magnitude faster (like minutes instead of hours or days). But when it comes to write the fix for the bug? It's usually faster and better if I do it myself.
More generally I am interested in burnout-avoidance tools; things that help me start, finish, things that write tests I guess, certainly code scaffolding.
But I am fully unconvinced that my burnout will be improved by ending up owning the responsibility for wobbly or inscrutable AI-generated code with potential landmines in it; that will keep me up at night just the same.
I can ask it to be curious, and it will reply with what people think curiosity should look like, but it’s a simulation of an emotion it will never be driven by.
The ramifications become apparent when you engage in activity like cross-domain discovery.
I do personally know people who pay for regular products with cryptocurrency. Including myself.
This is pretty funny because it's about the depth of understanding of every 'AI expert' on Linkedin. People who praise the context window as basically magic have no idea how any of this works.
"Spicy Autocomplete", I've heard it called.
I have opinions people apparently don't like, for no subscriber money.