Agreed.  There is a narrative programmers tell when complaining online.  It goes like<p>&gt; If only they would just leave me alone!  I would sit in silence for 4 hours pondering the depths of the system at hand.  Then I would spend 30 minutes invoking VIM macros at 240 actions&#x2F;minute (that&#x27;s why I spent 12 years integrating VIM into my lower cortex, after all).  Then I would spend 5 minutes admiring the perfection of my creation before retiring to the pub.  Tomorrow, everyone will find everything just works so much better than yesterday and they won&#x27;t even know how or why.  I&#x27;ll just lean back and say &quot;You&#x27;re Welcome.&quot;<p>But, the reality is that you don&#x27;t work in a vacuum; you don&#x27;t know the whole situation; your proposed solution probably isn&#x27;t as good as you&#x27;d like to think it is; other people are doing stupid things and breaking stuff because you never mentor them;  you are doing stupid things and breaking stuff because other people aren&#x27;t informing you about what you should be doing better; even when you are actively working on code, you spend less than 5% of your time actually typing code;  if you are a senior engineer working on non-trivial systems, you probably spend more time sorting out how other people&#x27;s code works than your own.<p>These realities don&#x27;t fit the <a href="http:&#x2F;&#x2F;hackertyper.net&#x2F;" rel="nofollow">http:&#x2F;&#x2F;hackertyper.net&#x2F;</a> narrative.  They&#x27;re embarrassing and require inter-personal effort to resolve.  But, brushing them off is making you a whole lot less productive than you should be.