"There are always a handful of resources who..."
People.
Are.
Not.
Resources.
Remote
Clark Rasmussen
@clarkjrasmussen@phpc.social
mastodon 4.7.3Words. Code. Art.
Father. Husband to @codecraftscraic@phpc.social. I talk hockey as @detroithockeynet@social.detroit.hockey and puzzles as @getsopuzzled@social.sopuzzled.com and @wearesopuzzled@social.sopuzzled.com. This is for everything else. he/him
0 Followers
0 Following
6 Posts
Joined November 10, 2022
Website:
Replying to
And, maybe more importantly, why would they trust that? I just got done telling them I was certain that it would work and now they want to hear - with certainty - what we'll do if it doesn't? That makes no sense to me.
"If Product wrote a story that Engineering doesn't like, just re-write it and do it that way" is a disappointingly toxic eng-centric way of looking at the SDLC.
Replying to
@stevegrunwell@phpc.social Yeah, I ended up switching it to something like "We will try to fix forward. If necessary, this change is safe to roll back."
The process just bothers me. There was also pushback on why the work was done in the first place. It's been on our board for weeks, it's been code reviewed and QAed. *Now* you want to debate the necessity and the specific language about what we'll do if the thing we don't think will happen happens?
Replying to
@stevegrunwell@phpc.social We've got what can charitably be called an "old-school" relationship between Eng and Product so our board is often used as a way for Eng to override Product decisions. Weaponized friction.