software_craftsmanship Google Group

Re: [SC] Good Papers?

2010-03-22T12:56:54Z

You could also look at UncleBob's book Clean Code, which is in itself a sort
of collection of papers, each of which would be fun to discuss as a team.

Re: [SC] Re: Good Papers?

2010-03-21T21:13:03Z

Revised: it's really tough to pin Glass down. His essays are so damn
short. Honestly, reading Software Creativity is probably the best way
to absorb his ideas.
Will.

Re: [SC] Re: Good Papers?

2010-03-21T21:11:26Z

"The Importance of the Application Domain Cluster" and "Does Good
Process Lead to Improved Product? A second opinion" are two really
good papers.
Will.

Re: [SC] Re: Good Papers?

2010-03-21T19:18:58Z

These paper look great! thanks everybody.
So looks like the suggested reading list (in no particular order) is:
Mock Roles, not Objects from Freeman, Pryce, Mackinnon, Walnes
[link]
Testable Java from Feathers
[link]
David Parnas "A Rational Design Process: How and Why to Fake It"

Re: [SC] Re: Good Papers?

2010-03-21T12:36:15Z

Reading SOLID and The Craftsman is a must from my perspective. Here two I
haven't found mentioned before:
Mock Roles, not Objects from Freeman, Pryce, Mackinnon, Walnes
Testable Java from Feathers
Kind regards
Markus Gaertner
[link]

Re: Good Papers?

2010-03-21T08:09:17Z

Which SOLID papers? The old C++ ones from Uncle Bob?
A good updated version of those is Pablo's "SOLID E-Book":
[link]
Another couple of free e-books I like are:
Karl Seguin's "Foundations of Programming"
[link]

Re: [SC] Developers, programmers, or computer scientists and our heritage as craftsmen.

2010-03-21T06:05:38Z

I think Yourdon specified them as "Mission Impossible" projects.
Will.

Re: [SC] Developers, programmers, or computer scientists and our heritage as craftsmen.

2010-03-21T06:01:01Z

Right...so if situation B is a "death march", situation A is...
?

Re: [SC] Developers, programmers, or computer scientists and our heritage as craftsmen.

2010-03-21T05:52:17Z

Working 80 hours a week because you want to is awesome.
Working 80 hours a week because you have to is FAIL.
Will.

Re: [SC] Good Papers?

2010-03-21T05:48:39Z

Err, Brooks, not Knuth.
Will.

Re: [SC] Good Papers?

2010-03-21T05:26:44Z

Michael Feathers posted a list of great
papers a while back:<[link]>DionOn
hoping to get a few good suggestions on papers (not >books) to read. The dev team at my company is pretty
evangelist. We >just finished reading the SOLID papers which we all loved >(One person even remarked: "I

Re: [SC] Developers, programmers, or computer scientists and our heritage as craftsmen.

2010-03-21T04:47:01Z

I think all night hack sessions fueled by passion and camaraderie (and
beer/soda and pizza) can be great experiences. 80 hour workweeks to meet
unreasonable and unsustainable deadlines feel like failure to me, and I have
no desire to repeat them.
I wish I had a better way to communicate the distinction between these two

Re: [SC] Good Papers?

2010-03-21T03:43:28Z

Excerpts from Zach Shaw zdsbs-at-yahoo.com |Software Craftsmanship/mailing_lists|'s message of Sat Mar 20 21:15:38 -0500 2010:
Hmm, I'm all for papers, but I'm wondering if reading books isn't a bad idea?
My argument would be something along the lines of:
- good books are probably easier to find

Re: [SC] Good Papers?

2010-03-21T03:34:45Z

If you want papers, then David Parnas's work is still stellar. His "A
Rational Design Process: How and Why to Fake It" is particularly good.
Robert Glass's essays will go where most essays won't. His output is
variable, but always interesting.
Knuth's "No Silver Bullet" is a classic, as is Reeve's "What is

Good Papers?

2010-03-21T02:15:38Z

Hi All,
I'm hoping to get a few good suggestions on papers (not books) to read. The dev team at my company is pretty young (no one over 6 years of doing dev) and I am the primary TDD / Pairing / craftsmanshipie evangelist. We just finished reading the SOLID papers which we all loved (One person even remarked: "I didn't know that I didn't understand OO until I read these papers")! I'm trying to keep the momentum going but I don't know what else to suggest to our team to read. So, I'm looking for some suggestions of good papers that we can argue over (there's nothing better for learning than a good argument :)) and discuss.