
My Favorite Functions and Patterns: debounce
This is the fourth post on my favorite functions and patterns in functional programming. Today, I’m sharing the function `debounce`.
This is the fourth post on my favorite functions and patterns in functional programming. Today, I’m sharing the function `debounce`.
Welcome to the second installation in my series on functions and patterns in functional programming, featuring function: curry, named after Haskell Curry.
This is just one segment in a compilation of my favorite functions and patterns in functional programming. This bit focuses on the with statement.
The Blockchain. I ignored it for so long. Too much hype. Too many stories of fraud. Those things are enough, but I absolutely hated…
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.
Having this Elixir-to-Node bridge allows us to use a tried-and-tested JavaScript library for our app while we get our Elixir client off the ground.
Before investing heavily into the entire IPFS infrastructure, you’ll need to wade through the misconceptions and the fud (Fear, Uncertainty, and Doubt).
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.
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.
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.
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.
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.