Brian BucklewApr 8, 2024
at this point im so old im not even hacking together a shoddy wordpress plugin for this project im just learning how to do it all correctly and securely building a nice controller pattern for it and using all the built in API tech god have mercy on my soul
mikoApr 8, 2024
Show threadBrian Bucklew

tiny young programmer: do it right because it's the right thing to do

big brain old programmer: do it quickly so it works

extremely ancient programmer: do it right cause what else is there to do really

Apr 8, 2024 at 4:30amWeb
Show threadRandom Geek in limboApr 8, 2024
@unormal might as well do it right or close to right, so you have a better understanding how to fix the inevitable bugs.
Show threadww 🩶Apr 8, 2024
@unormal do it right because no, it's not going to be replaced next month, in fact it's gonna run for the next 7 years, and each time something breaks you'll have to go into the database and manually fix the inconsistencies. the first time it'll seem easier to just do that and go home. but the fifth time you do it you'll realize that it would've saved you 8.5 hours to just do it right from the start. and then you'll remember each time something like this happened in the past and realize that you coulda spent over 500 hours in total doing something fun instead of writing one-off sql queries, but now it's too late, nothing can bring that time back.
Show threadBrian BucklewApr 8, 2024
@ww literally some of my code that I wrote at 18 is still running 27 years later on very important systems lol and lmao
Show threademailgeekApr 8, 2024
@unormal @ww this
Show threadMachine Lord ZeroApr 8, 2024
@unormal Do it right 'cause that quick hack that'll only be until a proper fix is made will still be there when it's time for your children to update the code
Show threadAlex GordienkoApr 8, 2024
@unormal first thing to do is to find as many ways as possible to not do anything!