Agile Otter Blog

Tim Ottinger's thoughts on Software Development.

Monday, March 3, 2025

There is No Automatic Reset for Engineering

›
Do you remember all those rushed changes that your developers implemented three years ago, and how they complained about the design damage t...
Tuesday, February 11, 2025

Pair Programming Listicle

›
There are many ways to collaborate, and pair programming is the first many people consider.  It's a useful practice, though it can be e...
Wednesday, December 11, 2024

Irresponsibility: Estimates and NoEstimates

›
Sometimes the argument is made that not estimating is irresponsible . I understand why people say it. I don't necessarily agree. It is...
Tuesday, August 6, 2024

Basic Microphone Usage

›
How to use  microphones (pay special attention to (3) and (12)!!!! : NEVER NEVER NEVER point your microphone at a speaker. Not even accident...
1 comment:
Friday, May 24, 2024

Profitable Struggle and Unprofitable Struggle

›
Imagine I have to work in an unfamiliar and tough passage of code. Unprofitable Code I spend time and effort to puzzle it out, and all I get...
2 comments:
Tuesday, February 27, 2024

Definition-by-Dysfunction

›
 I've done it. You've seen me. You've done it. I watched you do it. We've probably argued about it. The Defining Dysfunction...
1 comment:

Listicle on Flow and Teamwork

›
Some article links related to solo vs group, flow, productivity, and predictability. Stop using Per-Person Swimlanes Swarming Pitfalls of so...
1 comment:
›
Home
View web version

About Me

Agileotter
View my complete profile
Powered by Blogger.