2 ms·
You make it sound as though I could do all of this up-front design and analysis work, and it would all be time well spent, and it would save time and effort in
by commandlinefan 9y ago
You make it sound as though I could do all of this up-front design and analysis work, and it would all be time well spent, and it would save time and effort in the long run, and it would produce a better end-product and the customers and my boss would be happier with the results, but I'm not doing that because... I'm just difficult that way? I'm a lazy, coddled, spoiled, petulant developer who'd rather play with his toys than put on his big-boy pants and do some real work? Pardon me while I bristle with indignation here. First of all, under the repressive regime of "agile" methodologies which demand that I: say exactly what I'm going to do and exactly how long it's going to take and provide ongoing evidence that I did exactly what I was going to do and that it took exactly how long I said it was going to take, have something to demo every single morning to prove that I wasn't wasting the whole day goofing around on Facebook, something open-ended like design is an impossible pipe dream. What does a "design" even look like? A word document? A visio diagram? A powerpoint? In this micromanaged, "I know that you programmers can accomplish any task of any difficulty of any level of lack of definition in any compressed timeline I can think of, but I know you're not doing it because you're a bunch of overeducated spoiled brats" management environment, we've gotten the message loud and clear that we had better do whatever produces what appears to be working software as fast as possible, regardless of how inefficient or anachronistic it might be because in spite of the supposed "talent shortage", every one of us is one angry boss away from unemployment and a line of skeptical prospective employers who don't care how much education or experience you have, but do you know Angular 5? Because we only use Angular 5.
- TheCoelacanth 9y agoWTF kind of Agile process is that? I've never heard of anyone having daily demos. The processes I've seen schedule them for every 2-3 weeks. If you're referring stand-up meetings, the people involved in those aren't supposed to be managers, they are supposed to be the people who you are directly working with.
- DanielBMarkham 9y agoSure. You can have daily sprints if you like --- if you know what you're doing. The rule with frameworks is this: the more time you spend thinking and screwing around with the framework, the more you're either doing it wrong or it's hurting more than helping. Scrum/Agile should just work, just like your C compiler just works. It's a tool that operates almost invisibly in the background while you make stuff people want. If it takes a long time to work with it, or you spend a lot of time fussing with it or arguing over whether you're doing it right or not? You've got something backwards somewhere. People end up with long sprints and tons of meetings either usually because they don't understand what they're doing or they're doing it the wrong way. Personally I prefer week or less sprints. Anything else tends to grow a bunch of meeting BS over time that's non-productive.
- TheCoelacanth 9y agoThat is a completely unrealistic expectation. There is no human process that "just works". People are not computers. Scrum/Agile can help competent people who want to improve get better at delivering software that is valuable to their users. No process will magically turn incompetent people with no interest in improving into a productive software team.
- DanielBMarkham 9y agoYou are misunderstanding what I'm saying. I never said the purpose of Agile/Scrum was to turn incompetent people with no interest in improving into a productive software team. That's not the goal. That was never the goal. You know, you can spend a lot of time mucking around with your C compiler also if you don't know what you're doing. The goal of your C compiler isn't to make you a programmer. It's to help people who already know how to program do it better/faster. Process doesn't replace software engineering. It takes people who already know software engineering and lets them move as quickly as possible.