← Back to context

Comment by lapcat

1 month ago

> they were assigned because it would have been malpractice otherwise.

I don't know understand this means.

> This was very much a team built out of the resources available, rather than intentionally selecting only new grads.

Yet your other comment says, "this particular company paid way below market rate with the promise of interesting work. It without a doubt incentivizes hiring new grads where you roll the dice and hope the good ones will stay because they enjoy the job. It's very hard for them to attract experts at the salary that they're offering." https://news.ycombinator.com/item?id=43453700

> it being an internal project, it would have been killed once it had no active development.

I'm having a hard time understanding why this project needed to exist at all.

> But taking something to the extreme to see where it fails is a useful rhetorical tool.

I disagree, and it only created unnecessary argument in this case. You ended up having to retract and clarify anyway:

> I think 5 noobs to 1 expert is fine, just like 5 to zero is bad

But the team was 5 to zero.

> just like 1 to 1 is bad.

Why?

> I don't know understand this means.

It means, this team was very much a team built out of the resources available, because the existing experts in the company who could have been mentoring new grads were already working full time doing something with a direct contractual obligation to the company. I would have been negligent to pull them from an existing inprogress contract to mentor newbies, and the contracts had a hard limit on number of hours, (not years of experience), so placing a new grad on one of these contracts, replacing an experienced engineer would have degraded the success of the contract.

> Yet your other comment says, "this particular company paid way below market rate with the promise of interesting work. It without a doubt incentivizes hiring new grads where you roll the dice and hope the good ones will stay because they enjoy the job. It's very hard for them to attract experts at the salary that they're offering." https://news.ycombinator.com/item?id=43453700

Right, they're not conflicting statements. The company would hire a pool of engineers that can do engineering, then a different part of the company would sign contracts to complete work, than a middle part would place the engineers in the company onto contracts.

> I'm having a hard time understanding why this project needed to exist at all.

Well, because it was a really cool project that the company did end up marketing and selling to it's various clients. It was also a perfect project to put a bunch of new grads who otherwise wouldn't have been doing any work at all given the projects had contracts that stated they couldn't accept more engineers.

> I disagree, and it only created unnecessary argument in this case. You ended up having to retract and clarify anyway:

I didn't retract anything? Are arguments bad? I actually enjoy being able to arguing interesting points and topics. If you're willing to be wrong, you can learn things. As an example I didn't think my previous examples were so controversial. Nor did I remember that contract based engineering work isn't a common thing the most people already have intuition for.

> [just like 5 to zero is bad...] But the team was 5 to zero.

The team you called pathological? Yeah, it was bad. Missing deadlines is bad. I don't understand where you're confused.

> [just like 1 to 1 is bad...] Why?

I already answered. Because of politics a project that small would have died with a team with just a single new grad. It also would have been boring as fuck. So if I left, I'm sure the new grad would have also left. Which means the company who hired us both, would then have to hire two new people. This was years ago, but I assume some of those original new grads are still there. In part because that team was actually fun to work with. They were good people, and the team was just fun to be around. A team of just 2 is boring... I know because I've also been on that team with me doing all of the work, and it was soul crushing, and contributed to why I left.

  • >> But the team was 5 to zero.

    > The team you called pathological? Yeah, it was bad. Missing deadlines is bad. I don't understand where you're confused.

    >> [just like 1 to 1 is bad...] Why?

    > I already answered. Because of politics a project

    I was confused because I thought you were trying to make general points, but apparently you're mired in the minute details of one company and its extremely specific projects and politics.

    I'm getting the impression that there were so many idiosyncratic constraints on the project that it simply couldn't have gone any other way, and thus there's no real way to critically evaluate whether things would have gone better with a different arrangement. Be that as it may, I'm not sure what kind of general conclusion we're supposed to draw from such a constrained example? Going back to the linked article, the case of Tim didn't appear to be so constrained:

    1) They were thinking of getting rid of Tim, which presumably wouldn't have killed the project entirely.

    2) They expected Tim to make more individual contributions, which presumably wouldn't have killed the project entirely either.

    3) The team already had a mix of junior and senior engineers, not simply Tim and a bunch of new grads.