☕ J. B. Rainsberger at jbrains at mastodon.social Profile picture
(he) Swede in a Canadian body. Pro 5-pin Bowler. Trusted adviser to software professionals. Barista. Friend. Never blue check. https://t.co/bUTUiacwTi | https://t.co/RJiohbW2yH
Jul 28, 2022 8 tweets 2 min read
"What should we do if we're in the middle of a story/feature when the iteration ends?"

I'm not sure yet. I'd typically hide the work in process somehow from users and then plan the next iteration as usual.

What does it mean for you to do this? Does it bother you? Why? If you want to count partial story points towards your velocity, then you might have some dysfunction regarding estimates as commitments. That's complex, but worth delving into. Slicing stories more finely acts as a decent coping/defence mechanism... as a start.
Jul 28, 2022 4 tweets 1 min read
I'm refactoring some code that I did not write.

I just found some code that never _quite_ worked. Fortunately, I found it relatively easy to fix.

Golden Master makes this much less painful. With a static web site generator, put the generated HTML in git temporarily.

(1/2) Commit code changes as usual. If any build changes the generated HTML in a way that is acceptable, commit that separately with [DELETE ME] in the message.

`git diff` makes it easy to detect changes that disrupt the generated HTML. This is my pool of change detectors.

(2/3)
Jun 7, 2020 9 tweets 7 min read
@ThisIsFlorianK @overstood @allenholub The video might have some ideas to help you with your selling. Regarding a step-by-step tutorial:

1. Do not try to "sell XP".
2. Read _The New Strategic Selling_.
3. Read _Secrets of Consulting_.

:) @ThisIsFlorianK @overstood @allenholub More seriously, it depends how you think about "selling". I think of it as working to match what they need to what I can offer them, then asking for money to do the work. I consider it my responsibility to understand what they need and to evaluate how well it matches what I have.
Nov 6, 2019 15 tweets 4 min read
I can answer the questions from my talk at @jaxcon today. There were only two. @jaxcon "Can you recommend a book on evolutionary design?"

I can recommend a few. You can probably feel comfortable starting with any of them.

- Beck, _Test-Driven Development: By Example_
- Koskela, _Test-Driven_
- Jeffries, _Extreme Programming Adventures in C#_
Oct 26, 2018 4 tweets 2 min read
@RonJeffries I presume the #Agile Indu$trial Complex includes the people who roughly do this:

- "You should do these impossible things that feel weird and look silly."
- "We're not going to do that."
- "OK, then you won't succeed."
- "How do you know?"
- "...."

/1
@RonJeffries Or maybe they do roughly this:

- "You should do these difficult things that feels weird and look silly."
- "OK, show us."
- (Shows them.)
- "Wow, that seems difficult, feels weird, and looks silly."
- "I know. Good luck. Here's my invoice."

/2