3 ms·
constructive resolution tip: next time omit the info on the resolution
by twoslide 8y ago
constructive resolution tip: next time omit the info on the resolution
- kdeenanauth 8y agoconstructive resolution tip tip: next time avoid criticizing the meta
- keithwhor 8y ago:). The very first thing I ever put on HN in Ruby got blasted — hard — for not having tests. I never released OSS without tests again. It’s hard to discern rigorous criticism from kneejerk reactionary responses. I’m hopeful that the narrative is helpful in showing I’m appreciative and impressed by the effort, but have real concerns about the project and implementation itself. It’s not bad. It’s difficult to understand. Which is a classification of software we’re all likely to create at some point, and we can all help each other be better at writing about what we create as well as building the right tools and abstractions.