The programmer and the interns part 3.

Many of you asked me to keep posting about the interns that I'm responsible for.

I had the intention but never had the time or the energy. Since the interns only kept doing stupid, unthinkable things and just filtering out the good ones is a task of its own.

Time has passed, some interns left us by their choice, others were fired (for obvious reasons). Some stayed loyal and were given permanent positions. New ones joined. I no longer am directly responsible for their wellbeing, yet, somehow I am still their tech-lead and the developer of their tools.

Without further delay,

Case 0:
New guy get's into the internship, has his LinkedIn title set to ‘HTML Technician’.
Didn’t know about the existence of HTML5.
Been building static web pages in the early 2000s. The kind with embedded, inline CSS.
Claims that he is about to finish an engineering degree (sadly I believe him).
Fails the entry level Linux test. Complains about the similarity of the answer options.
Fails the basic web-standars test because "they change so fast, but the foundation is HTML and it's rock-solid!".
Get's caught taking home onions and milk from the kitchen.
Is spotted eating in a restaurant under our offices in his day off. Thrice. He lives a 30 minute drive away and comes here on a bicycle or by bus.
Apparently didn't know that the scrolling wheel on the mouse is clickable.
Said that his PC experience is mostly from his PlayStation (PC = PlayCtation apparently).
Get's fired, says that he'll go to the press. Never does.

Case 1:
Yet another new intern. He seems very eager to learn and work, capable, even charismatic. Has an impressive CV.
Does nothing.
Learns from the "case 0" guy and spends time with him until he is fired.
Comes to work at 8:00 AM and immediately goes to sleep on an office puff. In front of everyone.
Keeps dining alone, without a notice, at different times, for hours. Sometimes brings food into the office and loudly eats it there.
On his evening shifts keeps disappearing for long periods of time. Apparently drinking in the nearby bars and hitting on girls.
Keeps bragging about his success with getting their numbers and rants about those who reject him.
For over a year he fails his final training test and remains a trainee, without the ability to work on a real case.
Not fired yet.

Case 2:
Company retreat. Beautiful, exotic views, warm sun beams, all inclusive package for everyone on a huge half-island.
Simon (he's still with us, now as a true engineer!) brings his MacBook to the beach in order to work and impress all others.
Everybody get's drunk and start throwing huge inflatable balls at each other. One hits his laptop and it immediately is flattened.
Upset Simon is going in circles and ranting about the situation, looking for a solution.
Loses his phone on the beach.
Takes his broken laptop with him while searching for the phone.
Dips the laptop in the river while drunkenly ducking in order to pick a clam.

Case 3:
Still company retreat.
Drunk intern makes out with an employee's drunk wife.
Huge verbal fight. The husband says that he files for a divorce. Intern get's fired.

Case 4:
Still company retreat.
Three interns each take an inflatable swimming mattress and drift with the current. Get found on the other side of the resort three hours later, with red skin and severely dehydrated.

Case 5:
Still company retreat.
The 'informally fired' intern gets drunk again, climbs through a window into a room and makes out with an employee's drunk wife.
Again, gets caught when the husband returns to find a locked door but can see them though the window.

Case 6:
Still company retreat.
We all get ferociously drunk and wander off to the unknown in search of more booze.
Everybody does something stupid and somebody finds Simon's phone.
Simon is lost.
Frenzied horde of drunks is roaming the half-island in search of ethanol and the lost comrade.
Simon's phone get's permanently lost.
Five people step on sea urchins but find that out only hours later and then are unable to walk.
The mob, now including more drunk people who joined voluntarily, finds the sexually active intern making out with the enraged employee's wife yet again.
Surprisingly Simon is found sleeping in a room nearby.

Being the only dev in a media company, I believe my coworkers looked upon me as the evil Internet reincarnated into a living person.

Most of them avoided me like a leprous, and I experienced long periods being almost isolated.

I did almost quit so many times I've lost count.

I eventually found another job, where there's lots of love, caring and we all embrace each other's skills. It feels like I'm a butterfly who finally got to break out of my miserable cocoon.

I hate white boarding sessions. They feel unnatural to me. I simply don't work well when put on the spot and I have 3 ogres staring at me waiting for me to fuck up in front of them. Fight or flight engages, the adrenaline rush, my mind freezes. Suddenly it's like I forget how to code at all and I'm expected to solve a problem at once, correctly the right time, or I'm out.

I can't work like that. I need time to process a problem on my own, with my coffee in my one hand and a pencil and scratch paper in the other, not with some demanding employer standing over my shoulder the whole time scrutinizing my every key stroke. I get things wrong the first time sometimes, and more often than not have to google things I can't recall spontaneously. But I always figure it out, test it, make sure it's right before putting it into use.

I've been through several "probationary" periods when first starting a job. They just tell you, they're giving you a month to see if you can handle the job. If not, sayonara. I don't see what's so hard about evaluating candidates in a real world scenario.

So many employers have totally unrealistic expectations.

Am I the only one that thinks it's extremely fucking stupid that the software engineering industry is simultaneously experiencing a "shortage of talent" and maintaining the same ATS that filters legitimate talent just because the resume doesn't fit keyword specifications?

We see it every day. People with years of experience that should never be allowed to touch important code. People with little to no experience that learn fast and perform well. Fuck years of experience being the only thing some recruiters see.

"We generally don't hire people with less than 3 years experience" shut your fucking mouth. Ridiculous. You hire people out of college, don't lie to my face.

Oh and don't even get me started on how many people fabricate their industry experience and get interviews from it. That's what happens when recruitment patterns fail to catch up to an industry that increasingly trains people better up front, and in shorter time periods, and values skills that ATS doesn't give a shit about.

Crazy idea: make job applications test problem solving competency instead of weeding out quality candidates.

Job searching is frustrating.

when you read an awesome @practiseSafeHex rant and share it on Slack

OMFG WHAT-THE-ACTUAL-F

this is soooo fucking broken, my eyes now have many relations to periods

shit... @DevRant fix dat...

God, playing SoulSilver has made me remember an era (or two, but I wasn't alive for one and the other was my childhood) where games were actually fucking *GOOD.* Some games can be absolute home runs now on rare occasion, but if I name consoles from these periods, you can INSTANTLY tell me at least one game that is pretty universally regarded as a best-ever.

Examples and predicted responses:

-Gamecube: Too fucking many to even count. Instant answers vary immensely, but everyone who's played games on this thing have one.

-Original Xbox: Halo 2 is the one instantly on one's lips, or maybe CE for some. Also JSRF.

-Dreamcast: SA2 or Phantasy Star or JSR or...

-PS1/2: Resident Evil, Spyro, Final Fantasy, Ratchet & Clank...

-PS3: Lara Croft games, Uncharted, Infamous... (this one's right on the border, it seems)

-NES: The fucking birthplace of modernized gaming.

-Genesis: Sonic games, obviously. Some may answer with arcade titles, too.

-SNES: Mario games. Mario Paint, SMW, SMW2, SMAS, a couple like Super Metroid or Kirby's Dreamland or F-Zero may come up too.

-N64: Banjo Kazooie, F-Zero GX, Waveracer, 1080, Zelda games...

-Gameboy (all systems:) Pokemon is the instant answer.

Now, a harder one:

-Wii U? Maybe one of the Mii game things? U-less games? Not many people remember the games for this system.

-Xbox One? Halo 5, pretty much. You probably played everything else on PC.

-PS4? The PS3 lineup, but without any soul? You played pretty much everything here on PC, too.

Is there a point to this rant? Yes. Kind of.
Games used to be great, not just due to better hardware, but due to people putting some goddamn heart and soul into making games, and due to creativity stemming from working on such limited hardware. It seems the more powerful consoles (and PCs!) get, the more gaming becomes a soulless cash grab to drain cash from wallets on subpar products with paywalls every 20 feet you have to clear to get the "full experience." Gaming has become less about letting people have fun and being creative with games and more about the bottom dollar, whether that be through making games as fast and as cheap as possible with as much paid content dumped on top as possible, or the systematic erasure of archival efforts to preserve gaming history. From what I read here on devRant, that seems to be the moral of anything computer-related as well. Computers are made to slow down and fail far faster than normal via OEM bloat and shitty OSes, and are used to constantly empty one's wallets with constant licensing fees and free trials and deliberate consumer ignorance. None of it's about having fun anymore. Fun seems to no longer have a place in computing at all.

If you take anything from any of the madman-esque loosely-structured rambling i'm saying here, make it that "the enemy of creativity is the abscense of limitations... and the presence of greed." Another message i'd like to leave you with is "start having fun when making things whenever possible, as it improves not just the dev process, but user experience, too." You can't always apply this, and sometimes you can never do so, but always keep it in mind.

There are periods when my intolerance level is increased, my pet peeves are more present than they were. During this time every fucking thing pisses me off, especially noise. It's the bane of my focus and concentration. Got a couple of loud ass colleagues and let me tell you, I've killed them many times over in my head. Always going off topic and talking about random shit that doesn't even matter.

After nearly four days of fighting with Ruby, Gem, Bundle and a dash of JRuby just to make a plugin for logstash install, I can officially say I feel like Ken Mattingly.

It is all about the sequence, and a metric ton of RAM and CPU cycles and patience.

So how many generations of the same people are you raising simultaneously or are you people killing them in between passing all of us off as younger than we are ? Just curious
Wonder just how much of a group of monsters you all are since I’ve seen counting on 5 duplicates this far with periods of amnesia in between