My Rubber Duck
In software engineering, there is a best practice called rubber duck debugging. This practice involves explaining every line of code you write to a rubber duck, specifically explaining what that line of code does and why it works. This practice works because it forces a developer to articulate her/his thoughts, which forces that developer to think critically about each line of code. Without the duck, the developer mindlessly writes code, which she/he always thinks will work. The duck never responds, but its the act of explaning the thoughts inside a developers head that forces that developer to challenge her/his own assumptions and beliefs. This blog is my rubber duck.