3 ms·

Best: Github, MDN, Rust standard lib docs, Stripe. Worst: anything MS (excl. Github obv).

by oxff 4y ago

thebradbain 4y ago
C# has some of the best first-party documentation of any language I've worked with
- skribanto 4y ago
  subjective: I thought even Java had better docs than C#
shreythecray 4y ago
MS docs definitely make me want to cry sometimes
spacechild1 4y ago
What do you dislike about NS documentation? I always found it very thorough and useful. Definitely much better than Apple.
- mdtusz 4y ago
  I've found Microsoft documentation (Azure services specifically) to be a weird mix of marketing and semi-technical walkthroughs that seem targeted to point-and-click users following their happy path. As soon as you get to the technical reference (if you can find it) it seems to all be auto-generated and fairly poor quality, or handwritten and either out of date or just not very clear. The more "core" Azure services are a bit better, but it seems to always be a struggle and searching for answers is always difficult because you have to scroll through a full page or more of Microsoft marketing pages before you reach either Reddit or stack exchange results with the answers you're looking for. Weird example: recently I discovered Azure redis instances will drop idle connections after 10 minutes, but the network connection still stays open and your commands/queries will fail.
  - spacechild1 4y ago
    I guess we just had completely different things in mind. I often need to consult the Win32 docs and I always found them very clear and extensive. Here's a random example: https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createthread https://docs.microsoft.com/en-us/windows/win32/api/processth...
- DimmieMan 4y ago
  I think worst is an injury inducing stretch, but I'm not a fan of them personally. This seems to be a problem with modern docs but I find they're overly verbose and the focus is hello world tutorials to show off shiny things & advertise Azure, the quality tends to drop off from there. I think good documentation is something I want to have open on the side to answer questions like: * What module did I need again? * How do I do X? * Does this tool let me do X? I'm going to go straight to tailwind, MDN, GitHub etc. MS documentation I'm going to google first because I ain't got time to read through a half dozen long form articles that might give me an answer. ASP.net? probably, Azure anything? I'll leave more confused and thinking about AWS...

Best: Github, MDN, Rust standard lib docs, Stripe. Worst: anything MS (excl. Github obv).

by oxff 4y ago

Best: Github, MDN, Rust standard lib docs, Stripe. Worst: anything MS (excl. Github obv).

thebradbain 4y ago

C# has some of the best first-party documentation of any language I've worked with

skribanto 4y ago
subjective: I thought even Java had better docs than C#

shreythecray 4y ago

MS docs definitely make me want to cry sometimes

spacechild1 4y ago

What do you dislike about NS documentation? I always found it very thorough and useful. Definitely much better than Apple.

mdtusz 4y ago
I've found Microsoft documentation (Azure services specifically) to be a weird mix of marketing and semi-technical walkthroughs that seem targeted to point-and-click users following their happy path. As soon as you get to the technical reference (if you can find it) it seems to all be auto-generated and fairly poor quality, or handwritten and either out of date or just not very clear. The more "core" Azure services are a bit better, but it seems to always be a struggle and searching for answers is always difficult because you have to scroll through a full page or more of Microsoft marketing pages before you reach either Reddit or stack exchange results with the answers you're looking for. Weird example: recently I discovered Azure redis instances will drop idle connections after 10 minutes, but the network connection still stays open and your commands/queries will fail.
- spacechild1 4y ago
  I guess we just had completely different things in mind. I often need to consult the Win32 docs and I always found them very clear and extensive. Here's a random example: https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createthread https://docs.microsoft.com/en-us/windows/win32/api/processth...
DimmieMan 4y ago
I think worst is an injury inducing stretch, but I'm not a fan of them personally. This seems to be a problem with modern docs but I find they're overly verbose and the focus is hello world tutorials to show off shiny things & advertise Azure, the quality tends to drop off from there. I think good documentation is something I want to have open on the side to answer questions like: * What module did I need again? * How do I do X? * Does this tool let me do X? I'm going to go straight to tailwind, MDN, GitHub etc. MS documentation I'm going to google first because I ain't got time to read through a half dozen long form articles that might give me an answer. ASP.net? probably, Azure anything? I'll leave more confused and thinking about AWS...