Showing posts with label kanban. Show all posts
Showing posts with label kanban. Show all posts
Saturday, June 24, 2017
Sunday, February 19, 2017
Getting Better At This Coding Thing
Day 4 and 36 pomodoros in. I got stuck on writing Rspec tests, so I purchased an Rspec manual, studied it for precisely three pomodoros (black cells) and found I could write the tests I need. I have spent so far 3 x 20 minutes on study and 33 x 20 minutes on planning, writing, and coding for this exercise. The brevity of the study break excites me, because it is tangible, documented evidence that I have the intelligence, self awareness, and discipline to take a break from the main project, learn what I need, and then get back to work without wasting time.
Thursday, February 16, 2017
100 Pomodoros for the Month of February
This cycle was dominated by study (black) -- Toy Robot, Ruby documentation, 'Rails 4 in Action' -- and job seeking (red) -- lots of calls, emails, and networking at the Ruby Conference (2017) in Melbourne, Australia.
Let's see if we can make it two hundred pomodoros for the month of February.
At any rate, it's been a very productive one hundred pomodoros so far.
Let's see if we can make it two hundred pomodoros for the month of February.
At any rate, it's been a very productive one hundred pomodoros so far.
Wednesday, January 11, 2017
Progress Chart With A Twist (Or Pattern!)
My beloved helped me to create a handy stencil for my white board, with which I make a chart like this:
The chart works like this:
Black = Study, i.e reading about Ruby, learning the concepts.
Green = Code, i.e. working on code that goes to Github.
Blue = Blogging.
Red = Job search, i.e. applying for jobs, calling recruiters, etc.
This is literally a progress chart, in the sense that it represents my progress, rather than how much of a goal I have completed.
The twist of setting up the 10x10 table with a repeating pattern of four colours, instead of a neater set of coloured columns, is that gaps are unsightly. Each of these four aspects of my mission is equally important, and the discomfort of seeing an uneven distribution of filled cells induces me to turn my attention to activities I have been neglecting.
To be honest, I do not enjoy looking for work, and would much rather be busy coding and studying. Blogging isn't too bad, but coding is more fun.
Nevertheless, until I get my first gig, my job is looking for work, and so the red cells have to be filled in first.
So far, so good.
The chart works like this:
Black = Study, i.e reading about Ruby, learning the concepts.
Green = Code, i.e. working on code that goes to Github.
Blue = Blogging.
Red = Job search, i.e. applying for jobs, calling recruiters, etc.
This is literally a progress chart, in the sense that it represents my progress, rather than how much of a goal I have completed.
The twist of setting up the 10x10 table with a repeating pattern of four colours, instead of a neater set of coloured columns, is that gaps are unsightly. Each of these four aspects of my mission is equally important, and the discomfort of seeing an uneven distribution of filled cells induces me to turn my attention to activities I have been neglecting.
To be honest, I do not enjoy looking for work, and would much rather be busy coding and studying. Blogging isn't too bad, but coding is more fun.
Nevertheless, until I get my first gig, my job is looking for work, and so the red cells have to be filled in first.
So far, so good.
Friday, December 9, 2016
Thursday, December 1, 2016
Living a Kanban Life
I live a Kanban life. Every morning, I consult my Kanban whiteboard to plan my tasks for the day, and get better every day at converting what needs to be done into tasks, and working through those tasks methodically.
The major drawback of this excellent tool is that one can lose sight of the big picture.
That's where my second whiteboard comes in. I can use it for any kind of brainstorming.
At the end of a week, I take all the DONE tasks and put them up on the brainstorming board, to take stock of my work, and to give myself a wee pat on the back.

Every week I find an appreciable improvement in my use of the Kanban system.
Wednesday, November 16, 2016
Subscribe to:
Posts (Atom)
1,050 hours
It took me 13 working days to complete my first 100 "work" pomodoros as a Junior Software Tester at Profectus Group. Much of ...
-
I have finished re-writing my text adventure game, Tree House Prince, available here: ( https://github.com/clockworkpc/tree-house-prince...
-
NOTE: My fiancée wishes to stay out of the online limelight, and neither her real name nor her image shall appear in this or future posts. ...
-
It's 03:08 and I am finally starting to make sense of object-oriented programming. It's not that I didn't understand it concep...









