As a Dev,
I hate writing Docs.

As a Dev,
I hate it when there's no Docs.

Vicious Cycle.

Docs!

"Hey guys, so whats the name of the repo?"
"Oh, we are using Google Docs"

Commit strip true as always.
Always write docs! Remember!

*dev wants to find FFmpeg docs
*dev starts typing "FF"
*SwiftKey reveals dev's true personality

This is what happens every time I look at Microsoft’s C# docs after someone tells me to

When you try to dive deep into the docs.
oops

Update the frickin docs
Creds: garabatokid
Visit his twitter. Good guy he is

This dude is definitely going places. The entire code is documented like that. 👌🏻

Google Docs can apparently read minds now

I prefer docs.

Boss assigned me a task on Google Docs:

Boss: "Please remove this line"

Me: "What!? You're already there! How hard is it to fucking select the fucking sentence with your fucking touchpad and press the fucking delete key on your fucking keyboard!? Why assign me with such a fucking waste of time and fucking trivial task!?"

saw this while reading the docs for set_error_handler.

#PHP

Am I the only one who presses ctrl + s on google docs? 🤣🤣

Straight from the docs: just uglify being honest

I guess Elon Musk is too focused on colonizing mars to the point that he forgot to improve PayPal's API docs.

Susan, where are the fucking API docs?
Harold?
Jimmy?
There ar no FUCKING documentations for all our APIs????

Docs: If you get a 500 error [...] you may need to run chmod -R 777 storage[...]
I: wait *reads again*
Doc:s chmod -R 777
I: 😲
Docs: 777
I: rm -rf ./

Programming tip of the day:

Several hours of trial and error can save you many minutes of reading the docs.

Google's API docs are written by stupid idiots

Found in the Font Awesome docs

Unfinished documentation makes me wonder how easily distracted the developers were

Summary of my last hour (it's sunday night):
-Procrastinated 1 hour
-finally stopped procrastinating
-opended google docs
…

AH THESE BLOODY FUCKING DOCS. DO NOT CREATE A LIBRARY IF YOU DO NOT WANT TO WRITE DOCS. UGH

"Don't bother reading the docs, they're just technical crap"

Well guess who knows how the framework we're using works 🤔

Looked at Kotlin docs today.

I had a lot of fun.

PSA: Read your mails before sending them, because some shitty versions of autocorrect like to translate "docs" into "dicks".

Real friends write API documentation

fuck firebase docs, fuck material ui, fuck google

Them: Migrating their repositories to gitlab/bitbucket.

My classmates: using Google docs as Version Control.

The worst that can happen to a developer is good API with bad documentation

Google's API docs are some of the worst I've ever seen... :(

Researching theme shit with UWP. They had some interesting contrast suggestions in their docs.

Actual image from Microsoft's actual website.

I was asked to write a function that does stuff. But where should I write it? Google docs.

I am using MUCH more keyboard-shortcuts now...
Even in Googe Docs and Chrome

Have been coding all day and now writing the docs. I keep pressing ctrl+space and tab and expecting auto complete to work. So annoying

Why don't devs read the fucking docs?

Time and time again I find my coworkers inventing new ways of doing stuff that could easily be done with existing features.

Today I saw this on a code review (functions are from lodash):

head(filter(...))

That's what fucking `find` does, you dense motherfucker!

This is just a tiny example. I've seen so much of this shit. Sometimes it's almost art how they find ways to solve problems without actually reading the docs.

I love the LLVM docs.

I think my days as a dev are over
shit fuck!!!!
All i know is writing code, schematics, systems recommendations
Was given a tender doc for a project
the doc was in 2 parts "Technical" & "Financial"
I HAVE NEVER DONE A TENDER BEFORE and little did i know a shit load of documents are required
MY BOSS GOT FURIUS SINCE I DIDNT COMPILE ALL DOCS and 1 required doc was expired tried to get it renewed and renewal will take 3 week or 1 month and deadline was in 2 hours time
FUCK!!!!

F U C K M E ! ! ! ! !

While reading docs... ok i got it.. thats so easy .. starts coding.. Wait .what was the syntax?

Me: Spends extra time simplifying UI and usability, writes full docs just incase.
Users:

You really appreciate good documentation while you don't have access to good one.

When you gotta refer docs, write code and Test mulitplayer........you need the squad!

Working on implementig mulitplayer for my game!

No Microsoft Word, I'm pretty fucking sure it's spelled Git and not Gilt.
#Preparing Code Review Docs

WRITE YOUR FUCKING DOCS PROPERLY!!!

So I was browsing through some Redis docs and I find this. HOW THE HELL CAN YOU NOT KNOW HOW TO SPELL KOREA!!!!

Indeed, absolutely no issue with the new modern art laravel docs, dipshit.

*me* finding solutions on StackOverflow, Medium, API Docs for hours
*senior dev* walks in and changes one line of code
*works* O.o

Bad habit? Coding without reading the docs.

On a bus, no wifi. Time to code in a language i dont know without the docs.

I give MS a lot of cr@p for terrible API documentation, but even Google's API docs are pretty terrible to read through.

Seriously, guys... Your docs shouldn't read like an endless page of search results.

Well, thank you.

ceo: we need new docs, kiki should make them
tens of team members: lemme explain docs to kiki
ceo: don’t you fucking dare, let kiki execute their unique thought process
☺️

That moment when you found a perfect npm package but there's no f*cking docs whatsoever

There's goes the documentation

Writing a list of censored words is fun!
Hehe

I present to you,
The "Ruby on Roads"

Don't ask for docs tho, its not documented yet

Built my first chrome Extension by following docs.🎊🎉

What should I build next?

Was so confused what the new walrus operator did. Why don't the docs give a simple comparison example like this?

At work we have a lawyer lady who we pay a LOT of money and she suppose to handle our tech related legal stuff. We ask her to look at some stuff we shared with her via shared google docs. After being visibly uncomfortable for a while she called her tech guy at her firm and asked to get Google Docs installed.

MDN docs >>> W3School docs

Tbh, every time I open W3 I come out absolutely misguided..

Has anyone ever taken on a project where you dont know what you are getting yourself into, and then start it and going down the rabbit hole of docs and then at some point ask yourself "what the f u c k am i doing?"

My Friends: Celebrating XMas together
My Family: Celebrating XMas together
Me: Celebrating XMas by reading MongoDB docs 😏😏

There is no better way to celebrate xmas

I have a new motto to life:

"Just read the docs."

*BOOM*

If you ever get an idea for an OpenCV project: shoot yourself in the foot, drink some bleach, do whatever it takes to get it out of your head, because it will all be less painful than the python docs for cv2.

I hate it when people put time into making their docs look nice but none into making them actually helpful!

Email chains, screenshots shared in google docs, two comments per 1k lines of code, and sticky notes are sufficient documentation, right? RIGHT?

Had to integrate legacy code into the new framework.

Me: Where does the virtual sensor come from?
Colleague: It's in the docs.
Me: That step is not in the docs.
Colleague: It is, look into the file $FILE.
Me: Yeah, it's empty :D
Colleague: Nope, it's not.
Me: See, empty (pointing to laptop screen)
Colleague: Why is it empty? (keyboard typing...) Damnit, too many git remotes in my repo :D

!rant

I'm currently reading the Docker docs. This thing seems to be beautiful.

I can't believe this is part of an official documentation (wordpress).
Tldr, they want to tell you how to remove all characters in the end of a file lol

Unofficial devRant API Documentation
(Remake of the old devRant-Docs site)

What the fuck happened to laravel docs, what fuckwad thought the only docs across the entire internet that are properly readable, need its shit fucked up and made into borderless, bold fontweight, shit font dogshit.

WHY AWS Docs are so awful? 😠🤦

- When will we start to read the docs?
- The day Stock Overflow 404ed.

** PSA to all programming language and tool maintainers **

Please for the love of god have a dedicated examples section on your website where people can quickly evaluate what the thing even looks like

So often the next best thing is going to the docs where they tell you that the turboblub option should be set to 12 in these specific usecases whEN I DON'T eVEN KNoW WHETHER THIS IS A PROGRAMMING LANGUAGE OR A LAWN MOWER

I just pressed CTRL+W in Firefox to delete a word and lost 20 tabs of docs. 😣

Second place when searching "devrant docs". Fuck yeah!

thank you node-mongodb-native docs for these comments, I would have not figured those out

After trying polymer for a week, I can officially say that it is the most confusing framework ever.

They need to learn how to properly document their code.

Stack overflow doesn't help because the dipshit who asked the question ALWAYS "misspelled" a variable.

I love Flutter. So simple. Such good docs. Not totally shit multiplatform. Flutter is my new favorite framework. Good job Google

Why do most docs have grey text color over a white background! It's just incredibly difficult to focus on. And my brain is like a potato to begin with.

So I was writing docs for my project the hard way. Manually. Every time I added something new, I had to find the right place for it to be alphabetically in the reference. And god forbid I want to have the same information in two pages: I would need to copy/ paste and pray that I not forget to update the information EVERYWHERE.

I didn't feel like installing and learning some new markdown generating bullshit so I just made my own system. It's very simple and intuitive and I love it.

I made sure it can cover two use case: reading partial documents from the disk, and rendering in-memory objects to markdown too (like rendering a collection of tuples into a table)

I didn't care much for templating, so there's no templating capability.

That moment when you were finally able to make a plugin after 36 hours of frustration for a software with absolute shit docs and not many resources thanks partly to a small article (written in german which you had to translate) that you found lurking in the corner of web. 😌

Me: I should make REST API docs
Also me:

I started using Google Docs over the weekend working on my thesis paper for my CS degree. I've come to the conclusion that it's a suitable replacement for MS Office and my need for Microsoft's ecosystem. Don't know why I kept paying it for so long.

Discover that stackoverflow has documentation. Now they will start to yell "Check the fucking docs!!!"

One thing I hate about documentation and tutorials is they always seem to use the simplest examples they can think of. They show you how easy it is, but if you want to use it in the real world start digging further.

Current programming experience: Looking at the API Docs, and crying

Youtube's API docs for iOS is still in Objective-C.

when the API docs aren't very clear 🥴

Markdown. It is now used by MDN Web Docs and supported by Google Docs. End users will slowly pick up. Then even more (proprietary) flavors of markdown and their accompanying JS-frameworks will follow. All with good intentions, but it can only to end in a big mess and confusion like USB or USB 3.2 Gen 1.

Recently I had to work on a project using PrestaShop. Naturally I looked up the "docs" and found the part where they recommend to write documentation.

Fine until you realize they don't and the documentation website gives generic useless informations...

AWS write awful docs. The .Net SQS example code has spelling mistakes, bits missing and doesn't work.

Also would be helpful if it highlighted that the .Net Core implementation is fundamentally different.

Jerks.

So I just found an old branch, from an ex co-worker, with a whole bunch of unmerged docs. This effectively cuts my workload for today in half.

Today I'm going home early fuck yeesss

Also I will be sending that guy some well deserved couple of beers

That moment when you try to use your IDE keybindings on Google Docs :|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|

DevRant-API-Docs Site Update:
QA is in the works. Will try to keep it as simple as possible!

The "all questions" page front end is done. Now there's only the "new question" page and the "view question" page.

Can't we just read the docs and make a antiviral based on that?

I’ve been a solo frontend developer for a couple of weeks now with critical enormous features and some bugs to get out the door by the end of next week.

On top of that, I got a backend bug to fix which is fine since I know the stack. The SQL that’s causing a bug is an obvious fix but as a FE dev I have no damn idea about DB structure.

I decide to setup local DB to see it for myself. So as a reasonable developer I look for docs to set it up since it sounds like quite a process after confirming with colleagues.

ANNNND... SURPRISE, the docs ARE NON EXISTENT unless you wanna call an outdated diagram a sufficient doc. Just so you understand the pain, we have 9 micro services, a weird db structure and only 5% is documented.

I requested help from my colleagues, but their answers were similar to docs with a follow up of “maybe you can document it after you set this up”. Barely stopped myself from asking “do I look like I have time for this crap? Why don’t you document it SINCE YOUR SETUP IS READY TO GO?”

So I’ve been at it for a couple of hours and I gave up. Will go back to frontend development since still a ton of shit to do anyway. Tomorrow I will attempt this again.

Remember all official docs

having to remember damn parameters

Awesome library without docs....

code code and code. There's no better way to learn other than practicing the material learned from docs.

Few weeks ago: Please write the system design docs for feature X of the new project Y. We need it in two weeks.
Few days later: Stop working on the docs, the customer hasn't yet bought that feature.
Few days later: We found that we included that feature in the main contract already. We need the docs in two days.
Today (docs delivered a month ago): There was a misinterpretation of the requirements and the contract, the customer hasn't bought the feature with the main contract, it has to be sold additionally. You didn't do anything 'til now, did you?

It would be really nice, if sales could finally decide what the customer bought and then tell me about the requirements that are already covered in the docs anyway. But I fear it could end in asking the customer 🤪🔫

Why do you even bother writing docs if you don't include anything worthwhile in it!

That moment during your internship when you work on a project using a framework you're not familiar with, with no doc, and absolutely no comments, and you find a file with 1.3k lines of code without the ability to contact the previous dev

Cloud2Butt. Makes browsing any cloud-related websites and docs AMAZING.

FUCKING FUCK I CANT FUCKING HANDLE THIS

WHY THE GODDAMN ***FUCK*** DOES CINNAMON NOT HAVE DOCS FOR ITS DESKLETS

THE ONLY TUTORIAL RELATED TO IT IS FROM FUCKING 2014

THERES LITERALLY ZERO DOCUMENTATION ANYWHERE ON THE INTERNET

HOW ARE PEOPLE MAKING DESKLETS AND APPLETS WITHOUT DOCS

Getting webpack to work the way I want it. Only consulting the docs.

YouTube tutorials then enough patience to read docs.

What is the fucking point of creating an amazing device with amazing software, which has a very nice API BUT USELESS FUCKING DOCS.

The thing has features that are only visible in their software, it is mentioned nowhere in the api docs and I have no fucking idea how to access those important features. Fuck you

Why do all the cool things have terrible documentation?
I'm looking at you Gnuradio and OpenCV!
Doxygen doesn't count if you don't actually write doc comments!!

Thats the first time I'm seeing BUTT in the docs :D

Angular material is shit.

Angular material has literally no documentation. There is no search on their shit docs. And there is absolutely no info in their docs about some shit they use.
So when you need to know what the fuck does smth like MatOption mean (what inputs does this piece of fuck takes?) you will need to dig into the code.

Good luck finding docs for eclipse for a while

When you need to check the go docs

I always write a Google Doc before I start developing a feature to help me think what and how should I implement it and so I can share it with the team.

It is possibly the most frustrating process of the whole development cycle because Word and Google Docs still manage to make it a fuckin ordeal to insert a simple image without bombing the whole text to hell. How is it that after almost 30 years of history it is still shit to write a document?

onEnlightControllerActionPostDispatchBackendPluginManager

Who needs docs if you've got such speaking method names.

Love the docs that provide lots of segment examples everywhere, but no full examples. No source code. Very helpful

Me: I'll comment that later
Also me: Why tf isn't there​ any comment

No seriously, comments and documentations are really necessary. Today I've been debugging for hours, why a certain variable has a certain value. Age of code: 15+ years. No comments. No docs. 🙃

You know that moment, when you look for something on wikipedia, and after few hiperlinks you are reading about influence of penguins on Mars' day length or othen nonsense?

Just happened to me like 4th time when reading Django documentation. It is so well written and easy to understand, that I just click and click and want to go deeper, and then realise I have to read what I need, because I never ever got to it in the first place.

Gotta love the people who make such docs. I never could, and prbly will.

When you write a manual in markdown about "HOW-TO use this program"....

Kill me

I like Scala, but the docs suck.
The FAQ literally uses StackOverflow links as answers.
Not as references, where they write the complete answer and provide the link for reference or credits.
They actually just throw in the links.

Why do the AWS docs have to suck so much :/

I love how all the shorthands for events are deprecated, but JQuery docs still haven't been updated.

Build this as a monolith, microservices are to complicated..

Said no and did the docs first, to make it look easy. Problem solved ;)

Google OAuth docs is such a pain to read... I have implemented OAuth multiple times and understand the flow. Its never been a problem, but man, their docs is such a pain to read.

Their Java client library is also painful. Its needlessly complex that I just ended up implement good old HTTP rest to handle it.

Here's the intro of the documentation I'm reading in my new job:

...we have four sections. First 3 section will use LBC and the last 2 section will use HBC

🤔

I was too lazy to check Tailwind docs or existing templates. That backfired pretty hard.

Oh God Why?!

Love writing comments, hate writing documentation.

Ugh, I know it is needed but just don't care about it as much as the code/comments which is a more direct 'here is what this does' approach. Writing idiot proof documentation sucks. Any little change? Have to remember to update the docs. Yeah, not happy.

When your site was developed by someone with a programming degree from the 70s and has no API docs....wheeeeee

1.) Read the docs on the website
2.) Curse the Devs for bad docs
3.) Go to YouTube and pray that I find a food tutorial WITH AUDIO!

(jk,sometimes some docs r very neat and clean)

I've accidentally deleted a Docs folder with some important files. F.M.L.

Read the documentation!

...(follow docs)

Why did you do it that way?! The documentation is outdated!!

...(doesn't read docs makes best guess)

Why didn't you follow the documentation??!!

Sigh.

is there a google docs for ides? like, real time editing where you can collab while you are?

i think that would be cool.

anyone else?

Had a quick look at the push bullet API docs, thought they looked pretty good and comprehensive m.. oh how wrong I was!

Why on earth I am doing docs and sending them to the whole team, if they keep asking me how to do X and why is Y not working

YOU WILL KNOW IF YOU READ THE DOCS

GAAAAAAA

Oh come on. Even the docs itself are a parody on the framework

I won't push the documentation unless the guy pays me!

What's that "documentation" you're talking about?

Google documentation sucks!

Lack of practical examples. They show us very simple example like clicking on button and then straight away redirect to API docs.
Wait, let me at least understand how things fit in together.

Me: Hey google where is step by step guide, at least for setup?
Google: We don't do that here!

So, I've been trying to learn assembly. However, I can't find any assembly docs online, so I can't really do anything. I tried NASM and FASM but I just can't understand assembly. Do y'all know any decent way to learn assembly? (My dad said it's better to do it on my pi or should I do it on my desktop?)

Read the docs.

I was reading ionic native docs on the geolocation plugin 😂

Giving time to understand concepts to the core, rather than reading the docs, getting a surface level overview and coding.

I don't like things like "programming is copy&paste"
But if you think about it... Actually it is: when you don't know how to use a function or how to write a new language you read the docs, copying and using what they say 🤔

Stack Overflow? It's a doc full of examples 😁

Going through the docs of the new tech...

Being victim of an arbitrary worplace's culture on dev experience and documentation makes me a very frustrated dev.

Often I do want to document, and by that, I don't mean laying an inline comment that is exactly the function's name, I mean going full technical writer on steroids. I can and WILL get very verbose, yes, explaining every single way you can use a service - no matter how self explanatory the code might look.
I know developers (and me included) can, and sometimes will, write the best variable and function names at the time, wondering if they reached the peak of clean, DRY code that would make Robert Martin have a seizure and piss himself, only to find weeks later after working on something else that their work is unreadable. Of course.
I know the doc's public, it's me, and I've done this.

But then again explain for the people in the back how the FUUUUCK are we meant to suggest improvements, when we are not the ones who are prioritising features and shit WITH the business?

Just email me when the fucking team recycles, and no new team member knows how to even setup the IDEs because this huge piece of monumental shit called CompanyTM is also run by VPN. Fuck, no one wants to access that garbage, you have no docs.

I once tried setting up a culture for documentation. I did an herculean amount of work studying what solutions were internally homologated, how steep the learning curve would be from what we had at the moment (NOTHING, WE HAD FUCKING NOTHING, jesus christ, I even interviewed SEVENTEEN other squads to PROVE they FUCKING NEED
DOCS
TO WORK

You know what happened to that effort?
It had a few "clap" reactions on a Teams meeting and it never reached the kanban.
It didn't even made it to backlog.

I honestly hope that, someday, an alien fenomenon affects the whole company, making their memories completely reset, only to have the first one - after the whole public ordeal on why our brains became milkshake -, to say: "oh, boy, I wish we had documented this".
Then I will bring them to the back and shoot them.

Studying for college exam
- 2min/sitting

Coding/reading Docs/Book of interest.... after 12 hours
- " OMD ... I completely forgot, i own a mobile"

I've been trying to build docs that worked before for my little project for a fucking week. A problem with dependency, because it couldn't just install for whatever magical reason, although in another repo the dep was installed just perfectly.

A few seconds ago it built. Again, magically.

Does anyone know where are the *official* devrant api docs? Tried web searching but could not find them.

Best: Public docs, especially quick start guides... That actually work.

Worst: my team's. It's basically non-existent... I'm the only one that writes docs and design diagrams and well that's mostly for myself to remember/understand stuff and use when ppl ask....

My first response is usually like: "Here RTFM... (Now go away because I have other things to do)"

The day I read nodejs docs

When the tutorial/docs is so bad, so you rely on the code to be readable and works as expected

Is there anyone who has ever used frappe/erpnext?

It drives me nuts, as much as I like the framework doing any thing that needs some basic scripting is a pain!
I MEAN, COME ON MAN, WHY ARE DOCS SO HARD TO COME BY? WHY DOES YOUR "CUSTOM SCRIPT" EDITOR LACK BAISIC LINE NUMBERS? WHY ARE YOUR ERROR MESSAGES TELLING ME EVERYTHING BUT THE LINE THE ERROR'S ON, SO I'LL BE HOPEFULL THE ERROR IS IN THE DEV CONSOLE? WHY NOT USE MONACO, SOMETHING, ANYTHING THAT WILL SHOW SYNTAX ERRORS? I'VE WAISTED HOURS ON LITTLE AUTOMATION SCRIPTS!!!! WHY WHY WHY WHY????

Hey documentation providers! Some of us don't want to have to go to slow ass websites to look up everything about your code, system, library, api, etc. It also really sucks when trying to work on those systems without an internet connection. So, please provide offline documentation.

A special thank you to Python for providing help files with Python itself. This has been a life saver when working offline.

Also a special fuck you to Bethesda for not providing an offline version of the Creation Kit wiki. Everything else you do is nice, but please provide offline docs.

Using Microsoft's docs for Azure is about as fun as Spreading Your Ass Cheeks for an incoming elephant dick.

Who the hell is writing google documentation, If I see you, I want to fuck your stupid ass mofo... These docs are useless as fuck. I think it's the same person or maybe there are many copies of this washed head stupid ass writing the same kind of shitty docs all over the place.

when you have to learn </coding> all by yourself 😂😂😂

➡️ Started searching and reading the MailChimp docs.
⬅️ Ended reading the letsencrypt docs about CAA-Records. 🙈

I was playing with AWS and came across Rekognition! Although the docs are poor, the service is just amazing. Mind blown.

That moment where you find how to do it in the docs
But you had passed that section 3-4 6 times
But you had already formulated your own fix

And you have to redo that code block

Screw Facebook SDK Docs.

API docs. Why are they all, still so shit.

I was just clicking trough oracle's docs, on a page which had to do with manifest&sealing (kotlin/java)

docs of function getBook: `returns a book`
no way!
*slaps forehead*

I backed this Kickstarter project for a programmable E-ink display called "Displio". The documentation is about 40 lines and is basically just a list of globals without any explanation followed by a link to MomentJS docs. worst of all you have to modify the page with an inspector to see it all.

For Vue 2 users:

An Android dev created an offline Vue docs app. Search with 'vue.js'

My “DevOps” teammate for a hackathon saves code in Google docs and sends me his contributions on WhatsApp.

Wouldn’t replace him for anyone else though.

sometimes i have to remind myself "dude, the docs explain that shit well! why the hell are you wasting time on crappy resources??"

What do we call a group of doctors appointed by google?

answer: Google Docs😂😂

React Native's docs are so shitty 🙄

How are your companies doing on writing docs? Is it mandatory/optional? Would you say reading a doc by other team in your company would be enough to understand what their module is doing? Do you write docs per module/file/function? Also please mention main programming language if it's not a secret..