11–20 of 61 posts
What I mean is, there are lots of people who are not as smart as they think they are, and they won't STFU and RTFM, etc...
Send not to know at whom the Torvalds curses, he curses at thee.
Frankly, I think the author's original position was correct: Emphasize credit for authors of RFCs and you'll get fools authoring RFCs for the credit. Sheesh!
One huge problem is that September never ended... ( https://en.wikipedia.org/wiki/Eternal_September ) What I mean is, there are lots of people who are not as smart as they think they are, and they won't STFU and RTFM, etc... Send not to know at whom the Torvalds curses, he curses at thee. Frankly, I think the author's original position was correct: Emphasize credit for authors of RFCs and you'll get fools authoring R…
(There's only one accepted Rust RFC whose author I can name from memory, and that's only because it's an RFC that I didn't like. :P The knife cuts both ways!)
Small sans-serif body text means you hate your readers. Making it grey means you really hate them.
> But before you fly off the chain, prove your undeniable superiority, and prove that they are wrong, let me suggest instead that you do something crazy, that you do the opposite: that you prove they are right. I'm a bit uneasy about this. If you spend your time agreeing with a suggestion that your initial reaction is to reject, you probably won't have the patience to go back and question it after the fact. You'll al…
I think you have to differentiate between thinking and communicating. Thinking comes first, unhindered by concerns for social niceties and hurt feelings.
Then, you communicate by expressing what you've concluded in a way that does account for the fact that you're conveying a message to a human being, with all the baggage that entails.
Small sans-serif body text means you hate your readers. Making it grey means you really hate them.
One thing I wish GitHub made easier is responding to a pull request with a patch rather than encouraging reviewers to type up a bunch of suggestions that the original submitter will have to turn into a patch themselves. If you have a better idea how to accomplish part of a suggested change, you can communicate that more clearly by making a patch and leaving a comment explaining why. GitHub should encourage this and a…
> But before you fly off the chain, prove your undeniable superiority, and prove that they are wrong, let me suggest instead that you do something crazy, that you do the opposite: that you prove they are right. I'm a bit uneasy about this. If you spend your time agreeing with a suggestion that your initial reaction is to reject, you probably won't have the patience to go back and question it after the fact. You'll al…
One thing I wish GitHub made easier is responding to a pull request with a patch rather than encouraging reviewers to type up a bunch of suggestions that the original submitter will have to turn into a patch themselves. If you have a better idea how to accomplish part of a suggested change, you can communicate that more clearly by making a patch and leaving a comment explaining why. GitHub should encourage this and a…
Even if you added tons of tests, you'll get add more tests. It almost makes more sense to write tests and hold them, so you can respond with them.
One thing I wish GitHub made easier is responding to a pull request with a patch rather than encouraging reviewers to type up a bunch of suggestions that the original submitter will have to turn into a patch themselves. If you have a better idea how to accomplish part of a suggested change, you can communicate that more clearly by making a patch and leaving a comment explaining why. GitHub should encourage this and a…
The worst maintainers are the ones who refuse to say no when they mean no or want to say no. I've seen maintainers waste weeks or months of a contributors time on work that they never intend to accept because they're trying to avoid confrontation up front.
To use an example of a project I've contributed to, Dungeon Crawl Stone Soup has an explicit wiki page for "patches that we will not accept, so don't even bother asking": https://crawl.develz.org/wiki/doku.php?id=dcss:planning:wont...