I haven't read this study, but any study that isn't complete garbage normally would examine the to groups across all variables (age, gender, weight, health, etc) and deliberately control for any systematic differences between groups.
12,479 karma · joined April 18, 2014
I haven't read this study, but any study that isn't complete garbage normally would examine the to groups across all variables (age, gender, weight, health, etc) and deliberately control for any systematic differences between groups.
Tests are more valuable on more complex codebases.
Local tests (shifting left) is more valuable when deploying is hard/infrequent and screwing up prod has higher stakes.
These factors explain why most startups should code differently than big corps.
Should you fail (illegal pesticides, ingredients differ than label, too much lead, whatever) then you lose your deposit, all profits made that year on that product, and go through a process of re-earning the right to sell that product.
For small local brands I'd exempt them until the economics became viable.
During the learning stage we want input from every variable so that we are sure that we don't omit a variable that turns out to be essential for the calculation. However in any calculation a human does 99.9999% of variables are irrelevant (e.g. what day of the week it is, am I sleepy, etc), so of course the brain wouldn't use resources to keep connections that aren't relevant to a given function. Imagine what a liability it would be if we have had excessive direct connections from our visual processing system to the piece of our brain that controls heartrate.
I remember working at a place and our whole data-team (myself included) seemed like a useless waste a dozen engineers. I thought the company was adrift. A few years later it was bought for billions of dollars because the business people knew exactly how to threaten a dominant player in the market. And I realized my henny-penny attitude was complete noise, I just was out-of-the-loop about what the long-term play was.
I think a lot of this is that we each want to be the center of our own universe, we want our problems to be the THE problems, and to some degree understand that peddling our advice about tech X or Y is to some degree advancing our own influence.
Maybe this is part of the problem -- that it's called one thing (a plan to improve performance) but is used as another (legalese once you've already given up hope).
But I've never quite understood why. I imagine if I was a manager people would know if they are doing 20% as much as the best team member and would either be off the team or have shaped up within 6 months. That period where you genuinely are making sure that somebody understands you think they aren't doing well and clarify expectations seems valuable and ideally would happen long before it's too late.
That's not really what this article finds... the title is "Loneliness corresponds with neural representations and language use that deviate from shared cultural perceptions", but even that title is too general when it's only talking about a handful of pop-culture celebrities.
And also, remember when a researcher says "loneliness" they mean "self-reported loneliness," I know a lot of people with very little companionship who might insist they are a 0 out of 10 on the loneliness scale.
There's so many different ways to interpret this data:
Perhaps people who are willing to admit they are lonely (usually something that's very mildly frowned upon in my experience) are more willing to break with social norms. Or perhaps having wild takes on reality results in you becoming lonelier. Or perhaps a few outlier individuals really pushed the average. Or perhaps people who are less lonely are generally more knowledgeable/well-informed about these individuals. Etc etc.
Nah, most of that list is basically free for any company that uses an amazon loadbalancer and an autoscale group. In terms of likeliness of incidents, time, and cost, those will each be an order of magnitude higher with a team of kubernetes engineers than less complex setup.
> I can't see how it can take 4 months to figure it out.
Well have you ever tried moving a company with a dozen services onto kubernetes piece-by-piece, with zero downtime? How long would it take you to correctly move and test every permission, environment variable, and issue you run into?
Then if you get a single setting wrong (e.g. memory size) and don't load-test with realistic traffic, you bring down production, potentially lose customers, and have to do a public post-mortem about your mistakes? [true story for current employer]
I don't see how anybody says they'd move a large company to kubernetes in such an environment in a few months with no screwups and solid testing.
- One had only 2 services [php] and ran over 1 billion requests a day. Deploy was trivial, ssh some new files to the server and run a migration, 0 downtime.
- One was in an industry that didn't need "Webscale" (retirement accounts). Prod deploys were just docker commands run by jenkins. We ran two servers per service from the day I joined the day I left 4 years later (3x growth), and ultimately removed one service and one database during all that growth.
Another outstanding thing about both of these places was that we had all the testing environments you need, on-demand, in minutes.
The place I'm at now is trying to do kubernetes and is failing miserably (ongoing nightmare 4 months in and probably at least 8 to go, when it was allegedly supposed to only take 3 total). It has one shared test environment that it takes 3-hours to see your changes in.
I don't fault kubernetes directly, I fault the overall complexity. But at the end of the day kubernetes feels like complexity trying to abstract over complexity, and often I find that's less successful that removing complexity in the first place.
And in the end usually the company loses out - directors forge ahead with ill-informed projects (rewrite entire system X), don't measure/cherry-pick/game-metrics, and create a major threat to anybody on the team who surfaces any contraindicating metrics (e.g. "Our pipeline still takes Y hours and nobody is happy about it, including us").
Jail time to the CEO of that compary for fraud (because it wasn't FDIC insured) or full reimbursement of all creditors.
I'm okay with either, but if neither of those happens then it's a failing system.
Apparently police are allowed some threshold of deception (e.g. can outright lie but can't pretend to be your lawyer) but since 99% of people don't know this it really undermines the purpose.
Like if the police can lie, but tell you that you get an attorney, how is a client supposed to know that your lawyer can't lie to you too?
Part of the skill of engineering is knowing when you need to do upfront engineering and when you can just throw some code at the wall.
Like suppose you're talking to somebody over text and your gut says they're being an asshole, but your brain is rereading what they say and can't find anything specific to call out.
Which is correct?
Well, I've found that the gut is systematically unreliable in a number of situations... Are you in a bad mood for example? They say never go food shopping when you're hungry.
Not to say mind > gut, because that's just as stupid as saying gut > mind. The point is that there are dozens of variables (variables like mood) we need to learn in such evaluations, and generalizations can rarely be useful.
> soy turning me trans or social media turning me trans I agree is absolutely mind-numbingly naive.
However, I feel like there's only so many options for where sexuality and gender-identity can come from -- and if we know there's no god doing it, and we know it's not entirely learned (because of case studies of surgeons who assigned a gender to babies with ambiguous genitals), the remainder must be from the environment... and it just so happens that almost all of the body's signaling around gender, puberty, and development is chemicals in one form or another.
Would love to hear confirmation from an iOS developer
Every single engineer has to start over in their mastery experience by learning all the new quirks and issues, and all the tools, libraries, pipelines need to be rewritten.
IMO better to support the dominant tooling than invest in fracturing one of the few areas where engineers can agree on something for once (to everyone's benefit).
For example, if a parent exhibit autism symptom X (e.g. trouble understanding emotions), are there kids more likely to inherit symptom X, or ANY autism symptom.
If X is uniquely heritable, then perhaps it's best as multiple disorders. But if X leads equally likely to X, Y, or Z then it's better understood as one disorder.
Also a domestic plastic tax - by making plastic less cheap (perhaps have it go up 10% every year in perpetuity) eventually there will be incentives to find natural alternatives (paper, bamboo, woods, etc).
It makes no sense to me to claim the most productive country in all of history, with our AI and everything, couldn't replace plastic. It's the same thing people said about oil 50 years ago.