M&M Colors: ‘The Red Scare’
I love the way these guys convince you to sign up. ‘Less than your lunch’ and then why not save 20%? The small size of the boxes helps to make signing up less of a big deal.
The way we dealt with this complexity was by pushing the burden of knowledge onto a few experts within the company. These folks distilled customer desires into features and wrote up a implementation plans. When they vetted this with the others on the business-side, they gave what amounted to a very specific todo list to engineering.
This is harmful because, as a business, you’re trying to hire the best and brightest folks across your organization. By not allowing your employees to operate on the same data across the organization, you breed a culture of assembly-line workers: folks who don’t ask questions, just do what they’re told. This is not what you want the best and brightest to be doing!
The key behind solving this issue is sharing the whys behind decision. By coloring in some of the context around why a feature is necessary, you allow lateral thinking among your employees. If I, as an engineer, can accomplish the same “why” for a given story but with dramatically less work than the proposed implementation plan, that’s better for everyone involved.
This talk is bloody fantastic for anyone working in sofrware development, but particularly for anyone in a big organisation.
Broken windows are the reason most large software projects suck to work on. A little technical debt here, a few shortcuts there, and pretty soon you’ve got a codebase so full of broken windows that no one even cares if they throw another pile of broken glass on the heap.
But just as broken windows are contagious, so is a dedication to quality. Carve out a little piece of a messy codebase and clean it up. Sharpen the edges, polish the surface and make it shine.