Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Always ask for help if you don’t know how or what to do instead of pretending you know something or can handle it. Saves you the sermon and humiliation when you didn’t pull something off.
Also be professional and listen carefully. Seen many junior devs being an ignorant f**k and smart-ass
Goodluck on your job :)
andikaEka431y@InnocenceWine still. People will get annoyed if you bothering them with question the can be googled in 30 seconds.
@andikaEka I understand your point and it is good. I guess this is from my own experience and what I mostly see in most companies I worked with
To extend on that concept: Google before asking. And ask before wasting 8h in frustration.
Emails and slack are a great way to ask asynchronously, which is better than an interruption.
If you don't know something don't lie. Say you're not sure, but you can look into and get back to them.
If it's in person and you're going to be late one day, bring donuts and coffee. You don't have to do that but nobody will care about you ever being late again.
If there's after office beers, go. It's basically in person devrant.
Use the tools everyone else is using for a few months before you try something different. If you try something different, then don't ask them for help with it, you're on your own.
If you hear something you don't think it's right, ask before trying to correct, there may be a reason you don't know or you don't consider.
Don't clog the toilet if everyone knows it was you. Especially, don't just exit and pretend it didn't happen. (based on a story that was posted here a couple years ago)
Basically what the others have already said: if you don't know, look it up. If you get stuck or don't know where to begin - speak up, ask for help and for pointers [not solutions].
It may not feel like it, but being a junior is a very good thing. Because they know you will fuck up. And you're allowed to. You're a junior. Your job is to learn and build smth along the way.
A word of caution: companies tend to like devs stay juniors only this long. You have a year or two. Use that time well.
Explore, learn, search, ask for help, grow.
But most importantly - know your place. Seniors have seen and done shit it will take years for you to comprehend. There are exceptions, but usually experience deserves respect. I've been in this field for years, but still when some sr devs open their mouths, I shut mine and listen and I still get goosebumps.
Enjoy being a junior and use that time well. And have fun! :)
it took me too long to understand that it's actually awesome to be a junior 😁
Btw, did the hr get in touch eventually? Got the job you were aiming for?
@zemaitis congrats!! Have a blast there mate!
n00p281y@InnocenceWine Agree. Don't spend 5 hours trying to do something simple when a senior could answer in 5 minutes (at the same time don't ask for every little thing). Especially if it's about internal infrastructure. Ask for docs, if there's no docs unfortunately the senior developers are living docs. I'd also keep your own personal documentation, you'll probably need to go back and reference what you've learned, and you could easily turn it into actual documentation. Id recommend using markdown syntax, at least for blocks of code.
Starting a new position as a junior dev tomorrow. Any tips how to behave among the big bois in office? What to avoid and etc.?