Pro tip - Infect your computer with small viruses to build its immune system.
Kinda shitty tip

The last two frontend devs I interviewed.

First:

He had 15 some years of experience, but couldn't answer our most basic of technical questions, we stopped asking after the first couple.

Based on a technical test I got the impression that he couldn't distinguish between backend and frontend.

So, I posed a simple question "Have you interfaced with REST API'S using Javascript before?"

Which lead him to talk about arrays. I shit you not he droned on about arrays for five minutes.

"I have experience using big array, small arrays, breaking big arrays into littler arrays and putting arrays inside other arrays."

Never been in an interview situation where I've had to hold back laughter before. We refer to him as the array expert.

His technical knowledge was lacking, and he was nervous, so he just waffled. I managed to ease his nerves and the interview wasn't terrible after that, but he wasn't what we were looking for.

Second:

This was a phone interview.

It started off OK he was clearly walking somewhere and was half preoccupied. Turns out he was on his way back from the shop after buying rolling papers (we'd heard him in the shop asking for Rizla), and he was preoccupied with rolling a joint.

We started asking some basic technical questions at which point he faked that he'd seen a fight in the street.

We then called him back five minutes later you could hear him smoking "ah, that's better". After that the interview was OK, not what we were looking for, but not bad.

Top tip: If you require a joint to get through a phone interview, roll and smoke it before hand.

I interviewed to this small company. It was a position requiring a lot of experience they said. They did Microsoft SQL server and their technical interview questions were so easy it took me a lot of time to answer them because I was looking for traps, like for real. Think I might've answered too complex for them as well.

In the non-technical interview they joked about how they'd need to reserve two saunas in team events (Finnish thing) as they were all male and I would've been the first female.

Then they asked questions about my *children*. "Who takes care of them when they're sick?" Ummm, yeah, illegal much.

In the end they didn't hire me but they took two interns from the vocational school (or applied sciences). Yeah, so hard a job a Master of Science in Software Engineering with (at that point) three years of full-stack experience couldn't handle but some not even graduate interns could do?

Oh, and fun thing was. A couple months later a recruiter called me about the same company. I told *her* the story and she said she's gonna drop that company from her list and said no wonder they complain about not getting people for them. xD

I also send a tip to my unions discrimination department. They used my case as an example in presentations so suppose this experience served a purpose. ¯\_(ツ)_/¯

- Get invited to apply to job
- Technical interview, guy shows up late starts small talk wasting time and gives me the exercise
- Start implementing the first algorithm, finish it passing min test cases then realize there's a solution that would make both algorithms a breeze
- I pitch my solution realizing there's no much time left, cuz we lost almost 20 min of my test hour talking about BS plus the almost 10 min he arrived late, and reassure the interviewer it can be developed faster
- Interviewer says it doesn't matter, we should finish edge cases
- Kay no problem, finish the first algorithm successfully and explain pitfalls on the second part with the current implementation
- I tell him there's a better solution but he doesn't seem to care, he says time's up

Now here's the funny part.

I get called by the recruiter today (2 weeks later) and she says "They are happy with your soft skills but feel there are some gaps with your coding, they would like to repeat the technical interview because they didn't feel there was much time to assess the 'gaps' ".
Interviewers, either I'm competent enough to work for you or not, your tests must be designed to assess that, if you see you can't fit the problem you want in the time you have left change the problem, reschedule or here's an idea...LEAVE THE BS CHITCHAT TILL THE END AND START THE INTERVIEW ON TIME. When I do interviews I always try to have one complete free hour and a one algorithm exercise because I expect the candidate to solve it, analyze it and offer alternatives or explain it, I've never had someone finishing more than 2 an hour.

You can keep your job I'll keep my time. I'll write a similar problem on the comments to pass on the knowledge for people who enjoy solving these kinds of problems, can't give you the exact same thing, also tip guys don't do NDA's for interviewing it makes no fucking sense trust me no one cares about your fizz buzz intellectual property.

Last year, we had to do a big university project in randomly selected groups (5-6 students in every group).Three of the five guys were completely useless, I mean, both the other competent guy and me wrote around 20,000 lines of code each, the other ones wrote around 500 lines of code (combined).
After our first few meetings we quickly knew that we have to give them a small task which was so trivial that not even they can fuck it up. But we were wrong. Oh boy, so wrong.
They simply had to code the excel export of the data, which means they had to use two functions from a library and pass the correct data. But their solution was so bad, I lost faith in humanity and was fascinated by it at the same time.
For example, there was this simple class "Room", which had a few properties like size or number of seats and a few getter/setter etc. That was a core class and written by the other qualified guy. So how did the others fuck up the excel export? They somehow rewrote that class in German (although the other code was completely in English), implemented a function for each property that would write its value to a hardcoded cell in a hardcoded excel file.
And this was just the tip of the iceberg. Needlessly to say that I had to rewrite the whole export in the night before we had to present the project.

Interview tip #420

If you are asked to code a small app @ home, ffs, don't send the interviewer the node_modules folder!

This is the craziest shit... MY FUCKING SERVER JUST SET ON FIRE!!!

Like seriously its hot news (can't resist the puns), it's actually really bad news and I'm just in shock (it's not everyday you find out your running the hottest stack in the country :-P)... I thought it slow as fuck this morning but the office internet was also on the fritz so I carried on with my life until EVERYTHING went down (completely down - poof gone) and within 2 minutes I had a technician from the data centre telling me that something to do with fans had failed and they caught fire, melted and have become one with the hardware. WTF? The last time I went to the data centre it was so cold I pissed sitting down for 2 days because my dick vanished.

I'm just so fucking torn right now because initially I was absolutely fucking ecstatic - 1 week ago after a year of doomsday bitching about having a single point of failure and me not being a sysadmin only to have them look at me like I'm some kind of techie flat earther I finally got approval to spend around 5x more per month and migrate all our software to containerized micro services.

I'll admit this is a bit worse than I expected but thanks to last week at least I have recent off site images of the drives - because big surprise I have to set this monolithic beast back up (No small feat - its gonna be a long night) on a fresh VPS, I also have to do it on premises or the data will only finish uploading sometime next week.

Pro Tip: If your also pleading for more resources/better production environment only to be stone walled the second you mention there's a cost attached be like me - I gave them an ultimatum, either I deploy the software on a stack that's manageable or they man the fuck up and pay a sys admin (This idea got them really amped up until they checked how much decent sys admins cost).

Now I have very flexible pockets because even if I go rambo the max server costs would only be 15-20% of a sys admins paycheck even though that is 13 x more than our current costs.

New developers. Tip: There is no silver bullet.

If you like Python, please understand GIL's behavior before making a system that handles thousands of requests.

If you like Java, know that "Write once, run anywhere" is a fallacy. Even application servers don't like the same WAR.

If you like PHP, understand the life cycle of a request before connecting to the database from all corners.

If you like C#, don't make it a small command-line application that will be used on FreeBSD.

If you like C, meet valgrind.

If you like C++, templates are cool, but don't overdo it. And take the opportunity to meet valgrind.

Never use the same tool to do everything. Elect the language and framework for the given need with rationality.

Every time I see a "Java Man", a "C++ Chad" or anything like that, it comes to mind that if he were a carpenter, he would be tightening screws with hammers.

Every lock-in is bad.

There was an issue whilst you were away, we had to make a small css change.. We pushed it into master but it said something about the branch being behind the tip by 50 commits or something. It's okay, we forced it up though and force pushed it to production as well but the site went down.. In the end we had to ftp it up manually but the customer is saying things that were there before now aren't there any more?

I thought you put this "release process" in so things like this wouldn't happen! I think we need to review it as it clearly isn't working.

small tip

Probably everyone at least once had situation when they receive a meaningless screenshot with 500 page, a message "Application doesn't work fix it" and 0 info whatsoever.
Here is my tip that saved me a lot of trouble.
I display error id in the center of the screen, large enough so no matter how small and blurry the image is (yes users, send us photos of theirs displays) , It is always easy to ready it so we can start investigation without talking to those monkeys.

!rant
Someone got a tip how to start contributing to open source projects? I really want to spend some time to help out but I have some problems finding something small to begin with. It seems that everything i find needs some kind of specialist know how.
So my plan is to start with some small things to work myself up to bigger projects

Thanks :)

Well, I'm no professional developer, still at school, but I thought about this, regarding convincing PMs of you writing permanent fix instead of a temporary workaround: Just tell them that this one particular issue can't have a hotfix, and that you need time to fix it.

I finally have a vServer again, now I need to fill it with 'life': secure it, build a small website and mailserver.

The main idea is to have some basics to look more professionell. I'd love any tip and idea how idk, save work before I run into stupid beginner mistakes, or things you had good experiences working with when you had similar tasks? :)

Become a better programmer tip 1: write large amount of code everyday. Read and understand large amount of code every day. Plus have to do self reviews after each small tasks.

While fucking my hot blonde gf this morning the Fucking DUREX condom BROKE and i creampied her. Here are the reasons why its not my fault:

1--Im not retarded

- 4 years of fcking my hot blonde gf with no protection and nothing ever happened cos im !retarded. Its a bigger risk to fuck with condom than without, how is this fucking normal???

2--I use condom the right way

- i was holding the tip so air comes out, just like it was explained on the box, but while rolling it down i was still holding the tip to make sure the air doesnt come back up

3--She was wet

- she wasnt dry. My hot blonde gfs pussy was so wet from how horny she was so its impossible that it got torn due to dryness

4--First verification

- it wasnt torn or ripped. It was normal. Everything looked absolutely fine

5--Second verification

- when i put it inside my hot blonde gf and fk her i pull it out in the first 10 seconds just to make sure it isnt torn--it was good and nothing was ripped so i slowly put it back inside

6--Condom is not thin

- i took the regular durex one (fuck this fucking dead fraud company I'll piss and shit on their grave) so it wasnt the thin bullshit one

7--Dont got a big black dick

- its normal. Average. Not small nor big. So latex elasticity isn't my problem

8--50-50%

- every FUcking time when i fked my hot blonde gf with a condom i always stressed if it'll break or not. This is not the first time it broke. FUCK the product that is THIS MUCH unreliable, unsafe and fragile! I'll fuck the whole durex company up. Im not the only one who had this problem. DUREX IS THE BIGGEST OVERRATED SCAM COMPANY SPENDING BILLIONS ON MARKETING FOR A LOW QUALITY SHIT PRODUCT THAT DOESNT EVEN WORK

9--Package didnt expire

- i bought a new box in the store on 8th march for womens day (modern women value having gifted with condoms more than flowers). It wasnt bought in a shit china quality shop. I fked her in the car at night and also creampied her but the condom did NOT break. Then i fked her this morning in bed with condom from the SAME BOX, and now it DID break. Are you Fucking kidding me???

10--Emergency contraception

- i died from high adrenaline of running so fast to the store to buy her contraception. Had to run to 4 fucking stores cause all of them don't work before 7:30am. Finally found one in the 4th store and she drank Escapelle within 20 minutes of incident, as soon as it was physically possible

11--And now what

- now what. What do i do. I did everything i could. Nothing is my fault. My hot blonde gf wanted me to creampied her it was her idea so shes at fault partially. She will get tested in 15 days while this contraception lasts. Dont know what else to try. This bullshit never happened before

Learning Tip:

While learning some new tool/technology never just go and start looking at the handbooks and/or tutorials. Always set small goals for yourself first or ask someone proficient in that tool/technology set these goals for you so you can follow along and make real progress while learning.