This reminds me of the Diátaxis framework [0], which has a nice visual representation of the different types of documentation.
They have a fourth type they call "Explanation" that's "Here's why we made the flaps behave this way, and how that relates to the theory of aerodynamics"
Not parent, but let's take each side's numbers at face value:
The Gaza Ministry of Health says as of today that 35,562 people have been killed [0].
The Israeli Ministry of Defense in March said it has killed 13,000 Hamas operatives [1].
Leaving aside the two month gap between these figures, the civilian casualty ratio is 1:1.7.
I tried to find a source for what a "typical" casualty ratio is in urban conflicts. This source [2] claims that 90% of overall casualties is a typical number. That would be a ratio of 1:9.
John Spencer, who chairs the Modern Warfare Institute at USMA, and seems to be an authority on the subject, has a tweet addressing this specifically [3], in which he cites the Battles of Mosul, and Manila as having casualty rates of 1:2.5, 1:6 respectively.
I don't think proving the negative of "lowest civilian casualty rate in modern history" is feasible, but a nearly 5x improvement in civilian casualties compared to the assumed norm, and lower civilian casualties than Spencer's comparisons seems to indicate that the claim is not without merit.
It’s hard to believe those numbers when (according to anonymous Israeli military officers) the Israelis are willing to routinely accept civilian casualties of 20 to 1. https://www.972mag.com/lavender-ai-israeli-army-gaza/
Neither the Gaza Ministry of Health, nor the armed wing of Hamas have released the number of combatant casualties, leaving the IDF's number as the only estimate available. If that estimate is incorrect, they could and should challenge it by putting forth their own.
The source you provided says "for every junior Hamas operative that Lavender marked, it was permissible to kill up to 15 or 20 civilians". This is clearly an upper bound, and makes no claim about how close to this they actually come.
In the same way, I might offer my customers an SLA of two nines in their contract, but never drop below three in practice. Part of effective planning is describing the worst case scenario, but that doesn't imply it will actually happen.
Neither the Gaza Ministry of Health, nor the armed wing of Hamas have released the number of combatant casualties, leaving the IDF's number as the only estimate available. If that estimate is incorrect, they could and should challenge it by putting forth their own.
Modern History is already quite good compared to the entirety of history. The bog standard Siege of La Rochelle ended up starving the civilian population of 27,000 to 5,000. War is brutal, and when you dealing with brutal enemies like Hamas it's never going to an orderly affair.
I have a standard bike bell mounted to the back of my seat post. It took a bit of practice to be able to find the lever while riding, but it works quite well, and has helped me avoid more than a few collisions.
That's a really good idea! I could also see one being mounted under the front of the seat being a convenient place to reach -- but maybe just a handheld bell (maybe one that strapped to ones' fingers?) would be best.
> I have always said that commercial dating apps have the wrong incentives.
What if commercial dating apps actually had their incentives aligned with their users?
I'm imagining an open clearinghouse of profiles that can be be consumed by multiple apps. The owner of each profile puts up a bounty. When a app proposes a match that causes the owner to go inactive for more than say a month, the app claims that bounty.
Obviously, there's some details missing here, but directionally, this incentivizes apps to propose good matches, so they can claim the money. It also allows head-to-head competition, forcing the whole market to improve.
Mount Washington sits at the end of a long, wide east-west running valley, in an area with predominantly western winds. This gives the wind an unusually long "fetch" to build strength over.
That, combined with the orographic lift as the air flows over the mountain, leads to unusually strong winds.
In that field, it seems typical to have both engineers and technicians working on projects. Engineers are responsible for design, and have degrees; Technicians do assembly and maintenance, and only need on-the-job training.
I’ve often wondered what our industry would look like if we adopted a similar distinction. In which case, bootcamp graduates would be a natural fit for a technician role.
The difference is that mechanical engineers need math to understand what they are doing. Engineers are essentially applied mathematicians. They are responsible for design because you cannot design without math.
For software development, you don't need math. This may change when data science is taken more serious and companies have to guarantee the quality of the derived knowledge. So it's the other way round. When our industry changes, we will adopt a similar distinction.
Software doesn't need math because testing is enough.
Unlike physical objects, it doesn't cost much to test software, especially because reproduction is almost free. Additionally, with SaaS, software doesn't run unsupervised and thus there is constant testing. In that environment software can almost always be adjusted and reproduced when there are problems.
This is an interesting idea, but I wonder what the effects would be on smaller or newer platforms. Would it cost say $5 for a post on Facebook, but only $1 for a post on my neighborhood's Nextdoor?
FWIW, I did some thinking about this general problem a while back, and my best idea so far is to make content artificially scarce, by limiting the number of users that can see a given post in a given period.
This has the nice property of not requiring expensive moderation, complex algorithms, or (as is the proposal here) usage charges.
Patientco | Engineering Manager, UX Designer | Atlanta | ONSITE
Patientco is the consumer payments experience for healthcare. We design easy to use technology that eliminates the pain points around paying healthcare bills.
We're looking for an engineering manager who will lead the team that builds products millions of patients use every day.
You will be:
* Managing three mid-level full-stack software engineers
* Writing and reviewing code
You'll be working with a state-of-the art Kubernetes-based microservice architecture, deploying code dozens of times a day, in several languages, including PHP, Javascript (AngularJS) and Golang.
They have a fourth type they call "Explanation" that's "Here's why we made the flaps behave this way, and how that relates to the theory of aerodynamics"
[0] https://diataxis.fr/