4 ms·

> People like their 150K paycheck and know that they're replaceable if we allow more workers. can you elaborate? as a senior dev myself, I am def replaceable,

by itake 5y ago

> People like their 150K paycheck and know that they're replaceable if we allow more workers. can you elaborate? as a senior dev myself, I am def replaceable, but my role in the company is completely different than what is expected of a junior engineer. There is zero chance I could/would be replaced by a junior engineer and I love have junior talent on my team to do the work I am not interested in. > 2. Companies made their bed and are lying in it. no... companies love hiring junior engineers directly from college because they are wayyyy cheaper than senior talent, it doesn't matter if they leave after 2 years. Training up an employee only takes a few months.

m00x 5y ago
> Training up an employee only takes a few months. Uh??? No it doesn't. There's a huge skill discrepancy between senior devs and junior devs. You can train them to be somewhat useful, but it'll take years for them to champion complex projects by themselves, and even then, it takes years on top to be able to gather reqs, ask the right questions to stakeholders, and make a scalable, solid implementation. Juniors are great if you have low hanging fruits, or you want to invest in a great hire.
- ianleeclark 5y ago
  > Uh??? No it doesn't. There's a huge skill discrepancy between senior devs and junior devs. Most companies take the bet that they don't need to train juniors to seniors, they just need to get them to some minimum level of positive contribution. > it takes years on top to be able to gather reqs, ask the right questions to stakeholders, and make a scalable, solid implementation Sometimes you just need some people to update HTML templates, update an API call to your charging platform to include a description, or any number of smaller tasks that pop up. It's why it's called shit work.
  - itake 5y ago
    +1. The senior engineers write the spec and JIRA tickets (addressing the harder system wide issues) and junior engineers execute.

by itake 5y ago

m00x 5y ago

> Training up an employee only takes a few months. Uh??? No it doesn't. There's a huge skill discrepancy between senior devs and junior devs. You can train them to be somewhat useful, but it'll take years for them to champion complex projects by themselves, and even then, it takes years on top to be able to gather reqs, ask the right questions to stakeholders, and make a scalable, solid implementation. Juniors are great if you have low hanging fruits, or you want to invest in a great hire.

ianleeclark 5y ago
> Uh??? No it doesn't. There's a huge skill discrepancy between senior devs and junior devs. Most companies take the bet that they don't need to train juniors to seniors, they just need to get them to some minimum level of positive contribution. > it takes years on top to be able to gather reqs, ask the right questions to stakeholders, and make a scalable, solid implementation Sometimes you just need some people to update HTML templates, update an API call to your charging platform to include a description, or any number of smaller tasks that pop up. It's why it's called shit work.
- itake 5y ago
  +1. The senior engineers write the spec and JIRA tickets (addressing the harder system wide issues) and junior engineers execute.