News for hackers. Stuff that matters.
Re:How product teams should set deadlines by metadat on Monday May 02, 2022 @11:03PM (#31244001)
"should" is a pretty poor choice of wording, and best to avoid using in nearly all cases. Why should we consider to this opinion? Given the crappy title, why should one even bother clicking on the link?

Sorry, it's intended as a personal criticism (in fact, my intention is the opposite!), but the decision sets the stage for quite a weak and unpersuasive argument.

Re:How product teams should set deadlines by kadoban on Monday May 02, 2022 @11:43PM (#31244300)
> why should one even bother clicking on the link?

You can't even avoid using the word in your admonition against using the word though. What's better phrasing, and why?

Re:How product teams should set deadlines by metadat on Tuesday May 03, 2022 @12:16AM (#31244546)
I used it sarcastically, there's always a better way to say it. Use your imagination!

"How we make life better for our team by setting deadlines"

The possibilities are endless.

Re:How product teams should set deadlines by kadoban on Tuesday May 03, 2022 @12:26AM (#31244609)
> How we make life better

That's overly ambitious, and the meaning is also completely different. That says that setting deadlines itself improves life, which is not what the article or original title are saying.

> Use your imagination!

My imagination is okay with "should", when the benefits will be spelled out later, which they are in the article.

Re:How product teams should set deadlines by metadat on Tuesday May 03, 2022 @12:55AM (#31244793)
It's all good, glad it works for you. I found that for me, when I paid attention to the "shoulds" it was a bigger burden than it was worth for not much gain. Thus I learned it's best to filter them out in favor of messaging that is less preachy and more nuanced. It's a tradeoff, as inevitably I'll miss some good ones but overall it seems like a better way to allocate my attention.

Ymmv :)