Regarding this week's survey question...
-
"Which software development methodologies do you use?" What I think has been lost in all the noise of so-called methodologies is the total disregard for quality. And by that I mean simple things like DRY principle and even correct spelling (particularly customer facing UI's). We speak of passion for software development, but where is the passion for doing something well? I don't mean perfect, but the code I so often encounter just screams "I clearly don't give a shit." These methodologies, they don't address any of this. Where in these methodologies is "show that you care about your work?" It doesn't exist. Maybe I should create a Care-Bear[^] Methodology and write a "care meter" plugin for VS. :laugh:
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
"Which software development methodologies do you use?" What I think has been lost in all the noise of so-called methodologies is the total disregard for quality. And by that I mean simple things like DRY principle and even correct spelling (particularly customer facing UI's). We speak of passion for software development, but where is the passion for doing something well? I don't mean perfect, but the code I so often encounter just screams "I clearly don't give a shit." These methodologies, they don't address any of this. Where in these methodologies is "show that you care about your work?" It doesn't exist. Maybe I should create a Care-Bear[^] Methodology and write a "care meter" plugin for VS. :laugh:
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Marc Clifton wrote:
I don't mean perfect, but the code I so often encounter just screams "I clearly don't give a sh*t." These methodologies, they don't address any of this.
Totally agree. I believe you may find that the answer is related to what I call : Assembly-Line Programming Very many devs are writing only one small piece of anything they are building. This means you churn out your piece and someone else has the whole in mind. You don't care. It's just like the old Automobile lines. Screw on 3 bolts and let it go down the line. 3 bolts! 3 bolts! 3 bolts! Screw it, I'm tired today, 2 bolts! 2 bolts!! It is a human condition thing that is difficult to weed out in these large projects. Large projects where you are only one small little piece make you feel like you are accomplishing basically nothing. it's a human problem. However, those of us who create maybe the entire Software Product from end-to-end and even write the documentation and are completely "responsible" get a totally different experience from it. That's where the real energy comes from. But, how to do this on a large project!?! I'm not sure. EDIT And often on big projects you attempt to tell someone, "uh, I don't think this is going quite right." And they tell you, "Dont rock the boat, you trouble-maker. Sit down, shut up and get your bolts on!!" On end-to-end projects, you better get it right. You're the only one and you better rock the boat a lot. Edit 2 The word I always use to sum all of this up is: Ownership! Edit 3 This is also what the Agile Manifesto means by :
Agile Manifesto Principle:
The best architectures, requirements, and designs emerge from self-organizing teams.
It means you go out and find people who are engaged in the process and you "contract" them to build and own a particular piece. This is self-organizing team where each individual cares deeply about what s/he is building and owns it completely. However, teams are not created this way in BigCorp. They just give you devs or DBAs or whatever to do something (screw on a bolt).
-
"Which software development methodologies do you use?" What I think has been lost in all the noise of so-called methodologies is the total disregard for quality. And by that I mean simple things like DRY principle and even correct spelling (particularly customer facing UI's). We speak of passion for software development, but where is the passion for doing something well? I don't mean perfect, but the code I so often encounter just screams "I clearly don't give a shit." These methodologies, they don't address any of this. Where in these methodologies is "show that you care about your work?" It doesn't exist. Maybe I should create a Care-Bear[^] Methodology and write a "care meter" plugin for VS. :laugh:
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
The problem is it that quality is too expensive, and we live in a world where quality software just isn't very important anymore. So what if there is problems in the software, we can roll out a patch within 24 hours. It's not like the old days where you have to get it near perfect first time because the cost of a patch was just too expensive. The most obvious example of this is with video games. It used to be that the game had to work first time and needed testing to death, because nobody wanted the costs of a recall. Whereas today, they ship games before they are even finished and then release a "day one" patch in time for release/delivery day. In short, there just isn't enough consequence to releasing bugs anymore.
-
The problem is it that quality is too expensive, and we live in a world where quality software just isn't very important anymore. So what if there is problems in the software, we can roll out a patch within 24 hours. It's not like the old days where you have to get it near perfect first time because the cost of a patch was just too expensive. The most obvious example of this is with video games. It used to be that the game had to work first time and needed testing to death, because nobody wanted the costs of a recall. Whereas today, they ship games before they are even finished and then release a "day one" patch in time for release/delivery day. In short, there just isn't enough consequence to releasing bugs anymore.
-
"Which software development methodologies do you use?" What I think has been lost in all the noise of so-called methodologies is the total disregard for quality. And by that I mean simple things like DRY principle and even correct spelling (particularly customer facing UI's). We speak of passion for software development, but where is the passion for doing something well? I don't mean perfect, but the code I so often encounter just screams "I clearly don't give a shit." These methodologies, they don't address any of this. Where in these methodologies is "show that you care about your work?" It doesn't exist. Maybe I should create a Care-Bear[^] Methodology and write a "care meter" plugin for VS. :laugh:
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Marc Clifton wrote:
I don't mean perfect, but the code I so often encounter just screams "I clearly don't give a sh*t." These methodologies, they don't address any of this.
Totally agree. I believe you may find that the answer is related to what I call : Assembly-Line Programming Very many devs are writing only one small piece of anything they are building. This means you churn out your piece and someone else has the whole in mind. You don't care. It's just like the old Automobile lines. Screw on 3 bolts and let it go down the line. 3 bolts! 3 bolts! 3 bolts! Screw it, I'm tired today, 2 bolts! 2 bolts!! It is a human condition thing that is difficult to weed out in these large projects. Large projects where you are only one small little piece make you feel like you are accomplishing basically nothing. it's a human problem. However, those of us who create maybe the entire Software Product from end-to-end and even write the documentation and are completely "responsible" get a totally different experience from it. That's where the real energy comes from. But, how to do this on a large project!?! I'm not sure. EDIT And often on big projects you attempt to tell someone, "uh, I don't think this is going quite right." And they tell you, "Dont rock the boat, you trouble-maker. Sit down, shut up and get your bolts on!!" On end-to-end projects, you better get it right. You're the only one and you better rock the boat a lot. Edit 2 The word I always use to sum all of this up is: Ownership! Edit 3 This is also what the Agile Manifesto means by :
Agile Manifesto Principle:
The best architectures, requirements, and designs emerge from self-organizing teams.
It means you go out and find people who are engaged in the process and you "contract" them to build and own a particular piece. This is self-organizing team where each individual cares deeply about what s/he is building and owns it completely. However, teams are not created this way in BigCorp. They just give you devs or DBAs or whatever to do something (screw on a bolt).
Well put!
Technician 1. A person that fixes stuff you can't. 2. One who does precision guesswork based on unreliable data provided by those of questionable knowledge. JaxCoder.com
-
musefan wrote:
In short, there just isn't enough consequence to releasing bugs anymore.
Very good post!! You are totally spot on with that. Back in the day when you had to ship 3.5" floppies, you had to get it right!!
And in my experience didn't, wait for release beta before use...
-
"Which software development methodologies do you use?" What I think has been lost in all the noise of so-called methodologies is the total disregard for quality. And by that I mean simple things like DRY principle and even correct spelling (particularly customer facing UI's). We speak of passion for software development, but where is the passion for doing something well? I don't mean perfect, but the code I so often encounter just screams "I clearly don't give a shit." These methodologies, they don't address any of this. Where in these methodologies is "show that you care about your work?" It doesn't exist. Maybe I should create a Care-Bear[^] Methodology and write a "care meter" plugin for VS. :laugh:
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
I agree - that's why I use a VS Spell Check addin: Visual Studio Spell Checker[^] for VS2019, and Spell Checker - Visual Studio Marketplace[^] for earlier version. It checks and "red lines" spelling mistakes in comments, strings, ... everything but variables!
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
I agree - that's why I use a VS Spell Check addin: Visual Studio Spell Checker[^] for VS2019, and Spell Checker - Visual Studio Marketplace[^] for earlier version. It checks and "red lines" spelling mistakes in comments, strings, ... everything but variables!
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
"Which software development methodologies do you use?" What I think has been lost in all the noise of so-called methodologies is the total disregard for quality. And by that I mean simple things like DRY principle and even correct spelling (particularly customer facing UI's). We speak of passion for software development, but where is the passion for doing something well? I don't mean perfect, but the code I so often encounter just screams "I clearly don't give a shit." These methodologies, they don't address any of this. Where in these methodologies is "show that you care about your work?" It doesn't exist. Maybe I should create a Care-Bear[^] Methodology and write a "care meter" plugin for VS. :laugh:
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
If I could give you 5 upvotes I would
cheers Chris Maunder
-
If I could give you 5 upvotes I would
cheers Chris Maunder
I suspect you can, if anyone can! :laugh:
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
"Which software development methodologies do you use?" What I think has been lost in all the noise of so-called methodologies is the total disregard for quality. And by that I mean simple things like DRY principle and even correct spelling (particularly customer facing UI's). We speak of passion for software development, but where is the passion for doing something well? I don't mean perfect, but the code I so often encounter just screams "I clearly don't give a shit." These methodologies, they don't address any of this. Where in these methodologies is "show that you care about your work?" It doesn't exist. Maybe I should create a Care-Bear[^] Methodology and write a "care meter" plugin for VS. :laugh:
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Marc Clifton wrote:
"I clearly don't give a sh*t."
Which is a work ethic, not methodology. These methodologies are NOT SUPPOSED to have anything to do with a person's work ethic. Work ethic is out of scope to any methodology. You are either diligent in your work, or not. :thumbsup:
-
If I could give you 5 upvotes I would
cheers Chris Maunder
Chris Maunder wrote:
If I could give you 5 upvotes I would
You could if you wanted to. Just saying... :laugh: You do hold the keys to Castle Bob.
-
The problem is it that quality is too expensive, and we live in a world where quality software just isn't very important anymore. So what if there is problems in the software, we can roll out a patch within 24 hours. It's not like the old days where you have to get it near perfect first time because the cost of a patch was just too expensive. The most obvious example of this is with video games. It used to be that the game had to work first time and needed testing to death, because nobody wanted the costs of a recall. Whereas today, they ship games before they are even finished and then release a "day one" patch in time for release/delivery day. In short, there just isn't enough consequence to releasing bugs anymore.
While I think this is true for the most part, it also largely depends on your line of work. My software runs machines that produce a LOT of product every day. I hear about nearly every hiccup it has because it costs the company money and that is very consequential to a lot of people and their wallets. Me included.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
Marc Clifton wrote:
"I clearly don't give a sh*t."
Which is a work ethic, not methodology. These methodologies are NOT SUPPOSED to have anything to do with a person's work ethic. Work ethic is out of scope to any methodology. You are either diligent in your work, or not. :thumbsup:
I don't entirely agree. It seems to me the success of any methodology depends entirely on the work ethic of the participants. If they have none then failure is unavoidable.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
I don't entirely agree. It seems to me the success of any methodology depends entirely on the work ethic of the participants. If they have none then failure is unavoidable.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Rick York wrote:
the success of any methodology depends entirely on the work ethic of the participants.
we are not discussing the "success" of anything here. we are discussing which methodologies you use, per the original Poll. Marc is cross pollinating work ethic with a methodology. being successful and have a good work ethic has nothing to do with which methodologies a person uses.
-
musefan wrote:
In short, there just isn't enough consequence to releasing bugs anymore.
Very good post!! You are totally spot on with that. Back in the day when you had to ship 3.5" floppies, you had to get it right!!
-
Rick York wrote:
the success of any methodology depends entirely on the work ethic of the participants.
we are not discussing the "success" of anything here. we are discussing which methodologies you use, per the original Poll. Marc is cross pollinating work ethic with a methodology. being successful and have a good work ethic has nothing to do with which methodologies a person uses.
Slacker007 wrote:
being successful and have a good work ethic has nothing to do with which methodologies a person uses.
Well somebody has never been in management!
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
-
Slacker007 wrote:
being successful and have a good work ethic has nothing to do with which methodologies a person uses.
Well somebody has never been in management!
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
:zzz: I have been in management before. I still stand by my original comments.
-
Marc Clifton wrote:
"I clearly don't give a sh*t."
Which is a work ethic, not methodology. These methodologies are NOT SUPPOSED to have anything to do with a person's work ethic. Work ethic is out of scope to any methodology. You are either diligent in your work, or not. :thumbsup:
Slacker007 wrote:
Which is a work ethic, not methodology.
Exactly. And I contend that we don't need methodologies, we need better work ethics.
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
