decohen

For me, it was really the water that was problematic, as opposed to the food.

On my first visit, I was careful about the water I drank, but not very careful about other ingestion, and I got TD about halfway through the trip.

On the next visit, I was careful to keep my mouth closed while showering, and only use bottled water to clean my toothbrush, etc. Everyone else on the trip, eating the same food, got sick, but I didn't.

This is of course anecdata, but generally food, especially cooked food, is more likely to be safe.

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.

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.

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.

> 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.

Does this support loading nested models? Lack of this has been a huge pain point with other DB tooling for Go.

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.

Several of my relatives are Mechanical Engineers.

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.