Live data from Hacker News

Don't Feed the Thought Leaders

earthly.dev

181–190 of 289 posts

Re: Don't Feed the Thought Leaders

#181

Earlier quoted context omitted.

I did notice the irony myself :) The article talks about contingent advice being better than universal advice only in stage 3. If you're not then universal advice is helpful. I think that holds true for most people and most subjects, including myself. Originally, I thought the article did a great job describing a common scenario that occurs usually in decision making and I wanted to describe my intuition on why I thi…

That makes sense! I just realised my reply may have come across as mean-spirited rather than the light joke I intended. Sorry about that.

no worries! It is rather ironic.

Re: Don't Feed the Thought Leaders

#182

This is a bang on article and I would say that more people should be less confident in general. I also love his technology substitutions: springy search = Elastic Stoplang = Go IronOre = Rust BeetleDB = CockroachDB

Great technologies, but not very well known. I highly recommend Casey Muratori's videos if you want to learn more. (Big Zinc Oxide advocate.) https://www.youtube.com/watch?v=1HAXgM3mjSo

Yes, I got turned on to IronOre and StopLang from Casey in exactly this video. Great tech!

Re: Don't Feed the Thought Leaders

#183
post #67

Earlier quoted context omitted.

Sometimes, the features are really must-haves though. Let’s say it’s march 2020 and your boss wants you to design a mass-market covid vaccine. You have three requirements: it needs to be safe for human use, it needs to be effective at preventing covid, and it needs to be possible to manufacture. If any one of these is missing, your design is useless. I think a similar dynamic is visible in many software projects.

A manager once brought up "there are three levers - scope, time (deadline), money (people)", and while it's probably not revolutionary, it did stick with me. Add more "must have" scope, and something else has to give.

I would argue that the scope lever should be set to 60%, time 60%, and money 35% for software projects.

Software projects are kind of like ovens-- if something cooks perfectly at 300 (temperature units), using 25 minutes and using 5 (money units), that does not mean it will cook perfectly at 600 temperature units using 12.5 minutes and 10 money units. Most likely it will burn.

Re: Don't Feed the Thought Leaders

#184

Earlier quoted context omitted.

The minor conclusion of this article was the more interesting (and perhaps more practical) of the two: Hide concessions to various leaders in the project roadmap. This isn’t just a “bureaucratic trick” as the OP suggested, it’s actually a way to convert unconditional advice into contingent advice, by encoding a priority.

> Create an extended product roadmap and put those items at least a year off into the future “and as long as they don’t seem relevant, you can just keep pushing them into the future.” That actually seems to me like the root cause of all the calamity in the article, a culture of lying.

This is absolutely not lying and I'm disappointed that anyone thinks it is. This isn't "not doing the thing and saying you did", it's just setting its delivery date into the future, an entirely routine operation for every software project that actually ships.

Re: Don't Feed the Thought Leaders

#185
post #20

Found this to be a straightforward and interesting article. Not sure I've ever seen someone connect Tetlock's research to engineering planning before; I certainly hadn't made the connection myself. I also appreciated the tip that instead of saying no to something, you can just add it to a "future work" section of lower-priority but definitely-still-very-important-i-promise-really-i-mean-it tasks and everyone will end…

From How to Talk So Kids Will Listen & Listen So Kids Will Talk (1980): > My husband and I took Jason and his older sister, Leslie, to the Museum of Natural History. We really enjoyed it, and the kids were just great. Only on the way out we had to pass a gift shop. Jason, our four-year-old, went wild over the souvenirs. Most of the stuff was overpriced, but we finally bought him a little set of rocks. Then he started…

I do this to myself. Every time I want to buy something I stick it on my Amazon wish list. Then I forget about it. I almost never actually buy things on the wish list.

Re: Don't Feed the Thought Leaders

#186

Being a hedgehog is useful on the journey to domain mastery because sticking to frameworks saves you time and headache compared to not having any frameworks at all. The 3 stages of domain mastery: Stage 1 - No knowledge or structure to approach a domain (everything is hard, pitfalls are everywhere) Stage 2 - Frameworks that are useful to approach the domain (Map to avoid pitfall areas) Stage 3 - Detailed understandin…

I think this progression could make sense as a personal learning progression. The real world is probably more complex than this though.

See for example https://news.ycombinator.com/item?id=27468360 where the person mentions pressure to simplify advice and Tetlocks own work shows that the hedgehogs were the more famous and successful people. So some people may migrate backwards by simplifying a message for maximum impact.

Re: Don't Feed the Thought Leaders

#187
post #31

It's cathartic to read other people who have to go through this. I'm fighting red tape for my team as we build out a dashboard. Outlook is packed with 1–2 hour meetings for the next 3 months where so far I'm: * being asked to load test our system to make sure it can handle the load (of 3 people?) * being asked to integrate with various analytics platforms so we can alert some poor schmuck at 3 AM in case the API goes…

being asked to load test our system to make sure it can handle the load (of 3 people?) The problematic load in a dashboard isn't users; it's querying the data sources to get up to date information. For example, if you're running a query to aggregate a bunch of things with lots of joins and that query takes 1.5s to run but your dashboard tries to run it every second so it can be 'real time' then you're in for a bad ti…

I've downvoted your answer here as I think it is a ungenerous interpretation of the post you replied to.

It's just as likely that OP did already know that what you are insisting on is not relevant to their use case. That might be why they stated it.

Re: Don't Feed the Thought Leaders

#188
post #162

Interesting topic but terrible written article. Article is impossible to understand without knowing some TV series and cartoons(!), and some pop culture trivia from US :/ It could be done right with some kind of explanation of trivia...

I've never watched either of the two shows mentioned and I understood the article just fine. I'm not American either. The cartoon trivia is explained in the same single paragraph it's mentioned in, and the office trivia is explained in the single sentence that mentions it.

Re: Don't Feed the Thought Leaders

#189
post #117

Earlier quoted context omitted.

I’ll add to the list: - Ceremonial unit tests for every little thing. The whole system is buggy as hell and we don’t have any confidence that the unit tests are truly covering critical parts of the app. But alas, test coverage, the god damn Pope that can never be bemoaned. - I’m not making this one up: A/B testing for an internal enterprise app.

Test coverage is almost the perfect illustration of Goodhart’s law. Good programming practices do result in high test coverage, coverage is very easy to measure, but very easy to fake with useless “tests”. So, when the coverage is measured, the coverage goes up, but stops being meaningful.

> but very easy to fake with useless “tests”

While it doesn't alleviate the problems entirely, you can also run things like mutation tests that check that your unit tests actually test conditions, rather than just execute all the code.

Re: Don't Feed the Thought Leaders

#190
post #20

Earlier quoted context omitted.

From How to Talk So Kids Will Listen & Listen So Kids Will Talk (1980): > My husband and I took Jason and his older sister, Leslie, to the Museum of Natural History. We really enjoyed it, and the kids were just great. Only on the way out we had to pass a gift shop. Jason, our four-year-old, went wild over the souvenirs. Most of the stuff was overpriced, but we finally bought him a little set of rocks. Then he started…

I do this to myself. Every time I want to buy something I stick it on my Amazon wish list. Then I forget about it. I almost never actually buy things on the wish list.

I have now added this book to my Amazon wish list.
Post reply on HN