Comments by "Inconspicuous Chap" (@InconspicuousChap) on "Who's Solving The DEVELOPER SHORTAGE Crisis?" video.

  1. You know it's somehow both situations at the same time, I've seen it from both sides not long ago. The hiring teamleads (those who directly work with engineers) complain about difficulty to find a senior developer. They deal with dozens of poor candidates who can't answer simple technical questions and have senior positions open for months. And for a senior developer it takes 6-12 months to find a job. I guess the point is, the management want senior developers working for a middle-dev salary and their role is supposed to be some sort of a penal servitude for repeated felons, with hands and legs chained, rights thown out of the window, total control of paranoid bosses, etc., implementing technical designs from mad committees.
    2
  2. I suspect when a new methodology comes to replace Agile, it would be even worse. Scrum virtualizes the job, prevents people from seeing the bigger picture by focusing on some secondary unimportant matters. Next they are going to put a VR helmet onto everyone's head and stimulate them with an electric discharge.
    2
  3. Schizophrenics write job requirements to get liars hired. They get on well.
    1
  4. I've recently seen a funny example of this. In mid-2022 the managers had hired a senior guy to run a small project to build an ML module into their platform. He had collected loads of information, written a detailed project document, but they hadn't got on with him for him not being perfect, so he had left and they had frozen the project. A year (!) later (Q4 2023) they have hired another guy to pick the project up and continue it and fired him just a month later for not being blazing fast from day 1 (they have ambitious goals and KPIs, and blah blah blah). They are literally posting this vacation for months. Perhaps they are going to hire someone else in Q4 2024 to continue this thing, and these 1-year freeze periods are somehow an efficient way to achieve the project's goals quickly, may be that has something to do with Lorentz transformation of space-time, who knows...
    1
  5. They look at a limited set of trendy technology buzzwords in your CV. If you have them, you go ahead to an interview, otherwise you don't. It's that simple. Skill? Math? Architecture? There are very limited areas where these are still required. Most of today's software developer positions are intended for monkeys developing CRUD "microservices" using primarily copy-paste method... until their job is fully automated.
    1
  6. The business now does not require brains, they want hands on a pipeline of primitive tasks. Apparently you should dumb your CV down and find 2 parallel middle jobs, each 100% remote and without daily meetings. When you get interviewed, try to speak in CRUD application developers' language, the managers should believe they can control you, so you should look like their average employee. Never show that you are smart, let alone smarter than they are, before you are hired (perhaps it's also worth playing dumb after). If you could complete a middle developer's 8hr job in 4 hours, then you are in a fair situation. If you work faster, that's a net profit for you. It might feel bad not to be recognized as a smart guy, but after all, what do you need more - money or that recognition? A friend of mine had owned a factory once. He knew lots of people high up, at a city mayor level. Then he got bankrupt, lost all his luxury, was working as a taxi driver for a few years. He once said he started feeling much better when it happened. But a businessman is a businessman - eventually he learned how the system worked, bought several cars and other taxists pay rent to him now.
    1
  7. Perhaps those managers are "learn Java in 5 days" videocourse grads who have survived, got promoted and now make hiring decisions.
    1