One of the very few good things from the AI race has been everyone finally publishing more data APIs out in the open, and making their tools usable via CLIs (or extensible APIs).
It's not like Apple is putting any thought into either the UX or the engineering side of utilising the compute properly (except calculating those glass effects extra inefficiently).
Minimise SKUs and get some use out of the binned chips who have a few failed cores.
As you mentioned, scope definition and constraints play a major role but ensuring that you don't just go for the first slop result but refine it pays off. It helps to have a very clear mental model of feature constraints that doesn't fall prey to scope creep.
I find this a tad funny since ccc is my claude code alias, since cc is taken up by the actual, working, greatly optimised and really well made Clang C compiler.
'Before you joined' seems to that she doesn't anymore.
I find it a little amusing that AI companies provide free AI subscriptions to their employees and their families. Perhaps because I'd never thought of it that way.
That's kinda nice actually; I assume employees get early access to models to test (5.3 codex, for example). Do families get it too?
Should be, but sadly isn't; the incentive is to feed into the economically incentivised "bs" rather than be wary of it, which is just... disheartening. Schools often inculcate this enough on a subconscious level that I've seen my fellow college mates rather unable to shake off that residual behaviour.
My problem with AI support agents is that instead of being good classifiers for my problem, they're even more non deterministic now in terms of grievance or query redressal. If a listed option is not available, I'd rather talk to a human who'd know or have the ability to find out, instead of an LLM which would just make something up with no grounding.
Yeah, I feel Anthropic is just very deliberately theatrical about the way they present their technology and company and even how they price them. Dario's conviction seems too over dramatic to be real to me, but while there's a chance he's drinking his own kool-aid, they just know how to present it as a premium experience, and their developer adoption helps with that.
On one hand, with the top comments of the rebrand post showing how many insecure deployments there are, something like this alongside cloudflare zero trust is probably a much more secure solution.
On the other hand, I just wanna point out
> Firstly, Cloudflare Workers has never been so compatible with Node.js. Where in the past we had to mock APIs to get some packages running, now those APIs are supported natively by the Workers Runtime.
Deployed a project a couple of days ago, and compared to past attempts where I had to wrangle (pun intended) with certain configs for deployment styles for node based applications, the normal build tooling just worked out of the box. Planning to move a couple of my free-from-me high DAU user projects that are on the vercel premium tier over to CF workers.
I reckon that the majority of the HN audience is into older (perhaps more graceful) working technology despite all the fanfare that newer, shinier stuff garners.