In this next article in my Six-Figure Resume series, I want to cover some myths and mistakes people make in crafting their resumes that hurt your chances or guarantee that you’ll get disqualified from a job early.

Now that we’ve covered the value of resumes and common mistakes that will prevent any resume from succeeding, its time to talk about the core elements your resume needs.

Folks looking for their tech jobs make a common mistake when they look for openings. They fail to recognize how titles really work and how to find opportunities they’d miss. This article explains how to find those other jobs.

Flow-state is a zen-like experience for developers where code seems to produce itself with low effort. As much of a joy as this experience is, there are hidden dangers to this flow-state, so let’s explore them.

Feedback is a popular thing to offer and receive, but most of us have a love-hate relationship. Setting up the feedback conversation is key, and one technique is to ask about the type of feedback they want.

The basic elements to create your first online class are picking a topic, format, marketing, and long term results. I break those down in this article and how I’m doing them myself.

Technical interviews are brutal, but in this article, I explore two reasons why. Interviewers don’t know how to answer their own questions, and they’re full of bias.

Ever wondered why you don’t get an interview at some companies? The answer is that your resume wasn’t good enough. In this article, I will take a few moments to explain why that is and a few things you can do to stand out more.

Eventually you won’t know how to answer a question in an interview. In this article I walk through three alternatives to saying “I don’t know” that give much better results.

When you have a high-stakes project, how do you know people are just talking about software performance vs taking action? I share a way to use your use-cases to get started setting performance targets early.