loading...

Can developers challenge product decision?

fokusman profile image Ferit ๐ŸŒŸ๐Ÿ•Œ ใƒป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

Thanks for reading! I'm writing about my remote work journey thanks to covid-19 forced me to ๐Ÿ˜‚ I'm writing now almost a month now (Day 26 and 27)

Work-related

The beginning of this week is still mainly around tackling big pull-request and supporting our apps team.

I prepared my open questions about a 3K LoC AB-Test which seemed too big. Big in, it is not easy to answer what is tested.

Our open questions were:

  • Do we want to test the value of our Outfits API?
  • Do we want to test the value of the Outfits UI as entry point?

From my understanding, the test was about a), yet the solution seems to be about b). Therefore, we scheduled a meeting with the Product Manager.

At the end, she decides what to put in here, yet we raised our concerns in creating such big pull-requests and the team should have smaller work packages (slices).

One thing I will not easily forget is something she said, when she thought we were blocking this and we want less features:

I'm surprised that developers are now challenging product managers. I thought you do what we need.

Alt Text

This hit me. I believe in any lean / agile environment giving feedback and asking questions is the whole idea of having such processes. Even when this person is not in your team.

So, shouldn't developers request changes to Features? Yes you should.

Our job is not about doing what business and product want without questioning anything. Even if you have a good relationship personally, this will end up in Mini-Waterfall.

When a feature is given to us frontend developers, there are multiple levels we need to evaluate:

  • Is the given design consistent (challenge UX) ?
  • What hypothesis do we want to answer ?
  • Are we measuring the correct things to answer it?
  • How many different slices (work packages) do I see?
  • Is it involving some legacy codebase? ...

Today I (re)learned (TIL)

Debugging can be a lot of fun!

Debugging

What I learned were rather trivial things. Yet:

  • Be careful when using custom X-Custom-Headers. Some weird bugs I discovered were related to our Frontend overwriting them, when WebViews were injecting them too.

  • Scala Template engine (Twirl) is confusing. Nothing to add ๐Ÿ˜ƒ

Personal

This week is really intense. I have many topics and deadlines at the same week. Thanks to my wife, who took another leave from work, I can focus.

Yet, it's a lot of things and I will be happy when this whole week ends. Giving Feedback to 7 people, doing bug bashing for 2 weeks, fixing other stuff, questioning product designs etc..

I guess this is what happens the more experienced you get. You see more stuff. Otherwise I start enjoying working from home. It's stressful (the whole covid-19 situation) but I feel better. Not commuting means less time wasted in busses, trains. Less exposure to sickness.

Take care!

Cheers,

Ferit

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 Apr 24 by:

fokusman profile

Ferit ๐ŸŒŸ๐Ÿ•Œ

@fokusman

Senior Software Dev from Berlin. Working at ZalandoTech.

Discussion

markdown guide