Re:Things Every Programmer Should Know [wiki]
by grumpyfart on Monday February 22, 2010 @02:44AM
(#1142200)
- It's writing style is bad, somehow consistently bad
- Structure is no good (I think this is expected though) but I was looking for an overall consistency like in Founders at work.
- Most of the advices written in many words but can be summed to 2 sentences. And rest of the text doesn't elaborate the reasons like they supposed to mostly they are there to fill up space.
Overall I don't have one bad thing but it's like reading a bad novel, you don't feel like that the author or the book has a soul.
Again Founders at Work is a perfect example of having multiple people to contribute but keeping the book in a good writing format.
- Structure is no good (I think this is expected though) but I was looking for an overall consistency like in Founders at work.
- Most of the advices written in many words but can be summed to 2 sentences. And rest of the text doesn't elaborate the reasons like they supposed to mostly they are there to fill up space.
Overall I don't have one bad thing but it's like reading a bad novel, you don't feel like that the author or the book has a soul.
Again Founders at Work is a perfect example of having multiple people to contribute but keeping the book in a good writing format.