“Hello! I am a developer. Here is my relevant experience: I code in Hoobijag and sometimes jabbernocks and of course ABCDE++++ (but never ABCDE+/^+ are you kidding? ha!) and I like working with Shoobababoo and occasionally kleptomitrons. I’ve gotten to work for Company1 doing Shoobaboo-ing code things and that’s what led me to the Snarfus. So, let’s dive in!
If it’s an instruction to a dishwasher liquid, you better write it for first-graders.
Sure, if you write a documentation to some developer tools, use developer language.
But if it’s something you expect regular folk to use, think of how much more people could use it if they wouldn’t need to learn something entirely out of their field of expertise to use it.
You can make dishwashing liquid kit that would require extensive knowledge in organic chemistry to use. It would be cheap and darn simple to develop. You could release it today! You just…shouldn’t.
Remember people have their lives, and shouldn’t be forced to comprehend everything around them at a professional level. Many developers seem to forget about it A LOT somehow, shifting it to the user and saying “I’m done here”, sitting in the bubble of experts and treating users like stupid rats who can’t simply get a computer science degree to use their computer. As a food technologist, I recently developed a premix for home-baking of phenylalanine-free pastry, and 70% of the work was making it idiot-proof. It is true for any field, yet it is important. People can’t learn everything every time they need something, and it’s not their fault.
Microsoft uses Microsoft language, and the only people who understand it are people who have been Microsoft programmers for a long time.
Yep, the Microsoft ecosystem is completely unwelcome to newbies. It’s by experts for experts, and everyone else can go to hell