4 ms·
As someone who work with new recruits, we are not excepting stellar contributions from day one. We are more looking for people who are willing to learn and grow
by seren 11y ago
As someone who work with new recruits, we are not excepting stellar contributions from day one. We are more looking for people who are willing to learn and grow, and start contributing steadily in a few weeks or months.
As a rule of thumb anyway, if you are new, you are not going to be in charge of a critical piece of the infrastructure for years to come. Likely you'll be giving relatively straightforward tasks, and once you'll have proven to be reliable you'll be given harder and more challenging tasks.
It depends on the place, but I would say that 80% of software development is rather mundane and "easy". And for the time being the harder decision will be taken by more senior people. So actually, starting is pretty comfortable and easy most of the time.
One piece of advice, do not hesitate to ask questions. We expect people to have generic CS knowledge, but it is often not enough to understand 20 years old spaghetti code. The worst recruits are the one that are too paralyzed to ask any question, and as a result you have to spend twice as long to train them because you have to guess what's wrong first.
Personally, I don't mind answering question or mentoring new people, I see it as a form of investment. Sure I am "wasting" a few hour today, but your contribution will save me countless hours in a few weeks.
- kspaans 11y agoYup, don't hesitate to ask for help when you need it. Don't waste time spinning your wheels fruitlessly. If you are worried that you are asking for help too early (i.e. before you have explored the problem to the best of your abilities), then try writing an email (or something similar). I find it to be a useful way to anticipate the questions that others will ask ("Oh, have you tried X yet?", "Have you tried turning it off & on again?"). If you can't answer any of the extra questions that you come up with composing your email, then it's probably a good time to ask for help.
- Bdiem 11y agoThe process of structuring and explaining a problem to yourself via email or as before mentioned as "something similar" is available as a service: http://duckie.me/#about_section http://duckie.me/#about_section Related information: https://en.wikipedia.org/wiki/Rubber_duck_debugging https://en.wikipedia.org/wiki/Rubber_duck_debugging This method helped me alot as I found myself explaning a problem to a colleague finding the solution through the indepth explanation, wasting both of our time and focus.
- mrits 11y agoYou won't let someone take charge of a critical piece for years? This certainly can't be good general advice.