3 ms·
I don't know. It's great that you wrote it and I can completely understand what sort of undertaking it was, but the problem with any mentoring book is that it s
by huhtenberg 13y ago
I don't know. It's great that you wrote it and I can completely understand what sort of undertaking it was, but the problem with any mentoring book is that it should come from a recognized and credible source. If this were an auto-biography book, written from the "what worked for me" angle, it would certainly have an audience. But if it just dispenses advice, then it begs the question what makes you think you are in a position to do that.
I am also not sure who it is written for - pretty much every developer above summer intern thinks of himself as a senior :) Over-inflated self-assessment is a norm.
- lucisferre 13y agoOr a few people could read it, review it favourably and it could become recognized as a credible source. I'd suggest either reading it, or letting others read and comment on it. Don't judge a book by it's cover as they say. I would suggest though that the author should have solicited a few reviews before posting about it here.
- kranner 13y agoPerhaps soliciting initial reviews was exactly the point of posting here?
- lucisferre 13y agoI wasn't going to assume that, not sure if anyone else will either. Unless it was mentioned somewhere I missed.
- tcopeland 13y ago[disclaimer: I helped proofread the book] FWIW, I worked with Dave at LivingSocial and took over a bunch of code that he wrote. Whatever a senior developer is, DaveC is that. He wrote great code, was excellent in terms of executing on tasks, made major contributions to tons of projects, was helpful, cheerful, all that good stuff.
- dpritchett 13y agoThis blurb needs to be on the landing page!
- ternaryoperator 13y agoReally? Nothing in that blurb tells me that he's exceptional. Just a nice guy who writes good code.