And when their meetings are 100% buzz you better start distributing your CV because things are not going to last.
I was in a meeting at a company that started doing that agile horseshit. Someone mentioned "stories," which is what we used to call user scenarios. Nobody asked what it meant but they figured it out and within minutes everyo…
And when their meetings are 100% buzz you better start distributing your CV because things are not going to last.
I was in a meeting at a company that started doing that agile horseshit. Someone mentioned "stories," which is what we used to call user scenarios. Nobody asked what it meant but they figured it out and within minutes everyone was shoehorning "stories" into every sentence. Nodding vigorously, so compulsive in their conformity I wanted to vomit.
We don't need to die to go to hell. It's right here.
Scott Adams got rich with his "Dilbert" cartoons because they capture the phenomenon so precisely. I had one "peer" that I found it difficult to not refer to as Wally. There were Pointy Haired Bosses everywhere.
Those methodologies have destroyed software development. They all require tons of meetings, recurring meetings, and when you hold a meeting for no other reason than its appearance on the calendar the chance of it being any use drops to zero, along with its chances of letting out early or being canceled.
Breaking a good developer's concentration is the best way to crush his productivity and the quality of his work, so another fad, er, approach came along in which software testing is more important than writing software. "Flow" is a thing of the past and even ordinary concentration is out of reach.
I think Dilbert was out for a few years before this horrible stuff started.
And when their meetings are 100% buzz you better start distributing your CV because things are not going to last.
I was in a meeting at a company that started doing that agile horseshit. Someone mentioned "stories," which is what we used to call user scenarios. Nobody asked what it meant but they figured it out and within minutes everyone was shoehorning "stories" into every sentence. Nodding vigorously, so compulsive in their conformity I wanted to vomit.
We don't need to die to go to hell. It's right here.
Scott Adams got rich with his "Dilbert" cartoons because they capture the phenomenon so precisely. I had one "peer" that I found it difficult to not refer to as Wally. There were Pointy Haired Bosses everywhere.
Those methodologies have destroyed software development. They all require tons of meetings, recurring meetings, and when you hold a meeting for no other reason than its appearance on the calendar the chance of it being any use drops to zero, along with its chances of letting out early or being canceled.
Breaking a good developer's concentration is the best way to crush his productivity and the quality of his work, so another fad, er, approach came along in which software testing is more important than writing software. "Flow" is a thing of the past and even ordinary concentration is out of reach.
I think Dilbert was out for a few years before this horrible stuff started.