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
Marc Clifton wrote:
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 sh*t."
I find more of a "I clearly have no damned clue" often being screamed by some outside code.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
-
DRHuff wrote:
Do you even have a sense of humor?
sorry, not today, I guess. :sigh:
And my apologies as well - rereading this a day later I have to say that my response was a bit dickish. :sigh:
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)
-
stoneyowl2 wrote:
Generally figured a week at each site
Those were the days when you could get out of your cubicle! Now you're stuck in the grey walls and all you have is the Internet. :laugh:
Well, now I am (semi) retired, and my cubicle is a spare bedroom. The walls have my own paintings on them, and I listen to music as loud as I want :)
A human being should be able to change a diaper, plan an invasion, butcher a hog, navigate a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects! - Lazarus Long
-
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).
