I personally consider myself a career-shifter from academia (though in a closely-related field) to CS. I just want to know how career-shifters are usually onboarded at work. In my experience, it feels like I am severely underprepared for the tasks that I am working on. I was just given some courses on the programming language that we use, some info on our product (what it is, our goals, etc.), and was thrown to the backend. I genuinely don’t know what I’m doing, and though I have made some minor progress, I don’t think my boss takes me seriously when I say I am not confident with the things that I’m doing.
Is it really like this? There are codes (with no comments at all) that I really just can’t read. For the parts of the code that I can read, it was all self-study. It seems like I am walking through a minefield here trying to see what works and avoiding breaking the code. A colleague even mentioned that I just have to ignore legacy codes, and she wasn’t clear about what those codes are. I feel like I have so many clarifications to ask but everyone’s too busy to explain these things. Do I really just have to read the code without external help? Why are they expecting me to know a lot at this stage?
submitted by /u/krabbypatty-o-fish
[link] [comments]
r/cscareerquestions I personally consider myself a career-shifter from academia (though in a closely-related field) to CS. I just want to know how career-shifters are usually onboarded at work. In my experience, it feels like I am severely underprepared for the tasks that I am working on. I was just given some courses on the programming language that we use, some info on our product (what it is, our goals, etc.), and was thrown to the backend. I genuinely don’t know what I’m doing, and though I have made some minor progress, I don’t think my boss takes me seriously when I say I am not confident with the things that I’m doing. Is it really like this? There are codes (with no comments at all) that I really just can’t read. For the parts of the code that I can read, it was all self-study. It seems like I am walking through a minefield here trying to see what works and avoiding breaking the code. A colleague even mentioned that I just have to ignore legacy codes, and she wasn’t clear about what those codes are. I feel like I have so many clarifications to ask but everyone’s too busy to explain these things. Do I really just have to read the code without external help? Why are they expecting me to know a lot at this stage? submitted by /u/krabbypatty-o-fish [link] [comments]
I personally consider myself a career-shifter from academia (though in a closely-related field) to CS. I just want to know how career-shifters are usually onboarded at work. In my experience, it feels like I am severely underprepared for the tasks that I am working on. I was just given some courses on the programming language that we use, some info on our product (what it is, our goals, etc.), and was thrown to the backend. I genuinely don’t know what I’m doing, and though I have made some minor progress, I don’t think my boss takes me seriously when I say I am not confident with the things that I’m doing.
Is it really like this? There are codes (with no comments at all) that I really just can’t read. For the parts of the code that I can read, it was all self-study. It seems like I am walking through a minefield here trying to see what works and avoiding breaking the code. A colleague even mentioned that I just have to ignore legacy codes, and she wasn’t clear about what those codes are. I feel like I have so many clarifications to ask but everyone’s too busy to explain these things. Do I really just have to read the code without external help? Why are they expecting me to know a lot at this stage?
submitted by /u/krabbypatty-o-fish
[link] [comments]