Make the first design obvious. The first PCBs were understandable with the naked eye1. (1" wires to 1 elecctron-wide wires) The same should be done with software designs. Make the obvious, malleable, and simple. Do not be concerned with performance or adaptability; these will be handled on subsequent passes.
For example, if you design includes a cache, remove that component until you are about to reach a v1 status. Adding in a cache increases complexity and could prevent you from getting to a v1 on time.
Make the first design obvious. The first PCBs were understandable with the naked eye<sup>1</sup>. (1" wires to 1 elecctron-wide wires) The same should be done with software designs. Make the obvious, malleable, and simple. Do not be concerned with performance or adaptability; these will be handled on subsequent passes.
For example, if you design includes a cache, remove that component until you are about to reach a v1 status. Adding in a cache increases complexity and could prevent you from getting to a v1 on time.
<sup>1</sup> [Learn Engineering - What is a PCB?](https://www.youtube.com/watch?v=YJr-kHy6STg)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Make the first design obvious. The first PCBs were understandable with the naked eye1. (1" wires to 1 elecctron-wide wires) The same should be done with software designs. Make the obvious, malleable, and simple. Do not be concerned with performance or adaptability; these will be handled on subsequent passes.
For example, if you design includes a cache, remove that component until you are about to reach a v1 status. Adding in a cache increases complexity and could prevent you from getting to a v1 on time.
1 Learn Engineering - What is a PCB?