I recently started a blog to collect the ideas of my mind, it will share my experience, work as a reference, act as my thoughts archives for future, and getting involved in community. Thus more people reading my blog will make the efforts productive.
Before going that much further the blog must be decently user friendly.The theme I use earlier was Spun Theme, my idea was all the recent blog will be displayed on the home page. Thus helping any reader to choose the topic. So recently I pushed it to 2 of my friends Ritesh Haria & Gautam Shah. Both have noticed some basic remarks.
Observation by Ritesh Haria : The links in the page was not visible clearly, on mouse over the color of the link change is not noticeable.
Observation by Gautam Shah : The main idea of displaying all blog on home page was not visible correctly on Gautam’s machine, which was justifiable.
So anyone has an observation please feel free to put in the comments. Thus this post will help new bloggers.
On 11th January 2014, I thought of a kind of debt we keep living with through out the life which is work. I thought of coining it as “Working Debt”. I tweeted it when it was fresh in my mind @ twitter
#WorkingDebt When you don’t follow clean code, design principles, adaptive practice & leadership get slogged at work.
The Idea here is that when we do a shabby work and don’t plan what do we want to work on, in future. We end up cleaning our own mess and fire fighting at work. This might sound Philosophical but haven’t you felt lately why don’t this day just finish at work, How am I going to face my boss, How will the client demo go? When will this project end and many more such feelings.
Shouldn’t our work be well orchestrated, our team working like a unit with common team goals. Shouldn’t we feel like we are driving a Ferrari in autopilot mode.
So the idea I am trying hard to explain here is when we don’t systematically conduct our self as a Software Craftsmanship we add on to our debt of working days ahead.
We must really understand the ways through which we can make a quality software, increase the standards of our professional life. Thus making difference to the world and people around us. Our life must become a accumulation of working practices assets. Thus making our life stress free, financially free and work free.
I thought about doing a Pair Programming Dojo with a friend outside my work, Gautam Shah. I checked with him and he was ready. I just started to write an email then suddenly I remember the talk by Scott Hanselman @ here. He mentioned when the technical email goes beyond 5 lines then write it on your blog so that in future you don’t have to write them again.
Inspiration for our Dojo:
Problem set taken from Roy Osherove: String Calculator
TDD Code Kata by Andy Mehalick : @ vimeo
TDD Rules from Uncle Bob (Robert C. Martin) : 3 Rules of TDD
Pair Programing steps :
- Driver writes a Test while Navigator observes it.
- Driver passes the keyboard to Navigator to write production code.
- Switch of Role: Navigator becomes Driver and other way around.
- Driver now write the production code and fix the failing test.
- Repeat Step 1 through 4 until problem set is solved.
- Take break every 25 minutes for 10 minutes.