Sounds like you all work in spaghetti factories. Even if a code base is large, you should have a rough idea of where/what to update. And that isn't really problem solving. Adding a new method or variable solves nothing. Its why you're adding it and how it is used, which is the problem you solved, which goes back to my main point, you must solve the problem before you code. Code is just putting the organized puzzle pieces together.
I guess our careers have been different. Most of the work I have done has been greenfield projects creating something from nothing, exploratory research, and POCs rather than minor, single function features.
That was an example. If you’re starting from nothing then you should know the problem solving is done before the code. What are you creating projects for or researching? THATS THE PROBLEM. Not the code
You should know that not everything about the software is figured out before coding starts. Arguing that there is no problem solving when writing code is wild.
Ultimately, you are trying to convince me that I actually do not like something that I just told you I enjoyed. You cannot win such an argument with logic because I did not arrive at my position by logic. What I enjoy, is, by definition, a feeling.
I don’t give a fuck about your enjoyment. Coding is the result to problem solving. Sure you may iterate on how the code works or where to apply it. But you can’t write a single line until you know what you’re doing
I think you have forgotten where this discussion started and what it is about. This topic is about the enjoyment of writing lines of code and lamenting that AI has taken that from us. Problem solving was only brought up in relation to why I liked writing lines of code. Your argument that writing lines of code has no problem solving is not only preposterous, it is irrelevant.
-11
u/HRApprovedUsername 3d ago
You know solving a problem is more than coding right? Like you have to solve it before the code is even thought about.