kaksles.org

errordriven.blogspot.com

Error-Driven Development: July 2006

http://errordriven.blogspot.com/2006_07_01_archive.html

Moving from cowboy coding to agile development. Wednesday, July 26, 2006. Although I think I have been doing too much reading (both books and blog posts) and too little actual development work, I am happy I kept reading and came across a link in Dave Nicolette's blog. It pointed me to James Shore's Change Diary. One of the most interesting points was somethings James wrote in the "Years Later." section of "Week sixteen". Subscribe to: Posts (Atom). View my complete profile.

errordriven.blogspot.com

Error-Driven Development: November 2005

http://errordriven.blogspot.com/2005_11_01_archive.html

Moving from cowboy coding to agile development. Thursday, November 24, 2005. First Randori Session in Helsinki. I participated the first randori coding dojo session. In Helsinki today. In short: it was fun. Thanks again to all the guilty parties (Markus, Pekka, Lasse)! Saturday, November 19, 2005. Being Agile on Project Level. Now, to fulfill the latter purpose, instead of writing something ignorant about using XP on project scale, I'll just let the more competent writers take the stage. Finally I decide...

errordriven.blogspot.com

Error-Driven Development: September 2005

http://errordriven.blogspot.com/2005_09_01_archive.html

Moving from cowboy coding to agile development. Friday, September 30, 2005. Diving into the World of Agile Methods. I think it's time for me to abandon the general small talk and get to some serious business. So, from now on, I'll try to stick to more software-related things. Today I attended a lecture on software processes by Professor Inkeri Verkamo. The highlight of the lecture was a short comparison between agile and traditional processes. The view on agile process was based on Alistair Cockburn.

errordriven.blogspot.com

Error-Driven Development: September 2006

http://errordriven.blogspot.com/2006_09_01_archive.html

Moving from cowboy coding to agile development. Friday, September 01, 2006. Old Habits Are Hard to Break. In the last two weeks I've spent some time writing a small program, which I finished a couple of days ago. It served its purpose but looking back, I see some room for improvement. Second, since I didn't know how to write good tests for the interface, I started slacking with writing tests altogether. When I was running out of time, I also reverted to the "good" old cowboy coding style.

errordriven.blogspot.com

Error-Driven Development: A New Beginning

http://errordriven.blogspot.com/2006/11/new-beginning.html

Moving from cowboy coding to agile development. Sunday, November 05, 2006. The first couple of weeks in my new job have been really nice. The atmosphere is really relaxed, yet ambitious and supportive. Also the people have been nice, so I've settled in very well. I also had a talk with the colleague that gave the JUnit presentation and asked him to join the next Coding Dojo. Only one or two days later the next dojo. Invitation was announced, so the timing was perfect. We went there together and talke...

errordriven.blogspot.com

Error-Driven Development: August 2005

http://errordriven.blogspot.com/2005_08_01_archive.html

Moving from cowboy coding to agile development. Tuesday, August 30, 2005. Said in an interview. That "To motivate yourself and keep yourself committed, you need to have pride in what you're doing." I think this is absolutely true. I believe the most important thing you should remember is that you can affect your surroundings. So, instead of finding a perfect workplace, you could try making your current workplace one. Don't live with broken windows. Subscribe to: Posts (Atom). View my complete profile.

errordriven.blogspot.com

Error-Driven Development: August 2006

http://errordriven.blogspot.com/2006_08_01_archive.html

Moving from cowboy coding to agile development. Tuesday, August 15, 2006. The other guy" tried checking out the tests and running them, and everything went smoothly. He also thought the tests were a good example of finding small bugs in existing code. Since everything had worked, I updated my paper and added some technical details about running the tests. Let's see if I'm just fooling myself or if my colleagues also start writing some tests. Friday, August 04, 2006. Subscribe to: Posts (Atom).

errordriven.blogspot.com

Error-Driven Development: February 2006

http://errordriven.blogspot.com/2006_02_01_archive.html

Moving from cowboy coding to agile development. Wednesday, February 15, 2006. Once again it seems I won't be coding much on my free time in a long time. My plans suffered a serious setback when I found out that the research group I wanted to join. Friday, February 10, 2006. On Wednesday I spent three hours at Reaktor. Again, participating in an Agile Finland's coding dojo. Session for the second time ever. It was fun, and this time I had a particularly good lesson about (lacking) test coverage. For (Stri...

kijoe.blogspot.com

Kijoe's blog: Coding Dojo - time to refactor?

http://kijoe.blogspot.com/2006/11/coding-dojo-time-to-refactor.html

Wednesday, November 1, 2006. Coding Dojo - time to refactor? Yesterday we held a coding dojo. At our office. This time we were supposed to code a sudoku game (without GUI). There were some new things that were tried, like having a product owner, and dividing the coding time to iterations. This time we had a group of 14 or so a good many more than in the previous one I attended where only 6 people were around. Don't get me wrong. I think TDD fundamentals are very important. Like 10 minutes for the pair an...