3 ms·

> that doesn't mean that they can explain it to you. I'm sorry what? I don't expect them to teach me, I just want them to tell the difference. By the way, the

> that doesn't mean that they can explain it to you. I'm sorry what? I don't expect them to teach me, I just want them to tell the difference. By the way, the ones that can't say: "they told me to always use let". I'll send them to you :D. Best of luck. > I've never seen a senior developer fired for poor coding. I've seen plenty. If a junior dev needs to help you out of trouble every time, you know there is something wrong. Some people just reach their limit very soon, and can hide away in some comppanies. Probaly companies where you seem to work. Other companies probably just have a higher bar, no disrespect meant.

Cd00d 4y ago
Look. I've seen a lot of your comments in this thread, and I don't think you're listening. You don't seem open to hearing. What I read is a knee jerk justification for your hiring methodology without being open to any feedback. You should take a breath. Clearly people disagree with you. Try to empathize with where they're coming from and understand the point they're trying to make.
- koonsolo 4y ago
  Ok, so what's the ideal hiring practice then? According to some here, it's just a little talk about previous experiences, not going into technical details at all. Sorry, but then you end up with people who are technically very weak. Been there done that. Look, I have a lot of experience with the hiring process. It's very difficult. I will listen to someone with a lot of hiring experience. But just saying "it's broken" isn't going to cut it. And remark that a big part of our hiring practice is to put the candidate at ease. I even say that they won't get everything right, and that's no problem. I help them out when they get stuck, etc.
ipaddr 4y ago
I've worked in a number of places and people don't have the limitations you believe. A junior helping a senior? Shame on them? Fire the senior? That sounds really foolish. You realize that junior/senior/etc are labels and someone you hire a junior can know more syntax than a senior in a framework. That's okay that the senior seeks helo.. it's natural and what a senior should do. p You are presenting your company in a bad light and making yourself sound inexperienced. Could you have reached your limit? Would your methods fly elsewhere? Apply the len to yourself and see where you end up.
- koonsolo 4y ago
  When other devs get stuck on something, they come to me or one of the other seniors. And then I or they solve it. Sometimes it's difficult, and sometimes it's a silly oversight. So yeah, I have no problem applying it to myself. I can't really believe that people here think when you have more years under your belt, you somehow must be good. People get fired in companies because they don't reach the expected level. If you keep them, other colleagues will get frustrated and leave on their own. And then you're stuck with the underperformers. And yes, everyone has limitations. Some sooner than others. Welcome to reality. I find the discussions here very silly that somehow you must hire everyone without a technical interview, and never fire anyone because people don't have limitations. Not going to respond anymore.

Cd00d 4y ago

Look. I've seen a lot of your comments in this thread, and I don't think you're listening. You don't seem open to hearing. What I read is a knee jerk justification for your hiring methodology without being open to any feedback. You should take a breath. Clearly people disagree with you. Try to empathize with where they're coming from and understand the point they're trying to make.

koonsolo 4y ago
Ok, so what's the ideal hiring practice then? According to some here, it's just a little talk about previous experiences, not going into technical details at all. Sorry, but then you end up with people who are technically very weak. Been there done that. Look, I have a lot of experience with the hiring process. It's very difficult. I will listen to someone with a lot of hiring experience. But just saying "it's broken" isn't going to cut it. And remark that a big part of our hiring practice is to put the candidate at ease. I even say that they won't get everything right, and that's no problem. I help them out when they get stuck, etc.

ipaddr 4y ago

I've worked in a number of places and people don't have the limitations you believe. A junior helping a senior? Shame on them? Fire the senior? That sounds really foolish. You realize that junior/senior/etc are labels and someone you hire a junior can know more syntax than a senior in a framework. That's okay that the senior seeks helo.. it's natural and what a senior should do. p You are presenting your company in a bad light and making yourself sound inexperienced. Could you have reached your limit? Would your methods fly elsewhere? Apply the len to yourself and see where you end up.

koonsolo 4y ago
When other devs get stuck on something, they come to me or one of the other seniors. And then I or they solve it. Sometimes it's difficult, and sometimes it's a silly oversight. So yeah, I have no problem applying it to myself. I can't really believe that people here think when you have more years under your belt, you somehow must be good. People get fired in companies because they don't reach the expected level. If you keep them, other colleagues will get frustrated and leave on their own. And then you're stuck with the underperformers. And yes, everyone has limitations. Some sooner than others. Welcome to reality. I find the discussions here very silly that somehow you must hire everyone without a technical interview, and never fire anyone because people don't have limitations. Not going to respond anymore.