Well, there is a lot here that I think is good. A lot of this is about what a good developer should and shouldn't do, so I think some attention to what their em

Well, there is a lot here that I think is good. A lot of this is about what a good developer should and shouldn't do, so I think some attention to what their employer should and shouldn't do is in order. A good developer should be okay with making estimates in order to be relied upon to build important things- so far so good. But if you're the only person left, who handles a workload that should be enough for three, and random shit pops up all the time where someone is yelling at you that this must be dealt with, and nobody actually knows what they want so the idea of what is being estimated upon will change 4 times before it's done, and oh yeah our dev infrastructure is broken in various ways........ you see what I mean. There is a point at which committing to ship something in a given amount of time, even when all that other shit happens, is really just a brick in the wall of burnout. Point made. But more generally there is little thought paid to what employers should be doing to hold up their end of the bargain, and ever more paid to what employees should be doing better.