How to Get a Job You're Overqualified For

If you’re a veteran developer looking for a new role, you’ve probably bypassed plenty of postings because you felt you were too experienced. Sometimes that’s valid—you have no desire to go backwards in your career.

How to Rock a Side Project When You Have No Free Time

We’ve all heard the advice: the best developers live and breathe programming. But you’re also a human being. Maybe you’re not the stereotypical 22-year-old with no ties or responsibilities, happy to work 18-hour days. Maybe you’re a mother or a father, a husband or a wife, a caretaker of an elderly relative.

There are millions of developers in the world, and they come in every shape. Most of us are not in our early 20s, many of us aren’t single, and few of us want to give our entire lives to our jobs. So how do we reconcile that truth with the general belief that the “best” developers are those who eat, sleep, and breathe code?

In other words, how can you show you’re passionate and committed without completely neglecting the rest of your life and responsibilities? Specifically, how can you find the time for personal projects without losing your mind?

Pair Programming and How It Can Make You a Better Programmer

Pair programming, where two developers share a single workstation, has grown more common and less controversial over the years, but many still haven’t tried it themselves. In pair programming one participant is the “driver,” who actually writes code, and the other is the “navigator,” who checks the driver’s work as it’s done and keeps an eye on the big picture. The two switch roles every few minutes, and talk to each other throughout the process.

Why Developers Should Always Be in Job-Seeking Mode

The ideal job-hunting situation is simple: You have a job, your bills are being paid, you’re comfortable, but you’re looking for a step up or a new challenge. You quietly apply for jobs while continuing to excel in your current role, find one that represents a comfortable advancement in your career, give your two-weeks notice, and move on.

How I Open Sourced My Way to My Dream Job: Mohamed Said

Mohamed Said got his first computer at age 13—they were just becoming commonly accessible in Egypt—and started learning to code almost immediately. Flash was what drew him in, he says, with its animations and color and, well, “flashy” stuff.

Developers: Trash Your Resumes

Last week we wrote about whether a college degree is a necessity for a developer in today’s market. We came to the conclusion that what you can do is more important than how many framed diplomas you can hang on the wall, and the most important thing you can to do make yourself hireable as a developer is to code, early and often.

Do Developers Need College Degrees?

Do developers need college degrees? Just a generation ago, it was a given that a college degree was the best way to maximize the likelihood of securing a high-paying job in the field of your choice. But the world has changed, and more and more you hear of successful developers who never earned a degree, or college dropouts who made it big in Silicon Valley. Think pieces are published every day pondering the value of college, the skyrocketing rate of student loan debt, and whether or not the entire institution is just outdated and archaic.

Is an Early Stage Startup Right for You?

Chances are you’ve thought about going to work for a startup. If you’re in software, you’re surrounded by startup chatter. Who’s hot, who’s funded, who’s the next Twilio. Maybe you’ve fielded an offer or two from startups sure they’re about to be the next Silicon Valley unicorn. Or maybe you haven’t, but you’d like to. But a startup job is not just a job. The startup environment, especially in the early stages, is unique, and it takes a particular kind of personality to thrive in one.

There are incredible benefits to joining a startup, but there are also some downsides. Here are some of the key indicators that can help you decide whether an early stage startup is right for you.

Do You Code for a Living?

Not too long ago, developers were treated as nothing more than interchangeable assembly line workers or typists. Developers were supposed to just write some code and let everyone else do the “real thinking.” Stack Overflow was founded by programmers, for programmers, in part as a reaction to this backwards approach. We don’t think developers are typists. We think they’re doing something much more important. They’re writing the script of the future.*