This industry already has a huge problem with prioritizing shiny new features over fixing bugs, improving performance, verifying correctness, etc. This seems li

This industry already has a huge problem with prioritizing shiny new features over fixing bugs, improving performance, verifying correctness, etc. This seems like a great way to enshrine that into your company culture. Team A: Added a wizzbazz button that says "Wizz!" when you push it with a cool noise! Look at this cool screenshot! Team B: Worked on fixing an elusive bug causing rare data corruption, but couldn't figure out what was causing it. Team A: Re-colored the header to the CEO's favorite color! Look at this cool screenshot! Team B: Fixed bug causing rare data corruption. Started looking into strange performance bottlenecks in UI. Team A: Added spiffy animations that play every time the user goes to the next page. Watch this cool video! Team B: Improved page responsiveness issue introduced by the wizzbazz button. Look at this graph; pay attention to the ninetieth-percentile time-to-first-render (dotted blue line) for dashboard users. It does actually go down quite a bit if you look. Team A: Added a thousand lines of code to the fluxborg module! Look at this graph! It went from FIFTY lines of code to a THOUSAND lines of code! Look at how much that is on this graph! Team B: Removed two thousand unnecessary lines of code from the wizzbazz module. We decided not to show a graph because the line goes down and we know you'll all think that's a bad thing. Which team is getting the axe when it comes time to lay off employees? You know. Come on. You know it's Team B. You know it's true.