Queso2469

Matthew "Queso" Niederberger

@Queso2469

Game programmer, designer, director; retired quadball player; antimeme; radical descriptivist; antilabel; Moose;

Working at Muse Games. Directed Embr, worked on Wildmender and Guns of Icarus, Making new secret stuffs

Opinions are everyone else's

log inask
Queso2469
@Queso2469
dukecarge
@dukecarge
eniko
@eniko

normal person:
this product needs a better interface

engineers, for some fucking reason:
this product needs a better interface story

eniko
@eniko

idk man maybe stop being so scrumbrained and jirapilled

Queso2469
@Queso2469

Agile Manifesto: The most important things are individuals, interactions, working software, collaboration, and responding to change. All process, tooling, documentation, and planning is entirely subservient to those ideals.

People that have learned "agile": Agile is when you use a very rigid process using extremely specific tools to compress all problems, interactions, and planning into a single abstracted workflow that we apply without thought to all problem sets.

You must log in to comment.

in reply to @eniko's post:

mullr
@mullr

Didn't used to be like this. But then our bosses hired a bunch of people to tell us that we need to be writing "user stories" of just writing down what the thing should do. And we really, honestly tried, at least some of us. Gave it a serious shot. It didn't seem to change much, tbqh.

But now it's just words that people say, and "write down a user story" means the same thing as "write down what it should do", except it also comes with the asterisk "I reserve the right to decide that you wrote it down without filling out the right mad-libs, and make you do it again."

In short, it may be the engineers doing it, but I don't think it's our fault.

login to reply
mullr
@mullr

.... it occurs to me that you may be railing against a different usage of the word Story. Ah well, what is the Internet for if not leaving unhinged rants in the comment threads of unrelated posts?

login to reply

in reply to @eniko's post:

gull
@gull

looked it up. this just seems... silly? its basically just "hey we should try to have stuff that does [x]" but stuffed in the mouth of a hypothetical end-user who really wants [x], and like... is it not enough to say that you should just aim to be able to [x]

login to reply
KindestWeapon
@KindestWeapon

Hiring non-devs to be scrum masters is a mistake. They take the fake training that costs $500 or whatever and feel like they need to use the verbiage exactly. Whereas when I'm on a team where the scrum master was me or another dev, it's way more human sounding and tasks are more intuitively organized and spelled out. It's just wild how much of a cult has been built up around it.

login to reply
KindestWeapon
@KindestWeapon

Yep. And the big problem is this is all younger devs know. So if they end up at a company that uses the terminology and get lost in the sauce of it all, then they legit do not know any better. A lot of younger devs also love to apply agile development to projects that are inherently not agile. Not their fault, sometimes corporate shoves it into their brain. Sometimes corporate lets go of all their experienced staff/the experienced staff leave for a better place and they are replaced with fresh out of school peeps who are not paid nearly enough, but no one is around to tell them otherwise or mentor them.

Really ruining a generation of developers.

login to reply