Live data from Hacker News

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

news.ycombinator.com

101–110 of 206 posts

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

#101
post #11

I just built two projects where one dogfooded the other and setup a fully working slack bot all in 1 hour. If you still want to manually do things you can. AI can answer questions about common topics way faster than searching docs. Idk why this kills peoples passions. Especially of you're old enough to not need a salary

How old is that exactly?

Abstractly, it's where log(forecast(assets)) exceeds log(anticipate(desires)) by log(safetymargin).

Molecular biologists are still searching for the pathways that govern the expression of assets, desires, and safetymargin.

Doctors and tax accountants are still arguing over whether the forecast and anticipation functions are learned or innate. And philosophers and used car salesmen can't even agree on where these functions sit on the cause/effect axis.

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

#102
for me the journey is the things i can do through creating various things in various contexts and authoring the code itself is a small step in the journey.

if it the puzzle solving metaphor, i'm taking solved puzzles as pieces to solve a more meta puzzle ... and i enjoying the journey at that level.

i try to practice tracing all the way down the stack and learning about new things added to the stack, but i'm not in it for the sake of the stack or its vagaries and difficulties.

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

#103
post #22

> it depends on what you enjoy: the journey or the destination This has been 100% my experience. I enjoy the puzzle solving and the general joy of organizing and pulling things together. I could really care less about the end result to meet some business need. The fun part is in the building, it's in the understanding, the growth of me . I have coworkers who get itchy when they don't see their work on production, and…

Your company isn’t paying you to solve puzzles. If you aren’t putting things into production, what good are you as an employee? > Being forced to use Claude at work, it really just took away everything that was enjoyable. Instead of solving puzzles I'm wrangling a digital junior dev that doesn't really learn from its mistakes, and lies all the time. Claude very much learns if you teach it and tell it to note things i…

> Your company isn’t paying you to solve puzzles. If you aren’t putting things into production, what good are you as an employee?

No, the company is exactly paying their employees to solve puzzles, which company labels them as problems or requirements.

And when an employee focuses on solving puzzles and enjoys it, the code naturally ends up in production, and gets forgotten because the puzzle is solved well.

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

#104
post #99

Earlier quoted context omitted.

> Your company isn’t paying you to solve puzzles. Actually they are, but it's also true that you need to put solutions in to production.

No your company is very much paying you to put things in production. Thats all they care about

No the company wants its problems to be solved and needs to be addressed.

When things are put to production as soon as possible without respect to quality, we see what's happening all the time.

Bloat, performance problems, angry customers, Windows 11...

You get the idea.

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

#105
post #92

Earlier quoted context omitted.

> PMs now expect that you can create a Java micro service that does basic REST/CRUD from a database and get it into production in a total of two days. Have you heard of malicious compliance? Give the PMs what they ask for, then show them how what they've asked for is flawed. Your job as an engineer is not to just take orders blindly, it's to push for a better engineered solution. It's really not hard to show that wha…

A new micro-service in two days is easy with an IDE and autocomplete. But now with AI the PM will likely push to have it in production in a day. Which is possible, but quality will be questionable.

> A new micro-service in two days is easy with an IDE and autocomplete.

Is your username accurate, are you currently retired? I hope you know there's a big difference between something that is functional and something that is production ready.

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

#106

Earlier quoted context omitted.

Your company isn’t paying you to solve puzzles. If you aren’t putting things into production, what good are you as an employee? > Being forced to use Claude at work, it really just took away everything that was enjoyable. Instead of solving puzzles I'm wrangling a digital junior dev that doesn't really learn from its mistakes, and lies all the time. Claude very much learns if you teach it and tell it to note things i…

> Your company isn’t paying you to solve puzzles. If you aren’t putting things into production, what good are you as an employee? No, the company is exactly paying their employees to solve puzzles, which company labels them as problems or requirements. And when an employee focuses on solving puzzles and enjoys it, the code naturally ends up in production, and gets forgotten because the puzzle is solved well.

And if they could solve the problem faster with AI?

But there is no “puzzle” to solving most enterprise problems as far as code - just grind.

And code doesn’t magically go from dev to production without a lot of work and coordination in between.

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

#107

Earlier quoted context omitted.

No your company is very much paying you to put things in production. Thats all they care about

No the company wants its problems to be solved and needs to be addressed. When things are put to production as soon as possible without respect to quality, we see what's happening all the time. Bloat, performance problems, angry customers, Windows 11... You get the idea.

The reason your login is taking 45 seconds and your database is locking up with 10 concurrent users isn’t because developers didn’t write good code following the correct GOF pattern.

If companies cared about bloat and performance you wouldn’t see web apps with dozens of dependencies, cross platform mobile apps and Electron apps.

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

#108
post #11

I just built two projects where one dogfooded the other and setup a fully working slack bot all in 1 hour. If you still want to manually do things you can. AI can answer questions about common topics way faster than searching docs. Idk why this kills peoples passions. Especially of you're old enough to not need a salary

How old is that exactly?

>= 60 apparently.

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

#109
post #99

Earlier quoted context omitted.

> Your company isn’t paying you to solve puzzles. Actually they are, but it's also true that you need to put solutions in to production.

No your company is very much paying you to put things in production. Thats all they care about

Putting solutions in to production. Not "things". Honestly I'm sick of dogshit companies wanting something done yesterday but are happy to spend the next 2 years having engineers debug the consequences.

I've just written the fifth from-scratch version of a component at work. The requirements have never changed (it's a client library for a proprietary server, which has barely ever changed). I'm the 5th developer at the company to write a version of it.

All because nobody gave engineers the breathing room to factor the solution in to well thought out, testable, reusable components. Every version before is a spaghetti soup of code, mixing up unrelated functionality in to a handful of files.

No well thought out interfaces. No automated end-to-end testing, and no automated regression testing. The whole thing is dire and no managers give a fuck.

AI cannot solve for a lack of engineering culture. It can however produce trash faster than ever at these toxic shops.

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

#110
post #92

Earlier quoted context omitted.

A new micro-service in two days is easy with an IDE and autocomplete. But now with AI the PM will likely push to have it in production in a day. Which is possible, but quality will be questionable.

> A new micro-service in two days is easy with an IDE and autocomplete. Is your username accurate, are you currently retired? I hope you know there's a big difference between something that is functional and something that is production ready.

Somewhat retired last year. Looking for something new to do. Basic Java micro service with Spring Boot ands it is three hours of coding to write and read from a database and expose over REST interface. Two hours for a tests. Rest of the time is to set up environments, coupling everything, documentation. Two days is do-able if you have a good CI/CD template and your Azure/AWS is setup correctly.
Post reply on HN