In a 1-on-1 session with a client, I'm reminded about when precise technique becomes important.
When you work on code that feels familiar to you, then you can follow your intuition more often, allow yourself to be distracted more, and generally this will not hurt you as much. This happens because you see more of what you expect.
=> More informations about this toot | More toots from jbrains@mastodon.social
When you work on code not familiar to you, then you are more easily confused, spend more time struggling to figure things out, and feel more stress from experiencing things that shouldn't happen and situations that feel like they take you away from your goals.
In those moments, precise technique creates safety.
=> More informations about this toot | More toots from jbrains@mastodon.social
Today, we struggled to write even a single automated test, but we used the Saff Squeeze, anyway. And it was hard to stay on task, because we're looking at all this production code and noticing all these things that we don't like... but the Saff Squeeze gives us two simple goals:
=> More informations about this toot | More toots from jbrains@mastodon.social
Even when we're struggling with manual tests and printfs, we can stay on task more easily with a single goal.
And, of course, I help my client by letting them run wild through the forest while I carefully write things down, since I have no idea what might be relevant in the next 30 minutes. And, for a few moments at the end, when we reflect, we reflect on the value of writing things done.
And if they write a few more things down next time, then I feel like I've helped.
https://experience.jbrains.ca
=> More informations about this toot | More toots from jbrains@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini