skysight-inc/HackerNews huggingface dataset:
Free will is another one of those things that people love to trot out because it's so ill-defined. To cut through all the crap though, it's very simple: "free will" === "unpredictable behavior". This inherently means that it's observer-dependent.

This has the benefit that it empirically fits how people think about it. Nobody thinks a rock has free will. Some people think animals have free will. Lots of people think humans have free will. This is everybody trying to smush a vague concept into the very simple, intuitive definition above.

Which is all to say that free will is about as relevant to any conversation as say astrology is: not one bit.
Will try once they release the version based on Ubuntu 22.04.
> "We only merge code that is ready to go live"

I like to go even farther, I advocate only merging code that won't break anything. If you're feature flagging as many changes as possible then you can merge code that doesn't even work, as long as you can gate users away from it using feature flags. The sooner and more often you can integrate unfinished code (safely) into master the better.
Inflection Point for ML and Art
Interview with a Vim Enthusiast 2022
Everything is exaggerated nowadays. “Unenforced suggestions to stay at home” = lockdown. “A minor inconvenience” = torture. “Sensible public health policy” = tyranny.

No US state implemented anything close to what a reasonable, sane person could describe as lockdown. Nobody was locked into their homes. Stay at home was routinely broken with zero consequences. Business closures went unenforced outside of a handful of urban areas. Calling it “lockdown” is clown world logic.
Although my theme has a minimize button, I think didn't use for more than a decade. If you need space go to a new desktop. And organize your files in you home directory sub-folders, if you need temporary space, use /tmp which will delete it on the next boot (beware of privacy issues if other people are also using your computer).

Since I got used to multiple desktops, I really don't see much value on the minimize button. I makes harder to use the app. If I want to alternate to another app, I just click it or alt-tab to it; minimizing it makes it harder to alternate to.
>> if people are malicious or negligent or just not good at their jobs, adding more process to get around that only makes things worse.

That's why there is a hiring and firing process.
Interview with a Postdoc, Junior Developer in 2022
Sibling here but I can talk a bit about how we do it.

Through infrastructure as code. We do not have a monolithic backend. We have a bunch of services, some smaller, some bigger. Yes there's "some frontend" but it's not just one frontend. We have multiple different "frontend services" serving different parts of it. As for database, we use multiple different database technologies, depending on the service. Some service uses only one of those, while others use a mix that is suited best to a particular use case. For one of those we use sharding and while a staging or dev environment doesn't need the sharding, these obviously use the only shard we create in dev/staging but the same mechanism for shard lookup are used. For data it depends. We have a data generator that can be loaded with different scenarios, either generator parameters or full fledged "db backup style" definitions that you can use but don't have to. We deploy to Prod multiple times per day (basically relatively shortly after something hits the main branch).

Through the exact same means we could also re-create prod at any time and in fact DR exercises are held for that regularly.
Non-prod is free.
This is not true. We and I had finished tons of projects. They are done in the true sense. We are OK with their state and they rarely ever change. They work.

We moved on other projects.
> Individual development is very important.

Not sure if you’ve misread the thread - the whole problem is too much importance on individual development and the pressure this brings.
I’ve been shipping software for over two decades, built multiple successful SaaS companies, and have never in my life written a single unit test.
Agree with that. I think I'm thinking of confident (not disrespectful) force. Just being assertive about what you think you deserve, that sort of thing. And some people are too excessive at it, possibly because others are insufficiently capable of it.

I look at Putin (also clearly a bully) and I think, was there a "posture" that Ukraine could have taken prior to this which would have discouraged him before he committed to what he is doing now? "Promising not to join NATO"? I guess the analogy would be a bully beating up a neighbor's kid to prevent him from joining a rival gang? I don't know. You acquiesce to the bully and usually the bully's demands just go up. Could Putin's advisors have gotten past their fear and been more honest with him? Well, that's the problem with ruling with fear (or perhaps I should say "using fear excessively" with the insinuation that plainly confident (but yet respectful) people do strike a bit of fear in others), you never get the whole truth.
Real interview with a Perl programmer in 2022
Disclaimer: I worked for a major feature flagging company, but these opinions are my own.

This article makes a lot of valid points regarding staging environments, but their reasoning to not use them is dubious. None of their reasons are good enough to take staging environments out of the equation.

I'd be willing to be that the likelihood of anyone merging code that isn't ready to go live is close to zero. You still need to validate the code. Their branching strategy is (in my opinion) the ideal branching strategy, but again, that isn't good enough to take staging away.

Using feature flags is probably the only reason they give that comes to close to being okay with getting rid of staging, but even then, you can't always be sure that the code you've built works as expected. So you still need a staging environment to validate some things.

Having hands-on deployments should always be happening anyway. It's not a reason to not have a staging environment.

If you truly want to get rid of your a staging environment the minimum that you need to feature flagging of _everything_, and I do mean everything. That is honestly near impossible. You also need live preview environments for each PR/branch. This somewhat eliminates the need for a staging because reviewers can test the changes on a live environment. These two things still aren't good enough reason to get rid of your staging environment. There is still many things that can go wrong.

The reason we have layered deployment systems (CI, staging etc) is to increase confidence that your deployment will be good. You can never be 100% sure. But I'll bet you, removing a staging environment lowers that confidence further.

Having said all of this, if it works for you, then great. But the reasons I've read on this post, don't feel good enough to me to get rid of any staging environments.
Dunno, haven't got one myself.
The pay gap stuff is bullshit with no real analysis.

I worked at a union shop where everyone was paid on a tenure based scale, and you qualified for advances as long as you had 500 hours of paid (working or not) time in a calendar year. There was literally no way to have a pay gap.

But… a group of women complained, and the company agreed to open a few female only promotions to buy them off.
Are you saying that wasn't his fault? I agree it's a false dichotomy between the process failing and people sharing blame.
> If they are being denied a promotion, then they're doing the same old job as their male counterpart.

In many tech companies, just because you’re the same level doesn’t mean the work you do is the same, and moreso performance at your work. Another restatement of what I said is that it would be interesting to also consider how quickly men get promoted over women given similar skill sets/levels, which I acknowledge is difficult to quantify.
At a previous workplace we managed flags with Launch Darkly. We asked developers not to create flags in LD directly but used Jira web hooks to generate flags from any Jira issues of type Feature Flag. This issue type had a workflow that ensured you couldn't close off an epic without having rolled out and then removed every feature flag. Flags should not significantly outlast their 100% rollout.
Well, humans aren't necessarily logical and consistent, are they? Obviously you don't see the people who are isolating at home trying to avoid this virus, because well, they're at home and not out and about being judged by you. What if they know that the people they're dining with are healthy, vaccinated (less chances of catching the virus and being infectious) and/or were recently tested?

Aren't the people who defiantly enter places with mask mandates without their masks also signalling their virtue of being "free thinkers" and "not a government sheeple"? But if I can guess, that's OK for you because they're the ones doing the right thing.

I'd tell you you suffer from confirmation bias, but hey, I guess you've heard that too. But no! You're right and everyone else are morons!
Thinking about Thinking
Most features are simply disabled by default but can be toggled. You can bloat it all the way up to a regular Windows 10 installation.
> women having and raising children should result in no interruptions of their career growth or earnings

is different from

> affects both equally

Perhaps the first should have been "women having and raising children should result in no interruptions of their career growth or earnings greater than those experienced by men".
The most crucial part is a setup that lowers the barrier to publish.

Something that you like to use regularly.
Going off on a tangent, if you liked that clip, I can only recommend to check up LMan's impressive remixes at RKO: https://remix.kwed.org/search/lman

Start with Turrican I end titles and go from there.
In case it helps, I think the original post was not meaning to say that the mind is not chemically based in the brain. I did not see it as a contradiction in their position.

I think their use of "chemical" was part of an assumed dichotomy between chronic disorders referred to in pop-culture as "chemical imbalances" versus other (learned or cognitive behavioral) disorders which could presumably be unlearned. The difference is mirrored in the assumed intervention: whether a continuous maintenance dose of some drug is needed to manage the chronic condition versus a transient dose or other therapy which allows the brain to assume a healthier posture and maintain itself thereafter.
> Students cannot miss a homework assignment, fail an exam, not achieve an A, make any kind of faux pax on social media, etc…

As someone close to a high school student, I’m actually surprised how much “make up” is allowed. All missed assignments can be done any time during a semester for no penalty. Two exams can be retaken for a max grade of 80.

When I was in high school there were no retakes at all.
Indeed. I remember interviewing for several positions and could have done them with one hand behind my back. A ~year later they were still trying to fill the position but hadn't.
So afraid to write bad, spaghetti code, I ended up writing no code at all.

This thread made me realize that it's better to have a working profitable project with bad code, than a perfect unfinished project, with meticulously chosen design patterns.

Afraid of being judged for bad code, I could not start until I had the right architecture.

I'm glad I read this.

This is developers therapy.
I mean, all these things are true. The middle class is disappearing, and society is quickly bifurcating into a few haves and the rest have-nots. When I was a kid, you could get B’s or C’s and have a good job after high school. Now you’re competing with the smartest of the ~50M other kids your age globally for one of the few tickets out of poverty. And you can bet if you miss that one homework assignment or get that one B, you’re way behind the kids who are doing everything to 100% perfection. I can understand how it is a pressure cooker of stress!
Interview with a senior PHP developer in 2022
Those bullets together explain how they can avoid having a staging environment.

There's a whole section of the article entitled "What’s wrong with staging environments?" that explains why they don't want staging.

They even presented their "why" before going into their "how." There is absolutely nothing weird about this.

Well, ok, it's weird that not all so-called "software engineers" follow this pattern of problem-solving. But that's not Squeaky's fault. They're showing us how to do it better.
I’m not blaming the progressive prosecutors—I’m listing them as a casualty of what happened. I do blame the rioting for the increase in homicides.
CORSIKA, current Version 7, is a program to simulate extensive air showers, ie particle physics in the atmosphere.

It's main file is 88kloc Fortran 77, started in the eighties, still actively developed.

https://www.iap.kit.edu/corsika/index.php

Currently a rewrite in c++ is underway.
A long time ago I played Galaxy Plus - a variant of Galaxy PBEM game with simple rules and a galaxy full of races controlled by humans - 50 players start a game, 1-3 win in the end.

It was one of the most intense gaming experience I have ever had. With 3 turns per week, a single game could last for a year, and to win you had to be a good diplomat to not get swarmed by your neighbors. It also taught me a lot about politics.
Why don't let customers decide? Just require manufacturers to be more transparent. I've argued long time that most regulations could be replaced with mandatory transparency. Manufacturers should be open about their quality and lifetime of their products. No one buys a bad product if they know about it.
I think we have different definitions of naked! I think you're taking it to mean: use a lot of infra, but maintain none of it. I thought it would mean: strip everything down to bare essentials. Services like CI are niceties, not essentials.

But I'm not the target audience. I think the idea of naked blogging is kind of silly. Blog if you want to blog, your clothing choices are your own.
The 2nd law should have gone the way of the dodo since this was discovered: https://en.wikipedia.org/wiki/Population_inversion

Science progresses one funeral at a time while stragglers are holding on to what amounts to a natural philosophy of the ego. General relativity does not conserve energy and quantum mechanics either does away with local realism or postulates consciousness as the creator of observable reality. - There is no place left to hide for the egos hungering for a Nobel Prize.
If you can, provide on-demand environments for PRs. It's mostly helpful to test frontend changes, but also database migrations and just demoing changes to colleagues.

If you have that, you will see people's behaviour change. We have a CTO that creates "demo" PRs with features they want to show to customers. All all the contension around staging as identified in the article is mostly gone.
I work at a different company. Typically feature flags are short-lived (on the order of days or weeks), and only control one feature. When I deploy, I only care about my one feature flag because that is the only thing gating the new functionality being deployed.

There may be other feature flags, owned by other teams, but it's rare to have flags that cross team/service boundaries in a fashion that they need to be coordinated for rollout.
I think they’re talking about the replies
Without a staging environment, how do you test that large scale database migrations work as intended?

I wouldn't feel at all comfortable shipping changes like that which have only been tested on laptops.
hermit: https://github.com/Track3/hermit/
>That said features and bug fixes were often times gated by feature flags

Sorry for maybe a silly question, but how do feature flags work with migrations? If your migrations run automatically on deploy, then feature flags can't prevent badly tested migrations from corrupting the DB, locking tables and other sorts of regressions. If you run your migrations manually each time, then there's a chance that someone enables a feature toggle without running the required migrations, which can result in all sorts of downtime.

Another concern I have is that if a feature toggle isn't enabled in production for a long time (for us, several days is already a long time due to a tight release schedule) new changes to the codebase by another team can conflict with the disabled feature and, since it's disabled, you probably won't know there's a problem until it's too late?
This exposure wasn’t mainstream until the early-mid 10s when every high schooler got a phone and social media. Before then, it was computer and game system based and that changes.

I don’t know real screen time data, but the use of phones probably added an extra 4-10 hours of screentime per day. And the type of activity is very different with notifications and pickups being top of mind.
> If you use a streaming service you're hearing the latter and might not ever realize the former existed.

On a number of live Bob Dylan albums, for inexplicable reasons all online versions (not just streaming, but the download releaes, too) are now missing the between-tracks content that on the physical CDs is part of the pregap, which means you're missing out on the funny stage banter on the 1964 Halloween concert, or the infamous heckling on the electric half of the 1966 Manchester concert.
People love to complain about things that are simple, fast, and easy to complain about, without regard to whether the complaint is insightful or useful. It's sort of the dark twin of bikeshedding.

If you divide the single 11k-line file into a thousand 11-line files, it may become objectively much harder to understand, but it'll also receive much less flak, guaranteed.

I suspect this is also why Architecture Astronaut-ery can be so successful within a company. If code is chock-full of superficial signs of order and craftsmanship, such as hierarchy, abstraction, and Design Patterns(TM), it takes a lot of mental effort to criticize it, and most people won't.
I got lazy in my old years. I just use rclone and google drive.
Oh, OK. I did misread it. My bad.
The company does some analysitics on highly redundant data (user behavior on website). They run a system with low requirements for a avaibility, correctness, and feature churn. Their product is nice to have but not important to mission on a daily basis. If their entire system went down for a day, or even 3 days a week, their customers would be only mildly inconvenienced.
They aren't Amazon or Google. So they test in prod.
Ask HN: How do I write quick and dirty, spaghetti code?
I want to start a project, with no concern for design patterns, clean code, separation of concerns.

I want to write the most spaghetti, working, hacky code that works.
C#, Java, Php, JS or python.
What tips do you have? You might need a throwaway for this hahaha.
The presumption here is that there is something to be liberated from. That men and women are generally better suited toward different aspects of parenting is not an artificial construction. Ideological commitments have taken the place of reason.

The result will be that those who do live in a way more aligned with human nature and the specializations each sex entails will out breed those who don't.
My assumption is the process is more like this:

Laptop --> pull request + CI --> merge + CI + CD --> production

I don't think folks are pushing code directly via Git or SFTP.
I still think there’s a place and need for such “computer-consoles” even today:

Self-contained devices that boot up within a second out of the box, and let you program right away. In this age of course we’ll need a basic GUI, and an app store as well.
Viktor Orbán expected to win big majority in Hungarian general election
> Economic forecasts being shit

Aren’t we in the longest economic boon ever? This might be the first bear market in over 10 years.

Schools didn’t require sats and other exams and were actually easier to get into during the pandemic. The past two years were like a glorious time for school admission.
One question is why try to start a trend if that isn't what men want? It seems like trying to manipulate desires to meet some other goal. If men want to care for children, then good! We should respect their wishes, but why try to change desires?
> I've seen code fail in each of the stages

How many of the failures caught in dev would have been legitimate problems in production? How about the ones in staging?

If your environments are that different are you even testing the right things?

And if yes, if you need all of those, then why not add a couple more environments? Because more pre-prod environments means more bugs caught in those, right? /s
How do I do that in iOS Safari?
I have a lot of questions, but one above all the others. How do you preview changes to non-technical stakeholders in the company? Do you make sales people and CEOs and everyone else boot up a local development environment?
What's Wrong with the Patent System?
You pointed at crabs and lobsters as proof of the frequency of asymmetry by citing two of the hundreds of species having two of their eight appendages being asymmetrical. I would suggest this might be confirmation bias in action.
How do you feature flag a refactor?
As a left handed person that has had to deal with a system designed for right handed people, can I also join the pity party, and call myself a victim of discrimination?
Did you contact support? Seems like they’d be able to handle that for you.
It's not about taking pride or lacking in humility, but simply about not considering it "normal" to screw things up. If you don't think of screwups as something "everyone does anyway", fixing them and making damn sure they won't reoccur becomes second nature. You don't need more than a simple apology, because everything else is implied and a spoken commitment would be meaningless anyway.
I don't work on systems where that factor is critical to our tests, but if I was I would start here (at least in my case since we use AWS) https://docs.aws.amazon.com/solutions/latest/distributed-loa...
People seem revolted by the idea of artificial wombs but I don't understand why.

Can you explain your perspective to me?
Unlike the OP's file, there's a rather substantial test suite and massive corpus of TypeScript code to work with, so at the very least, you'd have some grumpy people knocking on your door if you did something that negatively impacted the greater ecosystem.

Some documentation from Orta Therox on the checker:

https://github.com/microsoft/TypeScript-Compiler-Notes/blob/...
You copy your service into refactored_service and feature-flag which of the two microservices the rest of the system uses /s
Why not just TrueNAS?
But the outcomes are so the system is discriminatory.
How do you define a large scale database migration? If you're just updating data or schema, that can be done locally via integration test. No need for a separate environment.
> This might be common knowledge, but it was a recent TIL for me. Chip scale atomic clock

Old news indeed.

Facebook have been using it in production for a while now[1] and released all the details under the Open Compute Time Appliances Project.

[1] https://engineering.fb.com/2021/08/11/open-source/time-appli...
> First make sure you're familiar with background issues in numerical analysis/computation such that you're generally familiar with IEEE floating point and its foibles, numerical stability, basic error analysis etc.

So, what's the book for learning that?
Writing long files is okay, but u less a languages module system gets in your way seperating different aspects of your code into different files does no harm.

There is no need — at all — to be evangelical about it one way or another.