Hi everyone! Starting my first blog post here!
My name is Matt, I joined Habitica about a year into my first job.
I work as a tester by profession and have found many ways of using Habitica to support my role as a tester and feeding back into the community. I use To-Dos to research specific pieces of work, maybe learning a new tool, and use dailies to keep on top of my reading such as, read 3 pocket articles (this one is currently coloured red yikes!).
Because Habitica lends itself so nicely to the scrum (or sometimes Kanban) ways of working, I think it has an excellent way of working with the IT industry. I don't really know if this is what inspired some of the core aspects of Habitica, but either way it works!
Recently I added a new section to the Self Imposed Challenges: http://habitica.wikia.com/wiki/Self-Imposed_Challenges
Forget Me Not - Clearing Those Lingering To-Dos
The inspiration for this methodology (you guessed it) came from the Scrum way of working. In this way of working, you declare upfront what you want to accomplish within a given time period. Once you identify the tasks, nothing else can be added. So this means if you have "take out trash" as a todo and also "research that cool API", until you have cleared down your declared list of to-dos, including take out the trash! You cannot research the cool API. Its easy to get caught up in Habitica thinking, all productivity is good productivity, but task swapping too frequently can actually be destructive to your productivity. This is whay I feel scrum and Habitica just make sense to really take out a lot of tenuous tasks!