Archive for April, 2010

Robert C Martin on Craftsmanship and Ethics

Monday, April 26th, 2010

Found this video on http://www.infoq.com/presentations/craftmanship-ethics and wanted to have the sheets -in- the presentation itself so that I could show it to my collegue developers at work.

Means I had to get the video from infoQ first (FireFox has a nice plugin for that), than do stuff with VirtualDub to the video that I grabbed (do not ask, took me hours, I’m totally new to this internetvideo stuff), Than found DivXLand Media Subtitler for the texts on the sheets, type in the texts of the sheets as subtitles and carefully place those at several places in the video; not really my kind of work but I found this presentation pretty inspiring; alot of I-have-seen-what-he-is-talking-about, so well worth the effort.

So have a look at the presentation, to make it available on youtube I unfortunately had to split the presentation in five different parts, but it’s well worth watching.

Robert C Martin is famous for his book on Clean Code, just do a search and you will know who he is.

Introtext, shameless copied from infoQ:

Summary
In this talk Robert C. Martin outlines the practices used by software craftsmen to maintain their professional ethics. He resolves the dilemma of speed vs. quality, and mess vs schedule. He provides a set of principles and simple Dos and Don’ts for teams who want to be counted as professional craftsmen.



Robert C Martin on Craftsmanship and Ethics – Part 1
Robert C Martin on Craftsmanship and Ethics – Part 2
Robert C Martin on Craftsmanship and Ethics – Part 3
Robert C Martin on Craftsmanship and Ethics – Part 4
Robert C Martin on Craftsmanship and Ethics – Part 5

Liked this video? I was not really surprised about the “DO NOT REDESIGN” part but I must say that the redesign that we did at work really was beneficial, at least, from a maintenance point of view… But sure, the company has to have real confidence and patience to give developers time to go through with such a grand redesign. And no, we are still not entirely finished getting rid of the last parts of the old mudball.. ehm.. I mean ‘codename classic’… yeah, we do not (officially) call the old code the spaghetti-hell mudball that it is, but we use the gentle term ‘classic’ for it. Don’t laugh. Redesign is still dependend on classic for certain modules, but we’ll get rid of here, eventually…;-)