211–220 of 297 posts
Earlier quoted context omitted.
that's a quote from Johnny Mnemonic, right? ;)
Watch http://www.youtube.com/watch?v=eRVm_TAE24A and the context will be explained.
Earlier quoted context omitted.
Cuz we XPers are too busy Programming, Motherfucker!
Only 1/2 of you. The other half is too busy staring at Eclipse and pointing out the red squigly lines like you're contributing something in a pair.
Earlier quoted context omitted.
Nothing really scales. There is no process that will allow 100 hacks to make a Michelangelo, if you want a Michelangelo you're going to have to fucking hire him. If this bullshit really worked then corporate IT departments would be the envy of every startup out there. If your software is late/buggy/whatever the solution is rarely adding people / process. It's usually removing people / process. Process is what allows…
"the solution is rarely adding people / process. It's usually removing people / process" hell yeah.
The fact that I agree with all of this just makes me sadder at how it was presented. Thanks for building a handy straw man for the methodology developers to attack. I flagged this --- it's virtually content free --- but that's a futile gesture given how susceptible HN is to this particular form of social engineering.
...it's virtually content free... Not if you run it through ReadBetweenTheLines(). Hey Thomas, lighten up. Normally I'd agree with you, but not today. This post hit me just right... I'm having a shitty day. Really shitty. 6 levels deep into garbage that never should have been written, trying to add one little feature. Asking myself every 7 minutes if I have time to rewrite without shifting everything else out a week.…
- Douglas Adams in "Mostly Harmless"
Earlier quoted context omitted.
I liked the article, I just hate the inconsistency here on HN when it comes to humorous/evocative submissions and comments. We scold some for violating the guidelines, and we bless others. Can we sometimes be more relaxed about what is submitted? If the answer is yes as you are indicating, can we make it this way all the time? Ultimately the evolving community here will make the final judgement. I just feel that the…
We scold some for violating the guidelines, and we bless others. That's really the curse of comedy. The whole point of comedy is to be subversive, to sneak in under the radar of "good taste" and "propriety." But it's hard to do that, a lot of the time it gets rejected out of hand, and it seems very inconsistent.
Earlier quoted context omitted.
That's the thing, Scrum basically assumes that all software teams are so dysfunctional that they won't talk to each other unless and until everyone is watching.
Scrum! It teaches bad teams good habits! Nothing in scrum stops you talking to anyone at any time. The stand-up makes sure that you have to say a few words to the whole team and other interested parties, daily. I like to read criticisms of scrum, when they're not straw-man ones.
Earlier quoted context omitted.
Done.
You could do with a jingle too - http://www.youtube.com/watch?v=k8F3UE9qFsg
Earlier quoted context omitted.
I saw your comment and laughed, then realized you were serious. If you are working with 500 programmers, they are likely to be mostly mediocre - the good ones would have run away screaming to better jobs. Sure, if you have 500 mediocre programmers, you need to rope them in with systems. If you hire 5-10 great programmers, stand well clear and let them do their job.
I've struggled with how to respond to your comment. You seem to be taking the view that any project that requires more than 5-10 great programmers is inherently flawed. I think this is false. I've worked on very large software systems before, places that had around 1,000 developers spread throughout the organization. While there were a lot of mediocre, and truly some flat out bad developers, I guarantee you that 5-10…
Places with 1,000 developers spread throughout are working on hundreds of interacting projects. But, the communication and coordination isn't between all 1,000 developers.
Earlier quoted context omitted.
Nothing really scales. There is no process that will allow 100 hacks to make a Michelangelo, if you want a Michelangelo you're going to have to fucking hire him. If this bullshit really worked then corporate IT departments would be the envy of every startup out there. If your software is late/buggy/whatever the solution is rarely adding people / process. It's usually removing people / process. Process is what allows…
"the solution is rarely adding people / process. It's usually removing people / process" hell yeah.