←back to thread

1070 points dondraper36 | 1 comments | | HN request time: 0.247s | source
Show context
logsr ◴[] No.45070339[source]
> design the best system for what your requirements actually look like right now

this is the key practical advice. when you start designing for hypothetical use cases that may never happen you are opening up an infinite scope of design complexity. setting hard specifications for what you actually need and building that simplifies the design process, at least, and if you start with that kind of mindset one can hope that it carries over to the implementation.

the simplest things always win because simple is repeatable. not every simple thing wins (many are not useful or have defects) but the winners are always simple.

replies(1): >>45070384 #
1. amelius ◴[] No.45070384[source]
> > design the best system for what your requirements actually look like right now

But don't forget to ask your manager if they want to be prepared for future scenarios A, B, or C.

And write down their answer for later reference.