Make it work, then make it good

This isn't an original thought, it's most popularily coined from the beginning of unix OS.

It comes in other verbiages - don't let perfection get in the way of making something great, etc.

this speaks to my other post about ap2m2 (value multiplier).

Identify the problem, and solve that

i regularly see people knee jerking to use the latest tool/programming language/bit of software (and i am totally guilty of this) to solve issues.

the funny thing is that often, the best approach is to use the tried and proven methods, because they work. just figure out what the problem is and solve it. trust me, it doesn't need to be flashy (though building in some sugar is always preferred, and impresses) it needs to solve the problem, and well.

you don't want to have to keep coming back to it to fix.

noone cares how flashy something is. infact you don't need people to feel anythign about it, the solution needs to work, and if people aren't talking about it, it's doing what it's supposed to in a sense.

some of the most sophisticated systems int he world (figher gets, mars rovers, etc) rely on old programming languages, because they are good.

in the spirit of business, solve the problem and crack on.

there's a cool picture about making it work first, and then making it good later.

Make it work, then make it good

https://medium.com/swlh/coding-faster-make-it-work-then-make-it-good-6aa988ebd8ab