Can I go to CTO and demand that he will demote a "senior engineer" (who takes senior's paycheck) who don't know what "race condition" is, and how to design/deal with it?

Why? Why I can't?

Can you imagine how many CTO's / people's court cases he would be dealing with if that was a thing?

And whatever the problem is, it's not because random employees can't demote other random employees.

Someone or something allowed for this to happen...and if they are still there, it will again.

The Senior should die! How dare he?! Not knowing something inside the computer science field? It's not like it was plethoric!
Also, all seniors should know how to read AS86, disassembly, and how low-level GPU functions work! Even if they have had never to deal with it in their lives!

@jotamontecino are you sane man? I'm talking about some basic stuff, while you counterargument with some edge case super advance stuff. Damn... that's weird

@bzq84 absurdity doesn't work if you don't overdo it... And it a bitching about your bitching...

Now having worked on python projects with real tech performance needs, being able to read disassembly is a must-have. And we still hired senior programmers who couldn't before...

Being a senior is not about knowing all the how's, is about understanding the tech why and learning super fast.

@jotamontecino that's my point. In my project a race condition is a must have to understand. Yet there's a senior, 18months in this project, and still not getting it.

@jotamontecino
Not only knowing about them, but also being constantly aware about race conditions is one of the essential senior skills (in backend development).
Having your code not corrupting data when it is used concurrently is one of the differences between a junior and a senior.
You know about concurency, locks, transactions, data sharing and message passing - or you aren't a senior.

@Oktokolo Inside a server-side development. Sure.
There is a LOT more inside software engineering.
And a lot of languages/frameworks where you can't handle threads (or threads like).
And even inside server development, coding some handler/lib/stuff to handle concurrency is not "normal" in a lot of languages.

@bzq84 Then the problem is not that he doesn't know how to add/code/handle concurrency/races but that he doesn't know what the fuck is going on technically after a year and a half. And if management/leadership isn't too stupid, they should take it into consideration.

@jotamontecino indeed. When I speak with him it's like he simply don't understand. Today same observation was confirmed by another folk.

Senior guy and I have to explain to him like to an intern (when interns begin better than him). It sucks all my energy. And it looks like management is blind, even when I said it clearly - and this made me rant today.

@bzq84

That's really weird.

I mean I wouldn't be opposed to having a very measured conversation with a manager about the situation. Provided you trust / have a good working relationship with that manager / you think you're not going to blow up office politics.

But if there's any chance of it blowing up I wouldn't even mention it.

It's weird, I'm a grubby web dev with a boot camp 'education' and I can understand a race condition ....

@N00bPancakes exactly, f**king office politics. Manager acknowledge that "he is not too good maybe" but didn't do anything since last 18 months to solve it. And now assigned me to his team to somehow "fix" things, and make him grow.

Impossible task, sucking all my life energy.

Ahh, and since on paper he is "senior", in books it looks like 2 seniors working on that project.

And I asked to assign another good engineer from another low important project. They said "no" due to office politics, and other blurry reasons.

@bzq84 sorry you have to suffer from stupid manager and dickish cluster fuck politics...
Start searching a new position? :/

@jotamontecino I'm looking already, as I lost hope that anything will change. If I go to upper management and point that this 3 or 4 guys (2 managers, 2 individuals) fucked up project since last several months, and that they don't understand basics needed to do job good, probably they will fire me anyway.

@bzq84 good luck !

@jotamontecino
"And even inside server development,"[...]

When developing a server, every potentially concurrent request altering persistent data leads to a race condition if you don't explicitly protect against that.
But why would one do that if the concept of race conditions isn't known.

Servers dealing with mutable persistent data are quite common...

@Oktokolo yes, but again quite often isn't always.