On writing specs: I disagree with this. I believe the author left that out because writing 'good' specs is inconsequential. I used to think I had to write goo

On writing specs: I disagree with this. I believe the author left that out because writing 'good' specs is inconsequential. I used to think I had to write good specs, but then I realized that I was better off spending time with the team to make sure they understood the motivation behind making a change. If an organization told me that I was gonna be writing specs - I wouldn't want to work there. It's a waste of time. In brief: it's a waste of time because it assumes that one knows all the variables when creating something. If you are truly creating something, then by definition it's not be done before; thus, no one can know all the consequences of implementation. You're better off having an open mind and be quick to experiment and learn.