sillyquiet
You are only safe when you don't have bosses and all responsibility and power rests on yourself.
In other words that argument depends on the available evidence rather than speculation, like, you know, how science should be done.
https://twitter.com/KristerVasshus/status/161523653168960716...
https://twitter.com/Kristel_Zilmer/status/161546218260654080...
I also recommend Jackson Crawford's video on the subject as well:
https://www.youtube.com/watch?v=X_m2xcoU9Q0
He also had an in-depth interview with Krister Vasshus on his Patreon which will probably be on his You-Tube channel eventually.
So tldr; some people in a private focus group questioned the value of a 1/3 pound burger over the same priced 1/4 pound burger. It's not indicative of any system numerical illiteracy.
I will add there were no actual data released - it's solely based on an anecdote from a A&W restaurant executive.
https://skeptics.stackexchange.com/questions/28745/did-aw-cu...
Note it's not useful in all (most?) scenarios or in all stages of a product's development.
When you are in support mode for a product that's stable, standing up something from scratch, working on a POC or experimenting with frameworks or libraries - it's not useful, use kanban or something else.
But when you are working on a/b tests or adding features to an existing product it's extremely useful.
When done correctly: You get a two-way promise between leadership and a dev team. The dev team commits to getting stuff done within that <sprint-length> time - therefore they must carefully decompose work where that makes sense. Leadership commits to LEAVING THE DEV TEAM ALONE for that <sprint-length> time - no priority changes, no "Product Manager Chad had a dream if we implement X we get 1000% more revenue!", none of that nonsense. This means for bigger efforts, you get <sprint-length> chunks of working code "done" at time. This in practice means the devs drive how much they can get done in a certain amount of time - if a PM wants an earlier date out the door, that's <x> fewer sprints of decomposed work that gets done.
The tricky thing here is the use of the term "correctly" above. Sprint-based methodology isn't a tool for management to dictate or predict performance and it's not a tool to micromanage tasking. If leadership DOES have this distorted view of it, then it is useless overhead to no benefit for anybody.
It's also not useful at all if only the dev teams practice it - everybody has to respect the commitments required to do sprint correctly - if they don't, use kanban or something else.
This is a weird take.
1. old folks getting joint replacements 2. young athletes 3. middle aged construction workers or laborers
Pull quotes from the summary: "Cat bones from many trading centres show cut marks from skinning and highlight the value of cat fur. In contrast, the occurrence of cats in male burials points rather to a function as exotic and prestigious pets. "
As a Gen-Xer, I don't know how many times I read similar things growing up about my own generation, except it was metal or hair bands or glam rockers that garnered the worry.
I would have KILLED for some of the robotics and electronics kits that are widespread today.
"We conclude that it is impossible to say that taking SSRI antidepressants is worthwhile, or even completely safe. People need all this information to make informed decisions about whether or not to take antidepressants."
Which makes sense, given working in embedded hardware (especially in classified contexts) back then came with a lot of the same limitations described in the article - software had to be delivered by sneaker-net, installation was burdensome, you couldn't just fire up the application for a quick bug fix at home, etc. Not to mention the inertia of having Always Done It That Way.
Maybe! A well tailored and properly weight-distributed mail hauberk (which is also conformal) is surprisingly comfortable for extended period of time in all kinds of weather. (Source: my own experience in medieval re-enactment). What gets you in hot weather are the textiles - with mail its the necessary padding under the mail that will cause issues in hot weather.
the author's point that linen was more comfortable than 'rigid' armor was probably true, but I will point out that rigid armors were also individually tailored, balanced, and created for optimal weight distribution.
As an aside mail armor was a successful and popular armor for a millennium, from the Iron Age to the middle ages (and continued to be successful as an augment to plate and in other contexts like South Asia and India until probably the 16th century). It was probably contemporary to the linen armor of the article (In time, not geographically - it was used most heavily in iron-rich regions in central Europe at first).
I wonder if this also what led to the increase in other steel furniture like file cabinets, desks, chairs, etc in the 50s and 60s.
I don't know if anybody else ever sat at one, but the massive steel desks the government used in the 50s and 60s in offices and labs were built like tanks, and probably weighed as much.
The U.S., although gaining steam economically (pun intended), was still a backwater, rural, nation isolated by a whole lot of ocean (edit: I meant all this from a military point of view). I am sure the abolitionists in power in Parliament were interested in the outcome of the war from that point of view, but it was really of very little consequence to UK or Europe as a whole.