loading...
Cover image for Remote work journey - Day 10

Remote work journey - Day 10

fokusman profile image Ferit ๐ŸŒŸ๐Ÿ•Œ Updated on ใƒป2 min read

working from home (27 Part Series)

1) Starting remote work journey - Day 0 2) Starting the journey of remote work - Day 1 3 ... 25 3) Starting the journey of remote work - Day 2 4) Remote work journey - Day 3 5) Remote work journey - Day 4 6) Remote work journey - Day 5 7) Remote work journey - Day 8 8) Remote work journey - Day 9 9) Remote work journey - Day 10 10) Working from home - Day 11 11) Working from home - Day 12 12) Working from home - Day 13 13) Working from home - Day 14 14) Working from home - Day 15 15) Working from home - Day 16 16) Working from home - Day 17 17) Working from home - How to deal with big PRs? (Day 18) 18) Working from home - Make your software easy to change (Day 19) 19) Don't do Health Sprints - Working from Home journey(Day 20/21) 20) How to handle bug requests? - Working from home Journey (Day 22/23) 21) You should not be afraid of a conflict 22) Can developers challenge product decision? 23) Feedback, Feedback, Feedback - Working from home 24) Paying the bill for tech debt - working from home 25) How a wrong Hook can DDoS you - wfh edition 26) Calming down and starting architectural topics again - wfh edition 27) First relaxing week - wfh edition

General

Ok, somehow Wednesday seems to be a turning point. The first two days were really hard, chaotic, still productive but balancing 2 remote jobs + 2 kids seemed impossible.

We change small things:

  • Accept the situation.
  • Don't create a stressful environment for the partner (which I unconsciously did ๐Ÿ˜ซ)
  • Enjoy the moment with kids, put the phone away.
  • During midday nap of our son, our daughter is doing preschool stuff (iPad Apps, printed items.)
  • I work an hour after both kids fall asleep.

This situation is not perfect, yet I'm positively looking forward as every day we do small changes with my wife.

Our daily schedule is still in place (more or less):

Alt Text

We are also trying to ask our daughter how her day was, what she liked and what not.

Guess what? Her best moments are Watching TV, Playing on iPad and Eating sweet stuff ๐Ÿ˜‚ our kids basically have unexpected holidays for another 3 1/2 weeks (at least).

Corona is still rising, I'm checking the numbers and reading some news.

Work

Today, we had our first Zalon All Hands and Google Hangouts is more or less working reliable. When there is an issue it is a connectivity issue rather hangouts itself.

Alt Text

Still, there is a general rule establishing:

  • If you're not presenting, asking a question please mute + hide video
  • If it is a topic with a lot of questions take it to a separate meeting
  • We use https://www.sli.do/ which is a nice way to ask questions and let them be answered easily.

Regarding my presentation:

  • I'll write a blogpost dedicated to it.
  • I shared that "We need more Fun", my random take of Snap Camera and the need for Watercooler Chat. The outcome is that our Data Team is now sharing their funny standups. Looks like I triggered something here ๐Ÿ˜… (yet they were doing it already before).

All in all, I prepared it based on my past blogpost and 2h of investment. For that, I have to admit it worked out nice.

TIL

Writing down some thoughts and observation feels great! I'm trying to not overthink this. I'm not a native english speaker and had to speak / write more actively when I did my masters degree and when I joined Zalando.

Normally, I try to use Hemingway App or Grammar.ly but I feel that they overcomplicate my thought process. So this time, it's raw (most likely wrong) written english. Enjoy it ๐Ÿ˜…

Technically, there was not much on the React side. We found an issue in what kind of article ID I was sending and fixed that. Right now, I'm trying to get my head around a good way of functional testing.

At the same time, I tackled smaller tasks related to some legacy Scala Templates, Scala code. As long as developers don't go to crazy with functional Scala I'm always realizing that with a good clean code strategy, anyone can understand and change code no matter their background.


Past Posts:

working from home (27 Part Series)

1) Starting remote work journey - Day 0 2) Starting the journey of remote work - Day 1 3 ... 25 3) Starting the journey of remote work - Day 2 4) Remote work journey - Day 3 5) Remote work journey - Day 4 6) Remote work journey - Day 5 7) Remote work journey - Day 8 8) Remote work journey - Day 9 9) Remote work journey - Day 10 10) Working from home - Day 11 11) Working from home - Day 12 12) Working from home - Day 13 13) Working from home - Day 14 14) Working from home - Day 15 15) Working from home - Day 16 16) Working from home - Day 17 17) Working from home - How to deal with big PRs? (Day 18) 18) Working from home - Make your software easy to change (Day 19) 19) Don't do Health Sprints - Working from Home journey(Day 20/21) 20) How to handle bug requests? - Working from home Journey (Day 22/23) 21) You should not be afraid of a conflict 22) Can developers challenge product decision? 23) Feedback, Feedback, Feedback - Working from home 24) Paying the bill for tech debt - working from home 25) How a wrong Hook can DDoS you - wfh edition 26) Calming down and starting architectural topics again - wfh edition 27) First relaxing week - wfh edition

Posted on Mar 27 by:

fokusman profile

Ferit ๐ŸŒŸ๐Ÿ•Œ

@fokusman

Senior Software Dev from Berlin. Working at ZalandoTech.

Discussion

markdown guide