13
6 Comments

A quick reminder to all the builders...

8 questions to ask BEFORE writing code:

• What is it?
• When does it ship?
• How do we iterate?
• What problem is it solving?
• Who are we building it for?
• What does a solution look like?
• How do we know worth solving?
• How do we know we’ve solved it?

As much as we love to write code, a product must solve a customer's problem.

on September 11, 2022
  1. 1

    Big fan of this engineering approach. Lots of tech founders or executives or MBAs actually are just BS specialists without the ability to back it up...

    At the same time, sometimes we do need to think beyond and use our imagination... it's a complex world

  2. 1

    As Uncle Bob ( Robert Cecil Martin) stated in his Clean Architecture book, ''the code is still just an assemblage of sequence, selection, and iteration''. These 8 questions are useful to solve problems we face daily. Thanks for the summarizing all together!

  3. 1

    • What problem is it solving?
    • Who are we building it for?

    I especially like: "Is it a problem WORTH solving?"

    So many IH'ers just build, build, build but neglect market research. The market will tell you what to build and if it's worthwhile.

    Where? Simply by looking at reviews. It's insanely easy, but for some reason people just build, build, build.

    Great post!

  4. 1

    Great advice, thanks for posting!

  5. 1

    These are quite useful. Saving it man. thanks a lot