Clojurians Log v2

Yes, seen this quite a bit. This bad management habit is mutually reinforcing with the bad engineering habit of doing excessive theory-crafting during requirements analysis without any hands-on prototyping and experimentation. When managers notice some team members doing this, they can become concerned about how much time might be getting wasted on academic discussion instead of building stuff and may respond by pushing the entire team or org to be more iterative, which in practice can be an over-correction towards cutting out analysis altogether. When engineers see the results of this by suffering through projects that balloon in scope and timeline due to a refusal to plan in advance at all, they may overreact by insisting on doing detailed planning up front, etc. In my opinion good planning is also iterative - it involves multiple phases of analysis, discussion, prototyping and implementation throughout the project rather than strictly in sequence as separate phases

100%. It can be good or it can be pathological to start exploring an idea space by going off and making something without discussing a firm plan or doing a rigorous requirements analysis. That said...I've worked for people who consider "plan" a dirty word 🤣

Here's how you trip them up - tell them you need to plan HOW to reach your final goal while delivering iteratively