11–20 of 23 posts
Think about how you'd like to solve a problem. Then ask one of your more seasoned peers to talk through it with you. "Lisa, I'm working through the XYZ changes and I'd like a second pair of eyes on my planned solution. Do you have a few minutes to go over it?"
Running "lint" tools on your code can be helpful for catching basic things, http://eslint.org/ is my favorite one for JS, I know ones exist for other languages. After that, ask for code reviews. If you don't understand why the reviewer is suggesting a change, keep digging until you do. Also, as partisan said, reading through the code from the other devs will be a huge win. Even if it doesn't follow "best practices",…
Think about how you'd like to solve a problem. Then ask one of your more seasoned peers to talk through it with you. "Lisa, I'm working through the XYZ changes and I'd like a second pair of eyes on my planned solution. Do you have a few minutes to go over it?"
Yup. One of things I am planning to do much much more. Sometimes feel a bit lost when couldn't even "start" to solve a particular problem.
I personally would feel very pressured and don't know how much I could focus and be happy if I were in your situation. Perhaps you are not bothered by it at all, in which case I don't think my advice fits you very well. But consider it.
Try asking the seniors for help when you get stuck somewhere. But only ask for help after trying all the possible solutions you can think of yourself.
Try to come up with 3 or 4 test scenarios for your code and test them before you submit the code. Thinking up new scenarios will help you reduce the bugs.
Critically review your own code a few days after you've submitted it. Pretend it was someone else's code and think of all the possible ways to improve it.
If your seniors are willing, ask for a code review. Go through the review comments carefully and make sure you never get the same review comment again. Don't ignore any comment, however trivial it may look.
Spend an hour or two extra everyday to improve your knowledge of the system. Learn something new everyday about the tools, language etc.
Been there. Consider whether you want to stay there. If you aren't sure start looking for other jobs. Even if you want to stay consider other options. If you're going to have to do a lot of catching up to get where want to be is it going to benefit you in the long run? It could be an opportunity to learn and grow in the but don't expect them to do you any favors.
Oftentimes when you get assigned a task there is another similar part of the codebase you can use as an example for what to do. Try to understand what the code is doing and go from there.
I think there's a third option - perhaps it is in your best interest to work elsewhere. Somewhere with a CTO / team lead who accepts your skill level as junior where you can grow without your job being on the line. I personally would feel very pressured and don't know how much I could focus and be happy if I were in your situation. Perhaps you are not bothered by it at all, in which case I don't think my advice fits…