http://blog.ploeh.dk/2015/01/15/10-tips-for-better-pull-requests/
https://blog.jessfraz.com/post/the-art-of-closing/
> I’ve talked to maintainers from several different open source projects, mesos, kubernetes, chromium, and they all agree one of the hardest parts of being a maintainer is saying “No” to patches you don’t want.
http://ostatic.com/blog/more-bad-english-please
> And it’d be a shame if non-native speakers let fear or embarrassment hold them back from making a vital contribution or asking a question that could help them succeed in contributing or using FLOSS tools.
Coding is NOT the same thing as programming. Programming is problem-solving.
People often mistake coding for programming. They think that if they learn a programming language (such as JavaScript, Python or Ruby), they’ve learned how to program. That’s nonsense, of course. Learning a programming language without understanding how to solve a programming problem is pretty much worthless. It’s like learning Mandarin and not knowing how to express your thoughts effectively or eloquently.
Make no mistake: problem-solving is difficult. Coding is relatively easy.
Really nice (comment about an) article that warns new developers about the long path they need to walk to be Programmers and not just Coders
https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet
How to Crash Systemd in One Tweet
Interesting article (almost a rant) about how security, code quality, code design and readability should matter a lot in software development, even more than actual features