11 Ways: Start Working Remotely on Your Commute

Work Remotely on Your Commute

Think of it like this: There are 24 hours in a weekday divided by 3 segments of 8 hours. #1 is at work full-time, #2 is sleeping (right?), and that #3 segment is actually your "free time". I think a lot of us spend a huge chunk of free time commuting, and daydreaming of working from home instead. What if the pain points of both could be addressed simultaneously?

Pain points of commuting:
- Driving & biking require nearly undivided attention
- Transit requires more time

Pain points of working remotely:
- Missing skills / experience / mentorship
- Not enough time

I used to alternate between all 3 of these modes of commuting. I was surprised to find the traffic often took longer than expected, and crept up on the time it would take to bike or bus. It was more expensive, and I couldn't help but notice a feeling of starting the workday carrying the stress of traffic, fulfilling the workday, and then arriving home stressed from traffic. "The work I do could be done from home" I would think, exhausted. You might as well still be on the clock - Your employer requires that you have this commute to keep the job, but it's not compensated and the extra time lost on commuting actually cuts into your "free time" and ability to have a second job, or side hustle. Some people love their cars, but I thought the drive was an extension of my workday.

Taking transit created space for emails, Shapr, LinkedIn, and anything that could be done on a phone. When I switched to taking transit, I became much more bilingual, spending as much as 2 hours a day working on my French in Duolingo, and bringing it from 15% to 60% proficiency. That's when I realized that the time spent on a commute was a huge opportunity when you don't need to be occupied driving. 

11 ways to start working remotely on your commute:

1) Join groups for Remote / Digital Nomad networks on Facebook, Slack channels, and others.

2) Upload your resume on Indeed or as an email draft and apply for remote jobs during your commute.

3) Learn new skills for remote work - Sololearn for coding, or Udemy & Udacity for software and other hard skills, Duolingo for additional languages, Lynda, Khan Academy.

4) Take on clients for social media, and create draft posts during your commute. Many more people spend time browsing social media during those hours, so your posts can get more organic reach.

5) Draft blog and social media posts on your phone and drop in other content that is easier on your computer later.

6) Use apps like Shapr to network remotely, and spend some time browsing networking events in your area on Meetup or Eventbrite.

7) Listen to audiobooks instead of music - It's an excellent source of mentorship for entrepreneurial personal development and to passively get advice and new skills.

8) Create apps and website redesigns with phone apps like Marvel Pop App, Sketch, InVision and others. It's easiest to use a phone for haptics and to test responsive designs anyways.

9) Get Cryptokitties and to play around with Ethereum. Read cryptocurrency whitepapers, research the mandates and creators, and do your research to determine if trading during your commute is viable.

10) Create an online store and manage it via phone apps, such as being an Amazon affiliate, dropshipping, etc. 

11) Create profiles on Angel.co, Upwork, Toptal, and others.

Whether you call it remote work, location independent, or being an illustrious digital nomad - The resources available to get started are quickly increasing! If you are looking at your first "remote" jobs, sometimes it's good to start with a local company so you can become familiar with the actual challenges that crop up, and stop by in person if needed. If you can retain those clients for long periods, you can consider living in countries where the exchange rate will lower your overhead for living expenses, and sustain the cost of travel.

Share your experiences! What are your best tips for people to get started working remotely as a location-independent digital nomad?
 

AI & Smart Homes are for the Least Tech Savvy

Accessibility of Tech.jpeg

"Any product that needs a manual is broken."
- Elon Musk

We tend to think of Artificial Intelligence (AI) and smart home technologies as living in luxury homes, top secret vaults, or still in test phase as prototypes in the labs and Airbnbs of Product Developers. 

In general, we design for 80% of users - Address the largest pain points, which forms your minimum viable product (MVP), and then you iterate on that to refine it further on future releases. That seasoned audience doesn't have a big learning curve to understand how to make the switch from a familiar skeuomorphic button to a hamburger menu. In fact we prefer “intuitive” haptics and gestures, the less of an interface the better! Minimalism is sexy - But how intuitive is it? 

I gave my dad my old iPhone 5c in 2018. Coming from a flip-phone, it was the most advanced phone he’s ever had, and it was incredible to watch his interactions. His large hand held it daintily, and pointing in search of the right letters, found them too small to press individually. In fact, I realized, he types on a keyboard like this as well, searching with pointed index fingers for the correct letters, because he never took classes to use a typewriter in his adolescence, and didn't use a computer at work until the end of his career. 

Now there are new laws coming into effect, following the World Wide Web Consortium (W3C) in regards to improving accessibility to online design standards. Text to background colour contrast, font size, dictation, and other types of features are going to drastically change the UI of existing contemporary websites, and perhaps even brand style guides, for the online world as we know it. Especially for that 20%.

If Facebook is any indication, there is a huge recent increase in the 45-55 year old age range of people opening accounts. There are also some more elderly “early adapters” starting to emerge. I know this because they share my Facebook posts for a bulk foods client with remarkable frequency. Amazing! But what does it mean for accessibility? 

These demographics aren't as resistant to technology as we’ve made them out to be. It’s time to design for them properly, and that might not always take the form of a larger scale iPad instead of a tiny phone. Maybe we can skip the 44px CTAs and text based UI wth enough contrast, and basically move straight to systems such as Voice User Interfaces? It can even connect to my dad’s Bluetooth hearing aids

“Why can’t people just pick up the phone and talk instead of sending emails” - A common pain point, but expensive to maintain. Chat bots are perhaps an extra-friendly interface if we can get dictation right. Echo and Alexa can offer an extra layer of companionship. What about service dogs? If we can personify a Roomba, surely there’s more potential.

Artificial Intelligence and smart home technologies might largely skip the tech-savvy 80% by comparison, because there are already sufficient tools for their pain points. The biggest demand for these tools is basically going to be for people who don't currently have easier ways to achieve their goals. It's easy enough for me to unlock my door with a key, but for someone with arthritis, a smart lock is much more revolutionary. 

Smart Homes and AI are chiming in at the perfect moment for conversations around accessibility. How might we take a step back from teaching our parents how to use technology, and give them a chance to teach us how they would like these interfaces to be? It turns out the elderly, and people with accessibility barriers are the perfect early adapters after all.

When Tech Meetings Turn Out to be Dates

An actual wedding band, custom-made for a Microsoft Game Studios Software Development Engineer. 

An actual wedding band, custom-made for a Microsoft Game Studios Software Development Engineer. 

Let's set the scene: You've just attended the "hottest" tech talk on Artificial Intelligence, and a lot of intriguing new ideas are flowing through the audience. They've lined up to indulge the speakers, and everyone else is mingling enthusiastically.

Scanning the crowd, everyone is matched up, flapping their business cards and pulling up responsive portfolios and LinkedIn apps, like quickdraw. You lock eyes with someone across the room, and conversation ensues. It's great, they have a new project they're struggling on a certain area for, and it turns out you know that area really well. Cards flap, websites flow, LinkedIns link. You arrange to meet for a beer and discuss it further. 

The day arrives, and you're armed with a bit more research. Approaching the pub, you shoot them a message, "How can I spot you?" A reply comes through, "I'll be the handsome guy sitting at the bar." You stop at the door. 

Is that something you waive off? Walk in and give them a chance to redeem their stupid joke? Their confidence is positive. They're probably nervous. It can be politely clarified in the conversation. It hangs in the air, you have trouble keeping the conversation on track, and you walk away wiser.

"How might we prevent that?" In my case, I bought a fake wedding band. Where have you drawn a line to make professional distinctions?

We’re Asking Too Much of Developers

Recently I was looking at postings for UX/UI Design roles, and I noticed a pattern. So many of the ads were asking for these designers to have the coding knowledge to build their prototypes. Traditionally, UX/UI Designers are not trained in coding, so those roles would be somewhat hybridized. "Looks like what you’re asking for is a Front-End Developer," I thought out loud. It made me realize - We demand too much of Developers! 

UX/UI Design is a supportive role to help take some of the load off of Developers, who already use creative ideation for problem-solving practical website aspects. Many will attest to their frustration of an interrupted workflow to have to stop and invent something that was omitted from the blueprint.

Imagine this: UX/UI Designers and Developers, are like Architects and Engineers. The architect focuses more on the artistry and design of the building, while the engineer focuses more on the technical and structural side. In a highly cohesive team, these roles work in tandem, bouncing material back and forth to iterate on the best solutions. They understand and contrast each other’s skillsets enough to validate key concepts and coordinate more effectively. 

So how might we support Developers to be able to delegate their massive workload? To hone in and advance their expertise further? How might we support their healthier work/life balance and reduce burnout? Include UX/UI Designers as part of a healthy digital product team to support the success of developers and of the company overall.