Monthly development targets
Easy to hit; but hard to set!
Today I'd like to talk about something I've been testing out that I found to be pretty rewarding.
Setting a monthly target
So I tried adapting this in technology as well, especially with Test-Driven Development (TDD) as I was having so much trouble adapting TDD in my development workflow.
- I start my month by deciding on what my focus would be for the upcoming month. (usually by going through my personal board of stuff to learn and improve)
- I print my focus of the month and hang it in a visible place. (ex: print a big TDD as a visual cue and hang it on the office walls)
- I start slow, by scratching the surface first just to break my fear. (ex: fix the next bug in a TDD fashion)
- I put a mark down on my paper each day I follow-through on my focus.
- I criticize myself if I break my habit and redo what I can while following the habit. (ex: rewrite code written without tests)
I noticed that, for me, once I followed these steps I actually got to do and learn a lot of stuff way faster than I usually do.
I've been following this method for more than 6 months now:
- I've learnt Scala
- I've learnt Kotlin
- I've started my first fully Kotlin side project, Wally
- I've started my own blog again, after a couple of years of doing nothing
- I've gotten used to writing proper TDD with Kotlin on Android
These steps are not only limited to technology, they are pretty universal if you want to build a habit of anything. (As long as you have a motive for that habit)