So if that’s actually just a guess, I’m impressed, and you must have some experience in thin-film lol.
LCD panels actually use a thin film of silicon (I think it’s silicon) over each pixel. And cheap panels using TN technology often have this issue and very poor viewing angles.
It is hard, I agree. I’m not very good at it myself. But even semi-decent docs are better than googling around or stepping through a decompiled package.
And it’s super useful to new developers, and would have saved me a lot of time and frustration when I was new.
That’s fair. At my company we have technical writers for the external docs and internal docs are usually written by whoever has worked on something and got frustrated that nobody in the company could give them a high level overview, and they had to go through the code for a couple hours.
Tbf though, I’ll take docs that aren’t written super well that tell me how things from our internal libraries should be used. Or just comments. I’ll take comments telling me WHY we are doing something.
I don’t expect our internal docs to be MSDN docs. But I like to read an overview of at least the workflow before I jump into updating a large project.
I’d rather read the docs than just about anything. I love good documentation. I wanna know how and why things work.
The problem is that basically nobody has good docs. They are almost all either incomplete or unreadable.
Jon Skeet? He’s my hero, but he hasn’t worked at MS for quite some time I believe.