First of all. There's no point in programming for the sake of programming. You're either a developer developing products or you're building something that someo

First of all. There's no point in programming for the sake of programming. You're either a developer developing products or you're building something that someone else is designing. The age-old problem with development in big corporations is the following: How it should be. The agile way: developer <-> client What actually happens: developer <-> the people seeking a role between you and the client <-> client These people can be PMs, functional designers, UX-ers, architects etc If your company doesn't have Agile in its DNA, Scrum - if done properly - actually offers the solution. It forces a team of developers and a client (the product owner) to work together directly. The problem is, however, that these people still find ways to elbow themselves into the process. So you see many companies doing "their own version of Scrum". They implement SAFe etc. You suddenly have to deal with things that are not about the client needing a product.