<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship">
    <title>gmane.comp.programming.software-craftsmanship</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5817"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5816"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5815"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5814"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5813"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5812"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5811"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5810"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5809"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5808"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5807"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5806"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5805"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5804"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5803"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5802"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5801"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5800"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5799"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5798"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5817">
    <title>Re: How to coach or mentor software craftsmanship</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5817</link>
    <description>&lt;pre&gt;
There's been some good advice in this thread already, but no-one has 
mentioned the idea of Coding Dojos, so I thought I should :-)

You could encourage teams to set up their own Coding Dojo meetings, where 
they can discuss and learn skills. Software Craftsmanship is not only about 
a change of attitude/social pressure, but also about having skills in Test 
Driven Development, Refactoring etc. In the dojo you can address both kinds 
of issue. There is a place in these meetings for demonstrations, such as 
the one you did to show Refactoring. There is also much benefit from 
getting people to learn by doing - setting up Kata exercises so they can 
gain insight themselves from their own experience.

You could take a look at my book :-)

https://leanpub.com/codingdojohandbook

Regards,
Emily Bache

On Friday, 12 April 2013 05:39:47 UTC+2, Ashok Guduru wrote:

&lt;/pre&gt;</description>
    <dc:creator>Emily Bache</dc:creator>
    <dc:date>2013-05-20T07:27:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5816">
    <title>[ANN] The Coding Dojo Handbook</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5816</link>
    <description>&lt;pre&gt;Hi,

I've been thinking for some time about how to get average software 
developers in ordinary companies to learn practices like Test Driven 
Development, and I've been experimenting with the Coding Dojo format for 
teaching and learning. I've just published an ebook, "The Coding Dojo 
Handbook" which aims to be a helping hand along the way. My thought is that 
a team lead or enterprising team member could organize Coding Dojo meetings 
with their colleagues. This would provide a space for the whole team to 
discuss problems and issues around TDD, and to practice some of the basic 
skills involved. And it's fun!

In the book I have lots of practical advice, collaborative game 
suggestions, funny stories about dojos, and a catalogue of Kata exercises 
to draw on. I think it should be a useful resource to anyone starting a new 
dojo, or to get new ideas for an existing one. If you're in either of those 
positions, I hope you'll consider getting a copy. 

https://leanpub.com/codingdojohandbook

If you've alrea&lt;/pre&gt;</description>
    <dc:creator>Emily Bache</dc:creator>
    <dc:date>2013-05-20T07:19:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5815">
    <title>Re: Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5815</link>
    <description>&lt;pre&gt;Robi, Marcus,

On 5/7/13 2:54 AM, robi y wrote:

For other such papers, see the list at 
http://biblio.gdinwiddie.com/biblio/StudiesOfTestDrivenDevelopment

  - George


&lt;/pre&gt;</description>
    <dc:creator>George Dinwiddie</dc:creator>
    <dc:date>2013-05-08T13:04:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5814">
    <title>Re: Can we submit Vietnamese version of Manifesto?</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5814</link>
    <description>&lt;pre&gt;Hello,
Thank you for working to create a Vietnamese translation.  You may submit
it via this repository on github:
https://github.com/8thlight/manifesto_public

Add you translation to "jsons/manifesto" and submit a pull request.

Doug


On Tue, May 7, 2013 at 4:36 AM, Phạm Anh Đới &amp;lt;cibervn&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:


&lt;/pre&gt;</description>
    <dc:creator>Doug Bradbury</dc:creator>
    <dc:date>2013-05-08T00:09:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5813">
    <title>Can we submit Vietnamese version of Manifesto?</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5813</link>
    <description>&lt;pre&gt;Dear all, 
We are a group in Vietnam. We have vision to build a agile community in 
Vietnam. We have translated manifesto of software craftsmanship into 
vietnamese. Can we submit it to http://manifesto.softwarecraftsmanship.org?
Regards

Đới PA

&lt;/pre&gt;</description>
    <dc:creator>Phạm Anh Đới</dc:creator>
    <dc:date>2013-05-07T09:36:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5812">
    <title>Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5812</link>
    <description>&lt;pre&gt;Not really...
Here's an available research from Microsoft on the subject:
"Realizing quality improvement through test driven development: results and 
experiences of four industrial teams (2008)"
http://research.microsoft.com/en-us/groups/ese/nagappan_tdd.pdf

On Monday, May 6, 2013 4:03:41 PM UTC+3, Marcus wrote:

&lt;/pre&gt;</description>
    <dc:creator>robi y</dc:creator>
    <dc:date>2013-05-07T06:54:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5811">
    <title>Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5811</link>
    <description>&lt;pre&gt;Robi,

Thanks for this indication! I'm wondering why this book is so expensive 
(USD99 for the e-book format) though. Have you read it already?

Marcus

Em terça-feira, 30 de abril de 2013 04h44min56s UTC-3, robi y escreveu:

&lt;/pre&gt;</description>
    <dc:creator>Marcus</dc:creator>
    <dc:date>2013-05-06T13:03:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5810">
    <title>RE: Next Boston SC meeting - Practicing the code transition</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5810</link>
    <description>&lt;pre&gt;Thanks Zach, this is some really useful advice; I've passed it on to our guys who do inductions for new starters as it looks like we'll be able to improve our process a fair bit based on this information.
Alastair

--Founder, Cambridge Software Craftsmanship Communityhttp://www.camswcraft.org.uk/
Date: Tue, 30 Apr 2013 13:28:55 -0700
From: zdsbs-/E1597aS9LQAvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org
To: software_craftsmanship-/JYPxA39Uh5TLH3MbocFFw&amp;lt; at &amp;gt;public.gmane.org
Subject: Re: [SC] Next Boston SC meeting - Practicing the code transition

Hi Alastair,
The session went really well!
We learned more about what it meant to give a good code presentation than what it meant to be a good audience member (This is primarily because our presentations were too short for much audience participation).
Here are some of the learnings for people practicing the code transition:Make an agenda. Give the audience a picture of where you're going to take them, how long those pieces should take, and what they should expect to know at the endFollo&lt;/pre&gt;</description>
    <dc:creator>Alastair Smith</dc:creator>
    <dc:date>2013-05-01T10:51:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5809">
    <title>Re: Next Boston SC meeting - Practicing the code transition</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5809</link>
    <description>&lt;pre&gt;Hi Alastair,

The session went really well!

We learned more about what it meant to give a good code presentation than 
what it meant to be a good audience member (This is primarily because our 
presentations were too short for much audience participation).

Here are some of the learnings for people practicing the code transition:

   - Make an agenda. Give the audience a picture of where you're going to 
   take them, how long those pieces should take, and what they should expect 
   to know at the end
   - Follow an example end to end
   - Give an example use case and show it before diving into how the source 
   works
   - Tell the new maintainer what they might expect in their new role
   - Give high level tour of major pieces
   - Talk about what's stable vs what's changing
   - Walk through a debugging of the software
   - Talk about what the users are looking for / what's the end users 
   perspective
   - Talk about what kind of feature requests are coming in
   - Don't stop talking!

If you want to &lt;/pre&gt;</description>
    <dc:creator>zdsbs-/E1597aS9LQAvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-04-30T20:28:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5808">
    <title>May 6th next Boston SC - Practicing Modeling</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5808</link>
    <description>&lt;pre&gt;Hi All,

Then next Boston SC meeting is May 6th (Next Monday!) We'll be practicing 
modeling http://gathers.us/events/may-boston-software-craftsmanship-meeting

How many different modeling ideas do you come up with before you settle on 
one to implement? How often do you let your model concepts emerge from TDD?

Tonight we'll be putting aside TDD &amp;amp; code all together. The goal will be to 
stretch how you conceptualize what you'll build in software. You'll be 
presented with a concept to model and will work on a number of ways to 
model it.

This should be a blast and did I mention you won't even need a computer?

See you then,

Zach
Boston SC - Improvement through practice

&lt;/pre&gt;</description>
    <dc:creator>zdsbs-/E1597aS9LQAvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-04-30T20:18:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5807">
    <title>Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5807</link>
    <description>&lt;pre&gt;I understand you're looking for research data, maybe this book could be of 
help:
Test-Driven Development
An Empirical Evaluation of Agile Practice
Madeyski, Lech
http://www.springer.com/computer/swe/book/978-3-642-04287-4

On Tuesday, April 16, 2013 6:59:26 PM UTC+3, Marcus wrote:

&lt;/pre&gt;</description>
    <dc:creator>robi y</dc:creator>
    <dc:date>2013-04-30T07:44:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5806">
    <title>Re: Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5806</link>
    <description>&lt;pre&gt;Thanks for your link Michel! I appreciate it!

Marcus

Em segunda-feira, 29 de abril de 2013 11h44min44s UTC-3, Michel Löhr 
escreveu:

&lt;/pre&gt;</description>
    <dc:creator>Marcus</dc:creator>
    <dc:date>2013-04-29T19:07:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5805">
    <title>Re: Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5805</link>
    <description>&lt;pre&gt;I managed to get the time over the weekend to watch the presentation
video that Jim Weirich posted on Glenn Vanderburg's talk "Real
Software Engineering" from Ruby Scotland 2011. I can thoroughly
recommend it.

I shall now reconstruct my earlier position as: 'Software is not what
most people think of as Engineering (excepting the real engineers)'

Fox
--

On 29 April 2013 15:44, Michel Löhr &amp;lt;michel.lohr-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Sleepyfox</dc:creator>
    <dc:date>2013-04-29T14:59:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5804">
    <title>Re: Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5804</link>
    <description>&lt;pre&gt;Hi Marcus, this is a master thesis you could be interested in:

https://jyx.jyu.fi/dspace/bitstream/handle/123456789/41024/URN%3ANBN%3Afi%3Ajyu-201303071297.pdf?sequence=1

Cheers, Michel


Op donderdag 25 april 2013 20:53:24 UTC+2 schreef Marcus het volgende:

&lt;/pre&gt;</description>
    <dc:creator>Michel Löhr</dc:creator>
    <dc:date>2013-04-29T14:44:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5803">
    <title>Re: Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5803</link>
    <description>&lt;pre&gt;Has everyone here seen Morendil's Software Engineering History Maturity Model? http://plus.google.com/115091715679003832601/posts/VBJTGru3PeW

&lt;/pre&gt;</description>
    <dc:creator>Philip Schwarz</dc:creator>
    <dc:date>2013-04-27T07:58:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5802">
    <title>Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5802</link>
    <description>&lt;pre&gt;Raoul,

On 4/24/13 6:32 PM, Raoul Duke wrote:

I don't think so. He's still alive.

  - George

&lt;/pre&gt;</description>
    <dc:creator>George Dinwiddie</dc:creator>
    <dc:date>2013-04-27T02:05:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5801">
    <title>Re: Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5801</link>
    <description>&lt;pre&gt;Marcus,

This is an interesting find, but one that doesn't (yet) change much,
as one can still say that the 1968 NATO conference marked the
beginning of the popularisation of Software Engineering as a industry
metaphor.

Thank you for the correct attribution to Cameron, your link didn't
work for me, but a complete analysis here helped:
http://quoteinvestigator.com/2010/05/26/everything-counts-einstein/

Time to update my quotes database.

Fox
&lt;/pre&gt;</description>
    <dc:creator>Sleepyfox</dc:creator>
    <dc:date>2013-04-26T20:26:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5800">
    <title>Re: Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5800</link>
    <description>&lt;pre&gt;Another important historical fact that is often confused and that in my 
opinion needs clarification. It is often said that the term 'Software 
Engineering' was coined at the 1968 Garmisch conference as Fox pointed out. 
However, in this 1992 research conduced by Bertrand Meyer, he indicates 
that this is not correct. Maybe this is pointless in a professional 
standpoint, but it definitely matters in an academic one. 

Again, I'm really sorry if this is not the right group to discuss some 
aspects of our profession. I'm not trying to defend a given position, I'm 
not saying that A is right and B is wrong, I just think that trough facts 
and high level discussions we can certainly learn and improve ourselves.

Below is the link and the text that contains the research conduced by Meyer.

http://www.unl.csi.cuny.edu/faqs/software-enginering/archive/SEorigin

All textbooks on software engineering that I know, and many articles in the
field, claim (that is to say, repeat someone else's claim) that the term
``soft&lt;/pre&gt;</description>
    <dc:creator>Marcus</dc:creator>
    <dc:date>2013-04-26T18:37:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5799">
    <title>Re: Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5799</link>
    <description>&lt;pre&gt;
Fox,

*--*
*"Not everything that can be counted counts, and not everything that counts 
can be counted"*
*  -- A. Einstein*

Please don't quote William Cameron as Albert Einstein...

*It would be nice if all of the data which sociologists require could be 
enumerated because then we could run them through IBM machines and draw 
charts as the economists do. However, not everything that can be counted 
counts, and not everything that counts can be counted.*

You can double check this quotation in his book , "Informal Sociology A 
Casual Introduction to Sociological Thinking"

http://books.google.com.br/books?id=I6JIAAAAMAAJ&amp;amp;q=%22counted+counts%22&amp;amp;redir_esc=y#search_anchor

Thanks!


Em quinta-feira, 25 de abril de 2013 06h09min02s UTC-3, Nigel escreveu:

&lt;/pre&gt;</description>
    <dc:creator>Marcus</dc:creator>
    <dc:date>2013-04-25T18:48:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5798">
    <title>Re: Re: TDD Classification</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5798</link>
    <description>&lt;pre&gt;Michel,

Thank you very much for your assistance! I can definitely use that material 
as a reference!

Marcus

Em quarta-feira, 24 de abril de 2013 17h35min28s UTC-3, Michel Löhr 
escreveu:

&lt;/pre&gt;</description>
    <dc:creator>Marcus</dc:creator>
    <dc:date>2013-04-25T18:53:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5797">
    <title>Re: Perception that high quality equals Rolls Royce</title>
    <link>http://permalink.gmane.org/gmane.comp.programming.software-craftsmanship/5797</link>
    <description>&lt;pre&gt;David,

On 4/25/13 3:12 PM, David Wilde wrote:

Yes, I know all that. But there's a difference between doing the work 
for 100% availability and not doing that work and having 100% 
availability (for some specified period of time).


&lt;/pre&gt;</description>
    <dc:creator>George Dinwiddie</dc:creator>
    <dc:date>2013-04-26T02:22:59</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.programming.software-craftsmanship">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.programming.software-craftsmanship</link>
  </textinput>
</rdf:RDF>
