There's a cautionary tale here for developers. If you're productive, hard-working and have enough grit to complete projects, you'll get noticed and handed even

There's a cautionary tale here for developers. If you're productive, hard-working and have enough grit to complete projects, you'll get noticed and handed even more responsibility. Eventually it will be more than any single developer could handle and you'll burn out. Often, if you bring it up with management they'll do very little to fix the problem. Projects that could be completed in a few days when delegated to other teammates will somehow languish for weeks, at which point you get roped in anyway to hit the deadline, except now you have to do it ASAP and you're working nights and weekends. At the end of a project like that mgmt will consider it a success, since the project was completed, and the whole thing will happen all over again. The only thing they'll actually notice is failure. But who wants to let something fail? So keep your head low. Get a sense for how long it takes others to complete projects, and aim to be in the same ballpark. To get management to make rational scheduling decisions you need to control what they see. Which for this type of engineer is going to be really hard. Management should be better at this, but in general they're not, so it's either constrain your productivity or be successful for a year or two till you're overworked out of a job.