This the the pricing model for Anthropic now too for business customers over 150 seats - under 150 you can take the Team plan at $25/mth & it’s similar to the personal plans, but Enterprise you’re billed by the token (with a $20/seat minimum but the tokens are pooled together). This is the AI Uber moment where the VCs stop subsiding your fares.
The frameworks-and-tools make for good blog fodder too, as they are quite applicable across a range of areas, so many readers will find something that resonates with them, and claude-code-is-pretty-good-these-days is a less blogworthy topic.
But when you build a skyscraper you don’t one shot a completed building that stays static its entire life - you build a set of empty floors that someone else designs & fits out, sometimes years after the building as a whole is commissioned, usually several times in the lifespan of the superstructure.
And in the fitting out there often are things that exist only to get customer feedback (of sales), such as model apartments, sample cubicle layouts etc.
So yes, you are right that engineering can guide us to building something right first time - the hard part from software perspective is usually building the right thing, no the thing right.
An interesting analogy I came across once but could never find again is that with software systems, we’re not building a building, we’re designing a factory that produces an output - the example was a mattress factory that took in raw rubber feedstock & cloth and produced mattresses.
Workday’s student offering is designed as a full student management offering like Banner et al, with the carrot that it’s internally integrated into the financial & HR systems, which avoids another vendor and also a massive and ongoing finger pointing exercise.
It’s also one of the few from-scratch cloud-first student management solutions.
Your system was configured by muppets if you don’t have a search box - it’s a massive beast that like all enterprise-grade software is a toolbox for you to bend to your will, but the downside is that if your configuration people don’t have empathy for the users (and looking at you especially, contract architects) you end up with a system that is optimised for whoever talks with the vendor, and not for anyone else.
A two week delay on including new versions would probably work more or less as well with a bunch less effort, but a local proxy looks like it’s going to be a lot more common very soon I’m guessing.
Sure is - and o3 is missing from the OpenAI models that Azure is serving, which I suspect isn’t a coincidence - if OpenAI has some secret sauce that lets them undercut resellers this might shake up agreements for a bit.
Architect who works on a bunch of procurement - our approach is that a clean SOC2 Type 2 report is preferable, but not a deal-breaker (and reduces paperwork for me). But if you couldn't demonstrate that you could address the issues that SOC2 (etc) test, that would be a problem.