Progressive Development

Zany Adventures in Software Engineering with Maven and Motley

Browse by Tags

Tagged Content List
  • Blog Post: Motley says: "Affinity exercises? How do I work that sideways "8" into brainstorming?"

    Summary Motley: Affinity exercises? How do I work that sideways "8" into design brainstorming? Maven: Use affinity exercises for generating lots of ideas and prioritizing them. Define the topic, generate ideas, categorize, discuss, prioritize using dot voting, add up the votes, and create...
  • Blog Post: Motley says: "Checklist? We don't need no stinking checklist!"

    Summary Motley: Checklist? We don't need no stinking checklist! Checklists are for anal people with short memories. Maven: Checklists are very useful for activities like code reviews, where it is difficult to remember everything we need to look for. Good checklists are short, consistent,...
  • Blog Post: Motley says: "Ugh, not again..."

    Summary Motley: Developers keep making the same mistakes over and over. Can't they learn?!? Some kind of punishment is in order, like no more free soda! Maven: Don't just address the symptom - get to the root cause of a problem. Leverage the "Five Why's" to find root cause and come up with...
  • Blog Post: Motley says: "I just get picked on when my code is reviewed"

    Summary Motley: I'm not sold on this inspection thing. There were too many problems during our session. Plus, everyone just picks on the author and they hate having their code reviewed. Back to informal peer reviews for me. Maven: Follow inspection best practices: inspect limited amounts...
  • Blog Post: Motley says: "Inspections suck... time that is"

    Summary Motley: Inspections seem a bit heavy. They suck up too much time for little gain. Maven: Inspections are actually a fairly light-weight structured process that find more issues compared to ad-hoc peer reviews and team reviews. ______________________________ [Context: Maven...
  • Blog Post: Motley says: "Quick peer reviews are sufficient. Team reviews? Waste of time."

    Summary Motley: Quick ad-hoc peer reviews are sufficient to nail bugs early in the development cycle. Maven: A more structured team-based code review process can lead to more issues found. ______________________________ [Context: Maven overhears a code review that is happening in...
Page 1 of 1 (6 items)