One of the saddest parts of an #opensource maintainer's life is having to reject PRs, sometimes thousands of lines long, for no better reason than "this is not the project's direction right now and it will interfere with what we're working on".

I don't know where the "write code first ask questions later" approach came from, but I really wish we'd communicate with each other more. The fallout of not doing so isn't fun for anyone. 

 @8b926eed

Agreed. Always open an issue or discussion before you write a large PR.

Although that does create a different risk: what if I open such a discussion, the project lead thinks it's a great idea, and only when I start working on it do I realize it's going to be far more effort than I'm willing to put in? Now I've made a promise I really don't want to keep.