Simple: I don't quit while in the middle of working on a piece of code.
It's more of an obsession, really. If there is a part that is incomplete, I can't focus on anything else, or even sleep unless it's been resolved.
By the time I do give up, the code is either complete to a point that the bare essentials are in place, or if I'm working on a really long script, there is a exit or a return statement that marks "everything in the script is working up to this point".
Any "non-essential functions" that are incomplete but can be ignored while testing and prototyping (such as special character escaping, allowing for arguments instead of hard-coded testing values) are left empty and marked with a //TODO comment.
Does this mean that I'm sometimes up until 4 a.m. getting a non-essential piece of code to a stable point? Yes.
Is it healthy behavior that I recommend for other developers? Probably not. But it works for me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Simple: I don't quit while in the middle of working on a piece of code.
It's more of an obsession, really. If there is a part that is incomplete, I can't focus on anything else, or even sleep unless it's been resolved.
By the time I do give up, the code is either complete to a point that the bare essentials are in place, or if I'm working on a really long script, there is a
exitor areturnstatement that marks "everything in the script is working up to this point".Any "non-essential functions" that are incomplete but can be ignored while testing and prototyping (such as special character escaping, allowing for arguments instead of hard-coded testing values) are left empty and marked with a
//TODOcomment.