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.
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.
Choosing a text editor is a personal thing, but here’s how using Vim with VS Code has made me a very happy software engineer.
You’re not alone. Jason has a lot of smart friends who are into cryptocurrencies like Bitcoin and Ethereum. And he wanted to know what it is to get excited about, because blockchain technology is about to change everything.
You’ve tested. You’ve deployed. Your work is out in the wild. Then – WHAT IS THAT on your bug report? Oh… You have users on Internet Explorer. Jason shares how to test using Windows Virtual Machine on the MacBook.
Review your own code first before sending it for peer reviews. Here’s how to change the lens through which you’re inspecting your code.
If you write tests after you wrote the code, it’s hard to be 100% the tests are legit… If they wouldn’t have failed without the code you just wrote, they’re basically useless.
Jason says, “Revelry has always been on my radar as a company that works for the community and hires amazing people.”