My observations about this: * The more internal hurdles in place to prevent a developer from solving a programming problem the less of a hurry that developer w

My observations about this: * The more internal hurdles in place to prevent a developer from solving a programming problem the less of a hurry that developer will be in to solve such problem. Hurdles may describe additional tools, build steps, security provisions, dependencies, processes, manual steps, and so forth. * Some developers actually know what they are doing. Sometimes they appear to be 10x developers. They don't work necessarily harder, but just get things done. Getting more done in a shorter period of time leaves of idle time comparative to their peers. * Lack of productivity is typically reinforced by the environment despite all their claims and agile methodologies. For example consider how many hours a day you are in meetings not writing code. * Most lost productivity appears to be a result of poor choices of technology and/or training misalignments. It appears that Java turns any software authoring process into slow moving tar, for example. On the other side some developers won't even attempt to write code unless they have a favorite framework and a bazillion tools/dependencies. The excess extraneous bullshit chokes delivery into a coma. * Most bad technology decisions appear to be deliberate around people concerns. Nobody wants to invest in dedicated formal training, so instead employers deliberately make choices around lowing hiring costs opposed to lowering delivery costs. Why should they invest in training when the average developer will stick around for less than 2 years? So instead seniors get paid more to do the same beginner work as everybody else, but likely get it done in a fraction of the time with nothing else to do.