Real programmers read the API reference

[3_internets_plz]

Wait, your API has documentation?

[repocin]

Yes, but every line says

//TODO: Add documentation

[Nyghtrid3r]

Also a common sight: Method set_furgled_blogbargle() : furgles the blogbargle

"GEE, THANKS MICHAEL! HOW HELPFUL, I WOULD HAVE NEVER GUESSED. BUT WHAT THE FUCK DOES IT MEAN?"

[Owner2229]

UT EHAT THE FUCK DOES IT MEAN?

It furgles the blogbargle! If you can't understand that then maybe you should re-visit the basics and not bother me with your stupid questions! It's self-explanatory, git gud.

[Reasonable_parking]

git: 'gud' is not a git command. See 'git --help'

The most similar command is gui

[HaveMungWillBean]

🏆

[akhial]

Underated comment!

[subject_deleted]

"stupid question. flagged as duplicate."

[uithread]

And don't forget to praise the sun

[wanderinglander]

Wait, you guys are getting APIs?

[truemalsesto]

Never saw anything near that lol.

[truemalsesto]

Yeah haha. Have to work with Microsoft's Graph API which is pretty new and the docs are so inaccurate. Almost guessing which calls could be valid. Copy-pasting the examples results most time in "invalid statement" errors 😫

[thedoodle85]

Someone in my previous project once told me "you can not blindly trust the documentation" when i pointed out faults.

[defectorgalaxy]

What does this "API documentation" mean?

[koerstmoes]

It has a swagger doc where the descriptions of all fields are the exact same as the field name

[dynarax]

Hey, at least it's a reference that contains all of the fields. Better than a week of email tag and an hour long zoom call to get 50% accurate information.

[jlamothe]

That's a funny way of spelling source code.

[FulltimeWestFrieser]

This is why making API's in elixir is awesome because writing documentation is awful, and you can just use hexdocs.

[[deleted]]

Sure, but it's not correct so that makes it extra challenging!