2 ms·
While I don't have a job per see, I once did a 30 day experiment of time-boxing and scheduling. I did 4 hours every day. So each week, I clocked 28 hours per w
by kiba 18y ago
While I don't have a job per see, I once did a 30 day experiment of time-boxing and scheduling.
I did 4 hours every day. So each week, I clocked 28 hours per week. The hours were choked full of coding effort.
Mostly, I encountered difficult obstacles that would slow me for a day or two. I couldn't just solve it siting around so I go around to coding different projects.
It was actually a little understatement. I did a programming session in the middle of the experiment when I tried to develop a game in 48 hours for a contest. By the time I finish the project, I have a hard time protoyping newer versions of the game so I got something like last place.
I did a the same thing for a week back in the beginning of April. I ended up releasing a new version of a game I made but I worked really late. Mostly it is because I procrastinate until the last minutes. So quality of life suffered due to that. So I learn to not only time-box but also schedule my time so I don't end up hacking at strange hours.
I got time management down to a few set of tools that allow me to do a lot of solid coding. I can't get much better than that.
The actual major hinderance is the fact that I am extremely slow in term of programming speed. Veteran hackers can complete trivial games even with unit tests in mere hours while it takes me days or even weeks to accomplish the same feat.