Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'll just carry on using methods and practices that I've seen be really f**king successful in Real Life.

    This sort of thing used to really annoy me. People keep saying that these things don't work when there are lots of folk who are out there using the practices and getting really great products out of the end of it. Do they really think everybody is just making shit up?

    These day I've decided to just be grateful for the competitive advantage I get from people ignoring agile :-)

    E.g. pair programming is something I've found to be a hugely productive thing to do. Keeps both of you focussed on the code (hard to slack of reading perlmonks if you have somebody working with you :-). Continual code review. Excellent way of passing knowledge around the team. etc. etc.

    I do have some sympathy for him. There are a heck of a lot of people out there adding "agile" to their list of buzz words with very little understanding of how it works out - and the values the business needs to make the practices work well.

    It's kind of like those managers who read "productive teams socialise after work" and then proceed to make Friday night bowling compulsory to increase productivity.

    More and more often I'm coming across people telling me that their "agile consultant" said X - where X is about as far away from agile as you can possibly get.