well my career so far is only 30 days long LOL! I just started my first-ever dev role.
My company's stack is mostly RubyOnRails; I actually gained most of my Rails confidence from configuring DevTo's platform on my local dev and learning their codebase to the point where I could create PRs for some issues. Even though we learned Rails in bootcamp, it wasn't the same as working on a codebase that I wasn't the only developer on it lol.
That's one small drawback to the bootcamp experience, in my opinion. Unless your bootcamp has you working with other students, mentors and professional devs from the beginning, you get the habit of being judge jury and executioner over your own code. whereas in a professional environment its more about understanding what others have coded, synchronizing with your team's dev flow, being comfortable with code review, etc.
Wow congrats on you first dev job!!!! 😃. You are right about getting accoustom to using other codebase besides your own. In my bootcamp we are paired to do projects together and then our code gets reviewed via PR once accepted then we can merge. So far that has been a learning experience because I never did a PR before lol. We also will be contributing to open source projects I think and we do have mentors.Thats really cool how you pull the codebase for this site and studied and contribute that's takes patience and will power,I'm sure it's intimidating at some point.If you don't mind ne asking how difficult was the interviewing process ? Did you do a technical interview ?
Absolutely, the whole interview process took about 2 weeks.
First was a take-home coding exercise which they gave 3 days to complete. It was in Ruby and involved creating Classes and methods to process the data given. It was moderately challenging, for me anyways.
Second step was a non-technical phone conversation with the business people; this was more behavioral in nature - how do you work with others, etc. This was the most pleasant part of the process lol.
Last was a 3-hour on-site interview which was very technical; they used scenario-based questions, whiteboarding and pair-programming. At any given time I was speaking with 4-5 devs at a time, so it felt a little overwhelming. But I gave my best answers, and was sure to say "I don't know yet" when I didnt have a clue about a question.
Thanks for your reply, I guess there is no running away from it huh! Technical interview must present it self lol. You are a great writer also maybe you should write a book sometime.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.