4 ms·

Agile software development practices. Nobody created a user story for 'respect user's settings during upgrades'. If I had to guess, the settings were renamed/

Agile software development practices. Nobody created a user story for 'respect user's settings during upgrades'. If I had to guess, the settings were renamed/refactored and default values were enabled by default. Or perhaps the 'system upgrade service' doesn't talk to the 'system user setting services' and has no way to discover those settings. There's so many innovative ways to write terrible software, Microsoft is truly a pioneer in this area.

sls 8y ago
.
- linuxftw 8y ago
  Come'on I was taking a shot at dogmatic agile beliefs and Microsoft in one swing! I mean to say that strict adherence to 'agile' without qualified engineers and management results in obvious features missing because the left hand isn't talking to the right hand. The jab at Microsoft is to imply they employ such a detrimental process because it's the only conceivable way to arrive at such a poor quality product. I don't think Microsoft is engaging in what it believes is predatory behavior, I'm confident that someone in a suit somewhere is cooking up all these 'good ideas' about collecting 'metrics' and their underlings faithfully implement these 'good ideas.' Their behavior is bad, I don't condone it. I also don't use Microsoft products (see username).
- Forge36 8y ago
  Let's phrase it differently: agile causes two teams to desync. If for whatever reason to teams become siloed and are agile: if their sprints don't line up, then requirement thrashing causes agile hell. A needs Y B is working on X Given timelines: B must quickly switch to Y or A must implement it without support from B. The biggest problem I have with software development is coordinating 100 TEAMs to operate on the same page (I own a library of interesting and old functionality at my company). This happens on occasion, without someone to reign in affected parties: things rot faster from be features than can be managed

sls 8y ago

linuxftw 8y ago
Come'on I was taking a shot at dogmatic agile beliefs and Microsoft in one swing! I mean to say that strict adherence to 'agile' without qualified engineers and management results in obvious features missing because the left hand isn't talking to the right hand. The jab at Microsoft is to imply they employ such a detrimental process because it's the only conceivable way to arrive at such a poor quality product. I don't think Microsoft is engaging in what it believes is predatory behavior, I'm confident that someone in a suit somewhere is cooking up all these 'good ideas' about collecting 'metrics' and their underlings faithfully implement these 'good ideas.' Their behavior is bad, I don't condone it. I also don't use Microsoft products (see username).
Forge36 8y ago
Let's phrase it differently: agile causes two teams to desync. If for whatever reason to teams become siloed and are agile: if their sprints don't line up, then requirement thrashing causes agile hell. A needs Y B is working on X Given timelines: B must quickly switch to Y or A must implement it without support from B. The biggest problem I have with software development is coordinating 100 TEAMs to operate on the same page (I own a library of interesting and old functionality at my company). This happens on occasion, without someone to reign in affected parties: things rot faster from be features than can be managed