docondev.com
Messy Code is not Technical Debt — DocOnDev
http://docondev.com/2009/08/messy-code-is-not-technical-debt.html
August 31, 2009. Messy Code is not Technical Debt. August 31, 2009. Technical Debt is a common topic these days. How is it incurred? How should we track it? When should we pay it down? It is a metaphor commonly understood. Our customers get it. While they may not like it, they do understand. Technical Debt is incurred today and needs to be paid down; preferably sooner rather than later what with compound interest and all that. And Messy Code is not Technical Debt. What is Technical Debt? Doing things the...
docondev.com
Organizational Motivators: Autonomy, Connection, and Excellence. — DocOnDev
http://docondev.com/2015/07/autonomy-connection-excellence.html
July 4, 2015. Organizational Motivators: Autonomy, Connection, and Excellence. July 4, 2015. Organizational Motivators: Autonomy, Connection, and Excellence. July 4, 2015. I think I saw Daniel Pink's TED Talk on " The Puzzle of Motivation. Account to see what books I was reading. Unfortunately, there is no easy way to share all of the scientific articles and other sources I also consumed. During the time period when I was reading this material, Daniel Pink's " Drive. As pertains to the individual, autono...
docondev.com
Fist to Five — DocOnDev
http://docondev.com/2013/12/fist-to-five.html
December 10, 2013. December 10, 2013. Clear, binary options. The Fist to Five process works best for clear, binary choices. Should we use git? Works just fine. It is a relatively clear mostly yes or no question. Which do you prefer - git, mercurial, or SVN? Doesn’t work well. Too many options. Would you like cake? Is also not a great option. One option, but too vague. Would you like chocolate cake with strawberry frosting? All 3 and above, the proposal is passed. Move on. Forever Forward, Reprise.
docondev.com
Stabilizing Velocity — DocOnDev
http://docondev.com/2011/03/stabilizing-velocity.html
March 10, 2011. March 10, 2011. March 10, 2011. Have you ever been on a team where your velocity suffered wild variances? Maybe you ended up using a running average instead of yesterday's weather? Have you heard phrases like, "Well, our velocity last iteration was 3, but our average is still 22"? Have you ever heard the phrase, "Dude, we need to get this velocity stable.". Have you worked on teams where they took partial credit for done at the end of the iteration? But what if velocity doesn't stabilize?
docondev.com
The Three "R"s of Clean Code — DocOnDev
http://docondev.com/2010/12/three-rs-of-clean-code.html
December 2, 2010. The Three "R"s of Clean Code. December 2, 2010. The Three "R"s of Clean Code. December 2, 2010. Establishing Code Quality Standards. There was a good deal of discussion around people's historic failure to read and follow this type of documentation. Such failure to comply mandated policing. There were a number of possible solutions; training, financial incentives, managerial targets, code reviews, code audits, and code compliance tools. Ummm, yeah. Don't do that. Ok? This kind of governa...
docondev.com
The Love Contagion — DocOnDev
http://docondev.com/2014/06/the-love-contagion.html
June 28, 2014. June 28, 2014. June 28, 2014. We have an application internal to Groupon called the "Love Monster". It was written, in large part by Devin Breen. There are other contributors, but Devin is the one that made it happen. He didn't do it because it was on a roadmap or because it's part of our quarterly objectives. He did it because he and others wanted something like this to exist. So he willed it into existence. The science on appreciation. Let's Start an Epidemic by Doc Norton.
docondev.com
One on One Meetings — DocOnDev
http://docondev.com/2013/03/one-on-one-meetings.html
March 24, 2013. One on One Meetings. March 24, 2013. About 15 years ago, I started a simple practice with my fellow co-workers and employees. Every so often, we'd meet to discuss stuff and things. Nothing too formal, just a touch-point to make sure we were staying connected. I called the sessions "touch-point meetings". Over time, I made adjustments to the format of the meeting as various structures proved more or less valuable. One on One is about them, not you. This is not a status report. Don't ask fo...
docondev.com
Collaboration Contract (was Collaboration 8) — DocOnDev
http://docondev.com/2012/11/collaboration-contract-was.html
November 21, 2012. Collaboration Contract (was Collaboration 8). November 21, 2012. Back in April, I wrote about a practice we were experimenting with at LeanDog. I called it Collaboration 8. Has been a tremendous boon to the self-organizing teams to whom I've introduced the concepts. As I've been practicing Collaboration 8, I've learned from real-world situations and the practice is beginning to evolve. When we first created the system, we borrowed a great deal from Delegation Poker. Which are all steep...
docondev.com
Shaping culture through inaction — DocOnDev
http://docondev.com/2014/07/shaping-culture-through-inaction.html
July 4, 2014. Shaping culture through inaction. July 4, 2014. Shaping culture through inaction. July 4, 2014. I follow Dan Rockwell on twitter. His handle is @leadershipfreak. And he tweets quite a bit of good leadership content. If you don't follow him, I recommend you give him a look. Dan sent a tweet out about how reinforcing behaviors builds organizational culture. Behaviors you model, affirm, and reward build organizational culture. Dan Rockwell (@Leadershipfreak) July 4, 2014. Is available at CTO2.
docondev.com
Good Software — DocOnDev
http://docondev.com/2015/07/good-software.html
July 23, 2015. July 23, 2015. I saw a tweet this morning that caught me off-guard. If your software makes money it is good software by definition. Nothing else matters. #Agile. AgileFortune (@AgileFortune) July 23, 2015. It doesn't strike me as consistent with the type of thing AgileFortune. Usually tweets. My initial reaction was to reply via twitter, but didn't feel I could express my thoughts well in 140 characters or less. And by extension what is "good" software? Other aspect of "goodness". Let's lo...
SOCIAL ENGAGEMENT