I'm switching my post structure. I think if people read, starting with Work + TIL (Things I learned) makes more sense. For the motivated Reader there is a Personal part 😃

Work

I'm definitely now into too many things:

• The big pull-request (check out posts from Day 18-21)
• Our App moving towards WebViews for now. Me supporting them
• Our own A/B-Test
• Feedback Cycle (6 open requests).

At the same time our Sprint ended and we are moving into "Bug stream" Mode. This means our Team will try to tackle incoming and existing Bugs 50% and the other 50% is about finishing last Sprint tasks + research upcoming topics.

Inside Zalon (from Zalando) we decided to set up a rotating Bug responsibility.

Every Team (5) will be in Bug duty for one sprint (2 weeks). This isn't solving bigger legacy Tech Debt tasks but it helps stakeholders (Customer Care) to have transparency and expectations.

Right now, we have a dedicated Bug Kanban Board, we do Daily Standups with CuCa People to share updates, talk about possible new things (urgency).

How do you tackle them? Let's discuss here:

Besides that, the Apps topic is blocking me heavily from anything else. Most of the time I'm trying to reproduce bugs, discover half of my time that the code is fine and something is either missing or configured wrong, e.g. some hard coded URLs are outdated or BE redirects to wrong URLs.

TIL

When I was debugging a Back Button Bug, I discovered the following thing about React Router Dom:

• Be careful when using <Switch> Routes and having an unmount Hook.

Thanks to Apps, we discovered that inside a Switch Component for two different Routes which are part of one "User Flow", an Unmount was triggered.

Before (dummy names):

return (
  <Switch>
     <Route ... />
       {[FLOW_A_PATH, FLOW_B_PATH, FLOW_C_PATH, FLOW_D_PATH].map((path) => (
      <Route
        key={path}
        path={path}
        render={(props) => <AsyncComponent provider={providerComp} innerProps={props} />}
      />
    ))}
  </Switch>
);

After:

return (
  <Switch>
     <Route ... />
      <Route
        path={[FLOW_A_PATH, FLOW_B_PATH, FLOW_C_PATH, FLOW_D_PATH]}
        render={(props) => <AsyncComponent provider={providerComp} innerProps={props} />}
      />
  </Switch>
);

Checking React-Router docs it is clear why code above triggered unmounts where it shouldn't:

is unique in that it renders a route exclusively. In contrast, every that matches the location renders inclusively. - React-Router Docs

Personal

This week, Germany will decide how to lift some lockdown rules. If kindergarten will stay close for a longer period than we won't be able to continue this stressful schedule with my wife. It hurts.

Having a small kid (2y old) + 5y old is not easy to manage. Cooking, cleaning, educating etc.

Right now, we decided to not do much focused homeschooling until May, but this can't be stay for longer period of time. I also realize slowly that our kids need social contact. Playing with some other kids, learning basic interactions is important.

I've also realized how bad german school system is prepared. They don't have any online system for doing remote lessons. Using zoom, sending emails to parents etc. is not a healthy process for months or a year.

This is part of german / European education system. Government wants to educate kids in the way they need them. Not how they should. Also as a muslim parent it is even more frustrating every year our daughter grows and all the shitty culture against us (People of Color) is slowly hitting her.

Anyway, take care!

Cheers,

Ferit