> Imagine a future where a handful of people can conduct scientific research and engineering tasks much more rapidly, and with higher quality, than massive teams of scientists and engineers do today. By automating the loops of discovery, the world will be able to make much more rapid advances across countless fields of science.
The problem is that for this to actually become true, compute needs to become commodity again, otherwise this capability will select for people and environments with oversized pockets.
That's fine by me. I certainly won't be making any major discoveries on my own (not on this current life trajectory anyway), but am very grateful that other people have.
> I'm surprised they didn't eat it up until new releases when they often increase prices.
There may be an element here where announcing new hardware at a 30% higher price would largely make the latter the focus point, so instead they chose to take the hit of the price hikes separately.
> convincing someone that their excessive null checking is harmful is an uphill battle.
The argument that seems to hit home more often than not is that optionals effectively “fork” the state space, the possible states your program can be in. And the larger the state space is, the harder it is to reason about the code and maintain it. That’s actually part of what make undesirable states un-representable means.
Exactly, plus you now have a new superpower with AI — the ability to dig into and ramp up expertise in mostly any domain. I’d say the article gets it backwards.
True that AI lets you get information fast an efficiently. But it might just make you feel like you understand, even if you don't have the kind of hard won domain intuition that this article is talking about. I certainly often get delusions of grandeur when I learn a lot of something and haven't yet suffered with it in practice.
Wait, what? Double-clicking will prompt for Face ID to open your default card for oayment, and from there you swipe down to see the stack — which I suppose is the screen you’re looking for.
But you cannot edit, add, or remove anything in this stack, and there's no way to go from it to the wallet. You have to close it, and open the actual wallet app which will show a slightly different view, and more items
Exactly. The principle to go by for estimates is finding a balance between time/scope/cost, and figuring out which aspects of the context affect which dimension is the first step.
I’ve no experience with Elastic but what they’re getting at I think is indexes in Elastic is actually your data because that’s all it does due to the purpose it was built for, whereas in Postgres indexes are, well, indexes — that is, derived data, not the source of truth.
> Imagine a future where a handful of people can conduct scientific research and engineering tasks much more rapidly, and with higher quality, than massive teams of scientists and engineers do today. By automating the loops of discovery, the world will be able to make much more rapid advances across countless fields of science.
The problem is that for this to actually become true, compute needs to become commodity again, otherwise this capability will select for people and environments with oversized pockets.