I think it's up to the more senior devs to make sure the correct dev process is being followed because it helps reduce work later. Managers often don't understand those types of things, so you need to earn their trust first.
Maybe put a dollar sign on the cost of not doing it. For this case, it's actually costly. A miscommunication in a language spec can incur big rework. Not just on Micro$oft side. But on client side. Regular users or tool developers. I mean... this is a major release of the language..
Say 30 Million dollars (my wild guess), provide a breakdown of it in bullet points.
Maybe also argue that a language should have a spec, not having it would reflect badly on Micro$0ft's image; and the marketing damage (then bring in the marketing lead to explain).
4
u/13steinj Jul 30 '18
Except many won't risk getting reprimanded/fired.
I'm not saying this is a good thing. Just that it unfortunately happens quite a lot.