3 ms·
"The application is always what I consider to be "bug free" (we all know it isn't, but let me have my happy place). If I encounter a bug, I stop all forward mov
by hutzlibu 5y ago
"The application is always what I consider to be "bug free" (we all know it isn't, but let me have my happy place). If I encounter a bug, I stop all forward movement, and fix it; even if it is a "small" bug."
I have the luxory of no manager either, but I like to move fast and not have the cost of context switch, to immediately fix every small UI bug or glitch, like I used to.
I rather keep track of them and usually wait, till I drown in warning messages - and then I take the time to properly clean up and refactor things.
I found out, this way I am more efficient. Because since I suffer from perfectionism, I would get lost in fixing and improving small things. Now I mostly ignore them and focus on the important stuff and only fix things immediately, if they are in the way.
- ChrisMarshallNY 5y agoBelieve it or not, I move very fast. In fact, I often have to stop, because the rest of the team can't catch up. A lot of that, is because I've been writing code for over 30 years, and a lot of my personal process is "muscle memory."
- hutzlibu 5y agoI see, we have to do a coding competition at some point ;) But sure, routine helps. And probably also what you are building. I am mainly working on a big project with lots of legacy code involved, that is just not right. I cannot just fix anything I come across. I would never get the priority things of my list.