Agile Otter Blog

WARNING: the blogger "WYSIWYG" editor is really not very good about the "WYSIWYG" bit... so this article looks great in the editor but is a real crapshow in the actual post. I'm fixing it. Be kind, and bear with me. In our eLearning , we publish problems and solutions. Sometimes people contribute other solutions and we show those as well. Today's sample comes from our Test-Driven Development album. Geepaw hill tells us "everything matters" -- so today I'm going to nitpick at something that (in this case) is tiny and you might consider it insignificant. So be it. But just the same, I would like to introduce you to a process that can improve your code and design in ways subtle and profound. In this case, it stays a little to the subtle side, but that's okay for a blog. Here is a source code example: AreEqualWithPrecision(PhoneBill.calculateRate(PhoneBill.GOLD, 900, 1), 49.95); AreEqualWithPrecision(PhoneBill.calculateRate(P...

I came across an interesting article the other day, stating: EXPECTATION – OBSERVATION = FRUSTRATION I think this is really good. However, I think there should be more emphasis on spoken v. unspoken expectations, and then on agreements instead of expectations.  Also, the refusal to adjust expectations out of compassion and respect for others is poison. via GIPHY And yet, people are quick to judge the behavior of others rather than to approach surprises with curiosity . A lot of disappointments don't need to be upsets.  People judging situations scream "this is wrong" instead of "how fascinating!" We refer to the difference between expectations and actual behaviors as a " curiosity space ." It is where most of our learning takes place. One of my friends described it as a "cache miss" which is helpful to readers who are engineers or software developers (or both).  So, here, to help us understand, is my quick guide...