Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
LLAMS38054yFirst make it work, then make it right, then make it fast, then make it small.
I only realized that yesterday.
Or: Avoid premature optimization
I don't always agree. For me it's often:
1. Make it work
2. No time here is a new project..
palonE2534yDepends. I just try to make it modular af (many independent functions) that then are easy to optimize.
Brolls32394yThis is a fine line.
If you can do something right to start then do, even if it’s the second or third iteration.
I usually do a rough, disgusting version and then refine over a day or two.
Premature optimisation is an issue when you spend all your time on it and not building shit.
But similarly, getting it done and then delivering it tends to lead to project managers getting you to move on, and then you’ve got a lovely case of technical debt on your hands.
I think that with experience, you tend to cultivate habits that let you write better code on the first pass, which reduces the amount of refactoring. But if you ever get so good that you write perfect code first time around and don't need to review and refactor then you'll be kidding yourself.
CowboyBebop16"Don't give your 100%. Never. Once you gave, managers will start expecting more than that." - My mentor.
linuswillner15(Q: How much are you allowed to Google as a developer?) “You’re allowed to Google as much as you want. Th...
ripbit18Never delete code immediately. Always comment it out first.