Multi-month approval sucks, but to be honest I wish more companies were more skeptical of adding 3rd party dependencies. At the very least, do a code review of the dependency (and it's dependencies..) and acknowledge the actual cost associated with the addition you are making.

Hardly ever happens.

The issue that most "dev shops" can't estimate anything beyond three months so the best they can do is "this 3rd party dependency speeds up current process by X"

I don't want to seem sarcastic, since this is a genuine question: What are the positive aspects that would induce you to work or stay in such an environment?

You can code all day and stay in your corner without any external hassle.

That process being enforced will ensure that most code is buggy and development is totally unproductive. That will usually create an environment where noone expect anything from developers and you have zero accountability.

if it all goes well, you can toy around all day and not have to ship anything, still getting a paycheck, and not risking the comparison to your peers.

>That process being enforced will ensure that most code is buggy and development is totally unproductive.

I don't think I'm following you. The procurement process is quite different than our coding process which involves team reviews and the like. Yes, productivity isn't as high as it could be because we sometimes have to develop something in house instead of using open source code, but we still have code review, unit testing, and similar required.

sure, but… what about the mirror?

Approval process is outside the dev shop's control. Overall this is one of the least stressful positions I've been in, has the best pay so far, I enjoy working with my team, and has a short commute.

What industry are you with?