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.
There's also a reward for not over thinking it and letting AI bring the solutions to you. The outcomes are better when it's a question, answer, and execution session.
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.
You could use the AOSP launcher, or whatever your phone maker installs instead. I don't, because phone makers seem to really want to push an unremovable search bar that I don't want. And swipe left to see a totally confusing screen I also don't want.
'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.
reply