I found the blog of Miško Hevery last week; he is an Agile Coach at Googe. Scanning his recent posts, he seemed to capture many of my own thoughts, saving me the time of actually having to put them into words! Please check out his posts, topics range from testability, to dependency injection, to Changing Developer Behavior(1)(2).
His blogroll lead me to some other great sites: The Agile Buddy and Agile Journal. I have yet to read these two posts, but they really grabbed my attention:
I’m sure that I will enjoy this read, as the second paragraph of the Requirements Come Second post states that making the development environment more effective should be the first priority. I have been a huge advocate of creating an effective development within teams for a long time. I typically feel that I’m on an island by myself, as most people don’t really care what or how something gets done, as long as the date is not missed. Just getting it done has never been good enough for me. Obviously, projects have to get done or none of us would have jobs. So the question is, why can’t we get the project and and do the right thing? Hopefully, there will be some good wisdom in the post! Enjoy.
