The point that the author makes is very valuable, it is important to not throw out hands in the air. If you are not moving forward, you are falling back.
Though one (perhaps nit-picky) point I'd like to make is that these dictators are not dumb. They are incredibly intelligent. They themselves are probably not hackers, but they understand people and power. They are going do what they can to get what they want. We can't ignore the factor they play in creating these problems, and we need to take it just as seriously as we would a technical security exploit.
You don't have to be "incredibly intelligent" to pay some company to hack a list of your enemies. That just takes money and a list of people you hate, not insight.
I think it would be interesting to read case studies of different teams, their principles, how those decisions have impacted them, benefits, drawbacks from their approach, etc.
I think principles are great, but like you yourself have said, they require context. I would especially be a valuable resource for junior and mid career engineers, of which I am one.
I imagine teams will shared their principle lists on blog posts and put reflections there.
Not all of it would appear on the principles.dev, as I think the reflective nature would be best handled elsewhere. But acknowledging pros and cons on the website is very valuable.
The next big piece of work I have to do is on principle lists ( https://github.com/PrinciplesDotDev/principles/discussions/2...) and figuring out what features to include and where to draw the line is going to be tricky... I need to find the principles behind it, really.
It's interesting that you say they would be a valuable resource for a junior and mid-career engineers. I agree, it would. What I've found is it generally attracts people who are a) leaders (in some form or other) b) care about programming deeply.
We should investigate the benefits of sodium as well. Sodium is vitally important for many bodily function and is a very misunderstood nutrient.
Historically people consumed much more salt, and don't give me the "people used to die when they were 35" nonsense. There is a big difference between being kicked by a horse vs dying of a stroke.
I have a lot of older tennis friends and they suffer through cramps all the time. I ask if they’re getting enough sodium after sweating for hours and they say they’re on low sodium diets for blood pressure.
Folks you need to replace your sodium when you sweat!
Doing strength exercises for many years now, increased sodium reduced muscle cramps and lowered recovery times. If you experience nightly cramps, increase the regular sodium and magnesium citrate intake and reduce when symptom free. Unrelated, doing breathing exercises just before going Max helps to execute in near tranquility.
There's a strong genetic factor in the link between sodium intake and blood pressure. Some people are very sensitive to it, others can consume larger amounts without causing hypertension.
There are also sex differences in sodium handling ability.
Older women who have taken blood pressure medication for many years, e.g. 10 to 20 years, have risks of losing the ability to control well the concentrations of sodium and potassium in the blood.
If they follow a low-sodium diet, they have a high risk of hyponatremia (too little sodium in the body). Depending on the diet, hypokalemia (too little potassium in the body) is also possible.
If these conditions are not diagnosed promptly, severe illness or even death are the consequence.
Unfortunately, I was not aware of these risks. My mother belonged to this risk group, but nobody knew this and her periodic blood tests were perfect, because they included many other tests, except the sodium and potassium concentrations in blood, which are mandatory to detect this problem.
My mother had very serious problems because hyponatremia was detected too late, so I believe that more people should become aware of this risk.
There are a lot of old women taking medication for high blood pressure, so all should know that a periodic cheap test for sodium in blood can easily prevent reaching a stage when complete recovery becomes difficult or impossible.
Also, any low-sodium diet should actually measure or compute how much salt you eat, because too low sodium is even more dangerous than too high sodium.
People sweat regularly without any noticeable moisture droplets etc. As long as evaporation >= perspiration rate nothing builds up. It’s why a tight watch will often have moisture behind it even though you don’t seem to be sweating.
You can still buy salt beef. It usually comes in a plastic tub. You must soak it in water before cooking in order to remove most of the salt otherwise it is inedible.
I love sodium and virtually never heard of this "sodium is the devil" narrative before! (I know right, was I living in a cave?) Anyway a few weeks back me and my friend was ordering Chinese food. And he was like, meh Chinese food has too much sodium let's order something else. Turns out sodium is bad because it accumulates water in your body? After that I started being super particular about my sodium intake.
I don't think sodium accumulates in the body - Na+ and Cl- are both ions which are relevant to a wide variety of cellular processes, and as far as I know your body has a lot of tools for maintaining the balance of electrolytes in the body.
As far as I understand, the health risk associated with excess sodium intake is high blood pressure, i.e. more stress on your cardiovascular system.
Kidneys too, last time I looked. Apparently it's kind of a feedback loop where salt makes them work poorly which leads to high pressure which leads to damage and repeat. Some details here:
As I understand it's related in that salt dissolves in water easily and somehow causes your body to retain water. This in turn increases the water in your blood (plasma I guess), thus the pressure increases. A 'water pill' (hydrochlorothiazide) is often prescribed along with blood pressure reducing medicine to make you urinate and remove water from your system. While my salt intake is normal, it wasn't until I was prescribed a water pill in conjunction with my blood pressure pill that I was able to see better results and also able to take less of the blood pressure med.
I mean that is just basic chemistry. Basically your body wants to have a certain concentration of ions in your bodily fluid, so if you put more sodium in, your body needs to hold on to more water to dilute it until you're able to pee it out
Sodium levels are so vitally important to our health that we we have a couple (more or less) of specialized organs for keeping it at the right balance, called 'kidneys'. Oh, OK, they also balance magnesium and potassium and maybe some other iums, but the little glomerules function by pumping sodium ions around to adjust concentrations of solute on either side of a semi-permeable membrane. Or something.
Don't worry about sodium unless you've been diagnosed with a metabolic problem.
Don't agree with that. For example here it shows that sodium might increase your chances to survive heart desease: https://www.health.harvard.edu/blog/good-heart-keep-holding-...
Kidneys require sodium to function properly.
Adrenals via aldosterone impact sodium. And when you're stressed, your adrenals might be in a bad shape.
I think sodium is a big deal. And some people hit with that especially hard.
I think GP meant don't worry about an excess of sodium.
I do feel kind of bloaty when I eat wretched excesses of sodium all at once, usually ramen, but it passes.
Generally eat a high salt diet, add other minerals (mostly potassium) to drinking water, and take magnesium glycinate before bed. Minerals are easy to eliminate and if I'm not getting enough there's no alternative.
This[1] rather lengthy article suggests that the issue there isn't the salt, but rather the interaction between the salt and the raw fish which causes carcinogenic compounds to form.
I have pre-hypertension which is a BP between 120/80 and 140/90 and the quickest 'fix' is to follow a lower sodium diet. I think it's pretty common for people around 'parent' age to have this, especially if they eat the SAD, so it'll be something you hear as a kid. I know I did!
Maybe your friend was referencing MSG? Makes me extremely thirsty hours later, and then I HAVE to "accumulate water in my body", on purpose, to satiate the unquenchable thirst caused by MSG
MSG is often used as a food additive in combination with heroic amounts of fat and sugar which would otherwise be unpalatable without it - particularly in a Chinese restaurant setting which is what people associate with MSG...
You're probably experiencing a sugar crash.
I suspect you don't experience the same after eating a bag of Doritos but they're absolutely loaded with MSG.. plus in all likelihood also sodium inosinate, sodium guanylate and who knows what else.
I don't want to kick the hornet's nest, but isn't MSG avoidance just an example of nocebo? It's just a salt right and its connection to headaches has never actually been established, it's jut something people say.
Chinese restaurants in the US are notorious for using excess salt and sweeteners.
Though to be fair it's a form of arms race, most US restaurants overdo it if the regional palette has become desensitized. It's not strictly a Chinese restaurant issue.
But many Chinese dishes on the menus are defined by their sweet and salty axis, and being in this environment they're pushed to the extreme.
People used to die when they were 35 because they were getting stomach cancer from a lifetime of eating salted meat. The invention of refrigeration was one of the most important public health accomplishments of the last 150 years.
No, salted meat wouldn't make a list of the top ten causes of mortality back then. I doubt even the top 100, but I can't say for certain without doing more work than a comment is worth.
Apparently lots of people disagree with something that seems obvious? Source?
> Do you honestly think that "salted meat" would be listed on a death certificate?
Strawman argument.
So stomach cancer is currently 10% of cancer deaths, and cancer is currently the second leading cause of death at all ages. One can't extrapolate that back historically safely because cancer primarily affects the old and people didn't live long enough back then. But even if we just single out stomach cancer and assume incorrectly that 100% is attributed to salt, when frankly that would be a minority of stomach cancers, then it still wouldn't even make the top ten causes of mortality today. Never mind historically when people commonly died from lots of things we no longer worry about, like simple bacterial infections, childbirth, or poor dental hygiene.
The OPs argument is ridiculous and I'm surprised how many people can't see that.
Life expectancy at birth is a worthless statistic to compare to when looking at modern humans. Infant mortality was so high that it distorts the numbers. A more useful statistic is the modal age of adult death, which peaks between 65 and 75 across most estimates, regardless of era:
https://onlinelibrary.wiley.com/doi/abs/10.1111/j.1728-4457....
I've actually used this concept at an old job. When I was given a new project the business people always wanted it done at a particular date, but it was always an unrealistic timeframe. I'd then spend sometime thinking about how long I thought it would take me, but I would always add 2 weeks or 25% to the estimated time, which ever was larger, just to deal with the human element.
This could include changing requirements, poor communication, illness, being blocked by other changes, etc.
I learned that you can get away with giving people extended deadlines as long as you hit them.
I definitely prefer to read research papers in html. I like to zoom in a lot when reading a long piece on my computer since it helps me read faster and keeps me from getting distracted. I've been thinking about working on a side project where I convert pdfs to html for academic papers.
One benefit of PDFs for research papers is that you can easily save them to your own computer, build up a library of them, highlight lines with functionality built into most PDF readers. I generally prefer HTML for reading, but PDF has some benefits, too. Granted, most of these features are also available for HTML. But for some reason you need to look for browser plugins in order to highlight HTML pages, whereas in PDF you can just use the feature. And PDF is always about the content whereas HTML also typically contains navigation and other distractors.
I have installed an extension named "single file" in my browser, which allows me to save any webpage, as it looks right now in my browser, as a single HTML file. Images and CSS is inline, javascript (I think) is removed. Quite handy when you prefer a folder and file based workflow.
Epub is ok, but it has no support for math equations (practically all implementations just dump them into raster images) and HTML's typography leaves much to be desired.
There are plenty of good reasons why TeX and LaTeX are still the workhorse of scientific publishing in spite of the emphasis on fixed format layouts.
Somehow related: I find Snappy Snippet extension (for Chrome) very interesting. It's supposed to let you make a "live" screenshot of a DOM element. Unfortunately, I've not tried it much as I only rely on Firefox in day to day browsing.
Ugh, I really hate when I stumble upon a research paper only available in html and not in a standard two-column pdf - I find it much harder to read in general
An interesting thing to think about was people used to think of getting somewhere. Now we think of things coming to us. In a way, we did achieve the "zipping around", it's just that we did it via the internet and wireless communication. Of course, it is not the same, but it is similar.
An interesting question I've been thinking about, though I haven't really gotten anywhere is: At what point does a private platform become a public utility, so that censorship is not permissible on the site?
I agree that reddit shouldn't be censoring anyone or certain topics since it feel like a public utility. But if I were to have a blog, I think I should be allowed to block someone or delete certain comments based on how I think my blog should be, but my blog isn't a public utility. Or is it?
Your platform hasn't been granted a monopoly on anything and has no moat, so why would it ever be a problem?
daringfireball.net is a blog with no comments and at some point someone wrote a browser extension that just adds a comment section the owner of the site has no control over. Bit mean but that could always happen to you.
Great post from patio11 as usual! Reminds of the notion of taking small bets that Taleb often talks about. A side project might only take 20 or 30 hours of your time over the course of a month or two, but it can give you great upside.
Though one (perhaps nit-picky) point I'd like to make is that these dictators are not dumb. They are incredibly intelligent. They themselves are probably not hackers, but they understand people and power. They are going do what they can to get what they want. We can't ignore the factor they play in creating these problems, and we need to take it just as seriously as we would a technical security exploit.