Ask HN: Are we overcomplicating software development?
1. I think this is rather obvious, work with what you have. Maybe think about hiring specifically for areas your team is in lacking in, as long as the team as a whole will see decent benefit from it.<p>2. I hate to say you&#x27;re doing microservices &quot;wrong&quot; but I&#x27;d really question project structure and practices being the culprit behind the cost of doing devops with microservices.<p>3. This seems like an engineering fault, rather than some implicit principle behind those concepts causing more downtime.<p>4. How is CI a plaster on the problem of microservices? CI is useful with or without microservices.<p>5. Agile was always meant to be a <i>guideline</i>, not an end all and be all. It&#x27;s meant to get your team to figure out how it wants to work, and write code before process. See: <a href="http:&#x2F;&#x2F;agilemanifesto.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;agilemanifesto.org&#x2F;</a><p>The problems you are describing seem like big problems with your team, engineering and management. No amount of process and technology is ever going to fix a dysfunctional (sorry if that&#x27;s too blunt) team. What I get from this, instead of having processes in place that make it easy to move code out, you&#x27;re removing tooling to slow things down intentionally with the superficial result of &quot;stabilizing&quot; the entire development effort. The solution appears to be to get your team to write less code, and force management to bow down to the new reality of these &quot;stabilizing&quot; changes. Both of which can and sometimes should be done regardless of processes and tooling in place.<p>The best code is the code you don&#x27;t write. But don&#x27;t blame the tooling on making it easy for a team to be lazy and remove the all important characteristic of a team self-critiquing (i.e, &quot;Do we really need this feature&quot;, &quot;That&#x27;d be nice to have but right now we&#x27;re managing to get things done.&quot;, &quot;Did I actually test my code, was it reviewed, or am I just counting on the fact that I can shove something else out later while our redundancy systems pick up the slack?&quot;)