XP, TDD, BDD, what's next?
-
The trouble is newbie devs think that patterns, or scrum, or something else is a magic bullet. Those methodoligies help, but nothing makes you a better programmer overnight, and all software has bugs at some point in the SDLC, no matter how good your testing and how good the end result.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
all software has bugs at some point in the SDLC, no matter how good your testing and how good the end result.
This may sound ok to the development community, but not acceptable to end users. You can eliminate buggs if you understand the system well, know how to test it, and actually test it throughly. IMO, not being properly tested is a major reason for buggy software.
Best, Jun
-
Jun Du wrote:
Regardless, software is still not short of bugs.
Hell I start with a bug and work backwards, saves on design time. :)
I like long walks, especially when they are taken by people who annoy me. http://www.hq4thmarinescomm.com[^]
My Site -
Christian Graus wrote:
all software has bugs at some point in the SDLC, no matter how good your testing and how good the end result.
This may sound ok to the development community, but not acceptable to end users. You can eliminate buggs if you understand the system well, know how to test it, and actually test it throughly. IMO, not being properly tested is a major reason for buggy software.
Best, Jun
You forgot the major reason for not testing "properly"... no time! I mean seriously the understanding of a system depends on so many factors that its impossible to figure out whether its understood or not. IMO the reason for too many bugs is the count of young developers and the bug count at this rate is awesome and it should stay like this! We always have to consider that all of us were noobs once(I'm still, kinda) and that there will always be "new Guys" in almost every development project in this world :D and that is perfectly fine :D
-
Christian Graus wrote:
all software has bugs at some point in the SDLC, no matter how good your testing and how good the end result.
This may sound ok to the development community, but not acceptable to end users. You can eliminate buggs if you understand the system well, know how to test it, and actually test it throughly. IMO, not being properly tested is a major reason for buggy software.
Best, Jun
-
How's the narcolepsy going? Are you still being adversely affected?
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
I think she must have dozed off.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus!
-
Just came across an artical about Behavior Driven Development, which reminds me of Test Driven Development, Extreme Programming, Agile, Scrum. Just name a few. I'm wondering where these fancy terminologies came from. Regardless, software is still not short of bugs.
Best, Jun
Developer Profile Unencumbered by any solid experience this will suit recent graduates in particular. However any developer who is partial to pseudo-scientific new fads can easliy embrace this. Feeling of general superiority is not a must but would be a distinct advantage. Sense of humour and humility not required. Key Skills Advanced patronising of out-dated (i.e. working) dinosaur programmers. An inability to learn from the past or recognise any achievements in previous approaches essential. Extreme arrogance, enthusiasm to develop pseudo scientific BS terminology which any non BS developer can't take the time, or be bothered, to learn. Ability to create online cliques which reinforce sense of superiority with in-depth BS navel gazing. Key Phrases Keep it complicated Let them eat Lambdas I believe I have all the attributes of a rockstar programmer (e.g. no fans, no-one knows you, kids look down on you, etc) Another tool for the tool box!!
-
The trouble is newbie devs think that patterns, or scrum, or something else is a magic bullet. Those methodoligies help, but nothing makes you a better programmer overnight, and all software has bugs at some point in the SDLC, no matter how good your testing and how good the end result.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
I don't think the problem is "newbie devs", but managers. Too many times I've encountered "management by magazine article." Management will read some article on the plane ride home from whatever junket they went to, come into the office, and announce this wondrous vision they had that will make your code leffer and deffer, and reduce schedules by xx%. Or worse yet, at the junket, while half in the bag at some conference they "attended" they half heard something that promised to cut development in half, be bug free, and use cheap, beginning programmers. No thinking required.
Psychosis at 10 Film at 11
-
How's the narcolepsy going? Are you still being adversely affected?
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
Yeah, still living with The Sleepies. Winter makes it worse since there is such little sunlight this time of year. My work has a little library/closet area I go to for my naps. I have a doctor's note that lets me take three a day--great escape when I want to throttle co-workers. :-D
Soon...very soon...http://CraptasticNation.blogspot.com/[^]
-
Just came across an artical about Behavior Driven Development, which reminds me of Test Driven Development, Extreme Programming, Agile, Scrum. Just name a few. I'm wondering where these fancy terminologies came from. Regardless, software is still not short of bugs.
Best, Jun
Jun Du wrote:
Behavior Driven Development
Sounds like its just another attempt to create a methodology that gets users to tell developers what they want software to do. Users are unable to effectively do that, and a methodology isn't what's stopping them.
patbob
