Don't prematurely optimize

This morning I witnessed a developer trying to over engineer the hell out of his MVP so I would like to just write this short post as a periodic reminder of what not to do:

DO NOT:

prematurely optimize
create problems that don't exist (self sabotage)

Let the problems come to you. Then you will solve them.

I also do this 9/10 times so probably time for a next tattoo...

https://twitter.com/Web3Coach/status/1268850338725068801

Lukas Lukac

posted to

Growth

on June 5, 2020

Say something nice to Web3Coach…

Post Comment

3

This happens so easily for technical people because they LOVE building. Can't get lost in the sauce though.

roddanan

·
4 years ago
·
Reply
1. 2
  
  exactly. The problem is that sometimes we like more building than $$$$ (subconsciously) and then bad things happen.
  
  Web3Coach
  
  ·
  4 years ago
  ·
  Reply
1
I like to ask the folks I work with these three questions:
- How do you know we need that now?
- How will you know when we DO need it?
- What are we doing to make sure we're learning what we need to know to make a good decision?
andrewgassen

·
4 years ago
·
Reply
1. 1
  
  Good framework Andrew. "How do you know we need that now?" is a killer question. Will uncover so much often.
  
  Web3Coach
  
  ·
  4 years ago
  ·
  Reply