> Being right is good, but being quick is necessary.
This is a hard-earned lesson for me. Just after I graduated and started my first position as a software engineer, I was keen to bring in math (which was most of my studies) to solve problems. I got into academic discussions around speed and efficiency, only to realize that an okay-ish solution took a day to implement while my ideas were still on paper.
Sometimes speed and efficiency are essential, but for most apps most of us will build, whatever you have is probably OK.
Reminds me of what Reid Hoffman said: "If you're not embarrassed by the first version of your product, you've launched too late." Speed is a choice, and speed matters.
> Being right is good, but being quick is necessary.
This is a hard-earned lesson for me. Just after I graduated and started my first position as a software engineer, I was keen to bring in math (which was most of my studies) to solve problems. I got into academic discussions around speed and efficiency, only to realize that an okay-ish solution took a day to implement while my ideas were still on paper.
Sometimes speed and efficiency are essential, but for most apps most of us will build, whatever you have is probably OK.
Reminds me of what Reid Hoffman said: "If you're not embarrassed by the first version of your product, you've launched too late." Speed is a choice, and speed matters.