I've never worked on a codebase where using ORMs wasn't better than rolling your own queries. What are people writing that they actually need the marginal performance gains? And even if that's worth it, why not just use raw queries in your critical paths?
Every time I have to write or modify raw SQL it feels like I'm throwing away all my static checking features and increasing the chance of bugs, because I have no idea of the query matches my schema or if it'll blow up at runtime.
you can't compare it to the islands, because the GPS trace is in an area within that green circle, with a different scale. You can only look at the 300m scale in the bottom right, which looks in the ballpark of an aircraft carrier to me
The way I see it, for any code review there are going to be different levels of recommendation regarding the comments. When I review, I try to make it clear what's optional (/ nitpick) and what I'd really like to see fixed before I can approve it.
So even making some assumptions, I can't choose between 4 and 5 because optional and "less optional" changes are often in a same PR.
The only one I haven't done much of is #3. That one looks better if one has questions about code that was already reviewed, merged, and it's likely in production.
You don't need that assumption. Your assumption can just be "the person and vessel (or a point in the vessel, like its center of mass) don't diverge significantly over time".
Then, if you treat velocity as a vector and compute the person's average velocity vector over time, you'll have a pretty close estimation to the vessel's velocity vector.
After all, if those two average vectors (vessel's and person's) were to differ much, they would end up in different locations.
The average basically zeroes the vector for each lap the person does, so the remainder must be the vessel's.
yeah, I think the whole "water" argument really dilutes the case against data centers.
On a serious note, the argument works for areas that already struggle to supply enough water for consumers. Otherwise, we should be focusing more on the power stress to the grid, and the domino effect on supply chain of hardware cost increases that it's happening across many industries. It started with GPUs, now it's CPU, storage, networking equipment, and other components.
If these prices are too high for a couple of years, we'll start seeing generalized price increases as companies need to pass along the costs to consumers.
nope, opencode is better and actually open source