Live data from Hacker News

I'm 60 years old. Claude Code killed a passion

news.ycombinator.com

191–200 of 206 posts

Re: I'm 60 years old. Claude Code killed a passion

#192

Yes, it changes the nature of the work. Back when you started coding there were people experiencing the same thing about shifting to higher level languages. What some of them liked was the efficency and aesthetic of using just the right assembly language trick and good compilers with high quality instruction selection took that away. I'm sure there were programmers who missed the days of punching in hex into memory.…

https://justine.lol/dox/english.txt

Re: I'm 60 years old. Claude Code killed a passion

#193

Earlier quoted context omitted.

> Like imagine slandering a civil engineer "you just want a bridge that is safe and lasts for a century, you don't care about enjoying the journey of construction". Would you currently trust a bridge designed by a civil engineer using AI for all of their calculations ?

>Would you currently trust a bridge designed by a civil engineer using AI for all of their calculations ? Of course. I've seen how sloppy and lazy humans are, and I already use the bridge, and if the safety truly came down to the output of single person, then the risk is already significant. I must say, I got a chuckle at "using AI to do their calculations". Oh no, my agent is going to write a python script to do bas…

Bridges are not typically designed by the sloppy and lazy humans, but whatever

Re: I'm 60 years old. Claude Code killed a passion

#194
This is true. When I started coding I was enjoying it every new problem teach me a lot of new things that increase my curiosity about what the next level. But After AI agent writing code feel like headache. the task i done in 2 hours after a lot of hardwork the AI agent done same work in few minutes with perfection. So I thinking about to quit the coding because today i do vide coding which is not actual coding.

Re: I'm 60 years old. Claude Code killed a passion

#195
A Vibe Coder’s Tale

As there are so many claims out there about agents that are built in 10 minutes, 2 hours, or 2 weeks, here is the truth of what it takes to build something solid, at least according to our test users.

We started out 14 months ago here to change the way funding decisions are taken by VCs, PE, Business Angels, and Accelerator programs because, as serial entrepreneurs, we felt that there was a lot of bias involved, which has had a negative effect on the asset class as a whole.

So, in the beginning, we teamed up with a fellow Accelerator alumni who claimed to be an experienced AI developer and put a lot of trust into his capabilities. After 8 months of back and forth, endless excuses, and iterations without improvement, we received an MVP that was too poor to mention, not at all according to mutually agreed specifications, full of drift and hallucinations, non-reliable scoring, and a word count that exceeded the pitch decks it was supposed to analyse.

So.........another painful parting-of-ways and still no product.

In the light of super-confident claims by ChatGPT that it could help me to develop it on my own despite not being an experienced coder myself, I set out on the journey with OpenAI. At about the same time, I thought that I should probably gain theoretical knowledge about generative AI and enrolled in a Johns Hopkins University postgraduate course.

The former was a disappointment, the latter a game changer.

ChatGPT 5 simply does not have the memory span to keep context of a complex, deterministic agent. So I went to Gemini 3 with which I started to keep local copies of my scripts and keep a record of session documentations. But also that model, despite loading docus ahead of each development milestone, sent me from one post-mortem report to another. Things became even more complex when I started to apply guardrails, such as LangChain, RAG, or MCP, that I had learned in my course.

As I became more experienced with the Python code the model blurred out, someone on YouTube told me to give it a try with Claude’s Opus 4.5 and that turned out to be my salvation.

I will not engage in any advertisement for Anthropic (also they really don't need me for that), but let me tell you this:

if you put your mind to prompt engineering,

if you put an emphasis on keeping local copies of scripts and documentation (do not use Claude’s projects),

if you build a solid foundation of guardrails on how deep research should reach and what the definitions of judged decisions are,you will make it far.

Never allow it to deploy from its own sandbox, challenge it with an LLM-as-a-judge and an MCP layer, force it to work in mode absolute, and you may develop something that exceeds your own expectations.

Re: I'm 60 years old. Claude Code killed a passion

#196
That's a fair point. There was a specific meditative quality to the 'journey' of manual debugging and architectural planning that AI can make feel rushed or even redundant. When the 'middle' of the work is automated, it can feel like the soul of the craft is being hollowed out.

However, I wonder if the 'journey' hasn't disappeared, but simply moved to a higher altitude? Instead of the joy of the individual brushstroke (the syntax), perhaps the new journey is in the orchestration of the entire gallery (the system design)?

It’s certainly a grieving process for those who loved the tactile nature of the code itself, but as you said it’s not better or worse, just a different kind of travel."

Re: I'm 60 years old. Claude Code killed a passion

#198
I respect someone who knows what they like, but i love the journey as much or more, and i love AI coding. Not vibe coding mind you, deep engaged, specify tightly and review most edits in a high velocity flow state. Its not easy to read code at 80 tokens/second, but its fun, and feels more like im dreaming in code, using AI to type exactly what i want at 10x the speed. Which allows me to experience more of the journey..and i still get plenty of thorny bugs to work through. What would you code, if you could code anything you dreamed. Go code that today. Btw, 50 years old,started programming at age 9.

Re: I'm 60 years old. Claude Code killed a passion

#200
For me getting the AI harness to solve the puzzle has become the puzzle. Just one more level of abstraction. Just like I don't code in assembly language anymore, now I don't name every variable.

AI coding is just a non-deterministic programming language and compiler duo

Post reply on HN