↙ time adjusted for second-chance
Starlink Mini as a failover (jackpearce.co.uk)
>outcome shaping markets I heard something remarkable many years ago, that there are websites on the dark web where you can bet on which day someone is going to die. In other words you can pay to have them assassinated in a very indirect way. It's like kickstarter, for assassinations. When enough funds are raised, a willing volunteer simply places a bet on the day when they plan to carry out the deed. So they win the bet by default. Obviously this is a horrible use case, and I'm not sure if such websites actually exist or are just rumors. But I have to wonder about the model itself. I often thought about an inverse Kickstarter. Where you post an idea, people fundraise the idea, so the idea itself is validated. And then worthy contenders step forth to build it. (I guess donors could vote on who ends up getting the money to actually build it, or if there's enough they could even get divided between them for prototypes.) For example, there seems to be a lot of interest in e-ink laptops, and a successor to flash. People have been complaining for decades, but not much gets built. How much interest is there? Well we can measure that objectively! You vote with your wallet. Right now, it's a "pull" system. You have to hope and wait for a small number of highly motivated people. You have to hope they will launch something you're interested in. But what if you could push? I think we could do a lot more proactiveness on the crowd side of things. As a recent article here mentioned... people actually do know what they want. And of course this idea isn't just limited to products and services. I think there's a lot of potential for this idea in government as well.
It's interesting that you contrast Sweden and Russia, considering while I have not lived and worked in Russia, I've worked with Swedes quite a bit and my experience with them is that they don't really emphasize red tape that much - in the context of development, they don't really mind if you bend the rules if it's for a good cause - what I mean is there's a general attitude of pursuing sensible outcomes over blindly following processes. They're also not big on oversight and I got what it looked like to me a surprising amount of autonomy and responsibilty in a very short amount of time, that I felt out of depth for a while, but got accustomed to it. A very laissez faire way of work. I felt much of the system was informal, and based on the expectation of not abusing trust. Which was very refreshing, as most companies in my experience exist in a state of bureaucratic gridlock - you need to push the change to repo X, but Y needs to sign off on it, and it depends on changes by person Z, who's held up by similar issues etc. It's a very emotionally draining and unproductive way of working, and is usually overseen by bosses who create these processes, because they don't trust their employees, or to get a feeling of power and control, or they simply don't understand how and what their subordinates do, so they kind of try to force things into these standard flows. Which also doesn't work, but it accountably doesn't work. Even if a days' changes take a week, and still end up lacking, you can point to that Task A is blocked by deliverable B, which is at a low priority at team Foo, so lets have a meeting with that teams manager to make sure to prioritize that in the next sprint etc etc etc. This is how most places turn into that meme picture where there's one guy digging a hole and 5 people oversee him.
 Top