DEV Community

Omar Alshaker
Omar Alshaker

Posted on

My Thoughts on Working Remotely, One Year in

Barefoot to the Moon album cover by Echoes

A little intro

It’s been a little more than a year since I joined Starcounter. Working full-time as a Javascript developer mostly on Palindrom, JSONPatcherProxy, and fast-json-patch. All the team I work with is in the same timezone. We use Github, Slack and Google Hangouts for meetings.

I have never been happier and more satisfied with my life than I am now. It’s been a great year and I learned much more than I ever thought I will before I started.

Before I dive in, it is important to note that a lot of this experience has to do with my nature and my personality; everything I say in this post only applies to me, and may or may not apply to other people.


One the personal level, I truly enjoy socializing. But the way I define socializing is meeting once a week for a couple hours. I tend to think that meeting people every morning is a burden. And working remotely is a godsend for me.

However, in this year I learned several lessons when it comes to socializing:

  1. Your social attitude is as important as your skill set. We are social animals after all. Internally, I have never decided whether I liked a workmate based on how clean their code was. Or how their jsperf results scored. As much as I try to be professional and objective, I find myself liking and respecting nicer workmates more. And obviously, this applies to me too. And proving yourself nice remotely is harder than in real life.

  2. Networking is a different challenge when working remotely. There is no coffee break or lunch chitchat**. **You’ll have to step up your social media game, conference attendance and other networking activities.

  3. We project on people. In real life, we project all the time. We don’t know enough about people to understand them, so we assume a lot about them to sympathize (or the opposite) and understand what they’re saying without much effort. This can be a good thing, but can easily go wrong. When working remotely, you know less, so you assume more. When I first met my team after two months of text communication I was astonished how nice and cheerful they are. I painted wildly different images of every one of them based on the way they communicated on Slack. Not to say that my imagination was grim, but it was largely off. This was eye-opening for me.

  4. Seeing the informal side of my workmates was key. It was key to seeing them as nice human beings who joke, have fun and have some weaknesses just like I do. Partying with my teammates helped me a great deal to feel secure about myself, to express who I am as a person (not an engineer). And this is a two-way street, it helped me to know who they are, as people, not robotic professionals.

What I learned from the above is that meeting the team was absolutely essential for my morale, satisfaction, and mutual trust.

The efficiency factor

One of the upsides of text communication is the ability to think, research and even later-edit what you have to say. When a workmate asks me a question on Slack, I give them a solid well-researched answer with links to specific lines of code. This saves us a lot of time and energy. Every question is a chance to learn and feel more confident.

Also, I rely much less on memory now. I can go back to any conversation I want, and I use Slack search all the time to do that. Even though Slack uses a ton of memory, at least it’s not mine 😄. To me this is a priceless upside; I always struggled to remember the conclusions made in a meeting three days later. This gives me a clear head and the ability to only process one thing at a time. Because I don’t even try to memorize conversations anymore.

There is no lack of wishing sometimes that I could walk up to a workmate and ask them a quick question and instantly get my answer and move on. But the experience is close enough on Slack.

Another huge upside to remote work is readiness to work open-source. If you think about it, most of the time open-source work is remote work. You almost never meet your contributors nor the project owners of where you contribute. Having a job that trains you to work open-source is a blessing. I’m now trained to be unambiguous, direct and to more communicative. Add to that, most the libraries I work on are in fact open-source. This gives me endless satisfaction and pleasure.

One thing I don’t know about is how much extra effort my workmates are putting to support me working remotely. I try my very best to eliminate that burden but I’m pretty sure there is an extra mile they walk sometimes to support the remote part of the team. I don’t have a decent insight on this.


Now, I’m much more efficient than the times I used to commute. Personally, I find it hard to read or do anything constructive whlist commuting. Those are at least 60 minutes saved every day, which I spend in the gym. In a nutshell, I work + exercise in the same amount of time a commuter only works, and with less focus and energy.


Working from home is reputated to be unhealthy. Well, not in Warsaw. The only thing I can confess to missing is morning sunlight. But there isn’t a lot of it either ways here. And I try to make up for that:

  1. I go out in the morning during weekends.

  2. I work with a huge window next to me that is always uncurtained.

And smog is a big issue in Warsaw nowadays, so staying in can be even healthier than commuting to downtown everyday at peak pollution hours.

Regarding sitting for a long time. Working in an office isn’t a whole lot better. So remote or not, without going to the gym, my job would be extremely unhealthy. I can’t stress this enough; going to gym is crucial to my health now.


Another cool thing about working from home is the food. Everyday I have a decent breakfast. And recently I started cooking my lunch the night before. When it’s lunch time, I heat my food and make some salad in quick ten minutes, and enjoy every bite of it. Much healthier than eating at work; has the exact amount of protein and other nutrients that I plan to eat.


I would definitely recommend working remotely for a friend, but they need to make sure to meet their team occassionally, exercise and always give the benefit of the doubt when things are unclear. It’s also very important to find alternative ways for networking and self marketing.

This is my first post here, please excuse any mistakes or errors.

This was originally posted on Medium

Top comments (3)

alshakero profile image
Omar Alshaker

Thank you!

Yes, a little bit. I would say there is indeed a bigger chance of feeling less comofortable talking to some of your teammates more than others. But I would also say exactly one meeting for 1-3 days is more than enough to kill most of those thoughts and feelings. For me it was not about knowing who they are as full blown personalities. It was rather a moment of "aha! They sound totally different than I thought, my judgement was flawed" kinda thing. The first meeting had the biggest impact on how well I got with people. Following meetings were fun but not as necessary.

zoebourque profile image

Thanks for the insight. I, too, use Slack for work. On top of that, I also integrate Slack with Quire for better organizing and tracking my work. During working remotely, one of the ways to keep me sane is morning/afternoon walks. I found that walking every day soothes my mind and body.