To a non-developer, every application they read might as well be a list of buzzwords. They cannot comprehend a word of it. Web stacks offer the opportunity to list more and newer buzzwords. Do I set up an interview with the person who lists "C systems programmer" or with the person who is a "full stack React, Tailwind, Next.js, Node.js, Electron, Docker, Kubernetes, AWS engineer seasoned in Javascript, Typescript, HTML, and CSS"? Well, the latter certainly sounds 10x more impressive. Into the trashbin the systems programmer application goes, they just don't have enough skills for an enterprise of our scale!
replyA C systems programmer can definitely make a list of buzzwords as well.
replyAlso, let's say team A (10 C app/systems programmers) in a company asks HR to look for a C developer and HR comes back to them with 10 great web developers to be grilled by the engineers of team A - what happens then? Does team A shrug and say "welcome to our C codebase, we shall now rewrite it in tailwind or whatever because you are now here!" - I really don't see how it can play out
This supposes team A has 10 C programmers in the first place. By one means or another, teams of web developers are put together and made to do non-web-development projects, and now half of the Windows 11 userland is written in fucking React. I'm not the one making these stupid decisions, but probably they were originally hired to work on a web project, then later moved to a new OS-related project because they were the pool of idle employees available, and the fleet of React-in-the-OS programmers expanded as new hires were now being funneled directly into React teams working on OS projects.
replyBecause they lack any better signals from within the company. At several places I have worked, hiring is almost fully detached from the groups that need the workers. They never could find good candidates for our teams. This kind of disconnect is what corporate cancer looks like, and it is endemic in big business.
reply