Here are the stagnations I have experienced in my career: * An area of development where most of the programmers cannot program * Fear of automation from non

Here are the stagnations I have experienced in my career: * An area of development where most of the programmers cannot program * Fear of automation from non developers The first of these is tough because the only real solution is to change your line of work to something else. When you are surrounded by pretend developers confidence will be universally low. The problem with being that guy that can actually program means you are the enemy 80% of the time because the low confidence people fear being exposed more than anything else. As someone that can program you must intentionally waste your time to prove your compatibility to your peers or alienate your peers with original solutions. To solve for that I switched from web development to something different. In the different line of work I achieved early promotion by unintentionally demonstrating confidence, delivering rapidly, and trying to not do work. The second of my stagnations occurs when you can program but are surrounded by people that are not programmers. For me the only purpose of software is automation, the elimination of human work, but manual labor is means of participation for non developers. There is also a fear of ownership and solution maintenance by the non programmers. To solve for that you need some level of managerial title and use that title to impose direction. Yes, that means being a people manager and writing your own software. The solution isn’t your wonderful software creation but how you use it to solve business problems and achieve inclusion from the non programmers.