My explanation: Most developers just don't want to write specifications. They don't consider it to be their job. Similar like they also shy at writing documentation or even comments. Developers are lazy in this aspect.
Developers just want to code, fix bugs, create a nice UI, apply logical thinking, etc... They are used to _read_ specifications and implement requirements, which usually come from *other* non-developers, e.g. "product owners, product managers", but not to _write_ them by themselves. Also nicely illustrated here: http://www.codefieber.de/images/geek_and_poke_coders-love-t.jpeg http://geek-and-poke.com/geekandpoke/2012/2/5/simply-explained.html >> I have some ideas why they don't do this. > Could you share them? >> I know a lot of developers >> from different projects who is unwilling to write XEPs. So my answer is >> "I don't know". > If no-one is prepared to say why they won't do this but continues to complain > about the absence of XEPs then the assumption has to be that they are > trolling.
