InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Presentation: Fostering Software Craftsmanship in a Corporate Setting

Posted by Abel Avram on Sep 30, 2008

Sections
Topics

In this presentation filmed during Agile 2008, Scott Dillman talks about transforming developers into software craftsmen, people responsible for their work, continuously learning, taking pride in doing qualitative work, sharing knowledge and respecting professional standards.

Watch: Fostering Software Craftsmanship in a Corporate Setting (1h 23 min.)

Scott presents how software development is no longer an incipient skill of a young industry attempting to solve software problems, but it has become a craftsmanship. Scott defines craftsmanship through the following attributes:

  • Taking responsibility
  • Continuous learning
  • Rejecting specialization
  • Pride in quality work
  • Passing on knowledge
  • Meeting professional standards
    • Test-Driven Development
    • Continuous Integration
    • Coding Patterns and Practices

Scott continues on explaining how to proceed with turning developers into craftsmen by doing the following:

Evaluate

  • Interview
  • Survey
  • Metrics

Educate

  • Pair Programming
  • Centralized Resources
  • Educational Sessions
  • Craftsmanship Day
  • 10% Time
  • On-Team Mentoring
  • Upper Management

Measure Success

  • Continuous Evaluation
  • Performance Goals that Motivate and Educate
  • Performance Reviews

The last part of the session is reserved for answering questions.

stops at 18th minute or so by Pavel Veller Posted
Re: stops at 18th minute or so by Olivier Gourment Posted
Re: stops at 18th minute or so by Scott Dillman Posted
  1. Back to top

    stops at 18th minute or so

    by Pavel Veller

    the video rewinds to the beginning on or around 18th minute. I can't watch it any further. is it only me?

  2. Back to top

    Re: stops at 18th minute or so

    by Olivier Gourment

    the video rewinds to the beginning on or around 18th minute. I can't watch it any further. is it only me?


    working for me.

  3. Back to top

    Re: stops at 18th minute or so

    by Scott Dillman

    During the presentation, I noticed that the person video taping filled his tape and had to switch to a new one. During the time he switched tapes, there is a gap missing from the presentation of a minute or two. The presentation should resume, however, after that.

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.