Reading and understanding documentation and producing clear, written requirements will be more critical than it is today. We've always known documentation is important but it's frequently glossed over in many projects and not taken as seriously as code reviews. With AI though, it's going to be much more important that all requirements are written down clearly and captured.
How does a Dev's job look like in a few years?
21–25 of 25 posts
Re: How does a Dev's job look like in a few years?
#22I feel like I am rather a quality assurance guy, who controls what AI is producing.
Re: How does a Dev's job look like in a few years?
#23So based on the comments, I'm the only person who think our jobs will be diving into years-old LLM-generated code to fix it all, and laughing: "Oh my, do you all remember when the entire industry burned 5 years and b/trillions of dollars just to try to force a use case to work that wasn't even the right match for the tools?" I'm not even trying to be snarky. I just see that LLMs already work fine in almost every othe…
How long ago did you use the tooling? I've seen this take a lot, and I can understand it if you're looking at the output of Sonnet 3.5 copy and pasted. But models like Opus 4.8, that just is not the case. Sure, you can't just whack it into the codebase, it needs review. But lets not pretend that 85% of programming jobs are CRUD with some async messaging. And the newer models are perfectly serviceable for that sort of work.
Re: How does a Dev's job look like in a few years?
#24I think that teams will get smaller but their will be more products.
Yes we can vibe code, but they all look the same and have no users.
The edge will be well thought through designs and experiences that keep users sticky.
We are yet to fully embrace wearables such as glasses and robotics. These will both create whole industries.
I am not worried about my job as long as I keep learning.
Re: How does a Dev's job look like in a few years?
#25Things that I reckon will become a lot more important from a developer's perspective over the next year: - Shaping work so it is more decomposable, legible, verifiable and understandable - Property testing, formal verification (exhaustive proofs, and bounded model checking), and test verification (e.g. mutation testing) - Understanding product market fit and opportunity space - Application of product management techn…
[flagged]