I submitted one of his past articles and it was flag-killed. His post titles may seem incendiary, but he has the credentials to back it up and seems to identify concrete opportunities without leaning into doomerism.
12,699 karma · joined February 26, 2012
I submitted one of his past articles and it was flag-killed. His post titles may seem incendiary, but he has the credentials to back it up and seems to identify concrete opportunities without leaning into doomerism.
Automative insurance has entered the “regulatory capture” stage, which is the highest form of actualization in capitalism.
We can correct this by investing in public transportation and getting rid of government-provided free parking.
This is somewhat solved problem in other areas, like banking and government. Not zero, but asymptotically low.
I think we need to criminalize misuse more clearly, preferably on a federal level. We need clear justifications for each use of data. And, we should require periodic audits by an independent third party - perhaps funded in the purchase contracts as a line item and held in reserve.
This doesn’t solve the problem of legal use - which could be contentious now or in the future. But, this technology isn’t going away and good legislation to control it makes sense.
Same model as airlines.
Get a tractor, and spend less time farming.
The factory will save time making tractors, so everybody can have one.
Computers will make the factories more efficient.
AI will make the computers more efficient.
Your PM job will be a lot more about influence and communication.
Influence is often about getting people to trust you and get the last 10% done. Prepare to spend 3 months on a very technically-difficult project, then have the CEO rip apart your demo because the copy on the first screen isn't what he expects, without every getting deeper in to the product. That's the last 10% and your job is getting your tired team to care about it.
The way decisions are made will be significantly different compared to the egalitarianism of engineering. Understanding how your organization makes decisions and adapting to it is key to success as a PM. (Consensus? Founder mode? Disagree and commit?)
Good PMs make impact and at the end of the day. Your career is almost entirely dependent on your manager's subjective opinion of your work. You'll need to learn to "manage up" - ensuring that your manager agrees with your decisions and thinks that you have had impact.
The persona that fails in PM is the pseudo-academic who was told they were smart as a kid, and can't hustle, make a decision, or sell others on their ideas. You need to be prepared for conflict.
I wonder what the implications for radar-absorbing finishes are. Could they be more aerodynamic already?
All evidence today suggests Anthropic is passing OpenAI in relative and absolute growth. So where's the critical reporting? The DOD coverage was framed around the Pentagon's decisions, not Anthropic's. And nobody seems interested in examining whether the company that branded itself as the ethical AI lab actually is one. That seems like a story worth writing.
Interesting - why?
But, for anybody else who needs a quick fix - you can pin to the `community-archive` tag and it should unblock you quickly:
https://hub.docker.com/layers/localstack/localstack/communit...
As a developer tool, integrating Stripe Projects felt a lot like adding "Sign in with Google" - Stripe acts as a trusted identity and billing provider, but for agents instead of humans. The core insight is that agent commerce is a trust problem: an agent can't (shouldn't?) enter a credit card or verify an email, so you need a trusted third party to KYC both sides. Stripe already has that relationship with both developers and customers.
It's a smooth experience overall - try it out.
I wrote more about agent experience here: https://www.philipithomas.com/agent-experience
RTOs throw off a ton of energy: https://www.youtube.com/shorts/S6nZDGBPsak
Compared to what?
People push AI-reviewed code like they wrote it. In the past, "wrote it" implies "reviewed it." With AI, that's no longer true.
I advocate for GitHub and other code review systems to add a "Require self-review" option, where people must attest that they reviewed and approved their own code. This change might seem symbolic, but it clearly sets workflows and expectations.