Quite tired of hearing the line: "but computer-skilled people are the most sought after" when I'm here trying to find a job for ages.

I know most of you know this, but after having dealt with both recruiters and real companies I can safely say that recruiters are of no practical value.

I've wasted countless months of my life interacting with recruiters and getting nothing out of them. To me it seems they're only after fluffing their client base.
The only time I got a job was through the real companies themselves.

Now I have learned the lesson: stay away from recruiters.

Sales lesson: The more complex your resume looks, the more confused your employer is going to get and the lower the chances will be they're going to hire you..

And so, if I put 60 technical skills on my resume, my employer is going to sit there with their hands in their hair and be utterly confused (which has happened to me a few times before). They're going to have no idea what it is exactly that I'm capable of..

I'm not exactly surprised because in my English Business Skills course in college they also said in regards to quality: K.I.S: Keep It Simple.

Stick to a maximum of 6 skills and that's it..

source: an awesome YouTuber

lmao, this is true.

I'm not sure if this is a red flag but it appears to me it is, as I have seen it occur more frequently by self-interested employers:

When you don't respond to their inquiry and they keep prodding you about it, even weeks after it.

Man, it's hard getting a job in a field you have little to no experience in.. in my case: front-end.

I hate back-end..

Red flag, when a company says: "You're never going to leave us, right?".

Alright, could someone with more experience tell me if nowadays the job application requirement of "x years experience needed" is something fixed or flexible?

My friends say: "That's the ideal candidate, but they are flexible if need be." but I see employers these days state that the x years experience is in fact mandatory and required.

So.. who can demystify this for me? : )

Why do some employers make such a distinction between learning the tools at university and learning the same tools at the workplace?

Are they backward or old? Don't they know modern, high-quality universities have modern environments that are in fact real life?

Environments with acc-test-prod-dev with gitlab, ci/cd in Scrum teams and the works? Heck, at my uni we even worked at real companies, did internships there for months!

Come on.. to me this 'the tools you learned in school isn't the same experience as real life experience'. Right, these guys must be on some conservative backward model because there is in fact no difference.
I have worked both during my uni internship at a real company (in teams too) as well as irl at real companies and there is no difference, it's the same thing.
I don't care if I've learned to experience git + ReactJS etc during an internship through uni or at a workplace. It's all bureaucracy.

Does the company you work at have a CI/CD pipeline (Continuous Integration/Continuous Delivery, e.g. with Octopus Deploy)?

Sometimes it surprises me how many companies don't have this..

Job application reply: "We found someone better than you".

What a big surprise.

Is it too much to ask for companies in the current world to be.. oh I don't know.. honest and consistent?

If you advertise on your Job section: "We always give our candidates feedback, whether they got the job or not". Then, *****, give them feedback! I applied and they never got back to me. And no, that's not feedback.

After 2 years of applying for jobs and not getting any, I'm beyond tired of hearing employers complain to me and ask: "You have a Bachelors degree in Computer Science, you should be able to find a job without breaking a sweat".

Excuse me? In what world do you live in? Are you not aware that we have been living in an academically oversaturated market for more than two decades now? Nowadays you need a degree, plus a heavy portfolio plus crazy interest in the field (to an obsessive degree) because the competition is fierce.

It's not my fault I don't get jobs. It's always some "no fit", "not enough experience" bullshit.

Sigh.. seriously.

This one recruiter keeps calling me and leaving me messages on different phone numbers (mixed landline and mobile phones) and I have to block them all.

How unprofessional of an agency to continue harassing a candidate if they're not interested. I've muted their numbers now.
And this is not about being interested either on their side - I know them. They're full of recruiters whose sole purpose is getting their fat ass promoted by use of candidate database and track record filling. One of them even had the nerve to tell me he got promoted and how wonderful it is.
I think I'm gonna make a request to delete my data.

Can you guys believe this?

I've seen a job vacancy that asks for the following characteristics in a developer:

- extraverted, do'er (as opposed to thinker), out-of-the-box, curious, sees solutions and not problems, structural thinking vs. theoretical thinking, loves change, acts immediately, makes choices under stress, critically questions themselves if things go wrong

What the [censored] kind of programmer is that? Sounds more like a wannabe brogrammer type.

A typical, real programmer is introverted (for he is introspective, detail-minded and is therefore good at inspecting problems and finding solutions for them).

Seeing problems is not a bad thing, it's in fact necessary to be able to identify issues and not act like your typical manager who only wants to rush to solutions. He thinks deeply and theoretically before he takes action. Theory is the foundation of identifying a problem.

What programmer is stress-resistant? It's not normal for the human brain to be able to deal with stress; this is why switch-tasking is so hard.

Question yourself if things go wrong? Perhaps, but this sounds more like trying to shove the blame around.

Since we live in a rigid computer world with rigidly-defined protocols (say, HTTP), it is often useful to think in a conventional way. Out-of-the-box? Sure, if you're being innovative, or sure, as a tangential characteristic.

In my professional opinion, this vacancy reeks of bad corporate culture.. and the biggest alarm bell I find is: "There is free beer!" Err.. yeah. Anyway.

My CV clearly says I don't have any Php experience.. yet.. comes a recruiter ask me if a Php job would fit my experience.

What the.. urgh seriously.

If your boss is lately suddenly being a giant prick to you, then you're likely going to get fired.

Ever had a colleague who nosed into what solution you brought to a problem and then stole your credit, telling the CEO how they found the solution and not you?

Yeah.

You better not tie your ego to your job.

ImgBurn has one of the weirdest sounds ever..

-job completed- Some kind of funny instruments jingling
-job failed- Sexy woman voice: "Oh no! :("
-you press 'stop job' more than once'- Sexy woman voice: "Hey! I said I got it!"

Lmfao..

LoL, why do we even have job reference contacts? So your previous manager can tell your new potential employer how much you sucked?

It's all so pointless..

Sometimes I think of applying for a dev job as 'pick your poison', since the chance of landing a job with fun languages and few headaches is slim these days.

How active is your GitHub repository?

Mine's been dead for over 5 years. Lmao.

I have found that once you work for a company where you have to implement everything in its raw form using the raw language and raw logic, you really have to know what you're doing and knowing some basic/medium programming and having some algebra knowledge doesn't cut it (unlike some people think).

I've been at two sides of the coin: I worked for a company that had everything in place, a framework that handled all edge cases and what not and I just had to focus on user stories, but I also worked for a company where I had to do everything manually.

For example, at the latter company I had to know Discrete Mathematics; truth tables to their most convoluted and disgusting form, having to be able to apply this on a late Friday night with a headache and lack of food and sleep with the PM stressing out.
I've had to deal with NOT AND OR AND OR AND OR AND branches or whatever, where an OR behaves like an AND and if you want a value between an AND AND and an OR, you'd have to do a NOT OR.. to think about latches, all in my head, sigh, anyway, within limited time constraints, without even having time to write tests, having to make sure that everything checks out while the client is breathing down my neck. Yeah, not such fun times.

I'm happy for those of you who can just write some moderately difficult logic but you don't have to break your head over doing everything manually, as if you're in the coding stone age and nothing is taken care of.
Companies like these make me want to run away.

Contrary to popular belief, after having been in the working world I've realized that what matters and what is of value is book knowledge, not experience.

I find 'experience' an overglorified waste of time. Having in-depth knowledge of everything is what's important.

One of the most inefficient practices I've seen done in companies is the company housing 50+ devs having to hire an expensive consultant who is only available on a limited time to figure out mysterious or in-depth problems with the company's main application (for example, JavaScript problems).

Then the whole dev team sits on his shoulders and production can't run smoothly until he fixes things. Even worse, him having the so-called qualifications, being the 'expert', but when asked an in-depth JavaScript question, they don't know the answer.
When I suggest to figure out things in-depth so problems like these can be prevented in the future, I'm met with: "Nah bro, we'll just apply quick fix #2" just because I carry the title 'Junior Developer'. Makes me want to hit my head on the wall on how stupid these people are.

This could all be solved if the dev team would be competent in the first place, knows how to read documentation and isn't lazy, most importantly. I hate teams like that.
Grab, the damn, documentation, read W3C, read MDN, get educated, and stop using band-aid solutions! Gah.
Toxic companies like these are what's wrong with some places in the development world.

I'm a proponent of knowledge.
Fellas, know your stuff.

Since you started your job, how many programming books have you read to get ahead in your job?

Examples:
- You're a Java programmer, so you read the OCP for Java 11 and then you get your OCP cert
- You're a .NET consultant, so you read another .NET book

Hmm.. I've noticed a trend in teams at companies: they always seem to have similar personalities, rather than similar skills.

For example, if the team leader is a pathetic, pretentious, sarcastic, frigid, lifeless loser who pretends he's happy, then he usually has a herd of equally pathetic and frigid losers following him. I notice that every time I apply to a company that has such a group, they instantly disqualify me as a member. Interesting, interesting..

The same goes for a company that has down-to-earth people like myself, then the team is usually a down-to-earth manager and down-to-earth, warm-hearted colleagues.

It all makes sense now.

Explain to an end user 'like-I'm-five' why webpages sometimes cause stress on the CPU.

Does your company chicken out on doing multithreaded programming because it's 'too complicated and unpredictable' for their programmers? lol