Can't +1 this enough. Stated another way, I always think back to this slide [1] from one of Holman's old decks ("Drive-by opinions are less valuable"). For wha

Can't +1 this enough. Stated another way, I always think back to this slide [1] from one of Holman's old decks ("Drive-by opinions are less valuable"). For whatever reason, this is a very common phenomena in tech, and there's a positive reason explanation for it and a negative one. The positive one is that people really are engaged and enthusiastic and want to help make the product better. That's great, and far better than the alternative. The negative one is the same as the classic mid-level manager who arranges an unnecessary meeting with shaky pretext that everyone knows is just so that they can have their ideas heard for 60 minutes. It makes them look engaged and increases their visibility in the corporate hierarchy. Now, while that was a literal meeting back in the 90s, but 2020s version of it is littering smart-sounding comments all over as many key Google Docs as you can, all of which have your picture next to them, and which you know others will see. Too many ideas aren't necessarily a problem, but it can add a lot of overhead to a project, and the end result is often only incrementally better. I've worked on smaller projects where it took us 2x to 3x longer to ship by addressing tiny feedback from a large number of people, and the final product was like 5% better. That't not to say that no feedback is valuable, as a lot of it clearly was, but there's a happy compromise somewhere between taking too little and taking too much. In the end, the article author's advice rings very true: > “So, what are we going to do about it?” (With the emphasis on "we".) Give ideas/feedback, but make sure you're willing to engage with the work. --- [1] https://speakerdeck.com/holman/how-github-no-longer-works?slide=97 https://speakerdeck.com/holman/how-github-no-longer-works?sl...