cwingrav

One of the best ways to ensure you have energy is to reduce use and dependence. A huge amount of energy goes to heating and hot water so insulation and shorter showers with on demand can drastically reduce battery and solar panel needs.

Probably thin so it can make a foldable screen. That seems to be the thinking around this because nobody really cares about thinness after a point. Also, a bonus, thin/small generally means better efficiency.

A lot of bash errors are not understanding possible cases due to white space.. which shellcheck catches. After using it for a while, I don’t even really worry about white space because of the good habits I’ve learned/(been forced to use).

Also, use shellcheck. Incorporate it into you editor. Fix all warning and don’t ignore them. This will push you deep into bash syntax rabbit holes but you come out better the other side.

BASH is like Obi Wan. It isn’t the most powerful or flashiest, but it survived a long time, where others didn’t, for very good reasons. Bash runs basically everywhere. It has many modern features you wouldn’t expect. Its syntax is literally what you would type on the command line if you were diagnosing or fixing systems so you don’t need to transpile to another language. Its reliance on other programs means it is glue and can easily incorporate highly cohesive functionality/tools others write and maintain. Also, it’s been around and is everywhere so you don’t worry about trying to incorporate the current latest and greatest declarative tool (which will blow over in 5 years) into your other workflows. Basically, don’t disparage a Jedi/tool that has survived where others didn’t. There is a reason.

Sun

I’m chemistry, tiny changes to structure or single atoms can produce drastically different properties.

> It’s an easy time to fire a bunch of people..

Totally agree. This is just cutting in places they’ve probably wanted to cut for a while. They’ll hire back in a year or two as things ramp up, and on projects they consider important.

Agree on the economic approach and with a preference for cap and trade. Create a certain amount of emission billets and auction them off. Then restrict the amount each bullet allows over time. It has economics, planning and reductions all in one.

Agile is to Lenin as Agile processes are to Stalin.

Read the Agile Manifesto. That’s what Agile is. All else is either: - (good) trying to implement the Agile Manifesto, or - (bad) trying to make current process appear like Agile.

Mine cuts off at 35F and I have to manually switch on the oil. I live where winter is normally below 35 at night. Very annoying system. (I didn’t pick it)

Fukushima, Kyshtym… those are the other bad ones.

The stage of testing is important here. Early on, I agree with the author. Catch code/config bugs early with no wiggle room for retries. But later, testing in a live system that lives with unreliability, you need those configs that allow for it. This enters the chaos testing phase, where you can assume with some degree that the code works deterministically, but now you have to test how it works in non-deterministic settings. Or more likely, why it failed in retrospect and how it recovered previously. This is much harder.

This is a scientific article and the terms are used with precise definitions. If translated to a more vernacular venue, the language would either be different, or the terms defined in the article.