I think I know why you can't hire engineers right now
Frankly, it&#x27;s always hard to hire engineers. Either you can&#x27;t find talent or you can&#x27;t find money to hire talent.<p>No matter what the personal choices and predilections of any engineer, the software industry is fundamentally constrained by the twin forces of capital and engineering talent. When there is lots of capital, there are a lot of companies, and there is insufficient talent. When there isn&#x27;t a lot of capital, no one can nor wants to pay for talent so they can weather the storm. That&#x27;s been the case since at least the 1970s.<p>Through this cycle, there are so many &quot;engineers&quot; working tirelessly to put other &quot;programmers&quot; out of work (not the shift in labels there, because there is always an unjustified scent of snideness in the air) as well to reduce the cost of engineering. All the no-code revolution now is part of this cycle.<p>There&#x27;s a wonderful book angling for a Marxist revolution of engineers from 1977<p>Kraft, 1977. Programmers and Managers. The Routinization of Computer Programming.<p>I love it because it&#x27;s cute, and since it&#x27;s 2022, proven to be a dud. Like any Marxist analysis, it is accurate in assessing the problems and hopeless at prescribing a solution.<p>Regardless, the main lesson I have taken in my career is the absolutely top priority a senior engineer should have is building tools and processes to eliminate the need for code to generate business results. You will never be able to hire warm bodies fast enough, so all you can do is radically increase the power of each engineer on the team.<p>Those have always been the most fun teams I&#x27;ve worked on. It almost feels like being a wizard.<p>p.s. All that being said, I&#x27;m hiring. :)