| Most of the fast growing companies run into your described problems. As long as there is no upper management commitment to the values of "proper written tests and benefits" or "correct GIT usage" or something else, there will be no change but "Burn Outs" (the one's that try too hard to do 100%). Your "Head of IT" is most probably "forced" into dropping those values in favour of a "up & running" product. In my personal case (as Head of IT), I got a commitment to security from the upper management. This allowed me to drastically reduce access to resources like DB and SSH access and "force" people to document their needs which helps understanding where "South" actually is. While enforcing rules, many double/tripple/quadruple works where detected and migrated and also some new "Specialist" where found that were very good at their specifically assigned work. As a programmer, you and your team need to understand the companies goals and try to establish according rules/workflow for your daily business. For example: Your product is basically "done" and now management wants "Features". The "Features" Section of your products requires a clear interface for "plugins" and probably also a quick way to "prototype" new features. So you as a developer should find appropriate ways to optimise your workflow which might require to change your workflow for a specific section of your product. Of course, this is totally oversimplified, but I hope you get the point. Bye the way, this all requires Communication AND Understanding of all particpiants! Management need to communicate the way you are are heading and IT needs to articulate what is needed for the upcoming tasks. Be aware, most solutions are not found in a day. Complex Situations needs time to fully grasp and find solutions. P.S. If communication and understanding is missing, you are most probably on a dead ship. Be prepared to drown (evaluate your market value) and don't get emotionally involved (Danger of "burn out"). |