4 ms·

Ruby. The strongest agile proponents that I have met prefer Java. I think that's probably enough to estimate their "caliber" right off the bat. The strongest

Ruby. The strongest agile proponents that I have met prefer Java. I think that's probably enough to estimate their "caliber" right off the bat. The strongest proponents of agile that I've met use agile as an excuse for cowboy coding, though my friends and I generally refer to them as hackers, because all they do is hack things together in a big hurry. You work in "agile" environments like that for a few years, and you start to equate "agile" with "sweatshop." Since without exception every "agile" project I've worked on has been a sweatshop with an agile label, you'd be hard pressed to convince me to use agile methods for anything even vaguely related to developing software.

stcredzero 16y ago
Whatever happened to the "40 Hour Week" pillar of XP?
- Tamerlin 16y ago
  I don't think the agilistas get it -- there's too much hero worship in the industry, and the newbie developers who haven't bothered to learn how to design software that actually works play right into the hands of the legions of incompetent managers out there who still believe that lines of code and hours in seat are measures of productivity.
  - calibraxis 16y ago
    That makes sense. When I checked the Agile Manifesto, I expected to find something about a 40 hour workweek. What I found instead was something watered-down about "sustainability", which effectively means next to nothing. "Self-organizing" also is near-meaningless; it maybe means that teams won't be micromanaged (not that many managers want to deal with the most tedious issues of a team anyway), but working hours are treated as a macro issue. ("I don't know what you're doing, but you'd better do a lot of it!")
    - Tamerlin 16y ago
      I've had a number of projects in which the management complained that the developers weren't writing any code, but they refused to take the time to answer our questions about requirements. One actually said that if he was to write down the project's requirements, he might as well just write the software. (That project failed pretty impressively after I left it... I refused to bail it out a 2nd time.)
deleted 16y ago
[deleted]

stcredzero 16y ago

Whatever happened to the "40 Hour Week" pillar of XP?

Tamerlin 16y ago
I don't think the agilistas get it -- there's too much hero worship in the industry, and the newbie developers who haven't bothered to learn how to design software that actually works play right into the hands of the legions of incompetent managers out there who still believe that lines of code and hours in seat are measures of productivity.
- calibraxis 16y ago
  That makes sense. When I checked the Agile Manifesto, I expected to find something about a 40 hour workweek. What I found instead was something watered-down about "sustainability", which effectively means next to nothing. "Self-organizing" also is near-meaningless; it maybe means that teams won't be micromanaged (not that many managers want to deal with the most tedious issues of a team anyway), but working hours are treated as a macro issue. ("I don't know what you're doing, but you'd better do a lot of it!")
  - Tamerlin 16y ago
    I've had a number of projects in which the management complained that the developers weren't writing any code, but they refused to take the time to answer our questions about requirements. One actually said that if he was to write down the project's requirements, he might as well just write the software. (That project failed pretty impressively after I left it... I refused to bail it out a 2nd time.)

deleted 16y ago

[deleted]