![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
I’ll rephrase them, except in good faith:
-
Talking directly to the people about the work is better than a 95 state JIRA pipeline
-
Document your finished working work, not every broken POC, because that’s a waste of time
-
If the contract isn’t actually going to meet the desires of your stakeholders, negotiate one that will
-
If you realize the plan sucks, make a better plan.
My company paid to have Kent Beck come to workshop with our Sr devs. I expected to dislike him, but he won me over pretty quick.
I don’t remember what it was, but someone was like “Kent, we do X like you recommend in the manifesto, but it creates Y, and Z problem for us”
And he was like “So, in your situation it isn’t providing value?”
Guy was like “No”
“Then stop doing it.”
It’s not hard. It’s the most fucking common sense shit. I feel bad for them because these guys came from a world where there were these process bibles that people were following. So they wrote like, basically a letter saying “if your Bible doesn’t serve you, don’t follow it”
And all these businesses dummies were like “oh look, a NEW bible we can mindlessly follow”
Well the top comment was “fuck these people” so if the goal was to build broad public support it is having the opposite effect.
Alternatively, EVERYONE is cheering for those fucking Orcas, so… Imagine being dumber than a whale.