Programmers who know to use ai will replace thosw who dont.
That seems rather dubious. Some developers are far more replaceable than others. Developers reliant upon AI to do the work are only an administrative step away from replacement.
Ask HN: What is the future of tech roles?
11–15 of 15 posts
Re: Ask HN: What is the future of tech roles?
#12We’re at a stage, where we have to come up with ever more complex benchmarks, as the old ones are getting saturated, yet, anywhere I look, I don’t see any significant productivity boost. I can’t point to any product on the market or a company and say that they visibly increased their velocity.
Yes, it useful, but anyone saying that almost all software workers are getting replaced incredibly soon is either misinformed, or is selling something.
Re: Ask HN: What is the future of tech roles?
#13Trying to predict things is not my preferred thing.
I try to make myself easily replaceable by others. Non-special, in the context of a job. It's a hallmark of teamwork, for decades.
To face that prospect with AI as a replacement seems unexpected and the wrong kind of question. I can't transfer knowledge to it like I would to a team mate.
I don't understand your use of 'artistry' here. Do you mean your 'craftsmanship'? I will answer like you meant that.
Do something that is rare, valuable and honest. Share it with others so it doesn't fade away. There are many of those kinds of things. It does not guarantee you will be valued, and that's ok.
Re: Ask HN: What is the future of tech roles?
#14There is going to be a workforce reduction for sure with a shift towards more AI tools, however its going to be driven by the economic policy rather than usefulness of AI, as US economy slowly dwindles away. Of course service quality is going to drop as a result, but thats just how the cookie crumbles.
Re: Ask HN: What is the future of tech roles?
#15Engineering is being good at using engines. Knowing all the systems that this engine is composed of, optimizing it, making it do what it's meant to do with minimal error, coming up with tests to verify that it does, facilitating all technical communication.
There's plenty of that work coming up. People don't like working with a completely different engine but it's inevitable; before this everyone was complaining about JS frameworks. Once the AI dust settles, it's back to spending 20 hours of the weekend learning the next framework.