Live data from Hacker News

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

news.ycombinator.com

111–120 of 206 posts

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

#112

I will offer an orthogonal take: Spend less time on social media, news, forums etc. They are giving you a skewed view of what's important.

Good advice, thank you for the reminder.

Regarding the OP's dilemma. I am split. I enjoy both the process and the destination. With AI, the process is faster and less satisfying, but reaching the destination is satisfying in its own way, and enables certain professional ambitions.

I have always had other outlets for my "process" needs, and I believe I will spend more time on them in the future. Other hobbies. I love "artisanal coding" but that aspect was never really my job.

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

#113
“So what," the Chelgrian asked, "is the point of me or anybody else writing a symphony, or anything else?"

The avatar raised its brows in surprise. "Well, for one thing, you do it, it's you who gets the feeling of achievement."

"Ignoring the subjective. What would be the point for those listening to it?"

"They'd know it was one of their own species, not a Mind, who created it."

"Ignoring that, too; suppose they weren't told it was by an AI, or didn't care."

"If they hadn't been told then the comparison isn't complete; information is being concealed. If they don't care, then they're unlike any group of humans I've ever encountered."

"But if you can—"

"Ziller, are concerned that Minds—AIs, if you like—can create, or even just appear to create, original works of art?"

"Frankly, when they're the sort of original works of art that I create, yes."

"Ziller, it doesn't matter. You have to think like a mountain climber."

"Oh, do I?"

"Yes. Some people take days, sweat buckets, endure pain and cold and risk injury and—in some cases—permanent death to achieve the summit of a mountain only to discover there a party of their peers freshly arrived by aircraft and enjoying a light picnic."

"If I was one of those climbers I'd be pretty damned annoyed."

"Well, it is considered rather impolite to land an aircraft on a summit which people are at that moment struggling up to the hard way, but it can and does happen. Good manners indicate that the picnic ought to be shared and that those who arrived by aircraft express awe and respect for the accomplishment of the climbers.

"The point, of course, is that the people who spent days and sweated buckets could also have taken an aircraft to the summit if all they'd wanted was to absorb the view. It is the struggle that they crave. The sense of achievement is produced by the route to and from the peak, not by the peak itself. It is just the fold between the pages." The avatar hesitated. It put its head a little to one side and narrowed its eyes. "How far do I have to take this analogy, Cr. Ziller?”

― Iain M. Banks, Look to Windward

> It is the struggle that they crave

And yet, it's hard to shake the despondent feeling you get looking at the helicopters hoovering around the peak

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

#114
post #43

Earlier quoted context omitted.

>AI has just exposed that many "engineers" are "temporarily embarrassed project managers", which is fine in the sense that it makes it clearer who actually enjoys making things and who just wants the end result regardless of how it's made. AI has also exposed that many "engineers" are just "people who like fiddling with code" and that's fine in the sense that it makes it clear who are the actual engineers who are eng…

Haha! Your analogy doesn't work on multiple levels. Firstly, if you're outsourcing your work to AI you're not the engineer anymore. A civil engineer is different from a manager of a civil engineering project. Just like I wouldn't call myself an artist if I got AI to generate me some art, I wouldn't call myself a software engineer if I got AI to write all the code for me. Secondly, it's not just about "enjoying the jo…

[deleted]

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

#115

Earlier quoted context omitted.

> 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.

I hope the companies you worked for had someone else taking care of security, as what you've described is a ransomware writer's wet dream.

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

#116
post #109

Earlier quoted context omitted.

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 th…

And this has nothing to do with AI like you said. On another project my vibe coded API that I designed I also didn’t look at a line of code besides the shell script I had Claude create to do the integration tests with curl.

On the other hand, AI doesn’t care about sloppy code. I haven’t done any serious web development since 2002, yet I created two decently featureful internal websites without looking at a line of code authenticated with Amazon Cognito. I doubt for the lifetime of this app, anyone will ever look at a line of code and make any changes using AI.

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

#117

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? 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.

There still is. In most enterprises, the tasks are usually to take some data somewhere, transform it to be the intake of another process. Or to made a tweak to an existing process. Most of the other types of problems (information storage, communication, accounting,..) have been solved already (and solved before the digital world).

People can see it as grind. But the pleasure comes in solving the meta problem instead of the one in front (the latter always create brittle systems). But I agree that it can becomes hell if there were no care in building the current systems.

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

#118

I’ve made a bunch of tools to help me get around file system limitations on modern Macs (APFS) and treating my entire legacy file collection as CMS challenge and have cranked out more binaries in 3 months than in the 10 years before the arrival of these tools. If you know how to use these tools and how to think like an architect and not a hobbyist Claude is truly in the technological lead. I am a bit, but not much, y…

Are your tools open source? They sound kinda cool.

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

#119

Earlier quoted context omitted.

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.

There still is. In most enterprises, the tasks are usually to take some data somewhere, transform it to be the intake of another process. Or to made a tweak to an existing process. Most of the other types of problems (information storage, communication, accounting,..) have been solved already (and solved before the digital world). People can see it as grind. But the pleasure comes in solving the meta problem instead…

And they are tasks with standardized best practices. I knew that I wanted to write an internal web app that allowed users to upload a file to S3 using Lambda and storing the CSV rows into Postgres.

I just told it to do it.

It got the “create S3 pre-signed url to upload it to” right. But then it did the naive implementation of download the file and do a bulk upsetting wrong instead of “use the AWS extension to Postgres and upload it to S3”. Once I told it to do that, it knew what to do.

But still I cared about systems and architecture and not whether it decided to use a for loop or while loop.

Knowing that or knowing how best to upload files to Redshift or other data engineering practices aren’t knew or novel

Post reply on HN