_ketanbhatt

Happy user here! There is so much clutter on Twitter these days, sometimes opinions are fine and I want them, but sometimes I just want to get some useful links from my feed and see if I want to read something.

Thank you! It is a steal at this price, I will definitely pay more for this.

1. I do think that the kind of people we have on our team will almost always have some ideas to fix things.

2. The break-down and simplifying happens, of course. But the dev leads the breaking down, with careful guidance by the lead. And it is being solved together, don't you think? The example didn't describe the full end to end design process, but just a part of it which was relevant to explain the point. I think I could have made it more clearer. Thank you for the feedback, noted :)

Makes sense. 1. The manager (me) was awful at all the three things mentioned in varying degree, and what is written is what I learnt from my experience.

2. Yes, could have mentioned the measuring part. Thank you for the feedback

3. The tips weren't supposed to be connected. They are just a collection of unconnected learnings.

4. Well there are different kinds of teams, and each one needs looking after differently. In our case, these teams are very small, and in some of them I was the only dev (not counting the Machine Learning Engineers). So for some teams day-to-day monitoring makes sense, while for some it won't.

5. What you described as your job is more or less what I do as well, I think it didn't come out like that in the article maybe? Except that it is not "every few weeks" in my case, but twice-thrice every week.

Feedback noted :)