{"action":"opened","issue":{"url":"https://api.github.com/repos/ds4se/chapters/issues/121","labels_url":"https://api.github.com/repos/ds4se/chapters/issues/121/labels{/name}","comments_url":"https://api.github.com/repos/ds4se/chapters/issues/121/comments","events_url":"https://api.github.com/repos/ds4se/chapters/issues/121/events","html_url":"https://github.com/ds4se/chapters/issues/121","id":122982185,"number":121,"title":"Review of \"Inductive Software Engineering: What we do IS Different\"","user":{"login":"andreas-zeller","id":8246142,"avatar_url":"https://avatars.githubusercontent.com/u/8246142?v=3","gravatar_id":"","url":"https://api.github.com/users/andreas-zeller","html_url":"https://github.com/andreas-zeller","followers_url":"https://api.github.com/users/andreas-zeller/followers","following_url":"https://api.github.com/users/andreas-zeller/following{/other_user}","gists_url":"https://api.github.com/users/andreas-zeller/gists{/gist_id}","starred_url":"https://api.github.com/users/andreas-zeller/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andreas-zeller/subscriptions","organizations_url":"https://api.github.com/users/andreas-zeller/orgs","repos_url":"https://api.github.com/users/andreas-zeller/repos","events_url":"https://api.github.com/users/andreas-zeller/events{/privacy}","received_events_url":"https://api.github.com/users/andreas-zeller/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-18T16:37:49Z","updated_at":"2015-12-18T16:37:49Z","closed_at":null,"body":"## Title of chapter\r\n\r\n_ Inductive Software Engineering: What we do IS Different_\r\n\r\n## URL to the chapter\r\n\r\n_https://github.com/ds4se/chapters/blob/master/menzies/inductiveManifesto.md_\r\n\r\n## Message?\r\n\r\nWhat is the chapter's  clear and approachable take away message?\r\n\r\n_Read the indicative software engineering manifesto (or don't, now that you have the summary)_\r\n\r\n## Accessible?\r\n\r\nIs the chapters written for a generalist audience (no excessive use of technical terminology) with a minimum of diagrams and references?\r\nHow can it be made more accessible to generalist?\r\n\r\n_The summary of the inductive SE manifesto is great.  I won't comment on the manifesto itself, because if you change things, it wouldn't be a summary anymore, but as a summary, it works well._\r\n\r\n## Size?\r\n\r\nIs the chapter the right length?\r\nShould anything missing be added?\r\nCan anything superfluous be removed (e.g. by deleting some section that does not work so well or  by using less jargon, less formulae, lees diagrams, less references).?\r\nWhat are the aspects of the chapter that authors  SHOULD  change?\r\n\r\n_I was not too happy with the introduction -- it starts with name-dropping, which gives it an insider-only flavor.  I would prefer a motivation stating why a term like \"inductive SE\" would be needed, or how it would delineate itself from, say, empirical SE.  Also, it wouldn't hurt to define the term \"induction\" before using it -- yes, I know what induction means in this context, but again, there's a lost chance to delineate the inductive approach to SE from, say, the deductive approach.  In that sense, the chapter does not really deliver (yet) on the promise given in the title, but could easily do so by positioning \"inductive SE\" clearly with respect to alternatives._\r\n\r\n## Gotta Mantra?\r\n\r\nWe encouraged (but did not require) the chapter title to be a mantra or something cute/catchy, i.e., some slogan reflecting best practice for data science for SE?  If you have suggestion for a better title, please put them here.\r\n\r\n_Inductive SE is way cool._\r\n\r\n## Best Points\r\n\r\nWhat are the best points of the chapter that the authors should NOT change?\r\n\r\n_All from \"Principle #1\"._"}}