They likely were running data on EBS volumes instead of bare metal SSDs, due to ease of recovery (a failed instance does not lose data on the attached EBS volumes). You can only run your DBs on bare metal SSDs if you are prepared to lose a node’s data completely.
In fact, many instance types no longer have any ephemeral storage attached and it’s a default practice to use EBS for root and data volumes.
There are some instance types that have extremely fast EBS performance (EBS io2 Block Express), which has hardware acceleration and an optimized network protocol for EBS network I/O and offers sub-millisecond latency. However, these are expensive and get even more so if you go up in IOPS.
Even if the rollout was atomic to the servers, you will still have old clients with cached old front ends talking to updated front ends. Depending on the importance of the changes in question, you can sometimes accept breakage or force a full UI refresh. But that should be a conscious decision. It’s better to support old clients as the same time as new clients and deprecate the old behavior and remove it over time. Likewise, if there’s a critical change where you can’t risk new front ends breaking when talking to old front ends (what if you had to rollback), you can often deploy support for new changes, and activate the UI changes in a subsequent release or with a feature flag.
I think it’s better to always ask your devs to be concerned about backwards compatibility, and sometimes forwards compatibility, and to add test suites if possible to monitor for unexpected incompatible changes.
And think about what it’s like for humans as well—-spreading a feature over several repos with separate PRs makes either a mockery of the review process (if the PRs have to be merged in one repo to be able to test things together), or significantly increases cognitive overhead of reviewing code.
False. Mongo never pretended to be a SQL database. But some dimwits insisted on using it for transactions, for whatever reason, and so it got transactional support, way later in life, and in non-sharded clusters in the initial release. People that know what they are doing have been using MongoDB for reliable horizontally-scalable document storage basically since 3.4. With proper complex indexing.
Scylla! Yes, it will store and fetch your simple data very quickly with very good operational characteristics. Not so good for complex querying and indexing.
If you’re doing a restructuring of the company, i.e. mass layoffs, you’re allowed to do it regardless. In some states FMLA/PFMLA a company is automatically presumed a retaliation firing if it’s done within 6 months and the onus is on the company to prove it wasn’t—-the mass layoff is the cover, and large companies know it.
However, the fact that they cancelled her health insurance a week before returning and demanded she returned on a certain date or she’d be terminated despite a demonstrated disability, that’s pretty whack and might be hard to defend as company-wide restructuring.
Heavy mocks usage comes from dogmatically following the flawed “most tests should be unit tests” prescription of the “testing pyramid,” as well as a strict adherence to not testing more than one class at a time. This necessitates heavy mocking, which is fragile, terrible to refactor, leads to lots of low-value tests. Sadly, AI these days will generate tons of those unit tests in the hands of those who don’t know better. All in all leading to the same false sense of security and killing development speed.
I get what you are saying, but you can have your cake and eat it too. Fast, comprehensive tests that cover most of your codebase. Test through the domain, employ Fakes at the boundaries.
We know that severe stress (such as trauma) leaves chemical marks on the genes, potentially passed down to the offspring. For example, this paper writes about an “accumulating amount of evidence of an enduring effect of trauma exposure to be passed to offspring transgenerationally: https://pmc.ncbi.nlm.nih.gov/articles/PMC5977074/
Though “lived experience” can encompass a lot of things, it definitely encompasses severe stress.
For example, constantly worrying about money because you’re poor can definitely put you under severe stress. Also, growing up without secure attachment to your caretakers, being asked to do role reversal (having to take care of your parents as a child), things like that will generate complex PTSD.
The comment you’re replying to suggests “lived experience” is too broad, not too narrow. The issue isn’t that it fails to include your example. It fails to exclude other things. Part of my lived experience today was seeing a manatee. It is unlikely this will be passed on.
And the comment you’re replying to suggests that since many lived experiences are plausibly heritable, the term is appropriate. In any case, the context in which it is actually used in the article seems beyond all but the most pedantic reproach:
>The first is how a father’s body physically encodes lived experience, such as stress, diet, exercise or nicotine use
And that’s a single sentence partway through the article. From the beginning, the refrain is the list of the sorts of things that seem to have heritable effect, not the phrase “lived experiences”.
>Research into how a father’s choices — such as diet, exercise, stress, nicotine use — may transfer traits to his children
>Within a sperm’s minuscule head are stowaway molecules, which enter the egg and convey information about the father’s fitness, such as diet, exercise habits and stress levels, to his offspring
Etc.
The article is clearly not attempting to suggest that all experiences are heritable.
It feels so wonderfully weird reading about some else seeing a manatee today. I too saw a manatee while walking with my kids today. The interesting part was our navigational strategies complementing each other (me – misremembering the details of a road closure, and them - getting curious about what a bunch of people at a marina are looking at) to find a group of manatees in a place we didn’t know they can be found.
A lot of this is transmitted via the language. The stories we form as a result of events in our lives, have power to set our values in all areas. These myths of the self, have what is essentially a value manifest for someone. And these myths, can be so strongly held that it will influence the person and family’s moods, actions, habits.
What is important is to note that there are many formulas for consciousness. Some are truely bonkers, some are just fundamental truth. And some… have yet to be discovered.
Permutations and combinatorics create a hyperspace of all ridiculous things!
> The authors pointed out “there are significant drawbacks in the existing human literature” including “lack of longitudinal studies, methodological heterogeneity, selection of tissue type, and the influence of developmental stage and trauma type on methylation outcomes”
The literature in this area is a mess, has become highly politicized. I’d give it another 10 or so years before I made any strong statements about these effects in humans. Famously the study of Holocaust survivors’ descendants didn’t show transgenerational effects.
Additionally, warnings can be built into the clients themselves. If you connect to a host with less than 2 weeks cert expiry time, print a warning in your client. That will be further incentive to not let certs be not renewed in time.
reply