On Mar 1, 2006, at 7:36 PM, Kirrily Robert wrote:
In my experience developers latch on to test-driven development
like a crack habit because once they get into the swing of it, it
really is a very effective, stress-reducing way to work.
That was one of the really surprising (pleasantly
Matisse Enzer [EMAIL PROTECTED] wrote:
Jeff I think that is a good theory - I mean, it is a testable theory.
I hope it is true, but I am not sure. I suggest you interview a few
IT managers - come up with a list of 6 questions and ask them to
answer in email - I can introduce you to a
Hello everyone-
I'm working on a presentation of Perl::Critic for the
local perlmongers group. As part of the presentation,
I would like to make some comments about the current
industry trends around software quality. Basically,
I'd like to assert that there is a growing emphasis on
software
Hi Jeffrey,
* Jeffrey Thalhammer [EMAIL PROTECTED] [2006-03-01 09:40]:
By lowering maintenance costs via quality control, managers can
avoid (or at least postpone) having to scrap their entire system
and rebuild from scratch in India.
I think this is a bit of a stretch.
Can you think of any
On 3/1/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
In my experience it has more to do with the particular
programming community. In Java and Perl, there is a lot of
emphasis on testing. I don't know about its prevalence in the
Ruby or Python or other communities, but there is definitely
a lot
By lowering maintenance costs via quality control,
managers can
avoid (or at least postpone) having to scrap their
entire system
and rebuild from scratch in India.
I think this is a bit of a stretch.
I'm in the middle of one such situation. I have
inherited a 500k line legacy system that
Jeffrey Thalhammer wrote:
Is that still too much of a stretch? Should I forget
about the outsourcing stuff and just focus on the ROI
aspects?
If you're talking to a bunch of perl mongers I recommend talking about
perl instead of spouting management-speak. The Republic Of Ireland has
* Jeffrey Thalhammer [EMAIL PROTECTED] [2006-03-01 11:05]:
By lowering maintenance costs via quality control, managers
can avoid (or at least postpone) having to scrap their entire
system and rebuild from scratch in India.
I think this is a bit of a stretch.
I'm in the middle of one such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A. Pagaltzis wrote:
It has to be *REALLY* awful though. See Joel Spolsky on rewriting
from scratch[1] (the gist: *never* do it!).
[1]: http://www.joelonsoftware.com/articles/fog69.html
[...] If you want to equip programmers to talk to
* Dominique Quatravaux [EMAIL PROTECTED] [2006-03-01 14:20]:
Yours is a *very* interesting bookmark collection. Do you have
more?
I have a collection at http://plasmasturm.org/links/.
Disclaimer: it’s far from complete, of course. I try to keep to
really meaty stuff, so less gets added than
On Wednesday 01 March 2006 03:27, Jeffrey Thalhammer wrote:
Thanks for this. I've heard the term Technical Debt
a few times lately and I really like it. Unlike a
financial debt however, there is a possibility that
the principal and interest won't have to be paid. A
poor implementation
I'm with Aristotle. I think it's an urge that's come out of the
development community -- specifically, *certain* development
communities -- rather than from an end-user desire for quality. Many
of the best -tested pieces of software are the infrastructure type
things that only developers
12 matches
Mail list logo