Q:What's more dangerous than no documentation ..

A:Wrong documentation ..

Got my hands on an interesting API.
Look around on the site.
No documentation. Like, nothing. Not even examples.
Tried calling it.
Response code: 200 OK
Body: Unknown Error.

Well, fuck you too.

Phone rings
Uh oh
Answers the phone
Its my boss
>the latest tool you made isnt working
Um... Yes it is?
>we cant run it because its a jar file
Um..
>how to you run a jar file?
Um... You click on it?
>it doesnt work, nothing shows up
(Maybe if you fucking read my documentation, you would see that it just generates the files you need)
>there are no files
Yes there are we tested on every possible hardware, theres no way to fuck it up
>there are no files
Okay maybe you just dont see them on your desktop, move the jar to an empty folder
>how do i do that

*hangs up*

Yesterday I had to modify a python script that was written by the previous dev,
There was no documentation to understand the code, I had to read 10 files almost 900 line each, after a looooooooooong 7 hours, at the top of one of the scripts, the author name was same as mine
😂😂😂😂😂😂😂😂😂

Every fkn 3 to 4 days, some random dev shows up in my office really really fkn confused and frustrated about something he doesn't understand - because I have a dark secret.

Sometime, in cold lonely nights, when no one is watching, I write my documentation before the actual code.

Somehow, sometimes documentation without code attached to it makes it to production.

Today someone yelled at me for wasting his time because he wasted 3 hours trying to find the code the documentation belongs to - and demented I stop the practice from now on.

Agh.

"there's a problem with your API"
Me: "why?"
"I get no data"
Me: "what response code are you getting?"
"405 - Method not allowed. But only on the /version endpoint"
Me: "Soo... What request are you sending?"
"POST"

WHY THE FUCK WOULD YOU SEND A POST REQUEST TO AN ENDPOINT THAT **GETS** THE VERSION OF MY API???!!!!

Me: "Read the documentation. It's there for a reason"

Me: Can we do this with your module?

Creator: Yes

Me: How?

Creator: By adding the need values. Please see the docs. :)

Me: You have no documentation on this feature besides, "yes."

*Creator has closed ticket.*

So everyone is sharing their work again, so here is mine.
And no 6 monitors, 1 pc isn't overkill.

Well...

Maybe...

But just a little!

Usually, one is spotify, one iChrome, one development (center bottom), one execution of dev, one email&facebook split and one documentation.

There is no shame in using google to program.

'Back in the day' we had phonebook sized books of documentation on our desks we would reference constantly.

Why?

No one is going to memorize a phone book sized book. Not to mention three or four of them.

Being a good dev is about creativity, not memorization.

This genius made his very own super-flexible-and-versatile-never-seen-before-mvc-framework, with no documentation about the code, instead of just donwloading and implementing a popular one.

He left the company.

I maintain it.

Fell my pain.

The company I work for...
Has:

1. No CI/CD
2. SVN instead of GIT
3. Outsourcing to India (oof)
4. No Automated Testing
5. Uses Bugnet (ancient, outdated)
6. No clearly defined code standards
7. No real documentation on the code
8. Rubbish code
9. No desire to reduce technical debt
10. Poorly maintained DB
11. Poor outdated equipment
12. A useless PM
13. Still priotizes IE support (??)

On a scale of 1 to 10 how fucked is this company and anything they develop?

Newspaper: This CEO is one of the top entrepreneurs in the country, a true tech visionary shaping the future.

--- 3 months previous ---

Lead dev: O2 have said they are will pre-install the app on all their Androids but they need documentation from us.

CEO: documentation? on what?

Lead dev: Our unit test coverage, bugs found / fixed, security scan results, performance assessment, if and where its storing any data etc.

CEO: Ah were not doing any of that crap, bloody unit tests, its not necessary, tell them no.

lead dev: ..... eh ok

O2: *approved*

... true visionary, well done to everyone involved.

There are a lot of things that could rank up as the worst about being a dev, such as recurring meetings, documentation, shitty requirements, pm gnats, Monday, etc...but something that truly ruins it all is NO INTERNET CONNECTION.

NO FIREFOX AND CHROMIUM, I ALREADY SET THE FUCKING CORS HEADERS CORRECTLY ACCORDING TO THE OFFICIAL FUCKING NGINX DOCUMENTATION. WHY THE FUCK ARE YOU STILL DISALLOWING CROSS-ORIGIN REQUESTS?!

"I want my API to return insults as error messages if they forget shit"

Uh no, I prefer helping them out by writing proper documentation than sending a giftbox with me flipping them off like Linus Fucking Torvalds for their spaghetti usage of your API

Started working at a large company with promises of a great framework, stable environment and bleeding edge tools, decentralised working environment, only to find visual studio 2010, no git, no project management tooling whatsoever, all documentation stored on svn, no slack or other modern communications platform, still using uploaded word documents as documentation for projects and meetings, so yeah I can truly say :/

Hello, I just want to let you know I'm working on a 15 year old product and it is currently in production.

It uses Angular.js and one of the earliest versions of React.js. I cannot use ES6, we don't have Babel, no JSX syntax, no CSS preprocessor. No webpack.

I must support browser since IE6 with an ES3 syntax. (luckily I got some some polyfills for an ES5 syntax)

When I build a component I have to call React.createClass and React.createElement.

The render() function is basically a nested pile of React.createElement.

There is no documentation for this product, no tests, no anything.

I had to reverse engineer it in order to understand how it works.

The code base uses mixed programming styles and naming conventions, plus thousands of little js files.

Oh and obviously no hot reload, every time I make a change I have to restart everything.

Please, send help.
I'm in danger.

Sincerely,
An underpaid developer

....
I'm not crying, you are crying...

1. No more coding on paper! Why can some already write essays on laptops but programmers are stuck with "analog"?
2. No vendor lock-ins! Teach free, cross-platform development, not VB.NET.
3. No more professors stuck in the eighties! If all you know is 6800 assembly, GTFO. I heard NASA was hiring...
4. Enforce code style consistency, proper documentation and even VCS for larger projects
5. Algorithms -> scripting -> programming. Don't quickly explain the basics, then throw students straight into Java.

If you write documentation and no one reads it, did you ever write it in the first place?

TFW your client's git policies are so draconian that the dev teams use "develop" as trunk, and completely ignore the release process.

I wrote up 50 pages of git standards, documentation and procedure for a client. Bad indian director 9000 decides the admin (also Indian) who specializes in Clearcase and has no git or development experience is more qualified to decide and let's him set the policy.

FF to today:

- documentation, mostly contradictory, is copy pasted from the atlassian wiki
- source tree is the standard
- no force pushing of any branches, including work branches
- no ff-merge
- no rebasing allowed
- no ssh, because he couldn't figure it out...errr it's "insecure"
- all repos have random abbreviated names that are unintelligible
- gitflow, but with pull requests and no trust
- only project managers can delete a branch
- long lived feature branches
- only projects managers can conduct code reviews
- hotfixes must be based off develop
- hotfixes must go in the normal release cycle
- releases involve creating a ticket to have an admin create a release branch from your branch, creating a second ticket to stage the PR, a third ticket to review the PR (because only admins can approve release PRs), and a fourth ticket to merge it in
- rollbacks require director signoff
- at the end of each project the repo must be handed to the admin on a burned CD for "archiving"

And so no one actually uses the official release process, and just does releases out of dev. If you're wondering if IBM sucks, the answer is more than you can possibly imagine.

Poorly written code + no documentation = complete redo of the program 😞

The worst documentation is if you have no documentation. :-(

Task:
- Replace a 4 year old PHP API.
Old API:
- PHP script writing PHP scripts to /var/www/ for every endpoint needed
- Answers everthing with 200 (not even 404)
DB:
- MySQL 5.6
- ~ 1000 Tables, NO FUCKING FK's
Documentation:
- "Wasn't worth the effort"
New API:
- Not allowed to behave any different
.
.
.
😭

University logic - Provide outdated curriculum. Drop current relevant stuff from the course. Use a legacy software that has no applications anymore. Expect the student to be a master at a technology without documentation.

Published a well documented and tested API with project examples for basic use cases

- "Yeah we didn't use yours because we didn't know how to use it"
- "Did you look at the documentation or code examples?"
- "What where?"
- "In the repo you just cloned"
- "Yeah no <random guy> found a hacky way of doing what we want, his thing just works"
- "I..."

The previous developer left no fucking documentation of how he developed this fucking website. Did I mention no one else in the company knows how he developed this fucking thing.

Fuck.

I am sure this has happened to all of us in some extent with some variations.

Colleague not writing comments on code.
Ask him something like "How am I suppose understand that piece of garbage you have written when there is no comments or documentation?"
This keeps happening for a long time. Some time after, I write a kernel module using idiomatic C and ASM blocks for optimizations (for some RTOS) and purposely not write neither documentation nor comments.
When he asked for an explanation, I answered to everything he questioned as general as I could for "that trivial piece of code".
After that he always documents his code!
Win! 🏆

Ironically, the face I make when a project has no documentation is the same one I make when someone asks me to write documentation.

TLDR; I am a piece of shit who writes no documentation or no information whatsoever when I am doing something.

Created a custom version of Windows for our company couple of months ago. Before leaving, I am supposed to pass this valuable information to another new developer.

Obviously, since it has been a long time I have worked on that, I have forgotten a lot of core principles. The process is also automated in Jenkins so never really had to touch it again.

Now that I am about to explain the process to the new recruit, I realised that I have written nothing about that process. No documentation, no information. The only thing I have is a bunch of scripts automating everything for me. WHY WHY do I do this to myself :(

Let's start 2023 !

WHO THE FUCK imagined that having language like YAML is a good idea ??

Fuck you and your spaces. No editor produce any decent errors messages except "Your spaces are wrong".

When you edit an Azure debops pipeline, it's just 5 min ti do thing, 35 minuites to figure ou where to add/remove spaces.

NO, I WILL NOT read 25 pages of documentation to add a single step into pipeline.

Fuck YAML !

Yesterday I had to ask a classmate what the arguments of a method were (no documentation).

He said: "Uhmm it doesn't matter in which order you put the arguments into the method?"

No more to say.

You have a question.
You google it; nothing comes up.
You read the documentation; no good.
You ask it on stackoverflow; no answer.

You are in... The Twilight Zone

Today a new person joined the team.

Started bitching about the entire team for not having documentation for our already written code and software.

Asks the manager for a new task that he can take up so that he can write documentation for all our already coded works.

Manager says Go On.

Troubles me with 400 questions every 3 minutes in the name of Knowledge Transfer for writing his documentation.

Sends a proud mail to the team for writing this new documentation that no one else had time to do.
He is a newbie and had no other task to do anyway.

I seriously don't know if I should feel proud of him, for writing new documentation,
Or if he's doing this to defame me.

The team is filled with snakes.

So I've been doing some code jobs now and recently they pushed me to a new level.
This company worked with some silly management app made in cpp which they asked me to edit a little bit giving it another style and some additional functions.
Day 1: this code is a mess.
Day 2: this code is a mess.
Day 3: how does this code even compile.
Day 4: I no longer have faith in humanity.
Day 5: I found my first comment (Yay?).
Day 16: I'm done.
Day 19: I got paid.

If you're making a project in cpp just like that dev you do deserve a punch in the throat.

No documentation, no comments, no patterns, just some thick pasta of poorly written code, names like fCalcAllTaxFilesSizeMB....
This haunts me for real.

New job...
No introduction to project
No database overview
No documentation
No commented code

Shit, hope this isn't normal in the industry I have aimed the rest of my life at

I've been lurking on devrant a while now, I figure it's time to add my first rant.

Little background and setting a frame of reference for the rant: I'm currently a software engineer in the bioinformatics field. I have a computer science background whereas a vast majority of those around me, especially other devs, are people with little to no formal computer background - mostly biology in some form or another. Now, this said, a lot of the other devs are excellent developers, but some are as bad as you could imagine.

I started at a new company in April. About a month after joining a dev who worked there left, and I inherited the pipeline he maintained. Primarily 3 perl scripts (yes, perl, welcome to bioinformatics, especially when it comes to legacy code like is seen in this pipeline) that mostly copied and generated some files and reports in different places. No biggie, until I really dove in.

This dev, which I barely feel he deserves to be called, is a biology major turned computer developer. He was hired at this company and learned to program on the job. That being said, I give him a bit of a pass as I'm sure he did not have had an adequate support structure to teach him any better, but still, some of this is BS.

One final note: not all of the code, especially a lot of the stupid logic, in this pipeline was developed by this other dev. A lot of it he adopted himself. However, he did nothing about it either, so I put fault on him.

Now, let's start.
1. perl - yay bioinformatics
2. Redundant code. Like, you literally copied 200+ lines of code into a function to change 3 lines in that code for a different condition, and added if(condition) {function();} else {existing code;}?? Seriously??
3. Whitesmiths indentation style.. why? Just, why? Fuck off with that. Where did you learn that and why do you insist on using it??
4. Mixing of whitesmiths and more common K&R indentation.
5. Fucked indentation. Code either not indented and even some code indented THE WRONG WAY
6. 10+ indentation levels. This, not "terrible" normally, but imagine this with the last 3 points. Cannot follow the code at freaking all.
7. Stupid logic. Like, for example, check if a string has a comma in it. If it does, split the string on the comma and push everything to an array. If not, just push the string to the array.... You, you know you can just split the string on the comma and push it, right?? If there is no comma it will be an array containing the original string.. Why the fuck did you think you needed to add a condition for that??
8. Functions that are called to set values in global variables, arrays, and hashes.. function has like 5 lines in it and is called in 2 locations. Just keep that code in place!
9. 50+ global variables/hashes/arrays in one of the scripts with no clear way to tell how/when values are set nor what they are used for.
10. Non-descriptive names for everything
11. Next to no comments in the code. What comments there are are barely useful.
12. No documentation

There's more, but this is all I can think to identify right now. All together these issues have made this pipeline the pinnacle of all the garbage that I've had to work on.

Attaching some screenshots of just a tiny fraction of the code to show some of the crap I'm talking about.

PM, on kickoff meeting: good code speaks for itself, need no documentation

PM, on UAT day: how does this features work, where is the documentation for it?

Dev: Just do me a favor and go fuck yourself.

My current project is a fucking nightmare.

It started in 2007, using a solution developed by an Indian company due to outsourcing (aka low-quality code).

It's running on Java 7 on the back-end and its front-end side is pure Javascript files. There are thousands of little .js files everywhere, no documentation, no comments, differents coding styles, outdated API that were already outdated at the time, mixed oop and procedural.
Not even when I started coding, I wrote something so horrible.

Yo, it's a clusterfuck and I just wanna get drunk.

That moment when you quit your job where you worked for the past 4 years and you have your last 5 days at work when your supervisor says that it's time to improve our documentation. Oh really? Wtf have I been saying all along? We have almost no documentation at the moment, so I expect lots and lots of confusion once I'm gone...confusion or phone calls to me.

Re-writing IBM Asembler code to C. No documentation whatsoever. Code was our only reference.

> raw http request injected in the model
> 400 lines long method, followed by three 300 lines long methods
> no autocomplete, no comments
> code called by the whole application, I mess up once there's at least 150 other components that might break
> no documentation, no tests
> pyramid of doom, 13 levels of indentation

Those are the same people getting all puffed up because the cat dared to sit on my shoulder during a call. Management focused on the real fucking problems, no doubt.

No matter how much documentation you write, and how well you comment the code, the truth is always the code itself.

Thanks to the developer who decided to release his library with no documentation and hard coded values .. 10 hours well wasted !

I'm gonna decline the next time someone asks me "hop in chat with them" to discuss their stackoverflow problem.

I'd already given my two cents about the problem in question and I thought something was unclear about that so I say okay what the hell, made a chat room and invited him in.

Him: So I have this OTHER problem with [insert JS plugin]
Me: ... I don't know enough about it. I've used that specific plugin maybe once. The question I offered you my help with was PHP.
Him: Yeah but can you take a look really quick?
Me: I'd have to reread the documentation. I literally don't remember how to use it.
Him: No problem, here's the documentation. I want to do X, Y and Z.
Me: I don't think you can X without doing A and B first.
Him: I was told not to do A, so how can I do X, Y and Z?

Fucking hell I'm not gonna do your job for you. You know english. There is documentation available. Just read it and at least try things.

No documentation. Thousands of lines of code. Still learn enough about the solution to make a required change in a day. Now the company feels like I should be the one to lead training for the module, and I still don't know what the other half of the code does. T-minus two hours...

Ask a developer to code entire night

Developer:
😏🤓No Problem. I was born to play with fire 😤😎

Ask a developer to complete the associated documentation in next couple of hours

Developer:
😳🤬🤯 Better call the devil to take me to hell 😱🤒🥵

Went to a Hackathon, the platform looked like bs and the documentation was mehhh. So spent the time sleeping, waking only to eat Pizza :3.

(Know it was bs when no one cared >.>)

For god fucking sake, PulseAudio, write a usable fucking documentation for your library and remove idiotic silent exit(1) calls and properly log what the fucking issue was

I'm tired of debugging this piece of bull shit for over a month now already while the pulse library occasionally crashes for no apparent reason

Both apps I'm working on have legacy code:

iOS app has 100's and 1000's of lines of code with no documentation, no proper naming conventions and cut and pasted code off the net.

Android app has skeleton code from a Spanish taxi app + remnants of a funeral webcasting app, there's also the same no documentation, bad naming conventions and cut and paste code off the net.

The server is also as bad, it had methods that we're never used, I for one don't fully understand the server but from what I can see it's a mess.

I had a hard time understanding both apps and gladly majority of the modifications I made we're not including existing stuff, so I guess I just basically pilled my code onto of the already existing software.

I would have gladly started from scratch given the chance.

Holy fuck is learning new frameworks frustrating.

I'm trying to setup a simple fucking flutter app and all their tutorials are basic shit with no auth/complex routing.

Any feature of flutter that's not in a tutorial has absolute shit documentation with 0 examples on how to use it.

Material app has like 20 properties and if you click on something like on generate there is shit for knowing what the fuck it's expecting.

Stackoverflow has a ton a code but that's just it, code. I have absolutely no idea how they generate the code they have from the documentation on the site. They must have been following flutter from the start.

Ahhhhh! 😠

Saw this in the Python documentation. Why no taaabs 😭😭

tabs > spaces

- I am leaving the company, so you will work on my project.
- (looks at code) But there is no single doc string or any documentation apart from the installation guide.
- Yes, but the project is really easy to understand.

... I will just sit here trying to understand your code instead of doing actual work.

I have a lab at uni where my lab group have to refactor some code from an open source project. We got assigned some Apache project and jfc that code is a mess. Little to no documentation, hard to navigate, tests that you have no idea what it's testing, and so on. On top of that the teacher expects us to spend more time than we have on it. I'll be glad when this course is over :))

In the royal city of Aagra. My phone broke and knowing the exploitative bitch I used to meet back then I was certain had I disappeared amid a conversation she would break up with me, so I debugged an Android 2.3 image with no documentation and shaky hands from frustration while cursing her every family member in Hungarian. (Passers-by probably thought I was casting spells on my computer)

I have no idea how this code that I wrote last year work and there's obviously no documentation but thankfully I gave my classes very useful names such as "YuDoDis", "Texter467", "TheHolyButton", "GARBAGE", etc. Fucking hate myself sometimes.

At my job there is little to none documentation of the software. Software is from 2000 and updated since...

Imagine the features no one knows about.

Deprecated method and no documentation updates 😡

No, a 33 Page README is not the better choice.

Not for reading.
Not for writing.

Compared to a /Documentation/ folder
+ good overviews / links

I spent the last weeks rewriting a huge project which I had to hurriedly write a year ago. No comments, no documentation, spaghetti code. Part me was an asshole! But now I am done, all is new, everything is well commented, structured in classes with well defined tasks. Yay.

Fuck Azure, Fuck Windows, Fuck Microsoft.

Half ass baked products in the market. Half the time there's no documentation. When there's a documentation it is so bad that it makes me feel like biting my teeth so hard that I am left with fucking pieces of incisors. My blood fucking boils whenever I need to deal with "POWER"shell. Fucking weaklings.

Our documentation is currently stored in a VM image after the host died, meaning we have no access to anything - good times!

People who complain about wordpress have probably never tried working with Magento.

I've been going through their documentation for about 3 hours now, trying to figure out how this entire system works. And I'm no where close to understanding it...

When in internship you have to read 150000 lines of code to make changes and the code does not have any comments, no indentation, no documentation, no wiki. You'll be like fuck this shit. I'm outta here.

Workflow?
No source control. No documentation. No testing. Do everything on live server.

I’d rather we have no documentation than shit outdated documentation that just wastes our time.

"Your documentation doesn't specify what should be returned if there is no item matching the id, so currently I'm just gonna have it throw a 504"

Why on earth would you? What's wrong with you, you sick bastard?

Oldie but goldie.. after my studies, I was looking for my first job and did interviews. In one of the companies, they asked me whether I knew C. Well yes, I had been programming in C. Ah no, that wasn't enough - they asked whether I was really good in C. I got suspicious and argued that there was the project documentation anyway, right? Turned out, no. The code was the documentation, as I had suspected.
Then my question - as freshman, mind you: "Do you have any plans to get to a more professional way of developing?"
The interview was pretty much over at that point, the boss got actually angry. Well, interviews work both ways, and he had failed. I surely dodged a bullet.

What I have: [a, b, c]
What I need: [[a],[b],[c]]
No documentation
Just numpy things ¯\_(ツ)_/¯

IF ONLY DOCUMENTATION WAS IN ENGLISH

In the past I've seen documentation that is great, and documentation that is conspicuous by it's absence.
Over the last decade, I've noticed documentation is getting WORSE.
I believe the reason for this is that those tasked with creating documentation have become so accustomed to the jargon in their own heads that they have LOST THE ABILITY TO COMMUNICATE IN ENGLISH, and as a consequence simply don't bother.
New terms such as "ThingamyJig" are defined as "A Collection of ThingamyJigs" — so you end up going round in circles and get back to square one.
They make little or no effort to provide simple examples.
If only companies who create languages understood that those who wrote the language may not be the best people to write the documentation.

I spent the entire freaking day on one spec — one! — and I still haven’t gotten it to pass. Or fail. It’s still just breaking. Even the simple crap is breaking, so getting the actual complicated things I need it to do working? Bloody pipe dream (whatever that means).

Just. Goddamn this system is complicated and poorly designed.

And no, before you ask, of course there is no documentation.

I want my day back. 😡

no fucking documentation

no fucking explaination

and your example doesn't even work

let's just run around in circles until we all die

waiting to exit this 🤡 world

yeah, i know, everyone is like "why can't you chill more"

because this what we are stuck doing 8-9 hour a day!!!!!! this is literally our lives just wasting away!!!! and it's not even fun anymore; you can't enjoy it if everyone is so fucking incompetant any step at being productive is fucking battle

god so sick of it

My boss asked me two days ago to fix some errors in an application. From the errors I saw it would be a 5 minute fix. I fixed the problems just now because there was no documentation on how to set it up.
After setting it up it was just changing a value from true to false...

I ruined two days just because there was no documentation. Please everyone, I know writing documentation is boring but at least write some documentation on how to setup a project.

Sometimes, usually during the evening, I lower the lights in the living room, put some of my greatest Scotch in a glass, and stare at this fine and beautiful piece of code I wrote a long time ago that I am really proud of.

I like reading documentation.

BUT I really hate writing one for a project that I have nothing to do with it.

I am charged to write a documentation just because they think I am good on expressing and structuring ideas.

F_M_L

Just want to write code... no emails, no documentation, no meetings.

I've just realised something... I haven't ranted about work for a looooooong time.

It seems now all the monkeys have left the team and we've hired young people that actually knows how to get things done without blowing things up (though still need to work on documentation, bus factor still too high). So I'm no longer cleaning up their shit or the bugs they're too incompetent to analyze and fix...

No documentation....yeah....just figuring it out! 🤔😲

I've been working as a programmer for 16 years now, and would say I'm not inexperienced, so it's frustrating to feel like a noob after months at a new company when they have poor internal documentation, hundreds of repos with default readme, pretty much no use of docker, sub standard equipment and use their own weird software for deployment. It's hard to meet expectations under these conditions.

I have finished some docs for my project.
Going to bed.
GIANT insect in my bed.

I think i'll not sleep tonight...

I prefere the doc work.

Fucking piece of shit, i want to make a fairly thin app with some native functionality and

Flutter - no documentation whatsoever, what a surprise
React native - i need 3 extra modules just to do what i want
Cordova - fuck no
Litho - seems fine but i dont wanna use native, i dont even have adb on my laptop

I love to code but I hate to configure.😡😡

OK I hate to configure when it takes several hours and when there is no real documentation.

"A perfect implementation of the wrong specification is worthless. By the same principle a beautifully crafted library with no documentation is also damn near worthless. If your software solves the wrong problem or nobody can figure out how to use it, there’s something very bad going on. " - Tom Preston-Werner

Rant

I'm tired of this shit!!!

First I receive a task to create a new functionality for the app that I'm working on and some documentation (this is the only good part of all the rant) but no design.

It's been 2 weeks since I got assigned to this and still no design, no assets, no API calls that ACTUALLY WORK.

Today was testing a plist to get a banner link, and for 1 hour that little fucker didn't returned the image I was asking.

Better, I wasn't getting ANY IMAGE. Turns out that the link sends me to a HTML URL that doesn't have any image... go figure!

So I've been working on this from some images inside the PDF with the documentation given.

Oh! Wait! There's more!

The cherry on top is that I'm implementing a chat/voice call/video call into the app and the framework that I will be using is being created now, and it's not even finished!!!!!!

Scouring the internet for documentation, then you find a promising google result

THEN IT'S A FUCKING FORUM THAT I HAVE TO SIGN UP FOR FIRST

no thanks

You know what's fucking horrible?

Implementing new features to an Android app in production that another dev wrote...

...which has no architecture, no documentation, no modularity, no testability, everything runs on the UI thread, filled with spaghetti code and it somehow works smoothely so I have to not fuck it up.

Oh and I'm also a junior. So fuck me, right?

So I handed in my official resignation last week as I will be changing to a new job next month. So one of the last big things that I have been working on is a Jenkins server for the rest of the team to use and currently writing up the documentation for it.

However I haven't been told who I will be handing over my work to, but the bigger thing I feel is that even if I write all the documentation, no one will actually read it. Reason I think this is because I doubt anyone else in the team will even use the Jenkins server. The major issues are that no one writes unit tests and don't even understand what CI is!

So right now it feels like my final month of work will all be for nothing and makes me wonder if I should even bother writing documentation, especially if it isn't going to be handed over to anyone.

Fuck Shibboleth and its documentation, fuck examples for configuring it, ops sorry they have no examples at all so fuck them, fuck SAML fuuuuck!!!!! And I almost forget FUCK JAVA

Api with no documentation and obscure endpoints

So....
I was just told why the company's code has no documentation...

Quote: "It enforces devs to write simpler/better code"

Oh and added bonus - the whole backend is PHP with a bunch of tweaked libraries.

The worst part of being a senior software engineer for a team is that the legacy code of the company is not clear, and there's no documentation.

React router is shit
I have never seen more retarded library.

Not only those suckers change the 100% of the API every fucking update for no reason, also they have the most fucked up documentation ever.

No search in the docs!!! Fucking bullshit examples with no such easy things like how to create nested routes.

Please, stop using this piece of shit, I'm tired of working with this fucking abomination. Hope they will delete their shit repo one day.

PM: "Can you take a look at this app and see if you can find why it's producing errors and fix it"
Me: "Yea sure, can I see the documentation so I might be able to understand the system and why it's doing that?"
PM: "There's no documentation" ... "Also it was cowboy coded by an intern"

When I got in this job:
No test, 0% coverage
No teamwork
No documentation (front and backend)
Senior doesnt want to talk

1year later:
We have test prolly 10% coverage
Still no team work
No documentation
Senior doesn’t want to talk

Ps: tried doing documentation but I cant unless my senior will help me because I dont know the ins and outs of the codebase.

I say crap.

Part? The whole damn thing.

We are supposed to be practicing agile, but I haven't seen a single sprint plan till date. All we do is solve issues that are reported from production/QA.

Nobody follows proper documentation, no reviews, no proper version control... Can't wait to finish my contract here and get the hell out.

Worst documentation is the one so confusing and poorly written that even no documentation would have been better. And more than small projects, large corporations who don't give a fuck *ahem* Oracle *ahem* are guilty of this

The best kinds of comments:

/**
Gets user CC info datas.
*/
public Object getUserCCInfoDatas() {}

If you really want to outdo yourself:

/**
Gets user CC info datas.
@param someshit Outdated docs ftw
*/
public Object getUserCCInfoDatas(String unrelatedToDocAbove) {}

Honestly, no documentation is better in some cases. At least I can't be angry about their shitty quality... And they don't waste my time.

Currently doing my final handover, the "senior" developer is trying hardly to find things for me to change not in the code, no, in the documentation. Bitch, this is the ~most~ only documented project in the whole company!

#5 days left.

I've seen several rants on here about poor documentation on great libraries. Well I just spent 9 hours in a car today and I realized that even the ones that have great documentation absolutely SUCK at being mobile friendly. I'm no web developer but how freaking hard is it to optimize your stupid website for small screens??? There are a million frameworks out there you can choose from PLUS it's almost entirely text so it can't be that hard!! I have to zoom in about 300% to be able to read it, then I have to scroll back and forth because it no longer fits on the screen.

Whenever I have to ask about how certain code of someone else works, I feel bad. I feel like I should be able to figure it out on my own.
On the other hand, if people ask me to implement something within their code, that I am not familiar with, I kinda expect more info? Like if you don't have any tutorials or documentation on your tool, be prepared to answer some stupid questions about how to set it up and whatnot. How else am I gonna know how to start with? Having to read the entire source code is a massive waste of time, no?

tl;dr: if you don't provide documentation or tutorials, be ready to answer stupid questions.

Serious question for anybody who has dared to understand manager-speak: Do you know what a 'Task Rewind' is? We have it in our documentation, but google gives me no help as to what the hell it could mean.

...Or should I just take my original gut feeling and classify this as yet another word for the clown dictionaries?

- my (non-dev) supervisor at my job
- no documentation
- no source control
- people working in the same team with completely different programming/domain knowledge levels, but also very different ways of being
- bad within-project communication

Luckily not all of them are about my job. We do use source control.

Yay, I inherited a project with no documentation that is soon to be out of the prototype phase in a tech stack where I have no experience. It is already sold to customers and they expect it soon.

There are so many bugs, never been code reviewed but the main functionality semi-works :(

Technical debt.... so much technical debt it’s driving me crazy!

It’s not only that there’s commented out lines in abundance, methods and whole classes not used anywhere anymore in a decade and code using not only deprecated standard library functions, but some that have been REMOVED in earlier versions of the language (have no idea how those have even stayed functional...), and documentation that has very little to do with the reality... but today, I submitted a pr to fix the documentation for setting up dev env - which was outdated already when I started a few years ago!

I know we are understaffed and busy, but c’mon - it doesn’t take much to leave the code in a better place than when found...

I don't know why they made so many algorithms, data structures and big O questions during interview, when all they wanted me to do was to maintain some legacy, tight coupled, spaghetti code with no architecture, documentation, tests nor any kind of engineering behind :/

WooCommerce is shit

Just try to find anything in the documentation on their retarded website and you will get what I am talking about.

A billion of unstructured links. With absolutely no sidebar or table of contents.
IMPOSSIBLE to find any fuck there.
It is far easier to build an e-store from scratch, than to customize their ugly monster.

Now look Laravel or PHPunit documentation to compare how it should be.

It's disgusting how a package like compress-commons can have 1.3 million weekly downloads yet no documentation whatsoever and not even any relevant comments in the code. Honestly fuck the javascript ecosystem

Be me, get a consultant job, go to a supposedly great client that has fame of getting scouted by Google. (attn: I doubted all this shit before I started)

Learn the basics by a awesome mentor and trial/error stuff at the same time to get the hang of things, after that was done, I noticed there was no documentation whatsoever, code is spaghetti and your documentation, good luck!

Royal spaghetti, you can't make heads or tails of it, dev code in production, empty try/catch blocks, empty statements, if (true)... (incl. their core classes)

Keep in mind this is a multi milion dollar company...

Someone please understand my pain...

- i = ++i or i = i+=1
- No Documentation
- Not Splitting up a Stylesheet
- function()
{ }
if(){ } (inconsistent style)
- Using a ton of if's instead of a switch
- Installing Nvidia drivers manually on Linux thrice! Had to reinstall it everytime!
- sudo rm -rf /
- Being unorganized in terms of personal projects.

Working on codebase of a 20+ year old system that the company I work for bought five years ago and in that time there’s been no refactoring, no security updates, no attempt to create automated testing (there is none), new features have just been built on the codebase with no regard for quality and it’s just spun into the horror cesspool that it is today.

I joined one year ago and I’m slowly refactoring the codebase and updating it to get it to a more modern codebase, cleaner code, faster load times and creating a ton of dev documentation so the devs in India can start getting into best practices and start producing quality code.

Me: "Need help with build config problems, please help almighty documentation page!"

Docs Page: "Nah fam, I got 4 headers about problems with no text, a blank code example, and 2 error 404 pages."

And that's why I don't like build pipelines.

There is a commercially sold ERP solution that has it's DB schema in excel and Other documentations in MS Word. And its not even properly structured, no schema diagrams, last updated for a 4 year old major release 😒😫.
I have to develop a custom module for it and that requires building an ActivexDLL Project in VB fucking 6 😭😭 .

VB6
Unstructured Documentation
Legacy code
Incomplete documentation
FML

Tell me if you want ss in comments.

This little underscore (actually the absence of whomst'd) was the source of a very frustrating bug.

I tried to debug the sources of a 3rd-party library to no avail, but all I had to do was to read the documentation for the 1001st time. 😤

Documentation? That's the stuff of dreams for us.

Instead we have ancient code written by people who have long left / forgotten with no idea what the cryptic mess they left behind does.

Is it normal to have to sit in hours upon hours of handover sessions for a spaghetti software solution?

There's no documentation, we have to create it, hence the hours upon hours of handover sessions.

I'm so fucking burned out from the past two weeks' meetings.

Taking over development of a system from some other guy who just straight up dropped it with zero documentation. The code looks like he wrote it after watching some getting started tutorial. There is no structure. Some methods and statements are just empty. And he spelt 'connection' three different ways in the same file.

God help me...

Took over a NodeJS/SailsJS project from a previous developer that is no longer working at the company. There's no documentation or requirement docs and the models need to be rewritten as some have up to 67 attributes in them.

Looked through the source code file by file to see how bad it was and it will more than likely be easier to start over then to try and refactor and cleanup the existing project into a usable state.

As bonus, I was given the option to switch the entire stack if needed as well.

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.

How fucking hard is it to write simple documentation with everything you need to get something working for fucks sake. Several fucking hours of my life later and I'm still no closer to figuring out what the fuck is going on with something that should simple. FUCK!!

no one taught me how to host anything web, i had to figure out how to get things live by myself. it was awful, documentation on that stuff sucks, but i got through it knowing far more than when i started.

Yea sure, I'd like to refactor your fucking 1000 loc spagetti code "module" with no documentation at all...

Coworker: So should we just make a living document to keep track of how all these objects are going to interact with each other?

Boss: No, are you kidding? No one reads documentation!

I mean... he has a point...

How the fuck does a library with such shit documentation that makes no fucking sense have 43k+ weekly downloads

No documentation, even if it's for personal private projects.

I still can't wrap my head around code I made 2 years ago...

anyone else, when reading documentation to some API, and you come across section titled "doing [whateveritis] via SOAP", you just laugh "hahaha, no way, sweety", and scroll past that section as fast as possible? =D

Create a library without writing a proper documentation.

1. I'm lazy.
2. No one is going to use it anyway other than me.

AAAH, fucking aws. Why the fuck do you make documentation if it doesnt even make sense. I struggeled for hours to let your cock sucking Cognito work and I'm still fucking stuck. Why is there no proper documentation or tutorial available for nodejs. This pisses me the fuck off. I hate this piece of shit.

Ah... I feel better now.

So third party devs that my employer hired to build our web based application used fucking spaghetti jQuery to validate all of it with no documentation. What a bunch of cunts.

So, I joined a hardware company as a software developer few months back. I'm working on a c++ code base with thousands of files and no idea what the code is supposed to do.

I got one overview of what the product is supposed to do, which contains mostly electrical engineering jargon that I have no clue about.

Now my manager wants me fix a bug in this code. I have no clue what the expected behaviour is and no documentation whatsoever, and literally no one in the entire country who understands the code.

When I started this job 4 months ago, I was given a grace period of a week to "get into the groove of the code". I asked the lead dev where on pulse (intranet) the documentation was, he laughed and then resumed what he was doing. I shrugged it off and continued scrolling through the code.
A week later, working on a story, I'm stuck at why a particular function exists. I say "it would be nice if there was documentation, where is that anyway?". Lead dev replies, "one thing you should know about this company, there is no documentation unless it's API related".
Last month's retro, 80% of our (mine and lead dev) problems were related to a lack of kt, I laughed.

There's no provisioning script. Code repo's there, but no configuration files. Missing folders that break the app. No documentation on what to install, what directories to create, NO instructions. Nothing. Just an empty Ubuntu vagrantbox and a git repo. Took the entire morning and then some, just to replicate the dev environment. Fuck

The principal developer who wrote one of our APIs is on annual leave, there's no documentation.

It's in another language.

Add some points into scrumwise for 'Deciphering hieroglyphics'!

I am working for a company that has developed a custom CMS but has no documentation written for it and now no-one knows how it works... Best thing is that it advertises it in its website. Good job!

Almost..

I am a web developer and assigned in a project as Infrastructure Engineer AND Penetration Tester because no one is available. I survived that hellish experience, i learned clustering and other advance stuff on my own, studying even late at night, no training..just youtube videos. PM (who is currently has little to no involvement in this stage) has very little appreciation in what im doing(research, server estimates, diagramming, documentation, planning)

That's the kind of project I have to work on now which was developed for a year and has no documentation at all... 😰🖕🏻👿

Started a new job this week, picking up the front end development of a property management system, since they're old developer just left.

Oh my god was his code bad, inconsistent use of js versions e.g only sometimes using lambda for anonymous functions, variable names that were a single letter, no comments, no documentation, and over 30000 lines split into almost 30 js files, following the logic of it is as fun as a hedge maze with no exit.

- Implemented oauth1 - no body hashing
- URL contains credentials in plain text
- Used Azure API management feature as a proxy of the our API, however the documentation was on the our API, thus exposing the API URL with no management to developers.
- easy resource DDoSing because each trial user got a DB, the registration process did not have bot checks. You could literally freeze the db instance by spamming registration requests.

the worst documentation I've dealt with was (sadly) some I wrote myself.

We had a project - build with no maintenance agreement attached. so I half-assed the docs and tests... a year after launch we sign a support agreement and I'm struggling to figure out how the damn thing works!

Just got handed a dozen servers. Documentation shows a (Linux) database cluster is using ldap authentication. I try logging in with my creds. No joy. I look up the root password and log in.

Not only is it not configured to use ldap, it's also not clustered.

I need more coffee.

Apple just changed their file system to apfs across the board, but no recent documentation on the release. It automaticalky changes from hfs+ when you install the macos 10.12.4 update. In early docs it says that time machine is not supported, but surely they cant kill everyones short term backups?

Trying to learn Angular and reactjs, reading up the tutorial or documentation...

Why the hell are there ten million more shit I need to look at first? (such as rxjs, Babel, webpack... and whatever the fuck they are)

Now am I supposed to master those ten million tools/libraries before I can proceed?

Of course there is no ten million but mentally it's no difference. I'm just fed up with this.

Integrating Google recaptcha into my web service. For some reason it always errors, both on a production and development environment, correct domains configured, and with he simplest setup. I'm fucking lost, documentation assumes it actually works. Similar errors on stack overflow and Google groups either got no answers or have obvious issues.

Fuck this man

man this google android documentation fuckin sucks shit

i have NO idea in what order to read the document

they did a great job separating components into each different category but there are a lot of categories that use the knowledge of other categories so all of them are dependent on one another

and even when i read the documentation, they explain it like this in steps:

1. do this
2. do this
3. do this
7. do this
8. do this
45. do this
83. do this
84. do this
85. do this

and for the last step, step 2357 do this

The CEO just made a huge huge push-over to the developers.

He doesn't have any customers/clients and wants us to push our limits to make a Service Oriented Architecture where legacy code is needed to be revived, no documentation, and a single motherfucking mobile developer who has 3 projects already in his 1st month of stay.

!rant

Nothing worse than recieving little to no documentation/requirements on a project, garbage in = garbage out...

Something that really grinds my gears recently is ”black boxes”. I get a dll to work with, completly without documentation and any desceiptions. An hour later people asks me, ”so hows it going, done yet?”.
No, im not done yet and I probably wont be in any near future you fucking morons, start documenting your fucking software as normal human beings.

If you can understand the documentation then syntx tutorials aren't for you. And you're no beginner

JavaScript libs have a massive problem with quality and especially with quality of documentation and error reporting

For the entire day I've been staring at this stupid error and can't figure it out. The documentation stating that the source function sets the source dir, but not actual saying what 'source dir' means or what paths are resolved against it is no help either

npm is actually really awesome but almost every library I've tried just fucking sucks

In freelance world,

Some Computer Science degree holder (from client company) explain how good are they in Software development.

But when as soon as my team and I (after got criticized by this guy for the fact that my team and I don't have a degree in computer science) review their code, the code is a bunch of spaghetti! No proper Architecture, no documentation, and everything in one class?

Damn...

Just started a new job at a big co.
Expected to implement small new feature, no sweat about 30 LOC. Unfortunately no unit tests, no way to test without real data.

Spend 2 weeks trying to get it to run on the test rack. Lo and behold the entire testing system has been sitting broken for months and nobody knew. Why is all the documentation so vague!???

The project with the worst documentation is always my own. I always come back to a project and have no idea what anything does.

Nothing is more frustrating than working with technologies with very little documentation and no fucking resources online. Trying to debug a Program AB AIML project for hours. StackOverflow has unanswered questions.
Few more hours and I will start pulling my hair.

!rant!
I have replaced a dev in a company where the project already started and it is shit! The project is directed already to fail, no requirements documentation, no proper communications, and a stubborn dev teammate.

aaaaaaaaaaaaahhhhhhhhhhhhhhhh!!!!!!

All the documents that we have right now is I am the one who created it. Like c'mmon! this project is already going for 1 year and I recently just joined the team!

So I'm returning from parental leave on next week...
One of the projects I'm involved in, was at 10% progress when I left, had planning and documentation made by me, development environment and test suite setup by me and had tests and was being reviewed.
Right now it should be arround 75% progress, no longer is being reviewed, planning is not being followed and no tests have been made since I've left...
Why bother with dumb ass devs!

There is nothing common about "Common Expression Language"! Google is up their own arse again creating unusable and unlearnable standards that you suddenly have to learn. There is NO documentation about this shit at all, except for the highly technical and human unfriendly language specification.

Why why why the fuck would you assign the same variable name at the start of a function to completely different data? These aren't params, but variables being assigned different things, no comments, no documentation, crucial in the operation, but assigned wildly different values with different behaviors through the code.

When you join a project that has no testing, no component policy, a lot of css mixins, that has to work simultaneously as a pwa, android and ios app.

Oh, yes, obviously no documentation at all *flips table*

Magento, it's in the same category for me as drupal, joomla, WordPress,... Bloated, slow, general pain to work with... No learning sources, cap of a 'documentation'...

So you're telling me that you have no documentation, and your app business logic is made on only observables?

Uh no thanks.

Custom php api for huge known national software. No frameworks. Not following mvc structure. No decent documentation. Im the new dev and like how the fuck should i catch up before they think im not productive

Just found out that I have been reassigned to maintain an in house shitty project... It's full of crap code, no documentation, has lot of duct tapes to keep the project together and 20+ open bugs and issues...

I am so happy with my current project. But my manager is always pissed off at me for no apparent reason.

Fuck this shit... Any excuse or advice to dodge this BS project? Can't quit job, I am getting payed alot here.

Great how I’ve just started a new job, haven’t been given all the licenses I need to run the software, there are multiple products with little to no documentation (and by none I mean the word “Architecture” is all there is in one of the main products ReadMe file) and I’ve a year of this! How is a company that’s this big not in any way documented like! This is gonna be long 😑

Let's see what's on the menu today:

* Web Application Catastrophe Special *

Includes, but not limited to:
- Orphaned server processes in the configuration management cluster
- Microservice back-end architecture with no API documentation
- Poorly implemented cache microservice with no documentation
- Stale data causing everything to be shown as down in production, despite everything running fine

Cost: 1 developer's sanity

Took a software engineering class at my university. The class was online which is common at my school.

The entirety of the class ends up being the prof. scrolling through a google doc while sharing her screen. No watching her program stuff, no opportunities for us to program in class, nothing. Basically like reading documentation for 3 hours.

The final project? A fucking command line tic tac toe game written in python.

My group asked if we could do a tic tac toe multiplayer web app instead and she denied us with no reason

Complete waste of time

no matter how many books i read about a particular technology, if i don't read the official documentation ( no matter how large it might be ) of that technology, i always feel dumb and stupid

"Go check out the EAGLE documentation so you know how to properly parse its generated xml files"
(The whole docs just says "sorry, no documentation" every fucking where, not just the part in the picture...)

Google Apps Script is probably the worst scum of the earth I’ve come across in a while.

Shit documentation and JavaScript 1.6, really?

No wonder nobody uses this crap and has proper implementation of a vast variety of applications.

Convo b/w me & lecturer.

Me: Is one line that explains exactly what it does okay?
Him: No.
Me: Okay I'll make it a paragraph explaining it a lot more in detail...Is that okay?
Him: Nope, you need to elaborate for laymen.

I don't know what more I can add. Sick of useless documentation. Any one else have this problem?

Here's a fucking challenge:

Generate an MD5 hash in React Native!

crypto - NOPE deprecated, react native throws when you try to import it anyway

react-native-crypto - NOPE, needs to make use of a shim that recursively edits node_modules... hmmmm yeah you think thats a good thing to have?

react-native-fast-crypto - NOPE, no TypeScript types, no documentation in general, only supports sha512?! WTF

garbage fucking idiot tooling stupid dumbass stupid splat splat barf splat

Spent all week 40+ hours attempting to get my companies application up and running using the documentation written by one of the developers. Mind you, 20+ hours pulling and replacing files. Get to the end and nothing works, contact the developer that wrote the set up guide, and he has no idea how to fix and at some point admits her forgot some steps in the documentation and doesn't know what they are. Spent over 6 hours in troubleshooting meetings with that dev and another dev and made no progress. The documentation devs answer to try and fix it every five minutes, "do an iisreset". Fuck you and the camel you rode in on.

I have become the only thing I always hated in a developer. Building a project without a proper documentation.
As a solo developer in a company where I have to do database architecture, front-end, back-end, testing, NETWORKING (I am the most ignorant guy when it comes to networking), product design, there is no time for documentation.

But hey, I have structured the project, files and functions (with comment, parameters type and return type) properly and I understand what I've done even after 4-5 months without touching that specific project so I got that going for me which is nice... I guess.

"I don't know about changing that part of the platform"
-"Do you see any other way?"

"No, but this one is pretty complex"
-"Would you like me not to do it?"

"No, but like, really test it, OK? It's a very complex part of the platform"
-"Would you like me to include the phrase 'this was really fucking complex' in the release documentation?"

Sometimes I think my boss is against coding :/

I feel like crying because I couldn't configure ERPNext on windows (Virtual Box). Damn thing showed this error "Already Registered, There were problems" and redirect me to homepage.

Hate this when there are no error codes or no proper documentation.

Tried every possible solution in past 4~5 hours. I'll sleep

Is it me or most developers just write code so it compiles and passes tests?

No documentation, no standards, no "good practices", no"good design", no software principles, no performance analysis, nothing.

My coworkers are great; they actually manage to solve problems in really unexpected ways.

Problem: documentation is not up-to-date with latest changes.
My fix: update it, make sure it has all the latest modifications.
Their fix: if there's no documentation, they can't complain about it...

When a senior asks me, the guy who started 4 months ago about documentation on something that they’ve been using for several years. Haha, yeah bro, wouldn’t all of our job be a lot easier? I’ve been going down entire rabbit hole networks trying to find credentials and API tokens for the last month because there was no documentation 🤷🏻‍♂️

Those anyone has created a Chrome theme?

Dunno if Im a dumbass or there is no fucking documentation.. I have seen old forums of ppl coursing google for making it so difficult (apart from the standard upload a picture bs)

Trying to port a legacy Firefox add-on I didn't write to WebExtension. Failing so amazingly...

Vague explanations, no tutorials. Mdn has a nice documentation but no tutorials. What's up with that??

Also, JavaScript. And stuff I didn't write. Just perfect. 😑😑😑

When you have to work with functions clearly no one gives a fuck about... because who needs documentation... like... 2 decades later!? Oh yeah sure it might change tomorrow...

Your time is better used somewhere else, let the intern write the documentation. While the project was transitioning to a whole new team with no one from the old one.

Service I was needed to integrate to our system had such poor documentation and a separate pricing tier to access their APIs...

... Not having it. Used Guzzle to perform both the authentication and their search page, then made wrote a function to web scrape the result.

Job done. 😎 And yes, I have no shame to say I love PHP.

Losing faith in Netflix and their awesome open source projects.

Had a hard time trying to install Security Monkey : poor quality quickstart Ubuntu-only, almost no documentation, same instructions for latest (aka dev) and stable (aka prod) version, no depencies list ... oh and the UI display well only on Chrome ..

Then you surrender and just want to check the dockerized version they provide : it doesn't work neither (build fail or back end process just shut down) !!

I'm done ...

I hope there's a special kind of hell for project leaders / execs that make the decision to take down the documentation for older versions of a software.

I know we should have upgraded a long time ago, but come on. I have no clue what's going on now, and not much to go on either! All the documentation links in the configurations just redirect to the project's github repo, and I sure as hell am not going to read the whole source code just to find the possible logic behind the issue!

Ugh... Days like this frustrate me so much...

So started building a game engine in Vala using SDL2, I have never built anything from scratch and decided to do it with no tutorials and just looking at the documentation on valadoc... So of course all of the pages for SDL2 and it's sub components show up fucking blank... Well isn't this dandy .-.