Peter Hagen

Code wins arguments. If we tested a feature and didn’t like it, we rebuilt it until we landed on the best version. For some surfaces, like the activity feed, we rewrote it three times before we finally landed on an implementation that felt good enough.

We send people away for years, tell them exactly what to do every day and they get to make exacrly one choice every day: do you obey or not? That's the only choice you get to make. Then, after 3, 5, 10 years, we send them out into society and tell them, "Make better choices." But we haven't prepared them for that at all. We have given them almost... See more

The collapse of the GDR has many reasons, mostly it ran out of money during the 80s. There have been several reasons for running out of money, e.G. taking on massive credit in the 70s to produce more consumer goods and build flats (the reason Honecker was very popular after his coup against Ulbricht), which it had problems to pay back in the 80s.... See more

so long as Larian is generating enough revenue to make payroll, Vincke can operate the business in whatever fashion he chooses. The downside, of course, is that a single flop could completely tank Larian — hence the three years of early access.

But with all the recent blather of technology companies changing the world, I’ve become a bit more jaded of late on the impact of business given folks are so quick and cavalier in how they define changing the world. Atlas reaffirmed for me the power of and the good that businesses can do in a community if it’s there long enough. There are several... See more

To start with, leaders must not be afraid of their teams making mistakes. Copying from another comment: "Netflix's culture demands very strong leadership and probably works only when the company is small enough. From CEO and down, leaders in every level need to know how to set context for their teams, give enough freedom to their teams, while... See more

I really like the approach of Netflix of 10 years ago when it was still small. They hired mature people so they could get rid of processes. Indeed, they actually tried to de-process everything. As a result, things just happened. Non-event was often mentioned and expected in Netflix at that time. Case in point, active-active regions just happened in... See more

At CodeSandbox we use Firecracker for hosting development environments, and I agree with the points. Though I don't think that means you should not use Firecracker for running long-lived workloads.

We reclaim memory with a memory balloon device, for the disk trimming we discard (& compress) the disk, and for i/o speed we use io_uring (which we only... See more

ARKit persists

anchors and mapping data based on your location.

• Practically speaking, this means that if you use an app to anchor some paintings to your wall at home, then go to your office, you won’t see the paintings there. You can persist new paintings on the walls in your office. Then when you return home, the device will automatically reload

... See more