alt Hacker NewsFor now at least, I think it really depends on what type of coding that is.
I don't have any particular predictions going forward about it, but something I think about right now is, do I want to focus my time where the interesting decisions, the valuable contributions I make, are product-level thinking about what to build and what problems to solve? Or do I want to focus my time where the interesting decisions are technical ones, fully wrapping my head around a technical problem and coming up with a solution?
I do think both options are still available, and personally I love them both. But I don't know what types of coding would involve significant amounts of both activities anymore.
There’s still a lot of place for both. Because they are just a shift of perspective around the same thing: Solving a problem for someone.
Product is when you’re seeing things as the one who have the problem and designing the solution in a way that is usable. Technical is when you shift to see how the solution can be implemented and then balancing tradeoffs (mostly costs in time and monetary resources).
While the code is valuable (as it is the solution). Building it is quite easy once you have a good knowledge on both side.
The issue with AI is not in their capabilities, but in people rushing to accept the first version when there are still unknowns in the project. And then, changes costs almost as much as redoing the project properly.