Our Engineering team, apprentices, Front-End Developers, and Designers share insights on the development process
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.
The hard part of this was recognizing the algebra beneath layers of domain-specific business rules.
Before investing heavily into the entire IPFS infrastructure, you’ll need to wade through the misconceptions and the fud (Fear, Uncertainty, and Doubt).
The team that seeks out feedback and views it as an asset rather than a slap in the face is the team that delivers real value to clients.
Tweak your environment regularly. Try something new, and improve your productivity. One thing that definitely deserves some care is the terminal/shell.
I was lying in bed this morning planning the best way to handle a merge conflict I know is coming with a colleague’s PR today, and I realized I’d like to know a couple of tricks for certain situations. Here they are:
Make sure you’re doing this consistently, because down the line it makes a big difference to somebody digging through git history.
At Revelry, we are heavy users of DataDog so this solution leans heavily into putting metrics there.