News for hackers. Stuff that matters.
Re:How to Be a Programmer: A Short, Comprehensive, and Perso... by porphyrogene on Saturday December 22, 2018 @04:48PM (#18742638)
I read through some of the Beginner section that I thought seemed inappropriate for beginners and found a number of grammar and punctuation errors. While trying to navigate the file I found that the page numbering shown in the Table of Contents is off by two pages. His advice on "difficult people" sounds like he is talking about a single, specific person but is doing so in a vague way and expects that to function as actionable advice. That seems like a common pattern as I look back on the rest of the section. He talks about what were probably specific events or situations in a very non-specific way and by doing so falls short of providing useful insight. It would be more effective to write about the details than to try to adapt the story to a common experience.
Re:How to Be a Programmer: A Short, Comprehensive, and Perso... by blakejustblake on Saturday December 22, 2018 @09:38PM (#18744059)
Ha, so it's a pretty good example of how to be a programmer then huh?
Re:How to Be a Programmer: A Short, Comprehensive, and Perso... by walshemj on Saturday December 22, 2018 @06:51PM (#18743253)
And your point is?
Re:How to Be a Programmer: A Short, Comprehensive, and Perso... by jimmaswell on Saturday December 22, 2018 @07:02PM (#18743310)
What is yours? The point of the comment you're replying to is obvious. They provided some specific criticism of the material.
Re:How to Be a Programmer: A Short, Comprehensive, and Perso... by walshemj on Saturday December 22, 2018 @08:59PM (#18743896)
I was using a rhetorical device - all I saw was an anonymous complaint about grammar and no real substantive critique with know examples?