3 ms·
Will I be expected to hit the ground running and be a rockstar coding ninja? No. Will I have a mentor to help guide me through their massive code base and ans
by onion2k 11y ago
Will I be expected to hit the ground running and be a rockstar coding ninja?
No.
Will I have a mentor to help guide me through their massive code base and answer my questions?
No.
Will they patient with me if I'm slow?
Yes, but only within a certain latitude. You'll be allowed to make mistakes, but only once - if you repeat the same mistake that's definitely considered a bad thing. You'll be expected to learn from your experience, from code reviews, and from what other developers tell you.
While that might sound scary it's also worth noting that you'll probably be given relatively simple tasks, like building forms and fixing bugs, so there's nothing to worry about. You should be able to do what's asked of you because anyone who has the confidence in their ability to even apply for the job should be able to do those things. Being "mediocre" is OK. Developer ability fits a bell curve - most developers are "mediocre" in the sense that they're in the middle of the curve rather than "great" or "awful" at the top or bottom ends.
Follow the company's practises, think through things, listen to other people, and find what you're good at, and you'll be fine. To be honest, I'd rather work with a junior dev who knows they're not a rockstar coding ninja but wants to learn than a junior dev who thinks they are, even if they actually are.
- seren 11y ago> Yes, but only within a certain latitude. Another piece of advice related to that. If I am giving long, complex and detailed explanations to a new guy, and he is not taking any notes. I have to assume that : 1. He has a good memory, and he will remember everything tomorrow (and I am totally fine with that) 2. He is totally oblivious of what I am talking about, and he will ask the same question tomorrow. So please, never put yourself in category 2. Be a genius, or take notes. And always taking notes, especially the first week, is useful because you'll get a lot of information in a short time. It is good to be able to process it a bit later on. For bonus point, if this is actually some process we have not documented and should be, take this opportunity to create a reference document for the next guys, it will be appreciated by your co-workers. You have a fresh look on things, this is valuable.
- allan_s 11y agoI second that, especially for the bonus point part. You'll need note anyway, one day or an other, and writing them on the wiki/knowledge/whatever of the team rather than on a sheet of paper, will also permit you to have some double check from your team members, which may clarify even more your comprehension of the subject.
- i336_ 11y agoIn the general case, would recording the conversation (probably just audio) likely be found acceptable? I'd expect to prearrange terms for how the file(s) would be stored (encryption etc) and hard limits on how long they'd be kept.