Make sure you’re doing this consistently, because down the line it makes a big difference to somebody digging through git history.
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.
When every day is “same same but different” as they say, it helps to rely on habits for staying on top of responsibilities. This way, we don’t slip into feeling reactive and stressed out with our workloads.
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.
It’s too easy to drop the learning aspect from Agile when the default is to build. We believe in the value of design thinking principles, and our innovation partners benefit from the quick wins that come out of slowing down once in awhile. Here’s how we do it.
At Revelry, we are heavy users of DataDog so this solution leans heavily into putting metrics there.
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.
Once he wrote his own implementation of Conway’s Game of Life, Jonathan finally felt like a real programmer. He continues to apply this tactic when learning a new language or library. Here, he shares the results of using it on Ramda.
Jason had a theory: He dislikes abbreviations and acronyms, ambiguity and magic. And he likes explicitness and clarity. So he wondered why some code naming conventions seem to punish verbosity (when it’s required) and what this all has to do with language naming conventions.