I definitely remember thinking “this part seems too brief”, but I don’t remember where.
Probably Chapter 8, which is just a sketch, and of course Chapter 14, where I’m supposed to wrap it all up. My current dilemma is whether to leave the overall structure alone or basically write another half of the book, where I share my tips for reading papers in software engineering critically: how to parse a research paper’s structure, how to read a graph, how to assess an experimental setup, how to use Google Scholar, how do do basic bibliometrics… The idea would be to intersperse these chapters with the ones exposing the flaws in the literature.
I have no way of knowing who’s coming from LW, but since the grandparent comment was published three copies were sold netting me a tad under $25 in royalties.
I bought this, and I endorse it. It could be expanded in some places*, but it’s a great start.
*I should have taken notes while reading. I definitely remember thinking “this part seems too brief”, but I don’t remember where.
Thanks!
Probably Chapter 8, which is just a sketch, and of course Chapter 14, where I’m supposed to wrap it all up. My current dilemma is whether to leave the overall structure alone or basically write another half of the book, where I share my tips for reading papers in software engineering critically: how to parse a research paper’s structure, how to read a graph, how to assess an experimental setup, how to use Google Scholar, how do do basic bibliometrics… The idea would be to intersperse these chapters with the ones exposing the flaws in the literature.
I have no way of knowing who’s coming from LW, but since the grandparent comment was published three copies were sold netting me a tad under $25 in royalties.