I've literally never had an issue not separating laundry. Years of mixed loads never any colours bled, I thought the whole thing was a myth.

Last week I washed a red dress of my wife's with whites, and all my shirts came out pink like a sitcom. It's real people.

Don't upset the Basilisk guys

If you can't imagine a fate worse than that go read a history book

Are you perchance a race and gender that hasn't historically been persecuted under fascism? There are a few things worse than a flu.

I feel the Team Fabric point so strongly. My team has gone from 2 reviewers per PR, to now 1, and open conversations about going to 0 with only AI review.

Feels less like a team every day, and more like a room of individuals, with less and less understanding and insight into what others are doing. Everyone is carving out their own kingdoms in the repo, that only they and their agent understand and can operate on, with internal patterns and designs.

Do we not see how big a risk this is if anyone leaves? Code review was for finding issues for sure, but for me that is at most half the purpose. The other purpose is driving consistency across the codebase, and disseminating knowledge amongst the team.

I feel that despite the stereotype of software engineers as loners, a lot of people I've worked with are deeply collaborative, and this is fuel on the burnout fire.

Intimidation is not covered under free speech.

The cause of war in Ukraine isn't (widely) disputed or controversial, outside of extreme circles. Unfortunately human-caused climate change being the driver for extreme weather is.

Does it matter? They've already paid. I'd rather people who aren't into the movie left, than were disruptive.

I disagree. We're all accepting that the modern world exists primarily online, but instead of preparing our children for the online world, we build a walled garden with no access, until the age of 16 where they get unlimited, uninformed access.

The only solution to this problem is parents teaching and directing their children. The state cannot and should not be involved

I heard there is some football going on, not an expert tho

It also depends when you submit them though, if you only submit them in 2 months they can't tell how much was before and after the change, so will assume it is all after. This is even if they aren't estimating your readings.

Before Brexit the chosen enemy was Polish people/generic eastern Europeans. They are ostensibly white, but many conflicts were over the number of them that were coming to the UK to work, despite that they were mostly doing jobs with high demand like cleaners.

It's only since Brexit that non-European immigration has skyrocketed, as well as the onset of the small-boats issue, since we can no longer send them back to France.

Don't re-write history.

I think the idea is to pay these people to deduplicate and verify vulnerability reports, so the responsibility doesn't fall on every maintainer to do that same process individually, so they can focus on fixing the real bugs.

If you ever see someone ask a lawyer how they can represent a murder defendant, this is why.

I love that nobody watched anything on Yahoo! Screen except for that one season of Community

Interesting, could be a move away from typewise, do you support their gestures? Left to delete and up for capitalised.

Like, you might have someone working on something in a new codebase but misunderstanding the architecture or just going in the wrong direction in general and a review is the best way to correct course before getting too far in

I think the article is suggesting this person should be pair programmed with until they understand the architecture and can be trusted to contribute correctly, and I actually kind of agree - it always feels terrible to tell someone a PR they've worked on possibly for days is completely the wrong direction, and arguably this is already 'too far in' if they're going to need to essentially start again.

Intervening earlier in the process should lead to less wasted effort overall, but people often seem to treat pair programming like its two people at 50% efficiency, when it actually saves a lot of cycle time on reviewing code.

I didn't say programming is unecessary, and I'm a proffesional software engineer with a degree in computer science. When I say 'learn to code' is over I mean the pressure for anyone and everyone to learn to code because there are so many well paying software engineer jobs.

This era is over undoubtedly, because all the people who never really cared about software engineering and are just there to collect a paycheck are going to be replaced - but the profession of software engineering will still be necessary, and the abstract maths of computer science isn't going anywhere as a field of research.

'Computer Science is no more about computers than astronomy is about telescopes.'

Study computer science if you like it, it's never been about making good 'coders' or software engineers.

I don't think the number of software engineers will ever drop to zero, but the days of 'learn to code' to get a high paying job guaranteed are definitely over.

Any service you depend on in the modern world, you need to be asking yourself 'what will I do when this enshitifies itself'. And it is a when.

Short termism on all sides is destroying our society.