31–40 of 49 posts
I thought this was going to be about someone meticulously doing git commits after every tiny little change.
That's actually a really good way to 1) be known for hustle 2) be known as a finisher 3) work on mostly cool stuff.
There is no shortage of awesome possible work. Ever.
I thought this was going to be about someone meticulously doing git commits after every tiny little change.
Without commit messages.
Boy, did I pay for that one.
I thought this was going to be about someone meticulously doing git commits after every tiny little change.
People say finishing is everything, and they are right, but like most skills finishing is not binary "yes" or "no", once you can finish things you can progress to being able to finish them better, faster and with less code. Ironically, owing to the nature of learning and the human brain in general you will have a hard time improving your finishing skills unless you regularly wind up in the situation where it is very difficult, or impossible to finish.
After all, I developed a small app for myself, I hope it would help you while you're doing your side project ( I try to not sound like I'm doing advertising for my project... since it's free of charge, feel free to use it and give me some feedback if you like ).
www.vodolist.com is what I come up while I was still employed at my old employer. What I could do with this app is that, I decided to do only "3 tasks" for my side project. ( and only 1 task for some other smaller project. you can customize it ). With only a few tasks involved each day, I can force myself only work on the important and only crucial components of my side project.
This post gets a little long with the help of scotch so I guess I'll just stop here for now.
I am not completely cured of the habit, but what helped me with this -- and more importantly, what helped me actually begin finishing things -- is simply being very careful to only talk about what I've done, not what I'm working on or what I'm planning.
There's this thing called "substitute for completion" where if you talk about some project, even one with hundreds of hours of work remaining, your brain gets the same reward as actually completing it. A smaller dose, perhaps, but essentially the same thing. So your brain figures out that it can just keep coming up with new ideas and telling people about them and it will get an echo of the same feeling of accomplishment as actually doing it, without the hard work.
So what seems to work for me is only talking about my projects in the past tense. When I want to say "I started a new game last week and it's going to be the most awesome augmented reality zombie squirter ever", instead I say, "I wrote a new game event system last week and it turned out pretty good," because that's as far as I got. It's also motivating because I can't wait to tell people about all the cool stuff I have planned, but I have to wait until I actually do it.
I put out a second beta of my current project on TestFlight yesterday. It was a good feeling. It's been a ton of hard work so far. But it's not in the app store yet, so I'm not going to post about it until it is.
At first when I saw this headline and that the source was github I thought it meant making too many commits in git. I couldn't figure out why that would be such a bad thing.
All I could think of was making it difficult to find exactly what commit fixed/introduced what bugs.
I can't agree more. I used to work for a company that develops smartphones that still holds top 3 market share in US. The day-to-day work is eating up all my time. When I'm developing my own project, I never seem to accomplish anything. I planned out some huge tasks for myself each night and I was so determined to finish them all, but it all ends up with losing the focus. After all, I developed a small app for myself…