Very fun. Got a few minutes in. Is there a strategy for avoiding hitting the planes driving slowly across the runway for takeoff? It seems very hard to also pay attention to them when they have so little lead time.
Why would AI say that, when nearly every piece of training data is ever been fed would use milliseconds? I think much more likely that this is how the author thinks of it.
3 hundreds of a second == 33 Hz is very clean in my human brain.
I think the objection about AI-generated cards, or decks found online, is that the context of the card creation is lost.
What made you write the card? How did you find the answer/translation/whatever? What was all the learning around the card that the card is supposed to represent?
If you're just doing simple word translations into a new language maybe that's ok. But if you're trying to learn a concept in organic chemistry or SQL, then you're more likely to memorize the card itself than learn the concept.
> Hacker culture sees programming as a conversation with a machine as it runs.
I wrote about this a fair bit as a party of my master's thesis, about tinkering as being a "conversation" with materials. Hacking can absolutely be looked at in this framework.
The philosopher Donald Schön I think was the first person to formulate tinkering in that way. The process of engaging with materials -- whether it's a broken motor you're curious about or a tune you're plucking out as a complete novice or some code on Scratch -- involves asking questions of the materials, learning to hear answers, and noticing when the materials themselves pose questions. It's a really nice way of looking at things.
I can't imagine how much amazing and important literature you'd miss if you were snobby enough to think that you could only read things in their original language.
I'm so glad I get to read the Russians and Kafka and Calvino and Murakami and Camus and Marquez and Homer and Plato and, heck, the Bible.
I do know the feeling. I struggled through the start of My Brilliant Friend because I ought to read it in Italian, because I speak it pretty well. So then I didn't read it for years. Finally I just read it in English and enjoyed myself.
I was confused when I first read it as well, but the implication is that the higher reward-seeking risk tolerance can actually be more rational than the well-studied loss-aversion bias that the authors mention.
Looking into this more, studies have found that we tend to rate the possible loss of $100 twice as painfully as the pleasure from the possible gain of $100. This can lead to irrational behaviors.
Increasing the weight we give to potential rewards is not necessarily a bad thing.
I think this can help explain the "calming of the nerves" that slow breathing promotes. If you need to speak in public and your heart is racing and you're shaking, this is an irrational reaction to what ought to be a very safe situation. By focusing more on the rewards (the acclaim for a good speech or whatever) and less on the imagined risks, you can calm down and speak naturally.
> The favicon doesn't actually contain the whole website itself.
This is the kind of thing that is extremely idiomatic LLM speak. There's nothing particularly wrong about it per se, but it just makes everyone who is familiar with LLMs say "oh, it's written by an AI" and it just becomes disappointing.
> For the espresso samples, participants could not reliably tell the traditional and ultrasonic versions apart. There were no significant differences in aroma, flavour, bitterness or overall liking.
Nah. I have a Roku 3 stick and a brand-new $700 projector with Google TV. The Roku 3 is light-years ahead in terms of speed and UI ergonomics over the Google machine. And both are better than the smart TVs I've used.
But I fear this need means this time is ending, and we'll only be left with crap.
I'm a teacher. Our kids are using Chromebooks, and we want them to do research projects, but we don't want them using AI. Unfortunately with Google, it's impossible not to get AI answers. As far as we know, there's no clean way to filter out the Gemini garbage. I wonder if Kagi has considered making an educational pricing model, and letting our kids get away from AI.
Of course, the "Chromebook" part of my statement above is probably a hint that getting rid of Gemini won't be as simple as changing the default search engine...
I feel like unresponsive controls must have been a platform or hardware issue. On my (...Dell with Windows 3.1?) the controls were perfectly responsive, and they absolutely had to be. So many things relied on being able to, say, run and switch directions on a dime so that only your toe touched the platform that would then fall and break.
The tutorial made it seem a little too much like there is only one speed that would keep us in orbit. Any slower and we'd crash, any faster and we'd leave.
In fact, though, if you've ever played any game with orbiting mechanics you'd see that it's extremely difficult to get out of orbit if you're in orbit. Going faster simply increases the size of your orbit, and going slower simply shrinks it.
Note that no space program has ever managed (or tried) to send an object into the sun. We're already starting off with such a high orbital velocity, 30km/s, that we'd need to send a rocket backwards at nearly that speed just to slow it down enough to make it crash into the sun. That would require massively more energy than anything we've ever done before.
Everything you're saying is right, but I'm not seeing what's wrong with step 14. Did they edit it?
> Earth turns once every 23 h 56 min (one sidereal day) about an axis tilted 23.4° (the blue line). That spin gives us day and night; the tilt gives us the seasons.
Nothing in step 14 to me implies s procession of the axis.
It might be more on par with a for-profit fire department showing how -- oops! -- easily buildings catch on fire these days.