> So to clarify–your understanding of the article is that, it says that a product engineer should be working at an expert level (or at least same level as full-timers of those roles) in about 10 different roles in addition to developer? And they should be doing this during 8 hours of every single day, context switching between different roles in small time slices?
Yes, in my work experience, the dynamics of development had us discussing the tasks that we work on... daily, weekly or monthly.
One of my realizations when switching from product development to some of the other roles mentioned in this post is just how much time they actually take... all the discussions, the what ifs, the stakeholder back and forth.
Yes, I do believe that the article mentions characteristics that should be applied in the work context, which is 8hrs per day in hopefully an expert way.
> If the above is your understanding of the article, then I'm sorry to say, you seriously need to work on your basic reading comprehension skills.
Perhaps...
> And if you actually understood the real point of the article, that all of the described activities happen spread out over longer periods of time, as the engineers build up a momentum of total product/business knowledge/expertise/rapport with other stakeholders in the org, by actually being curious, asking questions, and offering measured feedback;
I believe I argument my understanding as I read the article in the post you replies to.
> if you really understood this, then seriously, I have to question why even bother to reply and waste everyone's time? Totally pointless.
I was hoping I got my point across. Maybe it made sense to some people, but just because I am dumb and lack reading comprehension means I can’t post here? Am I responsible for your time wasting decision?