Broadly agreed. But the triangle shirtwaist factory is about as far from "my boss calls me and it's stressful" as one can get! I'm disappointed that a some activists can inflict their preference for comfort on all of us.
Ultimately companies don't exist for the employees they exist to deliver something to the customers that rely on you. Stress and uncertainty are part of work and life. Why should that come before the people you're serving?
_Some_ people _might_ want - and a very privileged something at that! This is not west virginia coal wars. Why do a handful of ideologues get to insert themselves in the employee employer relationship for something so tame?
The line of what rises to the level of "solve it with force", eg solve it with legal intervention, is understandably blurry. But in the trash example, if you indeed never agreed to it, that's already a legal issue and rightly so. This OTOH is a private aspect of the employee employer relationship and not exactly a human rights abuse like some of the pearl clutching comments here suggest
FWIW writing as someone who went through and goes through very intense on call and all hours availability and firefighting for weeks on end, something I chose voluntarily. I don't want anyone interfering with my ability to choose that and accomplish what we accomplished.
Why is this a government issue at all? It was unclear from the article why some contingent that doesn't like their relationship with their employer ought to be able to inflict their solution on everyone in Michigan via politics as the mechanism instead of the market
It sounds like this is one of the few places that might be a leaky abstraction in that queries _might_ fail and the failure might effectively be silent?
Congrats guys! Curious how the read write splitting is reliable in practice due to replication lag. Do you need to run the underlying cluster with synchronous replication?
Why is that? Personally I appreciated the throwback look and it probably accomplished its goal of being memorable. Turbopuffer is another notable one seemingly leaning into this flavor of marketing
Tight integration with the typescript tool chain has been great for us with edgeql and is about an order of magnitude less error prone than ORMs I've interacted with. Gel is a winning formula especially in the typescript world.
We used TipTap to great effect in an old iteration of our product at credal.ai. It helped us create nuanced text tagging behavior without too much time investment. Would happily recommend it.
The AI Chief of Staff had a few layers. The first was data integration of both productivity data (slack, notion etc) and "big data" lakes/warehouses. The former tells you what is getting done at a human level and the latter has the potential to tell you whether and how it is working. The second layer was modeling of your business strategy and including dependencies between concepts like projects and
teams, which allows us to back out things like stakeholders and early warning recipients for any given progress or problems. The third was a presentation layer allowing humans to get a birds' eye view of what's happening including generating artifacts like meetings decks.
Ultimately this 1) wasn't successfully solving an urgent enough problem for most businesses and 2) was too difficult to adopt.
LLMs do break open opportunities in this space so I expect to see some more versions of this, perhaps on top of the Credal API!
Thank you! We haven't gone down the Foundry route yet. We do have some smaller scale apps and companies using Credal either as their AI API or chat platform respectively - would be interested to hear a bit about your use case and see if it's a match?