Get the top HN stories in your inbox every day.
mettamage
littlexsparkee
So much comes down to timing - lucky author that got to experience it for 30 whole years whereas some of us had a scant few to enjoy building as it was, flow state, and some semblance of security. At least I made plans the last 5 years in anticipation of change, can't imagine the sheer dislocation of just entering the job market now.
sho_hn
Pros and cons. Some of the people who were lucky to enjoy those 30 years are also emotionally being hit the hardest right now, and if life threw a few curveballs at you along the way you don't necesarily have attained the sort of stability where you don't have to worry, either. Plus ageism can make it even harder to pivot.
I have programmer friends in their 40s to 60s who are seriously depressed currently (and 20 year olds worried for theirnl future perspectives, of course). Mental health is not just a young person's game.
I strangely feel quite lucky that I got more and more into electronics and hardware over time as I moved from web and desktop more and more into embedded/consumer electronics and companies who also employ mechanical and EE engineers. When I was younger I used to dumbly worry this meant giving something up (the purity of software approaches, etc.), but instead it made me consider myself an Engineer with a capital E and strive to learn the engineering method more generally, and learn so many other fields of the trade. It turns out this is a much more resilient identity than just Programmer and I recommend that approach.
raddan
It's funny that you mention EE. When I went back to school for CS in the early 2000s (I was a philosophy major... dumb), I was taking night classes with EEs who were fleeing to software. This was in the Boston area. A large contingent of my classmates worked at Avid. They started moving jobs out of the US and employees were told that if they switched to software they could remain employed. The mood was pretty grim, and these folks commented to me more than once that I was lucky that I loved writing software, because largely, they didn't.
llmthrowaway20
> So for me, LLMs are amazing because I get to be an idea guy
Enjoy this while it lasts, because very shortly LLMs are going to be fundamentally better at being the "idea guy" as well.
I had the same feeling reading this article today as I did reading the NYT article about the closing of Butter Ridge dairy farm. All that family wants to do is raise cows, name them, and milk them but it doesn't work as a business anymore because the factory farm machine took the viability away.
I feel the author deeply; this is coming for everyone across most of the economy.
modriano
> Enjoy this while it lasts, because very shortly LLMs are going to be fundamentally better at being the "idea guy" as well.
Maybe for the ideas that are so far from novel that there's a corpus of training data that could train an LLM to reproduce it. But for actually novel ideas, LLMs won't ever be much use. They can't interact with the world directly, they can only interact with text (or I guess bits).
And I guess that's not much of a distinction, as truly novel good ideas are very rare and you can go very far applying a good idea into a new domain. But at the edges where true novelty is required, LLMs will either hallucinate or guide you away from the edge.
blks
No they won’t. And what you describe about the farm is just whitewashing marketing
undefined
artyom
Everyone is talking about the agents part. I'm going to praise this post for describing it very clearly that some people, from a young age, don't need phases, growing up, trying things, figuring out, exploring the world, finding themselves.
Some people are just born something (engineers, in this case), and they're that something for life.
I always have a hard time explaining to "normal people" that such life is not boring at all, in fact, I can't remember a single time in my life where I was actually "bored".
joecot
The people who go through phases are also born to be something for life: adaptable, and used to change. Being good at doing exactly one thing your entire life a certain way has the potentially fatal flaw of having significant issue doing anything else.
I feel like I've lived 3-4 completely different lives so far, but the constant is the ability to adapt to the next one, and still find joy in it while you're there. "Survival is the ability to swim in strange water."
Personally, the AI tools have been transformative for work, but haven't affected how I work much. I have always coded as a team. I'd often do the largest and most complicated parts myself, but work (both at work work and my hobby work) has always been about passing things between colleagues based on what our strengths were and how much time we had.
The AI tools are another colleague. They work incredibly fast, and I do less coding myself now, but my goal was always to solve the problem, not the code itself. The AI tools do a great job most of the time, but they sometimes screw up and need more guidance or me to step in to fix the thing (usually a very small error compared to the whole). If they screw it all up, we might need to start from scratch, or I might need to just do it myself. But that's not most of the time. And then I figure out the thing missing in my process to move them in the right direction, and improve it.
I feel like any software developer used to collaborating with, training, and mentoring other developers knows exactly how to work with AI tools, and the only main difference is how much effort I put into being really nice about it the whole time.
One main thing has changed. Before I would handle the most complicated problems people were having trouble with myself. Now I allow AI to work on them, even if I know I'll have to fix it. The difference is that I care about the time, the strain, and the morale of my coworkers. AI is just getting paid for iterating tokens, so I don't have to feel bad about what I ask it to figure out for me.
uncircle
> Some people are just born something (engineers, in this case), and they're that something for life.
Yes, and it's very not fun when your identity is being reshaped before your eyes in the matter of a couple years.
I wonder how many developers are going through real grief right now, while everybody else, lacking empathy, are just repeating "get a grip, it's just a tool" or "you better adapt or you're done".
Well, I know I have gone through these difficult emotions, and I choose now not to identify with my work, or at least my career any more. I certainly do not identify as what most people these days refer to as 'software engineer' any more.
hyperadvanced
This is a great reason not to identify too much with your work. I have enjoyed AI because it has reminded me that my real calling is art, and that I should be doing that at 8 pm, not coding
mday27
True, but if your true calling was coding, this change would be much harder to stomach
uncircle
Not sure if your 'enjoyed AI' is meant literally. I have escaped my existential crisis and found solace in art as well, simply because it's a very human method of self-expression and taking shortcuts to pain, effort and creativity by prompting LLMs is still frowned upon, at least by those that take art seriously.
The only way I can still enjoy programming now is if it's applied to artistic endeavours. I'm done with the soulless, cost-efficient software "engineering" (which by itself is a laughable proposition and a far cry from the high standards of other fields of engineering)
specproc
What I really enjoy is learning. I came back to computing after many years in another field, and was completely in love. Everything finally clicked, I'd spend hours reading everything I could, coding, trying things out, letting half-half-built projects pile up as I discovered new things.
AI has completely ruined this for me. Its boring having someone else do stuff for you. And worse, I feel I'm un-learning at a rapid rate.
The magic has gone, I'm not sure I want to be in this game in another five years.
ytoawwhra92
You don't know what your thing is until you try it.
Some people get lucky and the first thing they try turns out to be their thing.
meroes
Interesting that boring is the salient factor.
robotswantdata
IMO assisted coding (auto complete style) has more flow state than the old days of getting stuck on obscure bugs (as satisfying as those were to crack).
Full agent coding however is the complete opposite, you’re in constant damage control of a junior who moves fast and breaks everything. They’ve got better but still do dumb mistakes.
lot of engineers are discovering firsthand what it’s like to manage a team of eager but useless employees. Not fun at all
coffeefirst
The other thing is as far as I can tell, the power-tool style modes where you use AI to boost focus and do quick research is both much cheaper and, by the time you account for all the damage control/prompt tuning/other externalities, roughly as fast as full agentic.
I suspect with the prices going up, that realization is going to be pretty appealing.
jorvi
Prices are not going up. DeepSeek V4 Pro is 5-10x cheaper than Claude 4.7.
As some of us have been predicting, model capability had already mostly plateaued, and the Chinese have and will continue to relentlessly push cost down. Chinese models will be used for 95% of things, with nation-native models for security/sovereignity-sensitive workloads. Eventually (5+ years from now), efficiency gains and hardware progress will make running local models the dominant way of doing things.
And yes, that puts the investors of Claude and OpenAI in quite a pickle.
robotswantdata
I want the frontier on prem to be true but IMO not good enough yet unless async.
What started as all-you-can-eat $50 buffet has quietly become a $6k bill, frontier models that don’t ship your codebase to Beijing don’t come cheap anymore.
coffeefirst
Yes, that’s basically what I’m talking about. Without subsidies, that’s a lot of incentive to use more efficient/open weight models, but also to use them in ways that are less compute intensive—fewer tokens, shorter reasoning chains, less nonstop, and generally tie up less hardware for a lot less time.
slopinthebag
I agree, I also think there are long term costs to agentic coding that we won't see yet for a while, gradually and then suddenly.
It feels like nobody is even trying to iterate on the "power-tool style" usage of language models, everyone jumped straight to agents. It's not clear to me that removing a human from the loop is strictly more efficient though. Imagine an editor with an embedded language model (either running locally or using cheap cloud models) that is constantly churning, analysing code, reading debug logs, offering suggestions. Refactoring is not b̴e̴g̴g̴i̴n̴g̴ asking a chat interface to make changes, but structured refactors utilising the language models powered by the underlying ast representations to pull off much larger or involved refactors that surpass the abilities of current IDEs. Or doing codegen in your editor in a more structured (and thus repeatable) way compared to an agent spitting out code that you have to then review.
bluefirebrand
> IMO assisted coding (auto complete style) has more flow
I find this impossible to wrap my head around. Any time I autocomplete more than a single line, my flow is destroyed when I have to review what was just autocompleted. The only way I could remain in "flow" in this circumstance would be if I didn't review the code... I'm not ready to trust the LLMs that much yet
skydhash
> IMO assisted coding (auto complete style) has more flow state than the old days of getting stuck on obscure bugs (as satisfying as those were to crack).
I strongly doubt that. Flow state happens when you can disassociate thinking and doing. Most of your brain is on the thinking while the doing lags behind. It’s like driving on a well known road. You don’t pay that much attention to the act of driving. Instead maybe you start planning what you want to do on your next stop
Using ai auto complete would be like your well known road, but turned into an obstacle course. You need your full focus on the road. Not that different from someone that is unfamiliar with the road, but not a flow state either. Full agentic coding is you being in the passenger seat with a driver known to be sometimes erratic. Less thinking but more worrying.
nu11ptr
People are blown away when I tell them that, in the last 6 months, my job of coding has changed entirely, and that I now write very little code, but instead manage agents who write it. It is still engineering, and I still very much care what that code is, it's interfaces, how it interacts with the world, how it is tested, etc. etc., but it has taken me a while to get used to the idea of me not writing the code. I'm still not sure how I feel about it, although I am getting more done, and it has helped me keep better focus on "the big picture". That is tough to do when your day is spent in the weeds.
furyofantares
Really? When I've brought it up with anyone that doesn't code, I've found them to be totally disinterested in the topic.
nu11ptr
It isn't about the code (they probably don't even know what that is), they focus on the fact that my daily job tasks have changed entirely (iow, I used to do 'something', 'what' doesn't matter, and now I dictate to an AI to do it). Most people can't fathom this unless they change to a completely different profession/job.
thunky
> I've found that nobody that doesn't code is at all interested in the topic.
This triple-negative is hard to parse.
undefined
cindyllm
[dead]
TFNA
I don't code (well, I write scripts for my own personal use and use Emacs), but I follow with interest these reports from software developers. Why? Because my profession is similar screen- and keyboard-based intellectual work, and what has come for devs will probably come for many other careers.
raddan
It's worth mentioning that one reason LLMs can clean up on coding tasks is because of the volumes of available data. Not only has the world produced copious volumes of code, they continue to produce copious volumes of code, and some code can even be generated synthetically (ie, not from an LLM, albeit at high cost).
Other domains are not like this. There will probably never be enough poetry out there to make an LLM do anything but be a poor imitation of a poet. This data is extremely hard to generate.
jdw64
Reading this, I felt a familiar kind of sadness. I have also felt some version of this recently: the sense of loss, and the question of whether I am still a “real programmer” if I am no longer writing code in the same way. There is a strange grief in letting go of a skill that once gave you pride.
But when I think about it from the author’s position, I may actually have been lucky. For this person, writing code may have been a way of life. In my case, I only started doing field work and using AI relatively recently, so I was able to adapt faster than I expected.
If your whole way of life changes, the shock must be much greater.
In contrast, I had no real status or social position to protect, so perhaps it was easier for me to let go. If I had tried to compete fairly and directly, I could not have beaten the experience and accumulated skill of veteran programmers.
Of course, my ability to write code was something I was somewhat proud of. Giving it up was painful, and it brought regret and a sense of inferiority. But at the same time, I also find myself thinking: “Was I really supposed to fight against veterans like this?”
Recently, this feels very similar to Durkheim’s concept of anomie. While reading this, I kept thinking about categories such as conformity, innovation, ritualism, retreatism, and rebellion. There are many points here that make me think.
If, in the future, coding changes again from today’s agent-based coding into some other form, what will happen to me then? By observing how senior programmers are reacting now, perhaps I can draw my own conclusions and prepare for that moment.
Right now, agent-based coding that depends on specific companies is dominant. But I think the current price of agentic coding is too cheap. At some point, when it becomes more expensive, local LLMs may become mainstream. If that happens, damaged or weakened code-writing ability may become necessary again.
So the question is: how should I prepare for that?
This was an interesting post.
cmiles74
I understand that commercial companies want to get as much value out of each developer as possible, I understand that managers want work to complete as quickly as possible. I can see why they are so excited about LLM tooling and the current increase in output.
This post makes a good point: managing LLM models isn't really the same thing as thinking hard about a particular problem, solving that problem and then concretizing it in code. If the work becomes managing models, I think we're going to see a pretty stark divergence between what people enjoy about developing software today and what the job is requiring. I'm not yet convinced LLM tooling will stick but, if it does, it makes me wonder what kind of person will be doing software development. Maybe some of same people and they find something else to enjoy about the job but I bet a lot of a different kind of person.
Personally, I am very uncomfortable with the idea that all software development might be mediated by LLM tooling and, as a consequence, require payment to a large corporate entity like Anthropic or Google. Hopefully some open source projects will remain open to accepting PRs from people, like the author of the OP, who enjoy working in that "flow" state. I enjoy writing software as a hobby (as well as at my job) but it looks like the hobby might become a larger source of personal fulfillment.
gavmor
> I'm not yet convinced LLM tooling will stick but, if it does, it makes me wonder what kind of person will be doing software development. Maybe some of same people and they find something else to enjoy about the job but I bet a lot of a different kind of person.
TBH, I've often felt like a weirdo who enjoys "the wrong things" about software engineering.
undefined
undefined
jdw64
[dead]
cyberpunk
Yep, I’m in this boat too.
I’ve given up trying to get that feeling back at work.
We were lucky for 20 years, now if we want to do it for craft it’s time to contribute to OpenBSD or something — with phish on, not for money.
raddan
Ditto. I programmed for 30 years with Underworld on. Listening to the beginning of Juanita/Kiteless instantly drops me into flow state. And it no longer fits if I am using an agent. I appear to be almost the same age as the writer of the post; just a little older. And I got that grocery store job.
So I am working on a personal OpenBSD-related project. I have no idea if it will ever see the light of day. It scratches an itch and I am having fun doing it, and I don’t use AI. It’s forcing me to read man pages carefully and OpenBSD source code (side note: the lack of comments in their code is almost a “fuck you”).
I wonder if I should try out some Phish.
cmeiklejohn
To be fair, I often listen to Phish and Aphex Twin. Didn’t we all program to jungle in the 90s?
H1Supreme
> Didn’t we all program to jungle in the 90s?
Still do!
beej71
> now if we want to do it for craft it’s time to contribute to OpenBSD or something
I think projects like these will end up being the highest-quality pieces of software out there.
Mizza
If you found Phish twinned well with deep, focused work, you might enjoy grindcore for frequently interrupted work, since most of the songs are less than a minute long, like these: https://discordanceaxis.bandcamp.com/album/original-sound-ve...
tahoemph999
I have a similar tendency. I doesn't really work for me to write code and listen to lyrics so EDM and grindcore, like carcass, works for me. Either there are few words or you can understand them.
rglover
Choose when and where and how you apply it and the sadness goes away. There's zero rule that you have to use an LLM in your workflow; even if your peers insist it's "stupid not to."
When I started to get this feeling recently (the sadness around the flow state being knocked off-axis), I started asking myself "what are you rushing toward? Do you really need to be working like this? Is this truly rational or just socially congruent?" YMMV but may be helpful for some.
kaiwn
Programming with Claude is still engineering. It is like designing a bridge, which remains engineering even when a worker pours the concrete instead of you.
In the past we were forced to pour the concrete ourselves. I understand how many of us enjoyed the sound and the smell of the concrete being poured. Myself, I’m happy to never get my hands dirty again, and focus on the actual engineering.
blanched
This is like the third bridge + concrete comparison I’ve seen in the past two days from a new account.
Did I miss something?
Neywiny
"justify your existence"
"You're absolutely correct. I don't just need to exist-I need to justify why. It's like builders with concrete..."
undefined
kaiwn
lmao, I think I read it here and then I proceeded to think I came up with it myself. I’m a fraud. (I put “concrete” into the search field and found it)
jebarker
> the actual engineering
I was with you until the last three words. Craftsmanship in writing code is also “actual engineering”, it’s just not the engineering that people will pay a human to do now.
hamrocksissors
Chemical engineer here - I look at this similar to how a lot of professional engineers work, drafting gets passed off to eng techs, pfds get passed off to eng techs... The "actual engineering" is in the ideas, the applications, the reviews, and most importantly the final accountability.
pdhborges
Works great. No wonder China is eating our lunch.
skydhash
Studied Electronic Engineering and have friends in Civil Engineering. By the time, you get to the actual implementation, the design has been tested so many times that errors are often material defects, not design defects. Engineering is about ironing out all the design defects and have all relevant unknowns be known.
Working with claude is closer to “grandma recipes” than any engineering or scientific practice.
perrygeo
Thanks for this perspective. Do we really miss typing ascii characters into an editor? That seems to me the least consequential and least interesting part of building software systems. Always has been.
Dare I say those stuck on nostalgia for pressing keys are demonstrating that they cared more about their own personal experience than about the outcome of their work? Now that coding is automated, we have to elevate our ambitions.
Ironically, Phish's music emerges from egoless expression (to paraphrase keyboardist Page McConnell). Giving up your own personal stake in the process is literally what brings something as beautiful as Phish's music into existence. We need to do the same with our software; give up the notion that "our" code is meaningful.
yason
Dare I say those stuck on nostalgia for pressing keys are demonstrating that they cared more about their own personal experience than about the outcome of their work? Now that coding is automated, we have to elevate our ambitions.
YES. The beauty of programming is and always was that, first, you enjoyed it and, second, for some oddball reason you could actually get paid to do it. And one can't produce anything good unless you actually love working on it which means you want to put yourself working on it. The outcome might accidentally serve the one who pays for it but ultimately what did get the work finished was the sensation when you were reaching the point where you would finally tie things together and see everything you designed come to life and work together.
AI doesn't give you that personal involvement. We can do it but it's a different line of work and we care very little about what goes in and what comes out. We just do the grunt work of connecting the two ends. We're not for a fuck interested in elevating ambitions which is a word that relates to what is outside while all the good stuff comes from the inside.
cmiles74
I think concentrating on the physical act of typing on the keyboard is maybe taking it a little too far. The author of the OP talks more about holding a lot of the problem in their head and entering a "flow" state where they figure out a solution.
Most of my interaction with AI models and agents is still mediated by a keyboard and still requires a lot of "typing ascii characters". ;-)
perrygeo
The "typing ascii characters" angle is a bit hyperbolic, I admit. But my intention is to get people to think about their software, not their personal experience of it.
BTW, there's nothing preventing you from using AI agents and staying in the flow state. If you want that, the universe is not stopping you. In fact, not dealing with the minutia of source code may well free us up and allow even greater flow experiences.
giveaccountpls
> Giving up your own personal stake in the process is literally what brings something as beautiful as Phish's music into existence
Unless Page McConnell is creating his music with AI these days, I don't think this point holds.
bluefirebrand
> Do we really miss typing ascii characters into an editor?
Yes.
> Dare I say those stuck on nostalgia for pressing keys are demonstrating that they cared more about their own personal experience than about the outcome of their work
I care about the outcome, which is why I don't trust it to a fucking LLM
Valuing quality over velocity is not selfish
perrygeo
> Valuing quality over velocity is not selfish
Fully agree. I never mentioned velocity or advocated for lower quality. In fact, this statement very well sums up my point: we should care about the thing we're producing, not our personal experience of coding it.
foltik
It may feel like you’re designing a bridge, but in reality you’re just asking a worker to do that too, and rubber stamping it when the drawings look reasonable.
One day you’ll be asked why it collapsed and realize you don’t actually understand it anymore.
undefined
archagon
No, it’s management, not engineering.
konart
I'm not sure how I feel (or should feel) when I read posts list this.
Here I am still coding (mostly) by hand.
While I also sometimes do chat with qwen or use an agent to save some time writting tests or yaml, or "implementing" a draft version of a change, I can't really understand this "the job is changed".
Do some companies in some countries force you to use these agents? Are they going to fire you because Jack or Jill push changes two (or more) times faster than you?
Izkata
I have heard of companies that are counting how much you spend on AI in your performance review (higher = better). I'm not at one of these, but upper management is pushing it hard, and I'm lucky that my team has a technical manager who understands the limitations. So I'm not using it either.
tombert
When ChatGPT came out, I was beyond excited. I had a tool to generate config files, and bounce ideas off of, and help unblock me when I got stupid arcane logs I didn't understand. That didn't feel existentially depressing at all; it was just glorified Google in my mind.
When the vibe coding tools like Claude and Codex came along, I got into this kind of dread. I'm sort of required to use them for work (we are "AI-first"...), but even if I weren't the tools are useful enough to me that I kind of feel like I have to use them because if I don't I'll be left in the dust.
And now it kind of feels like a lot of my job has been converted into babysitting interns. I don't get to write a lot of code by hand anymore, because most of what I do ends up being yelling at Codex to automate most of what I used to do. It's not all bad; I never got any enjoyment out of the initial bullshit of getting the initial project and configurations set up or futzing with configuration files, but I did get joy out of writing the actual implementation of the code, and now I don't get to do that much anymore.
A silver lining though; I do get to think in higher levels now, which is kind of fun. A lot of what I get to do now is write stuff in TLA+ and/or Mermaid (depending on the complexity and how much fancy concurrency I want to do), feed that into Claude, and get it to implement that. That part is fun, but I fear that I'm an outlier and that kind of programming won't catch on because engineers love to take the fucking idiotic position that they "don't need to do math to do programming".
foolserrandboy
Can you describe how you work in this higher level? Sounds like scratches a similar itch that traditional programming offers.
tombert
Sure; for reference most of what I end up doing is concurrent and distributed systems, so that's more or less what I focus on. I don't know if this stuff translates to other domains.
Basically, when I have an idea for a project, I usually start drawing a diagram for how I think things should work. I usually draw it with draw.io first because it's easy and quick. After that, I usually translate this to Mermaid, primarily just to have a second draft, but also because having a text-based system makes it easy to copy and paste around, and that kind of stuff tends to translates well to state-machine based stuff that most distributed systems tend to morph into.
If what I'm working on is relatively simple, I feed the mermaid code into Claude or Codex, give it some surrounding context text about what I want, and get it to hack away.
For more complicated stuff, especially if I want to be more clever with concurrency, I will take my Mermaid diagram and manually convert it to TLA+. If I get stuck with the TLA+ translation, I will sometimes ask Claude for a bit of help but even then I almost always write 90+% of the TLA+ spec by hand.
After that it's basically the same. I feed the TLA+ spec, and provide context to it as well (e.g. how to translate a manual TLA+ mutex or channel implementation to whatever the language has built in).
Since I focus very heavily on the implementation, Claude and Codex generally don't have a huge issue with doing a one-to-one implementation.
stagger87
I'm in the same boat, I code mostly by hand. I really enjoy it. The OP seems to have given it up without a fight, and that doesn't make sense to me. Especially because with 30 years experience I'm guessing they have FU money and are probably better than most people using AI anyways. Keep doing what you love and "surrender to the flow".
wolttam
Yes, companies will hire employees that are significantly faster if they can do some for around the same cost.
And they can - the current crop of tools provide undeniable productivity uplifts to developers, even if they’re only using the cheaper open weight models.
I was like you, using them for one shot things until January of this year. My token usage has roughly 100x’d since then, once I saw the value in the agentic loop.
konart
>Yes, companies will hire employees that are significantly faster if they can do some for around the same cost.
And how do you test this when you hire? An interview where you have to implement something using LLM only?
zeafoamrun
Yes they will fire you. The sharks are circling those who just take tickets and implement what they say.
dekhn
The grateful dead were definitely my introduction to flow state. It wasn't just programming, it was using a MUD in the late 1980s. In my case, the Dark Star from Live/Dead (a long, extended jam that explores the outer reaches), I like a subset of the dead and phish for flow state programming but like the author find that modern work requires too many distractions to enter and stay in the flow state for a long time. In my case, large portions of the dead and phish don't work for me at all- the worst is when Phish is doing a great job and then suddenly they sort of lose the groove, or when they get stuck in repetitive loops.
JKCalhoun
Not Phish, but I have had music on in the background when coding for three decades at least now.
And not even necessarily when coding… I find that if there is no music playing, I will start a song in my head. That can get frustrating—the song loops, perhaps in fact just the chorus. So I turn on the external music and it seems to allow my brain to do other things.
Get the top HN stories in your inbox every day.
I feel his pain. I am more towards the opposite end of the spectrum [1]. I program to get things done. Usually, I don’t like programming. It’s too focused on one thing. Sometimes I like it though, precisely because it’s focused on one thing. But I love the things you can imagine and build with it. So for me, LLMs are amazing because I get to be an idea guy when I want but sometimes I can go deep, also when I want. I’ve kept up too, so I have the experience backing it up.
With that said, when I read this blog post. I feel the author’s pain. And it’s the first time that I emotionally get what the other side of the programming spectrum feels what it has lost. I feel sad about it. And because of it, I will also wonder about ways of bringing it back.
[1] not fully though. Something I can love coding by hand for months.