Reminders and Lessons from the CrowdStrike Incident
Last week’s CrowdStrike incident was a stark reminder of the importance of secure software development practices. While the specifics of the global event remain…
Transparency content on the Revelry Blog: Navigate our lab notes by using the tag system.
Last week’s CrowdStrike incident was a stark reminder of the importance of secure software development practices. While the specifics of the global event remain…
Here are 8 things Developers can do to balance the effort of communication across entire project sprints.
In the bustling city of New Orleans, where creativity and culture intertwine, Revelry has long been known for our commitment to fostering personal and…
At Revelry, we have a pretty solid internal Slack communication structure. Here’s how we collaborate with multiple innovation partners on Slack.
Getting stuck isn’t a bad thing. Actually, getting stuck on my first day on my first project may have been the most valuable thing to have happened. It was in that moment that I learned all I needed to know about transparent communication at Revelry.
I’ve chosen this specific list as part of an effort to foster a shared understanding of commonly used terms. This “glossary” doesn’t exist in a vacuum – it can (and should) continue to be challenged and evolve over time as our understanding changes.
A flexible work environment means that the team may be working or resting at many different hours. Believing that your teammates have achieved that essential personal balance is the first step in knowing that you’ll be operating from a place of trust.
You don’t have to allow interruptions. Take that pressure off yourself.
We have daily standups. We tried adding a thing called a daily 4:20. But in the end, we decided to improve our ticket comment writing game. And Aline led the charge on the how and the why.