For the past 11 days I’ve been working on a small project. I do one hour coding sessions after work to focus on something I’m passionate about. The current project I’m working on is nearing its completion, and I’ve learned a lot. But there are things I wish I did differently. Here are three things I want to do for my next project:

1. Identify the primary goal of the project I don’t want to be stuck in development hell.

Yesterday, I re-discovered Bob Nystrom’s Long Names Are Long blog post. When he was doing code reviews at Google, he noticed a lot of code creating “identifiers that were too damn long.” So he wrote this blog post to provide guidelines on how to create better identifiers. Here’s my summary of Bob’s four rules:

1. Omit words that describe the variable’s type or the method’s parameters It’s redundant to put the type in the variable’s name.

Do you ever get the feeling that your command line shell feels outdated? Is it slowing you down? The initial release date of the Bash shell was 1989. The Unix commands? Even older, the 1970s. They’re old, but they’re not obsolete. There exists, however, alternatives that can increase productivity. Alternatives for the modern software development era. These are the 3 tools programmers should install to modernize their command line.

1. The Smart And User-Friendly Command Line Shell The modern alternative to the Bash shell is Fish shell.