N and B are equal and loss of one depends on the current situation of the board :d

Forks and all of that comes with playing the game. It also comes from the easiest / most approachable way to play chess - puzzles. So far so, that it’s insanely popular on Facebook, where some guy pastes an amazing move from the past and a butt-ton of people stop and think about it.

Also, forks and stuff is often overkill. You can get to like 1200 rating by knowing like 4 - 5 moves in the start. Most games are decided by someone making a huge mistake. And in the first matches, that guy will probably be you. But then suddenly you’ll notice a huge fuckup and win a game over it. And then the fuckup will be slightly smaller, and smaller, and smaller.

But yah, chess isn’t all intelligence, it is a lot of practice and study.

The answer to the “chess” thing is “yes, you will get better if you play it for long enough”. It’s a lot about pattern recognition and the things you’ve seen in the past. There are certain rules to follow that help a lot - but someone needs to teach them to you first. It’s like saying “I suck at crosswords, I will never be good at them” - yes you will, with enough done you’ll start to see repeating “crossword words” that keep being used over and over.

Edit: also for the life thing - it’s the difference between wisdom and intelligence.

Only if it isn’t a single button.

The point is the same as with hiding the yt dislike button. It helps people determine if something is of higher quality or not.

I mean, that’s how the report button works site-wide. If we are talking about a button that works automatically, then you are basically copying the downvote, but worse, since it cannot be offset by many people upvoting.

You need to remember that it is hard to distinguish between a downvote / button use because of spam / harassment and because of people not liking something. You need a human to do that. Fetish content will get downvoted / buttonned by people “not into it” when obscure enough. Regular OCs will also get that treatment - since users will get bored and seeing new content from them may make them downvote / button.

Such buttons aren’t really supported in mobile apps though.

There is a difference because you have anecdotes, not data. You can’t draw conclusions from them. The entire “experiment” could be poisoned by a single person with joint disease. It could be poisoned by a single person lying about the severity of the pain etc.

Okay, but you can’t say “he killed him” when he could be brought back by anyone. Especially since even the museum guy knew that the gun is for dehydration, so that means Megamind’s powers / gadgets are relatively known.

Wasn’t he just a proud dude that disagreed with how the song of creation was to be sung - and sung his version anyway? But then it was “all according to plan” anyways?

He didn’t kill him he used the dehydration gun which turns people into cubes. He can be put into water and will be back like nothing happens. He even used that in the finale to defeat Tighten

Yeah, but that always was the point of Half Life - they wanted huge leaps in gaming to be possible to release the next game. That’s why HL2 had the first “physics” engine, ragdolls etc. That’s why GMod is possible. Now the “leap” is VR

Alyx is HL3, wdym

I mean, people will imagine a similar thing when asked to imagine something specific. At the end of the day there’s just so many ways to imagine someone pushing a ball off a table.

Depends on the area and location.

Why code a single time bounty for 6k that probably will take you months if you can work a regular programmer job and get 10k a month?

Had a “relationship” like this with my ex. Lots of “sexish” things, dates, furniture building together, inside jokes to denote “drop everything, it’s cuddle time”. First week we met after a long time of no-contact (we dated, broke it up, then she reached out after a few years and we started working together) we locked so hard in deep conversation, that we almost burned the house down (we left a pot of boiling soup on the stove; then remembered about it a few times and conciously decided not to check it because we were feeling so great talking). We thought “oh we are just talking for 10 mins, it’s fineeee” when that shit went on for hours.

Yet it “wasn’t a relationship” after it fell apart. That shit ruins a person. I basically felt gaslit hard, questioning my sanity, the choices I made. Still trying to recover really

Well, there you go - the issue is with the company and the irreplacable boss. He is the weakest link obviously. Imagine he gets into a car crash, gets hit by a bus. Suddenly all his knowledge is gone, either for a while when recovering, or forever. Knowledge transfer is incredibly important. Things like tickets, scrum, kanban etc are used because they work for every type of person - they serve to transfer knowledge, the hierarchy in a team protects the programmers from shit they shouldn’t be dealing with (that’s the project manager’s role, to be a shield for the team, to curate the the messages comming from “higher up” and the ones sent out by the team). The most important thing to know is that “do the needful” is about as shitty of an ask someone can pose to a programmer. People doing that don’t know what they want, and instead rely on what they don’t want - once you actually implement something that remotely fits what they needed. As for clients not reading specs - it might be time for someone to have “the talk” with them (obviously not you). One thing you need to know is that shitty clients can be fired too, once the development starts breaking down, the communication is arse etc.

For the people on the road - they probably took it as you trying to bail on them. But yeah, impulsivity when things are getting heated is never good, it’s better to stay silent for a few seconds and then say something, rather than immediately say something that can be taken very badly.

How long are you working as a software dev? Basically a lot of new devs want to “save the world” by closing tickets and using that as a metric if they’re doing well or not. The reality is that a software dev’s job is just about as much writing, as dealing with clients, going to meetings, etc. People might value you for things that you don’t think have value. For the cut out for this part - you most likely are. Imposter syndrome is normal, I had it too, even 6 years into my career. Been the “goto guy” for the team, multiple times a teamlead at 3 different companies / teams. Never had a problem I couldn’t google away. Yet in the back of my mind, there was always a “maybe you’ll encounter one on the next ticket? And they’ll fire you for it” etc. I managed to silence that shit and bury it deep behind all of my achievements.

For the second part - some people are just idiots, some are governed by emotion, etc. Also, saying “it’s not so bad” is a shit way to deescalate the situation ^^

2% yearly reductions most likely. Some shitty companies fire a small percent of their staff and hire new people - especially when someone has been there long and isn’t irreplaceable.

Who tests the useless survey? Everyone with regression tests. Like dude, everything you talk about has been written “in blood” from years of hosting production systems. If the useless survey is needed, then write a test for it, or a testcase to manually try it. Don’t just upgrade, see that the app is up and push to prod, that’s not testing, that’s asking for trouble.

Okay, let’s be angry at the company and frown a lot at what happened. Gurr, bad company, evil.

And now think of what you’d rather have - a working system, or a reason to be angry? If you have something that integrated with something else, lock it down at a specific version so you control the upgrade and know those versions work 100% of the time together. “Latest” is just asking for trouble - be it in a docker image, in dependencies or elsewhere. It’s absolutely not a “best practice” if it isn’t even a code smell or an outright bug. You could’ve had a slightly outdated version, which won’t be “exploitable” - you wouldn’t have enough time to exploit anything in that time, especially with smaller companies and obscure exploits.

Instead of putting out the fire, you could’ve been now looking into the upgrade, seeing on UAT or Test or whatever that forms aren’t supported, chilling till they are supported or complaining that they aren’t.

Upgrades breaking shit is like programming / devops 101, and a huge reason for technical debt in very old projects. Leaving all that to chance is just irressponsible.