# Community
Recently in our Discord server, an interesting discussion sparked around a video by Dave Farley about critical warning signs in software projects.
Here are a few red flags that stood out:
🚩 Rigid planning – Overplanning makes teams resistant to change, even when it’s obvious the plan isn’t working.
🚩 The “hero developer” trap – Relying on a few rock stars instead of building resilient teams.
🚩 Big risky changes – Instead of “Many More Much Smaller Steps” (MMMSS), teams often take big leaps that increase failure rates.
🚩 Strict control policies – Some teams require approval just to add a new class! This often happens in large companies with poor encapsulation, where changing one system risks breaking everything.
These discussions remind me how good software design can mitigate many of these issues. Functional programming, strong modularization, and clear feedback loops can help avoid these pitfalls.
👉 Have you ever worked in a team where even adding a class required approval? How did it impact productivity? Join the conversation in our Discord server and share your thoughts!