Ah, I see how my wording was confusing. I mean planning in the sense of “How will we complete the work that we already committed to?” and “What will we do today to achieve our Sprint goal?”
I arrived at the word planning because Scrum is sometimes described as a planning-planning-feedback-feedback cycle. You plan the Sprint, you plan daily (Daily Scrums), you get feedback on your work (Sprint Review), and you get feedback on your process (Sprint Retrospective).
lol I hope your standups are not actually like this! The purpose is to, as a team, plan how to achieve a goal
I agree with you: the FSF can seem unwavering in their stance, even in the face of practicality. I’m really sorry for this incredibly nit-picky detail, but I think practicality is ideological too. For better or for worse, we can’t escape ideas or be free from them, so we have to choose which we value. For example, while I tend to choose software freedom over practicality, I also have, at times, chosen practicality over freedom.
I agree. And that’s exactly my point 😅
Pro tip: think of a bracket as an S and a 2 on top of each other. Which one is on top of which will depend on whether you’re writing an opening bracket or a closing bracket. Just try it out and you’ll see which is which.
After you try it out, as another comment pointed out, think of your 2s and Ss as surrounding a circle. That way your traces get closer to the actual shape.
Adding to what others in thread have said, there are languages that are more usable and are more user-centric. I’ll say something that’s a bit gross but makes the point clear: if you’re brave enough, anything can be a sex toy. Ergonomics matter.