It seems possible to optimize for these metrics and still end up with a society where I wouldn’t want to live if I were randomly placed in it (high stress, low trust, poor quality of life).
Low trust is not a problem anymore. High trust societies these days are just a lot lot more vulnerable. High trust was a fluke brought about by close knit, protestant, racially and ethnically homogenous societies. Now everything is open to the world 99% of which have never been that way. Trust someone and you are a victim.
Stress level is something innate to a person. If they have anxiety problems, they will find what to stress over, no matter what. Even in absolute crime ridden hellholes in Latin America, most people have calm, stress-free lives, and in many Western societies people are literally dying of stress over things they largely imagine ("climate apocalypse", microplastics, etc).
Quality of life depends on someone's personal choices apart from the things i have already covered...
One thing to add is perhaps, climate metrics. Such as variations of temperature and precipitation over year etc. Because there are excellent places where climate just sucks and it kills all the fun (like UK).
There are certainly things that matter a lot, but idk how to measure them in a way that sounds trustworthy and quantitative enough. Like corruption. Say Serbia vs Belarus: countries are largely same thing except for that metric, and Serbia looks like an absolute piece of shit comparatively, and that's the only difference - but idk how to quantify.
Well, there's also race. Politically incorrect but everyone no matter the race will agree it's important [shows the Family Guy meme].
But to me, what matters is the actual change to main/master at the time the thing is merged — that is what affects the team.
Totally agree, if the developper goes in wrong product direction at the beginning and add 10 additional commits afterwards: team + 6 month actually don't care about it.
I certainly see no point in merging it in when it based on an ancient ancestor
If you want the CI to run, before the merge on the result it will produce on main branch ?
To some extent Tesla could be Starlink's AWS. Every Tesla user could be a potential starlink customer. Could we even imagine a more efficient data collection?
The service isn't expected to work very well in the urban areas where I assume most current Tesla owners live, so I'm not sure this is a particularly natural fit. Also, it requires a bulky receiver.
We are using ActiveAdmin to manage our backoffice since few years, but we are facing some issue, especially in dev env, where the more you have models, the slower will be hot reloading of the code.
Before considering to kill it to create a new backoffice in our rails app from scratch, I wonder if some HN people faced these issue and found some best practice to put AA at scale.
