I try to embrace a particular way of working with code: it should be minimal, idiomatic, and performant by default. Sometimes it is necessary to trade performance for readability, or readability for performance, or even break the deal if the trade is not worth it.
Today I spent a good amount of time trying to understand why a specific spec was failing. Turns out I was getting a rspec expectation failure, saying that it expected to change oldest_post from oldest_post to nil but it did not.
What code of yours isn’t tested? Is it code that deals with complicated situations that you don’t control? Threads, running commands, git, networking, or UI?
A 10x programmer is, in the mythology of programming, a programmer that can do ten times the work of another normal programmer, where for normal programmer we can imagine one good at doing its work, but without the magical abilities of the 10x programmer
Could you be using Git more efficiently? The answer is probably a resounding “Yes,” which is why Toptal Software Engineer Ursula Clarke wrote today’s post. In it, she teaches you how to use git stash, git reset, git bisect, git squash, and git rebase for maximum productivity.
Making software is not a manufacturing process. In the 1980s everyone was running around terrified that Japanese software companies were setting up “software factories” that could churn out high quality code on an assembly line