Maybe it's established in case law that this is 40 for a salaried worker? (I'm not a michigan employment lawyer). I wonder if a draft of this proposed hardcoding it at 40 and they had a reason not to?
> The judiciary opposes measures that shift the costs of providing access to PACER to litigants filing cases in federal courts, unduly hindering access to justice
That's their response to the open courts act of 2021, which would have made pacer free.
As a user of both courtlistener and pacer, I mostly believe freelaw can deliver a better cheaper equivalent than what exists, even including the submission systems. (With the caveat that I have used state court e-file systems but only briefly touched the federal ones).
If pacer revenue is paying the filing clerks, I probably feel differently; clerks are necessary components of the system who cannot be replaced by technology today.
courtlistener is providing a much better service at no cost to the public through donations; it's reasonable to say 'govt is required to feed new data to courtlistener and friends', gov doesn't have to operate pacer anymore, everyone is happy
It's not everyone, but thoughtful managers do think beyond themselves.
They know they will outlast some of their reports, so they're incentivized to build memory and maintainability at the levels below them.
And good managers get promoted, i.e. leave the team but stay in the company, so there's a reputational incentive to leave things in a good place for whoever comes after you. (Though this is only true at good orgs -- at bad orgs, the next person will get fully blamed for a bad handoff).
The best leaders have values that transcend their bank account, and understand their legacy depends on being able to transition effectively.
Your career and relationships transcend any single gig, and there is a dignity that people recognize in departing well, and even in making the best of a bad job. Campground rule, leave things better than you found them.
Hopefully we get more ergonomic ways to do this? Like of the tools listed in the post, dafny + iris are the closest to being industrial I think. And amzn S3 has a history of TLA use in-house I think. But we probably haven't seen the typescript in this space yet, a zero cost abstraction that drops into existing tools, and people genuinely prefer it to the old way.
(And custom linters are also still pretty bad to write. Like golangci-lint is a painful codebase, haven't tried semgrep but the rules engine seemed intimidating. I've yet to use an AST API that I liked)
been exploring clickhouse and while it is definitely not a general purpose DB, for time-series shaped data that can survive some insert latency, the automatic partition-based TTL is very nice and, at least so far, requires zero attention to maintain
which I guess is solved by `pg_partman` at the bottom of the post
yeah -- have been playing with this as well, ai's spatial reasoning is not quite there yet but with precise construction instructions it can often do the job
for shapes that are hard to print with a traditional slicer, LLMs are also surprisingly good at generating gcode with fullcontrolxyz if you're specific