Sounds like you contributed to the issue here. You should have been helping the junior dev out as a senior not punish him. I'm hearing a lot of complaints and not many solutions, sure you're a senior?
I don't see it that way - all I see is a predictable corporate reaction to pointing out micromanager tendencies.
Also putting down non "first world" coders before they have even been given a chance. I can see that "flagging" is obviously easier than comprehending and rectifying the unfair situation that OP is putting these people in. It is clear that he views such candidates as below him or at least that is how it comes across.
"It always comes down to trust - how can I make sure that if I work with you, you're going to commit code that I won't have to do a ton of cleanup on?" - This is what I have the issue with - it's generally the difficult clients who won't trust you and have a general arrogance where they believe they are generally entitled to judge before you have written a single line of code. If you are going to have this attitude, try not to get hurt feelings when someone points out your shortcomings.
Not really if a manager is going to list demands they expect from their subordinates the least they can do is ensure they understand the difference between similar sounding words.
ah did you edit this? I noticed you wrote "you may think you're God's gift to programming, but you're wrong." before removing it (it was gone once I had refreshed). Did you realise you know nothing about me so saying something like that is ridiculous?
I just think people starting out should be supported and being arrogant about it doesn't really help anyone.
You said mid generously so I think it was fair to say lower middle.
No need to get competitive about who has the highest score - sounds like this guy dodged a bullet from having to work with you anyway. You seem like you would be a nightmare to work for.
I said Front end as an example could apply to most developer jobs really.
Anyway, this guy you placed as a "lower mid", this is your judgement, how do you know it's correct? Did other people say the same? Perhaps he didn't have the skills you were looking for but was good at other things. Saying the other company didn't do their diligence is easy but is that really what happened?
If you are hiring developers and placing them as lower, mid, lead etc. you are going to get flak anyway as you're just jailing them and hiring a load of people who only agree with what you think.
You're going to get people who are good at developing software who don't care about math(s) or machine learning, give them 2 seconds and Google and they can answer your Modulo question.
Is it not about the willingness and enthusiasm to learn? Or do they have to go through "hard" tests to prove they can work out some academic nonsense they are never going to need to use. To prove themselves to the frat. I'd argue a lot of really clever people good at the hardcore Computer science and data analysis type subjects aren't always as good at writing decent code.
So what Modulo is there to catch people out. If you were a front end developer do you really need this?
The fact employers will reject based on a test that is fashionable just because a few coding blogs said so doesn't mean they can't provide value. What about their past work or qualifications?
Cocky. Sounds like a clique i'd want to avoid at all costs.
I was 255 in Jan now at 235lb by not eating cereal, bread, sweets, drinking sugary drinks etc.
Seem to have stayed at 235 for a few weeks now so i'm guessing it's easier to lose the first lot of fat.
Been going to a gym most days but then i'm a student so have the time in the middle of the day. It would have been difficult to go that much with a FT job. Went a bit far with the cardio and now have hurt knees so watch out for that. Good luck.
Conceited. There is never an excuse for workplace bullying. You don't know how to manage if all you can do is criticise in your 'TODOs'. You are not as advanced a developer as you would like to think if your best solution is to rewrite.
Who cares there are plenty of places that will hire you without all this "super smart and get things done" cliché.
More trust should be given to younger employees just starting out. They might still provide lots of value but not need to tick off a certain % of clichés valued by a senior dev who think they know the correct way.
“I use this test on all levels of developers, but my criteria is stricter the more senior I expect you to be.”
Who would really want to work for someone who treats you in such a subordinate way.
A lot of the time the personality issues are with the super arrogant hiring developers at companies. I had this issue trying to get jobs out of uni, being able to code but not knowing the trends.
If you answer the correct questions (led by what is fashionable according to top developers/industry figures) and fit into their view of what a great developer is then you will get the job.
It’s almost like you could come up with a stock set of answers about subjects to pass (clean code, unit tests, maintainability, logging).
What about the project which provides your pay check, isn't getting to grips with that just as important?