A while back several Revelers were chatting in Slack about learning and working as a software engineer. Some interesting ideas were being thrown around…
Personal development content on the Revelry Blog: Navigate our lab notes by using the tag system.
Meet Jeff Ramos: Youth Soccer Coach, Talent Recruiter, Mardi Gras Parader, and the CEO’s Little Brother
Jeff grew up in New Orleans, attended Auburn Montgomery University to play soccer, then moved in with Gerard in Lake Tahoe to help him…
Don’t Get Turned Into Spaghetti By Tidal Forces As You Approach The Event Horizon Opinions about ‘scaling’ and ‘change management’ that flood expanding companies…
Technical interviews are broken. We do case interviews in order to take candidates from hearing the scenario, to asking clarifying questions, to giving broad opinions and concepts, to specific architecture and programming tasks.
Everyone is a leader at Revelry, and it’s because we let the process take the lead. Hang on though – we’re not cultists. When the process doesn’t fit, we allow ourselves and our team to change it up. We make the process work for us when necessary, not the other way around.
Maverick is a far more interesting read than the average business book. I heartily recommend it to anyone who wants to make their work place more energetic, effective, fair, and most of all, humane.
Aline wants you to go forth and be awesome, non-technical project managers: Acknowledge that learning new things is hard, be patient with yourself, and trust that the technical team will give you the same courtesy. Together, we make each other better. It’s the Revelry way.
If you take a cross-section of developers, you’ll find some very mixed opinions about pairing. Some devs hate it. Some devs write blog posts about how great it is. Why is this? Let’s chat about why pair programming is awesome, and what you can do to level up your skills.
At age 50, I was hired as a software apprentice at Revelry Labs after retiring from a 23-year career in finance. Here’s why… and how it’s going.