#communication

There are perfectly valid reasons for why you would write something even if you don’t expect it to become a top result on Google.

Don’t be a backseat driver, trying to take over the PR through comments.

The secret of good programming is to strip every statement to its cleanest components.

Here are my favorite technical questions to ask when interviewing software developers.

I want to engage in good conversations, but I don’t know where to do so.

Treat every support issue as a bug. Then fix that bug!

Remove everything that has no relevance to the design.

The best design does what it needs to, and no more.

Check code committed to version control for quality, and the code base will thank you.

Are developers rational machines or just out of touch with our emotions?

To make something easy to understand, its parts should be at the same level of abstraction.

If you don’t know what message to write, it was too long since you last committed.

Don’t use AI to write text for you, or you’ll lose the opportunity to sharpen your thinking.

Create abstractions to communicate intent to your fellow programmers.

Use creation methods when a constructor fails to fully capture the programmer’s intent.

A deep dive into unit testing looking to answer why, how much, and what.

Teaching is a great way to determine if you truly understand a subject.

A few examples of how viewing tests as documentation can affect your test writing.

When naming tests, include both the input as well as the expected outcome.