Do you want Agile and Uint Testing paradigm for Christmas? [modified]
-
I may be way out of line here, however, I am not impressed with the person/persons who came up with the whole "agile/Unit" paradigm. I would say that this is the general way that i program, however my practices are not nearly as formalized. so I Ask do you agree? Formalized Unit testing, wastes more time then it saves, is best for collaborative projects, is best used where turnover is high, or is best used when working with someone who sucks at programming? Agile/Scrum, Use this when your not really sure where the project will be going, or with people who can't handle independently coding large blocks of working code, or Use this when your told to. The reason I ask is that i recently was offered a job upgrading a program from pascal to c# (told all "code" was operational), yet the were going to be adding Unit testing, and doing so under a Agile/Scrum environment... and were 8 months behind schedule. To me that screamed mismanagement, false advertising, or poor programmers. Was i wrong?:confused: _fixed Uint/Unit issue.... (I'm dislexic :suss: )
I'd blame it on the Brain farts.. But lets be honest, it really is more like a Methane factory between my ears some days then it is anything else...
modified on Friday, December 25, 2009 8:31 PM
-
I may be way out of line here, however, I am not impressed with the person/persons who came up with the whole "agile/Unit" paradigm. I would say that this is the general way that i program, however my practices are not nearly as formalized. so I Ask do you agree? Formalized Unit testing, wastes more time then it saves, is best for collaborative projects, is best used where turnover is high, or is best used when working with someone who sucks at programming? Agile/Scrum, Use this when your not really sure where the project will be going, or with people who can't handle independently coding large blocks of working code, or Use this when your told to. The reason I ask is that i recently was offered a job upgrading a program from pascal to c# (told all "code" was operational), yet the were going to be adding Unit testing, and doing so under a Agile/Scrum environment... and were 8 months behind schedule. To me that screamed mismanagement, false advertising, or poor programmers. Was i wrong?:confused: _fixed Uint/Unit issue.... (I'm dislexic :suss: )
I'd blame it on the Brain farts.. But lets be honest, it really is more like a Methane factory between my ears some days then it is anything else...
modified on Friday, December 25, 2009 8:31 PM
-
ely_bob wrote (multiple times):
Uint
What to unsigned integers have to do with agile development?
Don't blame me. I voted for Chuck Norris.
-
ely_bob wrote (multiple times):
Uint
What to unsigned integers have to do with agile development?
Don't blame me. I voted for Chuck Norris.
Well, you dynamically replace them with an int when you need to assign a negative value?
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server -
Well, you dynamically replace them with an int when you need to assign a negative value?
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v serverpeterchen wrote:
Well, you dynamically replace them with an int when you need to assign a negative value?
Yeah, but first you have to cast them. I think the OP is some kind of C++ purist.
Best wishes, Hans
-
I may be way out of line here, however, I am not impressed with the person/persons who came up with the whole "agile/Unit" paradigm. I would say that this is the general way that i program, however my practices are not nearly as formalized. so I Ask do you agree? Formalized Unit testing, wastes more time then it saves, is best for collaborative projects, is best used where turnover is high, or is best used when working with someone who sucks at programming? Agile/Scrum, Use this when your not really sure where the project will be going, or with people who can't handle independently coding large blocks of working code, or Use this when your told to. The reason I ask is that i recently was offered a job upgrading a program from pascal to c# (told all "code" was operational), yet the were going to be adding Unit testing, and doing so under a Agile/Scrum environment... and were 8 months behind schedule. To me that screamed mismanagement, false advertising, or poor programmers. Was i wrong?:confused: _fixed Uint/Unit issue.... (I'm dislexic :suss: )
I'd blame it on the Brain farts.. But lets be honest, it really is more like a Methane factory between my ears some days then it is anything else...
modified on Friday, December 25, 2009 8:31 PM
I think you're absolutely right. I'm working on an agile project at the moment, and totally unconvinced of agiles "merits". I agree with "release early, release often" and "automate", but thats where I and the agile philosophy part company. I find it frustrating, slow and _MORE_ bureaucratic than the conventional / UML processes we were using before. Scrum for us is a waste of time, and Unit testing (currently at least) is doing nothing for us, because our application doesn't lend itself to unit testing readily. In short, maybe our managers are running it badly but I personally believe that agile is about 80% "Emperors New Clothes" based on what I've seen of it.
-
ely_bob wrote (multiple times):
Uint
What to unsigned integers have to do with agile development?
Don't blame me. I voted for Chuck Norris.
-
peterchen wrote:
Well, you dynamically replace them with an int when you need to assign a negative value?
Yeah, but first you have to cast them. I think the OP is some kind of C++ purist.
Best wishes, Hans