• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Pragramatic Starter Kit

 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I believe every developer should get this.I'm already in love with this whole set,even before using it
 
Author
Posts: 55
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Why thank you! Be sure to tell all your friends, blog it, etc. :-)
Dave and I really want this stuff to be helpful. So many teams that we run into could produce such great stuff if they could only fix a few basic problems first.
While we're on the topic, what other titles/ideas would you like to see covered in the Starter Kit or some other series? Are books enough or could we do something else that would be helpful?
 
Sheriff
Posts: 6450
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Andy Hunt:
While we're on the topic, what other titles/ideas would you like to see covered in the Starter Kit or some other series?


Hmmm... I'm sure there are many topics that could benefit from the pragmatic approach.
- project management
- OO design
- requirements gathering
- software maintenance
Shouldn't we take a pragmatic approach throughout the entire software lifecycle?
[ February 19, 2004: Message edited by: Jason Menard ]
 
Andy Hunt
Author
Posts: 55
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Absolutely! But as we've pointed out in other posts, ya gotta tackle these things one at a time.
If we came out with a 1200-page book that covered the entire development lifecycle, I don't think many people would read it. Or lift it. And that would be the cut-down, short version!
So we want to hit individual topics as we go along. Dave and I started with Version Control, Unit testing, and Automation because we feel those are the most basic elements that you've just got to do and do correctly. If you mess up on one of these basic elements, it doesn't matter that you've got a great design or a flexible, robust architecture, you will still be hosed.
But once you've got the basics in place, what's the next most important thing that people are struggling with? Where can we be the most help?
 
blacksmith
Posts: 979
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
May add something like "knowledge management"
to the list. I explain. From own experience
I've seen that problems often arise from the
simple fact that there is no/little 'collective
memory' of tasks or problems that have been
solved in the course of the years. Therefore
one problem is solved many times and little is
learned from previous experience.
Knowledge of solutions resides with certain
people and that's it. How do you build a
knowledgebase, what are the PRAGMATIC (here it is)
approaches for this?
Greetings,
Gian Franco Casula
[ February 19, 2004: Message edited by: Gian Franco Casula ]
[ February 19, 2004: Message edited by: Gian Franco Casula ]
 
Jason Menard
Sheriff
Posts: 6450
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Andy Hunt:
If we came out with a 1200-page book that covered the entire development lifecycle, I don't think many people would read it. Or lift it. And that would be the cut-down, short version!


I absolutely agree. I really like the approacch that you guys are taking with the Starter Kit.

But once you've got the basics in place, what's the next most important thing that people are struggling with? Where can we be the most help?


Maybe the next logical thing is reading and understanding other people's code. I'm not sure how this would translate into a book though. There is a book called Code Reading: The Open Source Perspective, but I can't say that I've read it (interestingly enough Amazon states that people who buy that book also buy The Pragmatic Programmer).
 
Ranch Hand
Posts: 445
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Andy Hunt:
But once you've got the basics in place, what's the next most important thing that people are struggling with? Where can we be the most help?


Do you have some plan to write for programmers using scripting language in their daily life? Maybe your Automation book of this kit will cover that topic?
[ February 19, 2004: Message edited by: Doug Wang ]
 
Ranch Hand
Posts: 81
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I bought the book earlier today and I am enjoying it very much. Even wrote test cases for one of my Java classes for my VoiceXML application. It felt very good.
I too would be VERY interested in a book on everyday scripting. I know that there are plenty of books out there on the topic, but I think that you have a different style and approach to the topic. One of the things that I constantly reflect on about the pragmatic programmer is that you should know your text editor well and use it like crazy. I think that the same philosophy could be applied to scripting.
I work on different Wintel machines, Linux and Solaris. I am constantly suffering because I don't know a scripting language. Although I know Java and C++, I've never taken the time to learn Perl or Kornshell. Consequently I sometimes find myself in the embarrassing situation of performing tasks manually that I am quite aware should be automated. I cringe when someone comes in my office and I'm renaming a bunch of files or whatever.
 
reply
    Bookmark Topic Watch Topic
  • New Topic