Just a few short years ago, working from home may have seemed out of reach for workers in some industries. Today, remote work is on the rise!
In 2015, 23 percent of employees reported doing some of their work remotely. This is up from 19 percent in 2003, according to the Bureau of Labor Statistics.
With the growth of the internet and the need for talented workers, more companies have started to accept working from home as normal.
As a software developer, I’ve definitely marked this trend. With my skill set, all I really need is a relatively powerful computer and strong internet connection, and I can practically work from anywhere.
I’ve been working from home for almost a year now. Working from home isn’t all sunshine and rainbows. Some days have been a lot better than others. Don’t get me wrong –– it’s great. I wouldn’t change it for the world, but like most things, it takes some getting used to.
I’ve learned a lot about working from home over these last few months. Here are my suggestions on the right way to work from home.
When feelings about a job are extreme, either good or bad, you know what to do. When you love your work and can’t wait to start coding each morning, it’s clear that you should stay. When things are horrible—I mean down right awful—most developers will do their best to abandon ship as quickly as possible. However, when you’re simply comfortable, you might not know what to do.
Sometimes you need to make a change and you don’t even know it. Here are a few hidden signs that it is time to leave your job.
“Everyone you know started off as an unknown until they did the thing that made them known.” —Gary Vaynerchuk
I recently heard this idea from a highly successful businessman Gary Vaynerchuk and wanted to elaborate on its applicability for software developers. The concept is that you’re one piece of content away from changing your life.
Being able to learn things quickly is an amazing skill to have—even more so for developers because of speed of technology.
Most people change careers 15 times throughout their life. Not jobs, careers! So it’s safe to assume that the average developer will have multiple jobs throughout their career. Each job change has the potential to require different skills.
The things that were commonplace even 15 years ago for developers are now obsolete. So, yes, it’s important for developers to be able to learn while on the job. I would argue, however, that a more important skill is being able to choose what to learn next.