CodeFaster
ArchiveTopDiscussionAbout
You’re supposed to fix That Bug. That’s it. But the code is so ugly. Oh my gosh no wonder they wrote a bug here. I should tidy up. I’ll fix the “broken…
CommentShare
I got a lot of flack on my last post for suggesting piping to ls a la: ls | grep file Why? Because...
CommentShare
Just Use Sed
Comment 23Share
If you have a list, say of imports, where there is no semantic meaning in the ordering, alphabetize it. Alphabetizing makes it easier to find duplicate…
Comment 2Share
There’s no reason to leave code commented when checking it in, just delete it. It’s one of the most common pieces of feedback I give while reviewing co…
CommentShare
A fast programmer lives in their shell. It’s so powerful, there’s almost no reason to leave it. So, it’s important to have a fast setup...
Comment 3Share
Austen’s a CEO, so I can’t answer him either. But for you Mr. programmer, I can: Do LeetCode Why LeetCode A musician plays notes. Practicing scales is …
CommentShare
Today, we’re not talking about code. We’re talking about...
Comment 2Share
It’s so true! But why? It turns out, FAANG interviews are all about...
CommentShare
 Let’s imagine, Le nix, a unix-style restaurant. If it’s your first time at Le nix...
Comment 8Share
The Rule of Separation is one of my favorites because it tells me how to modularize code....
CommentShare
This is part of a series on Unix Design Principles to help us design code that can be written faster. In this post, we’ll discuss the Rule of Economy. …
CommentShare
© 2021 Tyler Adams. See privacy, terms and information collection notice
Publish on Substack
CodeFaster is on Substack – the place for independent writing