Why I wrote a damning review of my own debut novel

Re:Why I wrote a damning review of my own debut novel by failrate on Saturday October 01, 2016 @04:36PM (#12619766)

I am tempted to try this on some unfinished projects to try to suss out their flaws that I only subconsciously am aware of.

[ Parent | on HN ]

Re:Why I wrote a damning review of my own debut novel by an_ko on Saturday October 01, 2016 @11:12PM (#12620893)

In a similar vein, I start projects by writing a README. It forces me to see with the user's eyes, which makes the difference obvious between what I think is a good interface and what is actually a good interface. It has worked well. I recommend it!

[ Parent | on HN ]

Re:Why I wrote a damning review of my own debut novel by johncoltrane on Sunday October 02, 2016 @05:03AM (#12621575)

There's a big flaw in your method: users never read the README.

[ Parent | on HN ]

Re:Why I wrote a damning review of my own debut novel by douche on Sunday October 02, 2016 @06:55AM (#12621799)

Github displaying readme.md by default has probably boosted viewings of readmes by a million percent.

Whether reading of readmes has gone up is still an unsettled question

[ Parent | on HN ]

Re:Why I wrote a damning review of my own debut novel by iamcreasy on Sunday October 09, 2016 @09:14PM (#12674484)

what does .md stand for?

[ Parent | on HN ]

Re:Why I wrote a damning review of my own debut novel by rexf on Saturday October 15, 2016 @05:40AM (#12713398)

markdown

[ Parent | on HN ]

Re:Why I wrote a damning review of my own debut novel by cJ0th on Sunday October 02, 2016 @08:35AM (#12622071)

I always at least scroll through it and enjoy it when someone took the time to write a great one.

[ Parent | on HN ]