A 'programmer trap' is something that feels productive but in practice adds very little value to a project. Refactoring can easily become a programmer trap.

What are some others?
Creating "the perfect abstraction" is a programmer trap. Most of the time you should just solve the problem in front of you, only occasionally is a full abstraction necessary.
Chasing the latest trends can be a programmer trap. Hot new framework/library that solves a problem you don't *really* need? Then don't use it. Can waste a lot of time 'evaluating' every cool new trend.
Optimization can be a programmer trap, but honestly I feel most programmers don't think enough about performance so I don't want to encourage them to think of it even less...
Memory usage can be a programmer trap but VERY few programmers really think *at all* about how much memory they are using. Which is why applications are so bloated.
You can follow @JJcoolkl.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:
Those who think consciousness raising & movement building are disconnected, or even a distraction from electoral politics have not paid attention to the history of social change.In this thread, we
Read more
The 2020s will be known as the Remote Work decadeA few predictions of what is likely to emerge[ a thread ] Third Space: Office and Working from Home will
Read more
1/29: Have you ever had a concept explained to you that helps frame complex issues you’ve been wrestling with and opens your eyes to new possibilities? A concept that I
Read more
By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.