Skip to main content

Initial Post: Why Blog?


I wanted to live deliberately, I wanted to live deep and suck out all the marrow of life, to put to rout all that was not life, and not when I had come to die discover that I had not lived.  Henry David Thoreau


Why write a web log?  I am beginning a deliberate process to take my skills as a software developer to a higher level.  I am not sure exactly what that higher level will be, perhaps I will explore that idea as part of this blog, but I have become discontented with the way in which my career has seemed to meander and stagnate.

I intend this to be a journal in the classic sense, a convenient place to capture and reflect on my thoughts and experiences.  I am making it a public blog in case others happen to find my thoughts helpful or interesting, however I have no expectations or goals to establish an audience or following.  My primary aim is to chronicle my journey as a software developer for myself.


Comments

Post a Comment

Popular posts from this blog

Managing for Motivation Not Efficiency

Beginning in the era of the industrial revolution, managers were trained and encouraged to focus on increasing productivity though increased efficiency.  This trend has continued into modern management with techniques such as Total Quality Management that focus on identifying and eliminating waste in a system. It can't be denied that this approach can be very effective when applied to a consistent, repeatable process like a manufacturing assembly line.  However, this focus on efficiency is inappropriate and even detrimental  when applied to creative, problem solving activities like software development, and unfortunately these lessons learned from manufacturing dominate the way software development is organized and managed.  It even influences some of the practices taught under the banner of Agile. This fallacy, that software development can be organized into consistently repeatable processes, was the assumption of the waterfall methodology.  Software developm...
Post a Comment
Read more

20 Reasons Why the Traditional Performance Review For Software Developers is Bad For Business

1. Undermines Teamwork Teamwork suffers when your incentive system primarily recognizes individual achievement. Collaboration is key to producing quality software. 2. Undermines Autonomy & Purpose Feeling like you're performing to get a carrot (raise or promotion) or avoid a stick (termination) undermines an individual's sense of autonomy and purpose which is strongly tied to intrinsically motivated behavior. It is critical to have intrinsically motivated people in creative problem-solving jobs like software development.  (See previous posts) . 3. Damages Trust Between Manager and Subordinate It reinforces the idea that the manager's role is primarily to evaluate and critique. Instead of being on the same team working toward common goals, the performance review clearly places the manager and subordinate in antagonistic roles on opposites sides of the table.  It reinforces the worst boss stereotypes. 4. Not Objective No one has found a good way to quantify a so...
1 comment
Read more