One thing that's under appreciated on the website of the demos is the Stanford demo where Ben showed uh anywhere between 3 to 25 images you can reconstruct that entire Stanford quad. But the thing is we had to show it from aerial view. But every single input image is been standing on the ground taking a picture from the ground. So, everything you see are generated but according to the laws of reconstruction.
And that's why every hype cycle produces a wave of absolutely spectacular demos and very few real products. And the recurring mistake of every cycle is spending on the demo when you should be saving for the nines.
unless the code is completely out of your control, the need for mocking often indicates a design problem-consider refactoring to make the code easier to test directly.
For years, it was faster to mock up software than to ship it. Designers stayed "ahead" of engineering with prototypes. Now AI coding agents make development so much faster that the loop has flipped.
I think that by the end of this year and we'll see demos of it like right away, but by the end of this year most people will be programming by talking to a face. A face as in a face on the screen.
Say goodbye to cycles of mock and doc feedback, and say hello to code-first prototypes with constant iteration (on prompts, models, etc) to answer three key questions.
mainly because of Interactive Broker's amazing "margin account" feature. This, when used very carefully makes it seamless to borrow cash against your own shares at some of the lowest rates on Earth
Conclusion: If you expect to regularly carry the device but not a smartphone, which is the case with very few people, the inReach is the better option. Otherwise, the Somewear is more attractive: its seamless messaging and cost-savings more than offset the 0.5-ounce weight penalty and its slightly larger size.
So that's precisely what I've done - intercepted my own traffic passed over an insecure connection and put together a string of demos in a 24-minute video explaining why HTTPS is necessary on a static website.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.