I like the way this started, but it gets nefarious in a hurry. I agree that the difference between real lead people and just another suit is what the dance looks like: core hacks make it work, whore slacks whine "can't be done..." while blame-throwing whenever the checkwriters in earshot.
Is OOP or methodology an enigma? Enforcing coding "standards" probably does more to educate and build sensible code than anything else. What I think is missing is the living standard: as a good hack gets out, baseline it as a way of doing business. A few hacks, and the production of industrial code, are worlds apart today for all the wrong reasons. Why not do it right the first time, and teach the kids by example, and hope the heck they get it. Oh, wait, I described an advantage of open source;-)
Get a clue bubba Bruce The root cause of the hack perpetualization is squarely laid at your feet: until the good hackers (and the incompetent) desist in the role of YES MEN and decide to stop supporting the BS of business pukes, building reliable apps is going to continue to be a hit&miss proposition. Companies will persist with the call to arms for heroes to make sacrificial lambs of their personal lifes into the dim light of night, while the manglement staff waddles onto the front 9 and stumbles off the back 9 none the wiser and without the wear. It just isn't a sustainable reality. Consider the outsiders view: afterall the Y2k fixes were a hoax, right Bruce? Do you think the next time this level of repair hacking is required, someone will gleefully foot the bill? "Can't those damn programmers get it right the first time", is getting louder and louder with those who hold the purse strings.
I likewise reject what looks like your theory that non-scaleable kludges make the man -a clean hack does- and the ability is not prevalent, although posers are everywhere...
Slashdot Mirror
I like the way this started, but it gets nefarious in a hurry. I agree that the difference between real lead people and just another suit is what the dance looks like: core hacks make it work, whore slacks whine "can't be done..." while blame-throwing whenever the checkwriters in earshot.
;-)
Is OOP or methodology an enigma? Enforcing coding "standards" probably does more to educate and build sensible code than anything else. What I think is missing is the living standard: as a good hack gets out, baseline it as a way of doing business. A few hacks, and the production of industrial code, are worlds apart today for all the wrong reasons. Why not do it right the first time, and teach the kids by example, and hope the heck they get it. Oh, wait, I described an advantage of open source
Get a clue bubba Bruce
The root cause of the hack perpetualization is squarely laid at your feet: until the good hackers (and the incompetent) desist in the role of YES MEN and decide to stop supporting the BS of business pukes, building reliable apps is going to continue to be a hit&miss proposition. Companies will persist with the call to arms for heroes to make sacrificial lambs of their personal lifes into the dim light of night, while the manglement staff waddles onto the front 9 and stumbles off the back 9 none the wiser and without the wear. It just isn't a sustainable reality.
Consider the outsiders view: afterall the Y2k fixes were a hoax, right Bruce? Do you think the next time this level of repair hacking is required, someone will gleefully foot the bill? "Can't those damn programmers get it right the first time", is getting louder and louder with those who hold the purse strings.
I likewise reject what looks like your theory that non-scaleable kludges make the man -a clean hack does- and the ability is not prevalent, although posers are everywhere...