Live data from Hacker News

Hey, n00b, we didn't hire you to complete tasks

newsletter.kentbeck.com

111–120 of 139 posts

Re: Hey, n00b, we didn't hire you to complete tasks

#111
post #86
post #66

[flagged]

> And when corporate needs to lay off 30% they’ll think nothing of it. Having seen this literally play out this year: it was all of the C’s that were first to be cut shrug

> Typical Kent, trying to do the right thing, regardless of the cost. Unfortunately, this time the cost was him losing his job.

Well Kent got fired from Facebook, so maybe he wasn’t such an A player in their eyes. ;)

Re: Hey, n00b, we didn't hire you to complete tasks

#112

So much of this is written with an air of superiority over the noob. Indicates a bit of an ego problem. Yes, the noobs are noobs, but the goal isn't to exercise your status over them. Or even to waste that much time trying to categorize between A, B, C. The goal should be to boost everybody's productivity instead of treating them like a game.

The seniors are superior to the noobs. Kind of by definition.

[flagged]

Re: Hey, n00b, we didn't hire you to complete tasks

#113
post #75

Earlier quoted context omitted.

Yeah good luck with that attitude over time. Most people don’t hang around in an org long enough to see that assumption scale to renting hardware than costs $900k a node a year.

Most orgs never get to that scale

And as you approach that point you should have fleet wide profiling (sample based) so it’s clear what’s worth improving.

Re: Hey, n00b, we didn't hire you to complete tasks

#114
post #51

Earlier quoted context omitted.

Related, but the best quality to have in a startup is knowing when and what corners to cut instead of going on these side quests.

I used to think this but you only know which were the right corners to cut after the fact. And most things are not obviously right or obviously wrong, instead it’s a slow zombie death by a thousand fuzzy signals. And the management tier of the startup will too easily color the signal by the flavor they want to see. My latest take on this matter is to separate speed as in fast from quick. Quick is the thing you want a…

And sometimes the yak shaving side quest yields big improvements that were not even on the radar.

Good engineering intuition, the ability to learn new code/systems quickly and the ability to quickly validate ideas is extremely valuable.

Re: Hey, n00b, we didn't hire you to complete tasks

#115

So much of this is written with an air of superiority over the noob. Indicates a bit of an ego problem. Yes, the noobs are noobs, but the goal isn't to exercise your status over them. Or even to waste that much time trying to categorize between A, B, C. The goal should be to boost everybody's productivity instead of treating them like a game.

I think the article is explicitly saying, "Ok, you're green, we know that. We're spending extra time with you to make you productive. You can help that process or hinder it, and if you're unteachable or uninspired, we'll probably end up letting you go. So here's some attitudes that get people singing your praises at this early stage." I'm not sure if this is the last gasp of this type of thinking as AI changes the la…

One possibility is it makes grasping these points quickly even more important.

IME new grad hires are break even effort for me for the first 6-9 months. If it’s clear they will become positive after that I put more effort into helping them.

LLMs may alter that break even math.

Re: Hey, n00b, we didn't hire you to complete tasks

#117
I’m a “junior” senior and I’ve got a junior whose faith I’ll need to decide in a few months. How do you know if they are gonna be good? And how do you give them all of the possible tools to actually be good? Not like I don’t have a clue, but I’ll appreciate some advice.

I think the biggest problem is that they almost dont ask questions. It’s like one question in two days. In past I had to deal with juniors who would flood me with questions, and with them it was pretty clear how they are doing (yes we talked about it).

Re: Hey, n00b, we didn't hire you to complete tasks

#118

I’m a “junior” senior and I’ve got a junior whose faith I’ll need to decide in a few months. How do you know if they are gonna be good? And how do you give them all of the possible tools to actually be good? Not like I don’t have a clue, but I’ll appreciate some advice. I think the biggest problem is that they almost dont ask questions. It’s like one question in two days. In past I had to deal with juniors who would…

I like to always tell interns/new hires that I measure their productivity in the amount of questions they're asking (whether its to me, seeing them roam into people's cubes or in company chat systems). AI has changed that calculus a bit since they can use the magic talking box to query the codebase with varying degrees of accuracy or as a search engine for someone's random internal wiki article/ticket from years ago.

Nevertheless though, we're blessed with a codebase that is several orders of magnitude larger than what the human brain can fully internalize so if you're trying to do anything remotely interesting, you're going to have questions.

Re: Hey, n00b, we didn't hire you to complete tasks

#119
post #75

Earlier quoted context omitted.

Agreed. Hardware is almost always cheaper than engineering time, until it isn't, and that's when you should spend the time on targeted optimizations.

Yeah good luck with that attitude over time. Most people don’t hang around in an org long enough to see that assumption scale to renting hardware than costs $900k a node a year.

Seeing what you made get to the point that that's an issue is a "a good problem". Yes, it's worth it to optimize at that point, but that's still an argument for what I consider premature optimization.
Post reply on HN