Agile Otter Blog

This is just a little bash script for those times when you know what you want to change, but aren't sure where it is in the directory. fixwhere() {     files=$(grep -ril "${1}" *)     if [ -n "$files" ]; then         vim +/"${1}" ${files}     else         echo "not found: [${1}]"     fi } I use this whenever I have a bunch of text files. It's especially handy when you're working with a markup language. I specifically wrote it to use ' vim ' and the  +/pattern function.  I don't actually know a good way to have it load any ${EDITOR} you use and search for the pattern in that editor. I suppose if the time comes and I need to generalize, I will write a load_search_and_edit () function. For now, it works for me and makes me happy. Cheers.

I write a lot about velocity because people ask me a lot of questions about it.  Here are links to the write-ups I reference most in my daily work -- which I tend to associate to "the things most people need to know." Velocity: Kent Beck's Recommendation 14 Weird Observations About Velocity "Managing" Velocity How to Use Story Points Stop Using Story Points No Estimates Esther Derby answers " Why Not Use Velocity as an Agile Metric ?" Ten part Q and A on Velocity blog series Harmful Metrics What SHOULD we measure then? I hope it's helpful.   A friend published a blog at Industrial Logic on Value-Based OKRs . I wonder if "objective-based" or "initiative-based" is a better term.  I'm not sure what my opinion is here, and I lack experience with them, but I provide the link in case it is helpful to you.