Comment by onebot

6 years ago

The point isn't "just start coding". The point is to focus on the product(customer development and all) and not the tools/technologies to build the product. I have seen many more focused on the latest and greatest stack instead of using the tools they are already good at.

As with most things in our field, the opposite of a bad thing is also a bad thing.

When stuff is new, people have a higher tolerance for repetitive, error prone things. For tedium. For bullshit. But over time a portion of your team will lose patience. Their allergy to bullshit will return. These are many of the same people who pull off productivity gains, hard performance fixes, who fix hard to find bugs. Who prevent whole classes of bugs. If they don’t get to fix the things that bother them, they will go somewhere where they can.

What will be left are the status quo people. If you don’t have your project in a good shape when that happens, it never will be. You will have achieved mediocrity.

If things are good and the allergic people are still pushing? At some point it’s appropriate to move on. Just make sure you know for sure things are good and aren’t just listening to feedback from the status quo folks.

  • > If you don’t have your project in a good shape when that happens, it never will be. You will have achieved mediocrity.

    But most times the alternative is not mediocrity, but no viable product at all.