659 karma · joined June 12, 2018
But for all the model rockets I've seen, their mass ratios are quite small, and their motors don't allow for throttling. They blow their load as fast as they can and then drift down.
Software is not the biggest problem, you need a hobby quality throttling and gimbaling rocket motor, and I'm not sure if they even exist.
I also think your overstating the risk involved in nuclear power. Even fukushima was pretty tame, and unlike Japan the USA has lots of relatively uninhabited real estate we can put the plants on.
Cost is one factor. Location is another. Reliability another. Risk another. Nuclear is a system of tradeoffs that is very hopeful for fighting emissions.
Of course this is all moot since even if the USA and Europe went to zero emissions, we won't make a dent in climate change. The developing world must be addressed with at least as much urgency as the West must be addressed.
I see webassembly terribly fragmenting the frontend skill distribution, not in a good way.
I see the next generation of programmers more populated by tech debt creators and less accepting of mentorship.
I see non-volatile storage gains dramatically changing how OSs think about RAM and storage, even to the point that we might see RAM mostly vanish (unless you need volatility, like crypto keys), and machine shutdown/startup becoming instant. As non-volatile storage continues to approach RAM latency, we'll need a new generation of operating systems and probably programming languages too.
I see people continuing to overpay for PaaS systems that can't scale, creating software that's ever more difficult to change and tightly coupled to proprietary cloud systems.
I don't think Neil Diamond is wrong but it's kind of baby's first reading on the differences between groups in the world.
I think CGP Grey does a great job at communicating the actual meat of Guns, Germs, and Steel here https://youtu.be/JEYh5WACqEk
I suspect it's a neurological difference. I've seen masters of CSS struggle with basic operational computing concepts that feel obvious to back end developers.
In the Californian model, you decide in committee where people ought to go (which is everywhere represented by committee members) and design something too big and expensive to succeed.
Now all we need is structural typing like golang so I don't have to explicitly tell the compiler that a class implements an interface.
I hear you saying a lot of shoulds which need justification by themselves, but even if I accept them, there's nothing we know of that can provide that.
A core contention between us is likely to be "how much of our current lives are we willing to risk to speculate toward the feel-good shoulds?" My answer is "all steps should be dramatically small and take a long time to make sure we can back out if we misstep." That's the core of what it means to be conservative, to me.
In other words, Hell is a long way down, we, all of us, have it too good to speculate dramatically in large ways or in fast ways.
One of my biggest fears with this line of rhetoric: Extreme is a relative descriptor. If the most poor of us made 100k/yr, then they would be on the "extreme" end of the income scale.
I fear that it's too easy to forget that making 15k/year today makes you dramatically better off than median income earners from 100 years ago.
Lol @ "phrasing can be condescending", that's a silly level of pretend objectivity.
Wrt to "feeling different", thats what every body mod enthusiast I've ever met or seen on TV said their reason is.
As far as my opinion? There's nothing wrong with it. But I wouldn't hire them for any potentially customer facing roles.
I'm a husband and father, and I respect my family, and I have friends outside of work, so one of the last things I would ever want to do is drink at work or after hours with my coworkers.
Feels like a non issue, a consequence of working with too many manchildren. If you don't like the brodrinking then don't be friends with them and find a better job.