Ask HN: Am I old?

The key is knowing when and how to use both.

If you can be twice as fast with something using AI and you're actively choosing not to use it, then yeah you're just being stubborn. Get over it or risk getting the boot.

There will be times though where you need to finish that last 10% of coding because the model just isn't refined enough for whatever task you're giving it. And from what I've experienced so far, that last 10% ends up being 70% of the work, which is where your expertise will come in.

Why not both?

I'm in my mid-50s. I enjoy writing a simple utility function by hand. I care about craft and form.

But, I also care about increased productivity, exploring new technologies, and the wonders of AI.

Being into one doesn't negate the other.

I believe this says more about the tendency for our minds to close off to new ideas and stimulus as we get older. There's a reason that most people's "ideal era" is in their high school years.

I urge you to foster more resilience and adaptability and shun the traps of "back in my day-ism".

I'm 61, and old Turbo Pascal/Delphi/Lazarus programmer when I get the chance. I've just decided to see what my GitHub copilot subscription can really do for me in implementing something like metamine[1], a language I first learned about here on HN that includes a magically equals[1].

It's slow going, learning how to use a virtual assistant to get things done, but it's patient with me, as well. Eventually, however (and to stay relevant to the conversation here), I've started exploring how the code works, and fixing bugs on my own.

Once I get the framework to the point where anyone can try it out, I hope to then go through and understand every freaking line of code, and expand it from there. You're not alone in the desire to grok everything you write. There's a lot of power in that knowledge.

Then I'll re-implement it in Turbo Pascal under MS-DOS... just to prove a point. ;-)

[1] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...

I use AI extensively in work, but I try to restrict its usage in my side projects because of the same reason as yours -- I enjoy writing programs and figuring out things, so I will definitely leave the hard part to myself, and the boilerplate part to AI. Even in work I still try to figure out the algos/proper design by myself first.

I want to be able to understand your point. For those who enjoy programming, writing code is indeed a pleasure. I spent the whole day today writing a JavaScript serialization package, and even though I know someone has already done it, I am still willing to write a new one for my specific scenario. On the other hand, I think that although AI seems friendly to newcomers (inexperienced developers), it is actually more friendly to experienced developers because you can have AI help you complete some tasks and then review them yourself. Inexperienced developers have difficulty accurately pinpointing problems when they encounter issues, causing AI to keep going in circles and hitting walls.

Do you want to do work or do you want to do your hobby?

If you get joy out of digging with your bare hands then you should do that. When you're doing work, use a shovel or heavy machinery if you want to get to the valuable output sooner.

I don't see that we're gonna lose that satisfaction you describe anytime soon. But if everything I typed is via prompt engineering, yeah I'll be a little sad.

It is like hearing about manual cars.

Those handlers... (Reaches for the tab key)

I get joy from money appearing into my account to exchange for goods and services. I have plenty of things I enjoy doing outside of work that don’t involve computers - spending time with friends and families, exercise, travel, concerts, etc.

And yes I’m old - 50. I started programming in assembly on the Apple //e in 1986 and haven’t written a line of code since 1996 that I haven’t gotten paid for.