4 ms·
Similar experience here. We interviewed a guy who kept referring to his book on the subject, experience he gained during writing the book, and so on. We took th
by PragmaticPulp 6y ago
Similar experience here. We interviewed a guy who kept referring to his book on the subject, experience he gained during writing the book, and so on. We took the bait.
> He would tell people they couldn't do things they'd already done and then back-peddle that it wasn't possible when he'd written his book
This was the core problem: Modern technologies and frameworks move fast. His book was about the state of the art five years ago, but it was woefully out of date for what we were doing. That didn't stop him from trying to exert superiority over the more knowledgeable team members.
Some of us read his book. It wasn't even a great resource on the topic. Re-reading the Amazon reviews, I have to believe most of the positive reviews were bought or fabricated.
Since then, I'm cautious about hiring anyone who tries to portray themselves as an expert in the field. And if you're hiring an author, at least read part of their book during the interview phase.
- andrewem 6y agoA former co-worker of mine recounted an experience with a person hired by his previous company who had written a book on software development methodology, Scrum or something. Evidently the way the author's employment worked is the company got the reputation benefit from having a famous expert on staff. In exchange he gave talks but didn't have to do any actual work for the company, and the company didn't have to follow his methodological orthodoxies.
- pc86 6y agoAnd that's how you end up with speakers saying ridiculous things that don't work in practice. Because they come up with some idea (or more likely, a very minor tweak to an existing idea) but because nobody has to actually do it, and all their time is spent speaking, nobody uncovers the critical flaws.