It would be odd to try this as copyrightable in the U.S, where there’s a pretty clear distinction between art added to a guitar, like PRS bird inlays, and the core body shape.
Similar work experience, I was with a CBS-owned music company that had a CNC machine with some old Fender Telecaster and Stratocaster body templates.
The hardware manager was cool and would let employees turn slabs of wood into Tele- and Strat-style bodies after hours.
When the Fender/German court ruling came down, my first thought was: Fender has had roughly 70 years with the Stratocaster design, and the broader industry has been making S-style guitars for decades.
Surely at some point a body shape becomes generic, right?
There's another dimension to the Salesforce CRM "build" argument; which is to reduce your 25 seats down to 5, and expend Eng resources to building "agents" to automate many recurring data-entry CRM tasks.
This is also the reason the stock has hit a 3-year low. Not because CRM can be replaced entirely. But because the seat count can be reduced 50%+.
I'd like to believe that stable state ends in a pair-programming structure, with a systems thinker/engineer and a domain expert.
Someone needs to spot when a linked list is better than a map. And the other needs to spot when clinical trial coding should happen before claims, audits, or patient outreach.
In agentic design, I keep coming back to the idea of “how easily we can compose elements”, along with Fowler’s OOP and refactoring principles.
It’s a new frontier, and there are no absolutes. But I suspect the most durable AI systems will be built around highly composable, well-orchestrated agents.
Customer: “I don’t want to pay more than $100/mo for my website”
Developer: “What are your goals?”
Customer: “1M daily visits, 1,000 monthly signups.”
And we've spent the past 25 years offering serverless compute, auto-scaling, pay-as-you-go for AWS and Internet infrastructure. And the economics are still a hard sell.
As someone working in the enterprise space with OAI, this still feels like we're in the top of the first inning.
Many teams remain anchored on equating AI with chat experiences, while a growing share of enterprise value is emerging from leasing compute clusters to run agentic workloads in containerized environments.
OpenAI has built a cloud-first architecture that supports this model. The desktop experience and applications are sexy, but enterprise usage will likely skew heavily toward asynchronous, background processing.
If I can run resume {session_id} within 30 days of a file’s latest change, there’s a strong chance I’ll continue evolving that story thread—or at least I’ve removed the friction if I choose to.
These articles are largely based on a false equivalence of LLM=moat.
That's not the case. OpenAI is advancing on many fronts; codex, vectorStore, embeddings, response API, containers, batch processing, voice-to-speech, image generation... the list goes on.
Leo knew and acknowledged his body inspirations (Bigsby and Rickenbacker), and considered his true IP to be in sound, pickups, mechanics, tremolo...
I really wish Warmoth or PRS could get some legal fee subsidizing to push back.