4 ms·
Oh, the other way that things have gotten more difficult is that documentation now seems to lack the depth it once had. For example, I tend to use Xcode for dev
by thewebcount 4y ago
Oh, the other way that things have gotten more difficult is that documentation now seems to lack the depth it once had. For example, I tend to use Xcode for development. There are all sorts of functions within the app that I know about but can’t comprehend (like the memory graph), and the docs are barely more than a screen shot labeling everything and giving a 2 sentence description of it at the most basic level. Like on the memory graph, what do the different symbols tell me? Why are some blocks of memory represented by a square, and some by … what is that? A pyramid? What’s the significance? How does that help me in tracking down my memory bug?
- pevey 4y agoI second this about the declining quality of docs. Part of the proliferation of different solutions to the same problem IMO is that existing solutions might have such poor documentation that it may seem easier to seriously reinvent the wheel. I can vividly remember when php3 came out because I happened to be working on a project right then. This was before you could carry around iPhones and iPads, so I printed the whole manual and put it in a 4-inch binder so I could read it on the train, etc. I can still see those pages. I was new to programming in general at the time, but I could learn anything I wanted to do with php using those docs. Every single function was thoroughly explained. Haven’t seen anything like it in a very long time. The Prisma docs comes closest.