I'm truly curious what part of XP gets in the way of programming.
The part where you talk more about how you're going to program than actually Programming, Motherfucker.
[deleted]
Untitled topic
121–130 of 297 posts
Re: undefined
#122Earlier quoted context omitted.
Who does that? I don't know anyone that actually does XP that does that. There's no such thing as XP certification, and I have never seen an XP class offered. There's not even an XP conference anymore.
> There's not even an XP conference anymore. I wonder why?
Cuz we XPers are too busy Programming, Motherfucker!
Re: undefined
#123I wish I'd read that before I forsook Common Lisp for Java to make myself marketable when I wasn't even looking for a job.
Re: undefined
#124I find this kind of shallow but maybe it's just me.
In contrast I thought the Cluetrain Manifesto was better developed: http://www.cluetrain.com/
Re: undefined
#125Funniest part? I KNEW it had to have picture of Samuel L. Jackson on the page.
Bingo!
Damn I love satire. I've always said we can say more through satire in ten words than we can with reasoned argument in a thousand. As long as it's not overdone.
To Thomas' point, yes, the author of this piece socially-engineered the hell out of it. But that's okay. I can deal with one of these made-for-hn pieces every week or so.
Not more than that.
There's an important point here that outsiders consistently forget: it's tough to be a programmer. It's tough, and the people who are trying to help us many times are just huge pains in the ass. They say one thing and mean something else entirely.
One of my favorite things as somebody who tries to help teams is when I tell management what's needed: more team control, less micromanagement, more freedom to experiment with various things to see what works (and not only the things in the book). Most times they look at me and say "We absolutely want to get better! Just don't change anything"
Their idea of "agile" is 1) doing the same old thing but sticking a new label on it, or 2) following some recipe from a book or a seminar and not giving a crap about what the actual developers are saying.
We need to make these jokes. We need to keep bringing this up. I don't think folks are listening. But the page is also pandering, so it's a close call.
Re: undefined
#126Is this really #1? Like, is it really the most important thing I can read today?
Having read it: no, no it's not.
I agree with the ideology: it would be better if programmers instead of managers made decisions, but I don't think this piece expresses that very well. It also seems that the only reason this submission is at the top is that it uses "shocking" profanity associated with incest. I'm unimpressed.
Re: undefined
#127By the way, I fucking heard that if you fucking abuse the shittyfucking cursewords, they fucking lose their motherfucking value. (This is gonna cost me some points, I am sure)
Yeah. If inflation gets out of control, you have to make up new ones. "That vishal meeting was a meepish waste of time!"
Re: undefined
#128Earlier quoted context omitted.
If it wasn't plain as day that Zed was serious about this, (a) I wouldn't be voted as high as it was, and (b) I wouldn't have commented on it. I just wish he hadn't built a caricature.
Yeah, I'm totally serious about it with that picture of Samuel L. Jackson right at the top. Totally dead serious. Going to start the conference tomorrow.
Apart from the picture of Sam Jackson and some but not all of the words "motherfucker" on this page, which part of this post do you not believe?
Note: we're just nerding out. I'm reacting to your attempt to imply that that this is entirely or even mostly a joke. I don't really care. And, like I said, to the extent that it's not a joke, I agree with it.
Re: undefined
#129Re: undefined
#130I enjoy when Zed is appropriately flippant (irony intended). While, I don't have experience working for any teams that consider "XP, Scrum, Kanban, Waterfall," etc, to be gospel, I can see that being more than "fucking" annoying. That being said, I can see some people who haven't tried these methodologies as immediately devaluing them. Don't do that. As long as you don't view the methodologies as a silver bullet they…
In all seriousness, all of the methodologies out there start out being used by some group of programmers. At this phase they're fairly successful since it's mostly programmers writing code and very little management overhead from non-programmers. Eventually though, all of the advocates of these methodologies realize that it's management that buys what they're selling. Management buys the books, hires the consultants,…
Agreed. Furthermore, I would say that's true of most things requiring a lot of experience
The people who come up with the methodologies initially are probably the people who have needed them the most / longest. They had experience that informed the development of the methodologies not methodologies that substituted for experience. Therefore, these methodologies are more successful given people who could figure out a similar methodology independently and could conceivably be worse than nothing for people who couldn't.