Ask HN: Am I old?
21–30 of 35 posts
Re: Ask HN: Am I old?
#22It is like hearing about manual cars.
Re: Ask HN: Am I old?
#23The 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 las…
I cannot think of any environment in which getting code fast is of paramount importance (ok, maybe in hackathons and the advent of code). In work based environments, the bottleneck is not writing code is human interaction (understanding requirements, making trade offs and communicating them, listening to feedback, etc.)
Re: Ask HN: Am I old?
#24Earlier quoted context omitted.
I cannot think of any environment in which getting code fast is of paramount importance (ok, maybe in hackathons and the advent of code). In work based environments, the bottleneck is not writing code is human interaction (understanding requirements, making trade offs and communicating them, listening to feedback, etc.)
If you follow agile one of the tenets is getting working code to users fast in order to get feedback sooner rather than later. Yes, the things you say are where the bottlenecks typically lie, but it's a cycle so the faster you can get working code out the sooner you can enter the other parts of the cycle. In theory anyway.
Re: Ask HN: Am I old?
#25Everyone else will take the easy route -- higher immediate productivity but overall capable of less.
Re: Ask HN: Am I old?
#26But then again I may be considered old, too (I'm in my 40s).
I don't think it's a great idea to become too reliant on it, just like it's not a great idea to only know how to copy+paste code from Stack Overflow. If you use it too much the coding muscle gets weak and you will become less able to identify when something is done incorrectly or in a less than ideal way because of this corner case or business requirement.
Re: Ask HN: Am I old?
#27Earlier quoted context omitted.
I cannot think of any environment in which getting code fast is of paramount importance (ok, maybe in hackathons and the advent of code). In work based environments, the bottleneck is not writing code is human interaction (understanding requirements, making trade offs and communicating them, listening to feedback, etc.)
If you follow agile one of the tenets is getting working code to users fast in order to get feedback sooner rather than later. Yes, the things you say are where the bottlenecks typically lie, but it's a cycle so the faster you can get working code out the sooner you can enter the other parts of the cycle. In theory anyway.
There's no mention of that anywhere in the manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
It's mostly saying to focus on active factors more than rigid rituals so that that the product evolves faster and in the right direction. There's no mention on pumping code out as fast as you can.Re: Ask HN: Am I old?
#28I just spent most of the day going back and forth with AI over stuff, and it kept getting more and more complex. Someone who didn't know any better would probably just take it and run with it, but I worked along with it, offering up more elegant suggestions to bring it back down to earth, where other people might be able to actually understand what it is trying to do.
I still get the most joy from writing tiny little scripts that help me (or others) do something useful.
Re: Ask HN: Am I old?
#29Earlier quoted context omitted.
If you follow agile one of the tenets is getting working code to users fast in order to get feedback sooner rather than later. Yes, the things you say are where the bottlenecks typically lie, but it's a cycle so the faster you can get working code out the sooner you can enter the other parts of the cycle. In theory anyway.
> If you follow agile one of the tenets is getting working code to users fast in order to get feedback sooner rather than later. There's no mention of that anywhere in the manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan It's mostly saying to focus on active fact…
https://agilemanifesto.org/principles.html
Specifically:
"Our highest priority is to satisfy the customer through early and continuous delivery of valuable software."
I guess there are religious texts, and then there are the interpretations of those texts.