Ask HN: How you ever quit because the engineering culture is too messed up?
This can be frustrating for sure. Your question &#x2F; post is a little light on details, so I am reading between the lines a bit here, but to some extent you&#x27;ll find this everywhere, and dealing with it can be a useful skill.<p>Can you provide a few more details on what you mean by &quot;management infrastructure&quot;? Are we talking source control &#x2F; build systems &#x2F; JIRA workflow stuff here?<p>I would suggest trying to find ways to be productive <i>yourself</i> that don&#x27;t involve changing what other people do.<p>Don&#x27;t try to sell &quot;ideas&quot; and &quot;proposals&quot;, lead by example, and if it works out people will follow.<p>For example, if people want to use subversion and do their development on trunk, but you want to use git with feature branches... then just do that for your local development, create and switch branches locally all you want, and then push to subversion when you&#x27;re done.<p>If there&#x27;s some dumb JIRA workflow, copy and paste the details to a text file, work on the thing, take your notes in the text file, paste it back to JIRA when you&#x27;re done. You will probably find you can isolate yourself from most kinds of silliness quite well, and if you&#x27;re productive doing so then others will follow.<p>As for your specific question, I think it&#x27;s worth trying to improve things for at least a year, or maybe two, before you consider leaving. In that time, you&#x27;ll probably find there are things you <i>can</i> change, learn that other things are actually not as easy to change as you might think, and generally build some useful experience in turning around a challenging situation.