| ▲ | ravenstine a day ago | |
"Solving problems" is a meaningless thing to say, and seems to be the next evolution of "full-stack engineer". It's a result of dissolving what used to be a specialty with its own subspecialties. Make the role of an engineer as generic as possible so they become interchangeable, easier to replace, and eliminated when possible. Plenty of software engineers are paid to not solve problems. Some are, but I would say that most are paid to do the thing. Orgs beyond the startup phase don't actually like problem solving because it introduces risk of instability. Just doing the thing isn't the same thing as solving problems. Business leaders would be very happy if they could eliminate the human from the doing the thing step, and not all of us can simply become the problem solvers because that's infeasible. | ||