There are many moving parts involved in product delivery. Ideally, we never utilize developer shortcuts or compromises. And even when we knowingly take shortcuts, the intention is always to come back and clean this up eventually.
Search Results for: pull request
Mutation testing involves running your test suite many times, modifying the application code in different ways to see if the tests catch the change.
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.
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.
You don’t have to allow interruptions. Take that pressure off yourself.
Speaking up about potential challenges is a normal and important part of our process. When a teammate raises a fire drill, available or relevant teammates participate in the topic thread. Sometimes, we resolve the issue in a few minutes. And other times, we identify a major challenge and take the conversation to the product owner to discuss next steps.
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.
This purpose of this article is simply to give an up-to-date example of a React Google Maps component using ES6.