It’s 2023, why does your language have semicolons at all?
Explicitly constructing your intentions are features of a language.
I LOVE types. I LOVE semi colons. I LOVE compiler errors.
Why? Because the ALTERNATIVE is finding (if you’re lucky) unexpected behaviour at run-time.
I promise, I promise SO HARD, that memes about semi colons or “my code doesn’t compile” are GREAT problems to have.if that’s what’s making you sad, your life is good and you’re getting paid 10x too much.
Sometimes. Sometimes it’s just “I can refactor this to use X pattern”. Or “I COULD push X logic to some other layer”
Yeah exactly. I think you hit the nail on the head with the “(and never look at it again)”.
It’s not explicit in the meme. “Not doing it” and “never look at it” are totally different things… But I think you’ll fill it in based on your personal experience.
I’m sorry your backlog doesn’t get regularly revisited.
If I were you, I’d push for setting aside time to get it under control.
If your backlog is gigantic, I expect there will be pushback just because once the problem gets sufficiently large nobody is brave enough to broach it.
But, you can apply story slicing skills to these kinds of problems too. Break it down into smaller bits with clear and realistic objectives. Setting aside 30 minutes with the goal of, say, picking 5 items on your backlog that you know you won’t ever do because they’re super low value? Pick 5 items and close them off as won’t do. Baby steps.
I’m the Sr. Dev in this meme.
I usually just do this when a jr has fallen in love with a piece of work and wants to keep polishing it. They start to confuse “I could do X” with “I should do X”… And confuse “less than perfect but still acceptable” with “bug”.
I tell them to slap it on the backlog and to move on.
We have backlog grooming meetings every few weeks. If they still actually want to do it, we can talk, but like 19 times out of 20 they’ve found a new shiny rock by then anyways, and we’re now in a position where we can both agree it isn’t a good use of our time, and close it out as a “will not do”.
You don’t need aggressive POs or scrum masters to operate as a pragmatic team. I far prefer having a lean overhead. When there are more people shouting directions than people actually coding you’ve got too many cooks.
Oof, owuchie, my segfault
You think that’s bad, just wait until you hear what C does
No it’s our retrospective meeting to evaluate our learnings from our meeting where we planned our planning meeting.
Not ADHD, AGILE. The 1-2 hours between ceremonies is all you have left.
I think the part that you need to think through carefully is how moderation policies may differ between communities or even instances. And there are a ton of reasons you might want to not subject users by default to comments from another (eg, a community aimed at a topic with “PG” comment moderation mixing with a similar community that is targeted more towards adults).
So, keeping in mind that the “social contract” of allowing community members to remain protected by the community rules that they signed up for should be something that can be preserved.
Not out of reach, though. Opt-in to per community xposts. Filter out by first non-allowed-community comment per comment thread. For sure do-able.
Just important to consider why we have communities in the first place and to consider the different types of stakeholders.
I use 8, but only when I’m operating on unsigned longs.