Go see Weird Al. It was a really great show. My wife only knew one of his songs (Word Crimes, she's a professional editor), and she loved the show. I loved it too.
The straw that broke the camel's back is the fuel spike due to the Iran War. That drained the remaining liquidity.
No idea if the extra time "normal" fuel prices would have allowed Spirit to find a way to stay afloat, but the fuel price spike stole any time they had to figure it out.
At the center of every security situation is the question, "is the effort worth the reward?"
We prepare security measures based on the perceived effort a bad actor would need to defeat that method, along with considering the harm of the measure being defeated. We don't build Fort Knox for candy bars, it was built for gold bars.
These model advances change the equation. The effort and cost to defeat a measure goes down by an order of magnitude or more.
Things nobody would have considered to reasonably attempt are becoming possible. However. We have 2000-2020s security measures in place that will not survive the AI models of 2026+. The investment to resecure things will be massive, and won't come soon enough.
Elon has always been the face of Tesla since he acquired it from the founders. Early he was a brand asset, but tying one's identity so strongly to a company is a brand risk when that person's image is tarnished.
Just look at Martha Stewart Living during her incarceration.
Celebrities are great at building brands, but they need to back away from their personal successes have bootstrapped the new brand before something they do becomes a liability.
Subway made their own celebrity spokesperson (Jared) and hitched their wagon to him for far too long. One or two years is understandable, but Subway had him so long it merged its identity with Jared until the truth about Jared was revealed.
I want to be able to hire a licensed Identity Service Provider that gets all of my verified identity data in an encrypted token and let me register it with the OS, and control what amount of the data I expose to apps, with age verification being one of the lower levels of access.
I pay the company to verify me, I am their customer. They take on the liability of the OS makers and app makers of age verification.
If you have a valid token signed by a licensed IDS that verified your age in your OS, that's all anyone needs to know.
This is the moment, but they refuse to market the product in a way that is acceptable, (and adds affordability) to consumers.
If they would do a 55/45 beef/plant-based meat blend and burgers, I think adoption rate would pick up significantly. Anybody who questions the taste is going to see that beef is the main ingredient. If the product comes in significantly cheaper than beef alone, more consumers will try it and look to it as an affordable way of eating beef.
For the bigger picture, 65 cows will stretch as far as 100 cows previously did, lowering suffering, environmental damage, inputs, etc.
For the people who like the 55/45 blend, it would open the door to an 80/20 blend plant vs. beef, and a 100% plant-based product.
There is so much undefined in how agentic coding is going to mature. Something like what you're doing will need to be a part of it. Hopefully this makes some impressions and pushes things forward.
It's not that we are all fans of AI, it's that it's career suicide to ignore AI. If AI were gone for everybody that might be a net positive, but if it exists, it needs to get into the hands of as many as possible else wealth and power will concentrate even greater than it is now.
I already invented this in my head, thanks for not making me code it.
Excellent idea, I just wish GitHub would show notes. You also risk losing those notes if you rebase the commit they are attached to, so make sure you only attach the notes to a commit on main.
Before manufactured insulin shots, the treatment for diabetes was a multi-day oatmeal fast. This has been around for many decades. The only thing that's changed is that you are finally hearing about it.
"Utilities" is a generic term suggesting it is small, potentially reusable, purpose-limited, and used to simplify a task.
"Utilities" doesn't indicate the audience or the intended longevity of use of the tool like "houseplant" and "bouquet" do.
Both indicate they are built for personal use cases, suggesting potentially low reusability. The longevity of "houseplant" suggests it's intended for ongoing use, while "bouquet" suggests a limited use tool.
With work, either could be made reusable for others, but I think it's implied that the scope is an edge case or uncommon case that likely only applies to its creator or a very limited audience.
I see value in the terms, but these terms may themselves be houseplant terms, not sure if general adoption is useful to someone not building houseplant software, they are mostly hobbiest terms by definition.
I think it's more like, "We don't want our harness to need to be able to interpret every version of our conversation format indefinitely."