1,463 karma · joined December 16, 2020
Maybe I'm just unaware, but it's crazy to me that these planes burn 40 kilograms of jet fuel per minute.
[1]: https://unherd.com/newsroom/the-next-time-wikipedia-asks-for...
It might sound like I'm splitting hairs here but I'm trying to illustrate the problem of defining a startup as an "AI startup" simply due to the presence of AI somewhere in its product. It would be like calling early-days Facebook (the actual website, not the diversified conglomerate that Meta has become) an "internet startup" instead of a "social media startup." Sure, the former is technically true but it's a near-meaningless description, because every company in the 21st century is an "internet company" in some respect.
The author calculates this by searching for the term "AI" in the name and description of each startup's YC page. But presence of the term "AI" doesn't make a startup an "AI startup," so to speak. For example, I picked one startup at random, Topological, which is "developing physics-based foundation models for CAD optimization." Just because the company uses AI doesn't make it an "AI startup." AI is rapidly proving itself to be an extremely useful and workflow-changing tool, and many companies now have adopted it somewhere in their product without suddenly becoming AI companies.
Code is an asset. It is the product of software companies. Having more assets certainly increases complexity, but this is almost definitionally true. Imagine saying “the US interstate highway system is debt, because it’s complex and difficult to maintain.” The premise is true, but the conclusion is such a one-dimensional way of seeing things.
The AI stuff aside, in light of the above, what is the author’s thesis here? “For the same code, all else being equal, it’s better to have less complexity than more complexity”? Sure, true, but that’s a pretty easy and obvious point.
It seems this entire article could have been profitably boiled down to “make sure your AI coding tools aren’t adding unnecessary complexity to your finished code.”
> When it comes down to it, what is being sent over the network is 1s and 0s
?
When it comes down to it, all of computing is 1s and 0s. This is not some feature that's particular to the wire.
> Wait. Five months now. Molecules all change. I am other I now. Other I got pound.
I think the Stoic philosophy has been hijacked somewhat by people who think of it as nothing more than "don't show emotion; be impassive and aloof." But I think Stoic philosophy inherently embodies universal love, which seems to be in short supply these days. Not everyone is our enemy.
My point is this: I spend over 100,000 minutes per year listening to music. Any unnecessary friction in the experience is therefore extremely frustrating and has a disproportionate effect on my life. In all my experience self-hosting, it adds a certain level of friction that just isn't worth it considering how much time I spend listening.
I am not hostile to self-hosting in other cases. I am very satisfied with my self-hosted Plex server, for example. But I don't spend 30% of my waking hours watching TV.
I don't travel internationally often at all. But when I do, access to my music becomes all the more important.
There's plenty I can do about it. If Spotify decides to "pull the plug" on a song or artist I like, it's my prerogative to switch providers or decide to self-host. I'm not locked into a lifetime serfdom with them, and it's not like the files will magically vanish from the internet once Spotify decides not to host them.
> who will willfully consume the most crappy audio codec
I listen to 99% of my music through Bluetooth on AirPods, so 320kbps is perfectly fine for my use case. If I was someone who cared deeply about audio quality, I would switch to a competing service with HiFi.
> hundreds of millions of clueless subscribers, such as yourself
At least try to be respectful.
This isn't even to mention the numerous features that Spotify has which are difficult or impossible to replicate on self-hosting. The "radio" feature, song recommendations, the DJ, AI playlists, stations, automatic playlist enhancement, social features, Canvas... the list goes on. And of course I never have to worry about managing a library of mp3 files. When an artist I like drops a new album, it'll be on Spotify at 12:00am exactly and work perfectly. This isn't possible with self-hosting.
When you look at it this way, the chance to pay 6 bucks a month to get all these extra features and ignore the headache of self-hosting is a no-brainer.
Just fudge. I know it might seem dishonest, but I think I fudge at least a little bit in probably 80% of my encounters. The most important thing isn't accuracy from the DM's perspective, it's fun and accuracy from the players' perspective. Unless the players catch wind of the fudging, it literally only has upsides:
- You waste less prep time fine-tuning stat blocks and can spend more time on the interesting and material aspects of prep, like designing NPCs, dungeons, etc.
- It makes the combat encounters more interesting, because encounters that would be super one-sided in either direction are instead close and nail-biting
- It allows you to end a boring encounter quicker or prolong unexpectedly interesting encounters
- You can create cool moments where a monster fails an attack at a crucial moment or succeeds when the odds are stacked against them
...etc. I think well-executed fudging is a complete win-win situation, as long as your players don't find out.
I don't think Fermi questions have mass appeal anyway. I don't think most people know what "order of magnitude" means, let alone understand dimensional analysis (ie., the conceptual idea of what it means for units to cancel).
I don't think making the game a little more complex would really affect its appeal, because it's already targeted at people with a certain level of scientific understanding.
FWIW, you can type an em dash on Mac with shift + option + hyphen.
Call the three numbers a, b, and c. This means c = a + b, but we still don’t know to which person each number belongs.
When person 1 (p1) is asked what his number is, he has no way to know whether he has a, b, or c, so he says he doesn’t know. Same goes for p2 and p3. Clearly p1 somehow gains information by p2 and p3 passing. Either he realizes that he must be either a or b, and such his number is the difference between p2 and p3’s numbers, or he realizes that he must be c and so his number is the sum of p2 and p3’s numbers.
That’s all I have so far. Anyone have other ideas?
If we only have two files, A and its duplicate B with some changes as a diff, this works pretty well. Even if the user deletes A, the OS could just apply the diff to the file on disk, unlink A, and assign B to that file.
But if we have A and two different diffs B1 and B2, then try to delete A, it gets a little murkier. Either you do the above process and recalculate the diff for B2 to make it a diff of B1; or you keep the original A floating around on disk, not linked to any file.
Similarly, if you try to modify A, you'd need to recalculate the diffs for all the duplicates. Alternatively, you could do version tracking and have the duplicate's diffs be on a specific version of A. Then every file would have a chain of diffs stretching back to the original content of the file. Complex but could be useful.
It's certainly an interesting concept but might be more trouble than it's worth.