Activity for jbrains.ca

I just drafted 1400 words about mock objects (and why you might struggle with them) that have been trying to get out for a long time now. These words might see the light of day, but members of The jbrains Experience are reading them now. ;) experience.jbrains.ca

WAT. blog.thecodewhisperer.com/permalink/a-...

If you believe you can help, then please ping me and let's figure out the details. BTW, if there is a chance to do something live and in person with a client in the area, so much the better. 😉

I will be in between cities and therefore looking for office space to use (and I don't expect it donated, although I would appreciate it if it were easy for you) to run the session. I merely need an internet connexion and a reasonable audio environment. Nothing elaborate.

I'm looking for Ottawa/Gatineau folks willing to help me with some office space. I am thinking of scheduling a remote workshop that would run 2 hours on 2 consecutive days, particularly May 12 and 13.

This is the work I wanted to do when I redesigned The jbrains Experience five years ago. It's happening. 💪 💜 experience.jbrains.ca

And for discussions in which we can confidently and openly acknowledge what's going on and even who bears responsibility for it and even explaining why that's happening, all without needing to assign blame and feel superior.

I feel so grateful again today to spend time in frank discussions with caring people who have genuine problems who want to go beyond blaming people for those problems.

It's a little thing, but when you can't figure out which window you need, you need to set the window title using a`tmux` configuration setting you barely understand. Everyone starts somewhere. https://jb.rainsberger.ca/permalink/byobu-session-name-in-terminal-window-title

Next step: use approvals.bash to run a suite of tests. 1. Install approvals.bash. 2. Run the commands as tests. 3. Diff each result with its expected.txt, then approve it. Now you can run all your tests with a single command.

Fixed a detect and accidentally added a feature. #realgitcommitmessages

Unit tests don't merely run more quickly because they execute a smaller part of the system. They eliminate irrelevant details, which makes spotting the mistake less expensive. #softwaretesting #softwaredesign

For some folks, yes. On the surface, #GTD makes you feel scattered in like this. Below the surface, I believe #GTD is asking you to confront the impossibility of making simultaneous progress on a million little projects and to learn to see ideas as options and not as obligations.

"I hate planning meetings!" Maybe. Maybe it would help if you saw people actually _planning_: - changing the plan to reflect changing reality - taking our anxiety seriously about missing deadlines - figuring out what to say "No" to, then actually saying it What do you think?

Glow Sticks Are Cheap On Amazon #ExcellentTourName /cc @kathleenmadigan.bsky.social

It would probably be a mistake for GTD to impose some WIP Limit on projects, because each person's capacity is different and it changes over time. Instead, it makes sense to me for GTD to provide the information about exceeding your capacity, so that you _actually_ confront the situation.

I don't think GTD, nor any productivity system, can tell you which projects to stop doing. Such a system can only make it clear to you that you need to stop doing some projects, you need to reverse some commitments, and so on.

Thank you. I think it happens like this: 1. You enumerate your projects and actions clearly. 2. You discover that you have Too Much To Do and that new requests are still arriving. 3. You are forced to confront the actual limits of your capacity.