I've given up on soft delete -- the nail in the coffin for me was my customers' legal requirements that data is fully deleted, not archived. It never worked that well anyways. I never had a successful restore from a large set of soft-deleted rows.
> customers' legal requirements that data is fully deleted
Strange. I've only ever heard of legal requirements preventing deletion of things you'd expect could be fully deleted (in case they're needed as evidence at trial or something).
While not common, regulations requiring a hard delete do exist in some fields even in the US. The ones I familiar with are effectively "anti-retention" laws that mandate data must be removed from the system after some specified period of time e.g. all data in the system is deleted no more than 90 days after insertion. This allows compliance to be automated.
The data subject to the regulation had a high potential for abuse. Automated anti-retention limits the risk and potential damage.
You're thinking of "legal requirements" as requirements that the law insists upon rather than requirements that your legal department insists upon. You often want to delete records unrecoverably as soon as legally possible; it's likely why you wrote your data retention policy.
I had an integration with a 3rd party where their legal contract required we hard delete any data from them after a year. Presumably so we couldn't build a competing product using their dataset with full history.
Maybe the best part of this legislation will be that people will realize it's not institutional investors that are driving up home prices. No, that's far too optimistic.
Home affordability is getting better anyways, which is great, because we are finally having a surge in new & denser home building in popular regions and there mortgage rates are more reasonable than they were in the COVID-era.
It's not debouncing, it's delaying. Ideally you can still update a specific dependency to a more up to date version if it turns out an old version has a vulnerability.
There are some good reasons it is lower now, like defense lawyers and Miranda rights. Obviously it'd be good if we had both good civil rights AND high murder clearance, but they seem in obvious tension with each other.
If you haven't, give Cursor's Composer model a shot. It might not be quite as good as the top models, but in my experience it's almost as good, and the lightning fast feedback is more than worth the tradeoff. You can give it a task, wait ten seconds, and evaluate the results. It's quite common for it to not be good enough, but no worse than Sonnet, and if it doesn't work you just wasted 30 seconds instead of 10 minutes.
Is this goal documented by the Department of War somewhere? Or are you guessing that there has to be a strategic reason for what seems quite wasteful. It sure seems like there's more efficient ways to achieve this goal.
What would you suggest as a more efficient way to achieve this goal? Building thousands of advanced fighter jets for private citizens? Keeping highly skilled engineers up to date on the most modern technologies and maintaining specialized factories is inherently expensive. You can't leave the factories mothballed because you need to keep the skilled workers employed and practiced with manufacturing.
Maybe there could be something like a weekend warriors but for machinists? One weekend a month, one week a year you build fighter jets. This does mean there needs to be private sector demand for those skillsets so the reservists have relevant day jobs.
Have legitimately successful aerospace companies that sell to other places, and create dual-use industries like autonomous driving with more DARPA challenge type stuff
This is messy. The countries that could afford to buy the jets generally have domestic industries they want to protect, and you never know when some President will come into power that is hostile to that country and tells the contractors to stop supporting that very expensive hardware. There is precedent for this: See Iran's fleet of F-14s.
reply