3 ms·
I can take my time and do my hobby code right. I can add only the feature I want to add. I can run lint with all options if I want. I can fix all the compiler w
by ryandrake 2y ago
I can take my time and do my hobby code right. I can add only the feature I want to add. I can run lint with all options if I want. I can fix all the compiler warnings. I can use asan and run valgrind to find every last memory corruption and leak. I can profile my code and speed up the hot spots. I can grind, and sand, and polish it to my heart's content until it is a beautiful work of art. And, I don't have to release it! I can take breaks when I want to, even years-long breaks, and nobody cares.
It's the total opposite environment of at-work code, where you grind through tickets you don't care about, write design docs as checkbox items rather than because they are needed, write status updates nobody reads, implement features you don't want to implement because someone's boss's boss's boss's boss wants the feature, and it's all deadlines, deadlines, deadlines. We ship on date X whether the software is high quality, barely working, or missing huge pieces. And then, after all that, it's time for the next sprint!
- Izkata 2y ago> We ship on date X whether the software is high quality, barely working, or missing huge pieces. And then, after all that, it's time for the next sprint! Or, halfway there, the project is canceled. Bonus points if they later wonder why you got so little done during that part of the year.