In my time at Atomic Object, I've worked on a range of different projects. I've begun thinking of each project as its own language.
Transitioning onto an established team can feel like being a newbie all over again, especially if the codebase, languages, or team dynamics are unfamiliar.
Onboarding is a tricky thing to get right. Most onboarding experiences I’ve had were brief and packed with information lacking immediate relevance.
When ramping into an existing team, asking questions goes a long way. Here are questions I've used to get to the heart of what matters.
I hope sharing this lingo will help new Atoms get a feel for company culture and kick off their experience with Atomic by feeling “in” on that culture.
I’d like to share some insights and lessons from the most recent recruiting season at Atomic Object that I hope will be valuable in the years ahead.
One thing that’s helped me teach and learn new tasks is our team’s emphasis on documentation and a defined way to pass along process.
Imposter syndrome can hit new devs hard during onboarding. There are some simple things experienced devs on the project can do to ease the pain.
You can use the "Remember the Future" exercise not just for a product launch or milestone but also to build a shared vision with your software team.
I have come to realize that taking an active role in the onboarding process is the best way to successfully ramp onto a new company or team.
Did you just start a new job? Are you struggling with confidence? Here are some tips and tricks that helped me get over my imposter syndrome.
Onboarding a new developer is a fun but hectic time for any project. I have found that assigning meaningful work can be the biggest challenge.