Do any HN constitutional scholars or lawyers who work in adjacent fields have any comments on the ruling? Having only read the introduction (which by definition is not a comprehensive argument, so I acknowledge that I'm drawing conclusions based on an incomplete understanding of the ruling), my intuition tells me the standing sub-decision could be abused by states, and the textually oriented picking-apart of the SecEdu's stance struck me as - forgive my ignorance, but - arbitrary and borderline petulant.
FWIW, I'm _not_ interested in discussing this from a socio-political standpoint. I'm just curious to hear opinions about the ruling from a legal perspective.
I just joined a company that does formal but unpaid oncall, coming from a prior co that had implicit oncall. I'm very much in the "if you built it, you run it" camp. This said, I think:
- if oncall is a part of the gig, you compensate _somehow_ (demonstrably above market salaries, explicit extra pay, time in lieu, etc); oncall culture (or the lack thereof) should be explicitly mentioned in any hiring process and employment contracts
- the team should be striving for 8 or more engineers in the steady state; temporary vacancies should be temporary
- primary should be handling 80+% of pages in the steady state; if this is not the case on average across the team, you are not building enough resiliency into your oncall culture, or relevant tech debt should be high priority
- relatedly, kpis/incentives should be structured such that as call gets worse, progressively more immediate investments are made to address technical root causes (a la SRE error budget)
I'm tinkering with that last one my head. It's easy to say, hard to execute
How much of this is possible due to the fact that "there is no real fear of the company collapsing?" This sounds like process-resembling-waterfall, which seemingly works well because use cases, constraints, and patterns are (relatively) so well understood at an established company. Is there "edge" or value in that process, or is the value in the understanding of use-cases, constraints, and patterns (or a drive to align towards reaching said understanding) that enables the process?
I did a baby bakeoff internally in my prior role ~18mo ago now. Prefect felt nicer to write code in but perhaps not as easy to find answers in the docs (though their Slack is phenomenal). Ended up going with Prefect so I could focus on biz/ETL logic with less boilerplate, but I'm sure Dagster is not a bad choice either. Curious to hear about parent's experience
FWIW, I'm _not_ interested in discussing this from a socio-political standpoint. I'm just curious to hear opinions about the ruling from a legal perspective.