2 ms·
I think this is the wrong question. I think you should find better compassion for yourself. Understand why you didn't do something the way you wanted. That's
by lallysingh 7y ago
I think this is the wrong question. I think you should find better compassion for yourself. Understand why you didn't do something the way you wanted. That's useful learning about yourself, other hackers, and the software development process on general.
Are you doing work where you don't care about it's quality? Why do the work? Some part of you didn't care about the result, or didn't believe that the additional quality would actually pay off.
That's completely normal.
Understanding which one and why is honestly far more interesting than most personal software projects.
- ttul 7y agoThis was exactly my thought. When I was in my twenties, starting my first company, I hammered myself every time I failed to deliver on my TODO list. Today, I'm far more introspective. If there's something that's dying on the vine, I want to know why that thing is apparently not very important to me. Spend time figuring out what's really important and make sure your TODO list is full of those things. The unimportant stuff? Outsource it or make changes so that you don't have to have those things on your list.
- JohnFen 7y agoWell said. I'll add my personal bent on this -- if a project (paid or otherwise) really turns my gears, then I have to be careful not to have it turn into an all-consuming obsession. Caring about productivity and quality is "free" in a sense, because it's all I'm about. This is why the most important criteria I have when considering taking a job isn't pay or benefits, it's whether or not I find the work itself interesting enough. When I find myself half-assing something, it's because I'm not really interested in it. That's the time when I need to change projects/jobs, or find someone else who wants to do the parts that I clearly don't.