I often see people split work into horizontal slices. Ticket A: database tables and models. Ticket B: controllers. Ticket C: front-end. There’s something better — full-stack slices.
Our communication practices can be very disrupting. Remote work has taught me to be more considerate of how I communicate with others. We should treat other people’s time as we like ours to be treated.
Most people learn vim’s
visual modes. But they’re only casually acquainted with vim’s powerful Ex commands. Let’s take a look at some.
Vim has a reputation for being hard to quit. But it turns out there are so many ways to get out of it — it’s like vim wants you to quit. Let’s look at a few.
Some tools and tips for remote collaboration from my experience being remote over the last two years.
With Ecto, 🎶 you can always get what you want. And if you try sometimes, well, you might find, you can select want you need 🎶.
My workflow usually involves squashing many commits into a single one. But sometimes, the workflow calls for the opposite action – splitting a single commit into many. This is how I do it.
Having your code reviewed can be daunting. But it can also be very helpful. As reviewers, we can make the difference. Here are five tips to make your code reviews more helpful to the author.
When faking external services in tests, start with something simple. I like having a public interface to adapters and having an in-memory adapter for tests. Let me show you an example.
Toggle between alternate files, edit files by type, and create files with templates — all with
vim-projectionist. If you’ve never used it, you’re in for a treat.