5 ms·
What's the difference between make it work and make it right? Aren't they the same thing?
by abybaddi009 1y ago
What's the difference between make it work and make it right? Aren't they the same thing?
- robertfw 1y agoMaking it work can be a hacky, tech debt laden implementation. Making it right involves refactoring/rewriting with an eye towards maintainability, testability, etc etc
- stavros 1y agoYeah, if it's not right, it doesn't work.
- darknoon 1y agoIn ML, often it does work to a degree even if it's not 100% correct. So getting it working at all is all about hacking b/c most ideas are bad and don't work. Then you'll find wins by incrementally correcting issues with the math / data / floating point precision / etc.
- DSingularity 1y agoNot true. Things can work with hacks. Your standards might consider it unacceptable to have hacks. So you can have a “make it right” stage.
- gabrielhidasy 1y agoDepends on your definition of "right" and "work". It could be a big ball of mud that always returns exactly the required response (so it 'works'), but be hellish hard change and very picky about dependencies and environment (so it's not 'right').
- stavros 1y agoNope, it's right, but it's not pretty.
- deleted 1y ago[deleted]
- gopalv 1y ago> make it work and make it right? My mentor used say it is the difference between a screw and glue. You can glue some things together and prove that it works, but eventually you learn that anytime you had to break something to fix it, you should've used a screw. It is trade off in coupling - the glue binds tightly over the entire surface but a screw concentrates the loads, so needs maintenance to stay tight. You only really know which is "right" it if you test it to destruction. All of that advice is probably sounding date now, even in material science the glue might be winning (see the Tesla bumper or Lotus Elise bonding videos - every screw is extra grams).