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.

I think what Apple is pushing for is computing efficiency. It still gets faster but with much less power. Focusing on performance solely would be the wrong way to evaluate these chips. https://www.tomsguide.com/news/apple-m3-chip

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.

I bought a used book online, and it had a person's last name and a book club in it. I was able to trace it back to a woman in the Carolinas that died without family. Her obituary gave a bit of her life story and I treasure the book all the more because I know a bit about the woman and how she loved reading and gardening (it was a gardening book).

Somethings do get passed on.

Corn? Must refer to something else besides what we call corn today. A different grain? Or “corns” of salt maybe?

Passive sonar picks up bounces. A mountain bounces background noise plus currents flow around it which would show that something was there (currents create temp differences and affect sound waves). They might not have had a clear picture, but they would have known something is there. (Source: a bit of experience)

Borax is incredible stuff. I used it as an insecticide in Florida. I could puff it into places behind cabinets and appliances. It doesn't kill by chemical means, but by getting stuck in insect chitin, ripping it apart and then desiccating it. It's safe for pets too. Amazing.

If you've ever eaten freeze dried, canned and dried foods for extended periods of time, you'll know the joy of something crisp and fresh. Leafy greens are spot on what you'd want. Before refrigeration, greenhouses and global shipping, our ancestors were the same way. It's why something like Polk salad (one of the first greens in Spring) or storing chicory roots for their mid-winter chicon (a single crisp leaf that sprouts from a single root) were so enjoyed. Fresh and green used to be celebrated, before it became too normal to worry about.

Agreed, and that is the heart of it.

- Someone fixing their own code fixes the codebase. Someone fixing someone else's code, generally only knows enough to make a fix at a single point, to fix an observed bug.

I think the abstract is just making statistical observations and hopefully in time will develop and test hypothesis that could create a theory. Anyway, they can use my hypothesis above and give it a whirl.

My SO did not want a traditional diamond gold engagement ring due to normative ways, consumption, global diamond trade, etc. but it’s hard to not buy such a thing number one, and two, u have to wear it each day. I bought a polar bear diamond (Canadian) which in addition to being mined in a friendly way (environment, labor, etc), uses a cut that hides its size. It’s brilliant in the light and sparkles like no other. Then I chose platinum as it isn’t as showy as gold and doesn’t corrode like silver. So overall, it’s an amazing ring to look at, isn’t traditional but so too hides its cost. Rings are for spending time thinking about your partner and what they want to be shackled with. She really liked it, even though she never would have expected it to look like what it is.

Agreed. I have it built into my vim editor, running after saves. Not only does it help catch errors, it catches potential errors, poor formatting and has become an amazing learning tool. Bash isn’t my favorite language, but many of the issues I had with it are no longer relevant.

That does sound fun. Formal systems approaches and automata always seemed more applicable to embedded development. State machines, statecharts, etc always seemed like something I was using on my projects. However, I also felt like I was always writing loops and tests for why some bit wasn’t flipping or some event didn’t occur. That’s the frustrating part... reading and rereading manuals and scratching your head.

Completely right. You are correct in what you should be focusing on. Only very large systems will see a return on investment in optimizing a system for hardware costs (bad code and crummy implementations should be worked out as tech debt). Focus on product, features and serving your customers. Get your market fit and burn your investor capital. Then when you reach that next stage, either sell to a company that is good at management or start hiring for performance.

From the article, "It said the lithium-ion batteries in the devices became less capable of supplying peak current demands, as they aged over time. That could result in an iPhone unexpectedly shutting down to protect its electronic components. So, it released a software update for the iPhone 6, iPhone 6s and iPhone SE which "smoothed out" battery performance."

True. Unfortunately, there may be a wide amount of practical experience shortly.

Additive vs Subtractive colors: https://stackoverflow.com/a/6531772/2664702

I once opened up a government code base (in C) that lead with this: "void * * * * x;". It took a while to learn that code. Taking time is fine and good managers will support you, so long as you have something to explain what your time is spent on.

Probably so when your 10 users grow to 1000, your efforts at 10x are good for 1000x, and you’re working on 100000x.