Got this from a recruiter:

We are looking for a **Senior Android Developer/Lead** at Philadelphia PA

Hiring Mode: Contract

Must have skills:

· 10-12 years mobile experience in developing Android applications
· Solid understanding of Android SDK on frameworks such as: UIKit, CoreData, CoreFoundation, Network Programming, etc.
· Good Knowledge on REST Ful API and JSON Parsing
· Good knowledge on multi-threaded environment and grand central dispatch
· Advanced object-oriented programming and knowledge of design patterns
· Ability to write clean, well-documented, object-oriented code
· Ability to work independently
· Experience with Agile Driven Development
· Up to date with the latest mobile technology and development trends
· Passion for software development- embracing every challenge with a drive to solve it
· Engaging communication skills

My response:

I am terribly sorry but I am completely not interested in working for anyone who might think that this is a job description for an Android engineer.

1. Android was released in September 2008 so finding anyone with 10 years experience now would have to be a Google engineer.
2. UIKit, CoreData, CoreFoundation are all iOS frameworks
3. Grand Central Dispatch is an iOS mechanism for multithreading and is not in Android
4. There are JSON parsing frameworks, no one does that by hand anymore

Please delete me from your emailing list.

When the API is not documented.

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

4 years ago I was placed on probation for not having the special format in source control check in comments. When I asked, the 'special format' was
clearly documented on page 18, sub-section 4, sub-paragraph 2, "All check in comments will include the solution name, separated by a colon,
and why the code was changed." My check-in comment was only missing the colon. Indecently, over 80% of the other comments consisted of 'adsf',
'bug fix', and several 'BOOM!'s. So I mistakenly said out loud 'This check-in policy appears only to exist to allow management to cherry pick
developers they do not like, find something wrong, and put them on probation.' That comment got on a 30-day ‘corrective action plan’ for openly disagreeing with a
company policy. Today, all those managers were either fired or quit and now I set policy. Dear Mr. ex-Bosses, I won.

##Real fuckening STORY##
Angry client: this feature is not working like we discussed !

Me: it is.. *giving some explanation*

Client : no, this is not the right way

Me: But this is what we documented while gathering requirements, and YOU signed in the documentation..

Client : that long document? you don't expect me to read all of that talk just for this simple feature..

Me inside: *killing him 5 times in 5 different ways

*casually clicking through aws services*

*discoveres ses (email service)*

*tries it out as email driver in laravel project*

*discoveres you are in sandbox by default, means you can only send emails to yourself*

*reads documentation, says to get out of sandbox request a limit increase with default values*

// 200 per day, max 1 per second

*request what is mentioned*

*while waiting, find threads of people with the most well documented use case requests getting denied*

*pretty sure i will be denied to, thinking of starting to look elsewhere*

// next morning

*opens mail*

# your application is now out of sandbox and can now send 50k emails a day with a max of 14 per second.

At an internship we had to make something and appearantly I learned php quite wrong at study so they decided that I'd have to pick a framework to program with.

Fair enough, a little research and I found one.

Held a presentation about the progress and mentioned the framework I used and everyone seemed quite impressed.

After the project someone came to me and asked me to take another look at that framework.

It appeared to be veeery fucking old, hardly documented and quite shit actually.

"so why did you choose it again?"

😁

So I was looking at the linux environment at my new job. Found 2 VM's in the local network, only one of them is documented. Noone knows about the other one or what it does, let alone usernames and passwords.

Spent over an hour trying to break in, only to find out that a couple of bored devs, that have long since left the company, set up a game server on there and noone noticed it for the past 3 years..

Requirements vs Delivery - Guide to Programming
This one is a killer and I've received it in multiple forwards in office email, and we always have a good laugh seeing this joke.

Client: “Our next requirement, and this is something big you know, we need an elephant”
IT Team: But why don’t you adjust with a buffalo, even it is big…. and black?”

Client: No, we need an elephant only, let me explain our current process……” (client explains for an hour)
IT Team: Fine, I understand your requirement. But our system supports only a buffalo…

Client:We need only an elephant!
IT Team: Ok, let me see if I can customize it for you”

Requirements are taken as follows:
Client wants a big black four legged animal, long tail, less hair. Having trunk is mandatory. The same was documented, signed off and sent to offshore for development!

At the Offshore Development Centre,

Design/Development – Based on requirement all features are supported in base product (as buffalo), for trunk alone a separate customization is done.

Finally the customization is shown to client:

Don't mind me, just writing maintainable, legible, commented and documented code. What's that, an email validation? Let me just
/^(([^<>()\[\]\.,;:\s@\"]+(\.[^<>()\[\]\.,;:\s@\"]+)*)|(\".+\"))@(([^<>()[\]\.,;:\s@\"]+\.)+[^<>()[\]\.,;:\s@\"]{2,})$/i

Boss: hey mech eng, we need a setup modification

Mech: no prob, boss, we can have it prototyped in 3 weeks, industrialized in 2 months

Boss: oh, right then, go on

---

Boss: hey, Soft Eng, we need a functional modification

Soft Eng: no prob boss, we can develop it in 4 hours, tested and documented in 2 hours and integrated and shipped to the client by tomorrow morning

Boss: what??? One day?? You just need to edit a couple of lines of code! I want it ready in ten minutes top!

"This is not a bug, it's a documented limitation"

The first documented time of "impressing ladies with my computer skills" 😄😄

I was 4 or 5 yrs old, using Windows 98 SE

Spent most of the day debugging issues with a new release. Logging tool was saying we were getting HTTP 400’s and 500’s from the backend. Couldn’t figure it out.

Eventually found the backend sometimes sends down successful responses but with statusCode 500 for no reason what so ever. Got so annoyed ... but said the 400’s must be us so can’t blame them for everything.

Turns out backend also sometimes does the opposite. Sends down errors with HTTP 200’s. A junior app Dev was apparently so annoyed that backend wouldn’t fix it, that he wrote code to parse the response, if it contained an error, re-wrote the statusCode to 400 and then passed the response up to the next layer. He never documented it before he left.

Saving the best part for last. Backend says their code is fine, it must be one of the other layers (load balancers, proxies etc) managed by one of the other teams in the company ... we didn’t contact any of these teams, no no no, that would require effort. No we’ve just blamed them privately and that’s that.

#successfulRelease

Rage..

Boss: 'I've got a PowerPoint presentation with 45 charts in it. Oh, and a huge excel sheet with the data for it. Please build some of the charts in our own software, with the given data.'

Easy, I thought.
Yea, thanks to the person that gave my boss the data.. The half of the important columns were removed (privacy stuff).
And.. Excel? Oh, and his calculations are nowhere documented nor consistent.

I converted excel to postgres, easy.
It took me 2 hours to fkn research what he calculated in one line chart, just to implement it in like 10 minutes.
2 hours, man I could made awesome stuff in that time!

I guess I should write this in CAPSLOCK to make it more interesting. I'm just raging in my head 😂

Just downloaded some big ass codebase and the first line i read is:

"// The source code is not well documented, but every advanced programmer will be able to understand it after some time."

Well... let's find out about your definition of "some time", Dickhead!

Literally how one of our developers documented functionality for our program in OneNote

I JUST FINISHED MY FIRST NEURAL NETWORK!!!

But first of all, as I know you guys, it's spaghetti code and even I as a newb see places where I used too few-dimensional array or passed useless parameters or simply wrote too many redundant lines of code. I know it. I will make it MUCH better next time. Period.

But OMFG this made me scream from happiness today!! Just these few seemingly random numbers... I'm really done.. That's why I jumped into coding year or two ago..

And for some background, I didn't study any IT school, I'm just highschooler (general grammar school) who traded gaming for learning. Also my maths teacher teached NNs on university and is very keen to teach me, so that's that.

Now I wanna make the best out of it and I'm looking forward to write some well documented and flexible library, parallelized and everything (I'm gonna learn a lot in the process of doing this) better then FANN.

Maybe I'm gonna fail(99% probability but hey, I'm programmer beginner, I still think I can code everything I want). But if there is just one moment like when I saw this screen today, I'mma trade my life for it.

Sorry for taking your time guys, I was just genuinely stunned... A lot

Hello, world!

Hey, it's me. It's been awhile. How have you been..? :3

For those of you who don't know/remember, I'm the lead developer of a Desktop and (to-be) Hacking Simulator Game. My project should still exist somewhere on here. I just thought I would hop on, and catch you guys up on my progress. ^~^

So far themes are a thing! You can add custom fonts, wallpapers(or just a desktop color) and set the color/opasity of everything in-game!

I have also implimented a modding API. It's under-documented, but it works very well! You can add apps, commands, or even redesign the entire interface using it. It executes modded functions on specific events, so you could really have it do anything.

As of yesterday, there is also a simulated FileSystem. You can navigate it using in-game terminal commands, and you can create and remove directories.

(in-game screenshots are also a thing, you can even set a timer - ps: this is a 100% mod! As are all apps and commands in the current unreleased version. PM me on Telegram @TheCyaniteproject to get a copy~)

Worst experience with cs profs? Oh boy....

Databases lab: "You'll need to work of this snippet, if your IDE tells you it's deprecated you don't need to care about it"
If you want to imagine the quality of the code base we were expected to work upon just think about that attached xkcd comic, basically an undecipherable black box.

The instructions where at the same time micro managing everything (he gave us frickin variable names to use, and no good ones, no the database connection had to be called datbc, yeah very descriptive) and yet so obfuscated that I'm not completely sure he didn't resurrect Kant himself to ghostwrite for him.

He also didn't like us to use any Java feature that was to 'modern', for example for each loops since "they offer no benefit over normal for loops".

Further, everything we wrote had to be documented with a relationship diagram and a uml. So far no problem if he hadn't invented his own flavor of both (which can be read about in his book).
Oh, and he almost failed me because I used a lambda expression in his 'code on paper' exam and this "arrows are a C command" I "must have been confused"... which is glorious coming from the guy who can't get operators and commands straight.

On call: part 2... WHY THE HELL ARE YOU GOING TO ASK US TO STOP RESTORING *YOUR* SERVICES SO *YOUR* CUSTOMER HAS ACCESS TO *YOUR* STUFF BECAUSE YOU WANT TO SLEEP. If you call me because shits down, I'm going to fucking fix it. Idgaff if you're tired because it's been an 8 hour day, I've been working for 15 hours and I am contractually obligated to get this shit up asap and you needing your fucking beauty sleep is not a damn good reason to fuck up my contact...

(They got my boss' boss' boss' boss' boss' boss on the line who told them that but nicer -its why she gets paid more- and they still insisted. But at least they owe US more money to cover some *legal contractual mumbled jargon* it makes it better, and it's documented so they can't turn it around on us)

Will someone please send coffee? I have 2 more days of this.

"Kids, which organization has poorly documented projects?"

"Apache Software Foundation!"

"Kids, which organization has poorly maintained projects?"

"Apache Software Foundation!"

"Kids,Which organization breaks backward compatibility with each release?"

"Apache Software Foundation!"

I fucking hate being the "ask me anything" guy in the office, how am I supposed to code if people interrupt me every 5 minutes?

OH LOOK AT MY HEADPHONES! MAYBE I'M CONCENTRATED AND HAVE SHIT TO DO! I mean there are other 10 devs, why don't you go to them? or maybe try to GOOGLE IT, I HEARD STACK OVERFLOW IS GOOD YOU PIECE OF SHIT!

don't get me wrong, I like to help people but I hate when those bastards come asking questions that could be easily answered if they read the code for 5 fucking minutes.

when I have to look at code that is not mine I try to understand it by myself, even if it's not documented, and I try not to bother anyone unless is really necessary.

But then this sluggish leeches think I know the whole codebase and that can interrupt me whenever they can.

First time ranter here..

So I started to work in this big company with allegedly many talented devs.

All excited to start and learn a whole bunch of new stuff.

There was this dev, with gazillion years of experience.

We were working on a similar parts of the code base and he told me I should be reusing his module.

I opened the module sources to learn about its internals.

Oh boy...

To illustrate it best, Let’s say there was a function called foo.
It was doing one thing. There was also a function called foo1. Doing almost exactly the same thing. There was also fooA.
And I kid you not, there was a fooA1.
All of them were doing almost the same thing.

Almost all of the functions were documented. The documentation for foo would be:
“This does X. I don’t like how it does it, so there is foo1 which is better.”

Additionally, only 1 of the functions was in use...

It doesn’t end here.
There were functions named like:
cdacictad

You ask what it means?
Well it means “clean directory a copy it’s contents to another directory” of course...

Months later he is no longer with us. I deleted this module.

PS
Glad to be here ;)

I've this review with this awesome super senior developer​ in about an hour.

I've been preparing for this for months. Now he's going to review my idea which I have documented for 8 fricking pages. It's my first major presentation after I got promoted a few months ago. So, the expectations are high.

I'm super nervous and it's starting to get really cold in here. I think I'm about to retch and poop at the same time.

*internal screaming*

If I don't come back alive, one of you guys find me a husband and tell him I loved him!

*internal screaming continues*

Admin work, because its all manual:

- Each new project has to fill out an Excel tab in a workbook, with a list of all the major tasks and who is responsible. This then needs to be used to create a Gantt chart, manually, in the same tab, showing in what month a task starts and ends.

- Every month we have to manually enter status updates into a powerpoint slide on a shared deck. Which has a collision at least once per month.

- Once a quarter we need to do something similar as the powerpoint slides, but into a word doc instead.

- Once a week we need to track our time on projects in a tool that can't be integrated with (no API or anything). Meaning we can't link up a ticket tracking system to it, so again, all manual.

- Once every 6 months a new round of research funding opens up and we write proposals. The status for which are tracked in another Excel spreadsheet, manually, once a week until the deadline.

- The instructions for what to do with the proposals are so vague and badly documented that there is an unwritten rule, that for the first time you will have to ask a bunch of questions to the project manager. This is accepted by everyone and its just the done thing.

- Everything is stored in a dropbox style system, which has become so cluttered I can only find resources by saving the links sent out previously.

- Some of these updates / reports also get a 1 hour meeting for everyone to stand up and read out what they've entered.

- From time to time random things will need to be reported on to the higher ups (how many publications, research papers, patents, times and dates etc.). Again rather than a tool, a new Excel spreadsheet is whipped up and emailed to everyone on the team. Whoever sent it out, then has to merge the 20+ copies into 1 doc.

- Some of the staff (mostly the devs), use a ticket tracking system to keep track of everything. Management refuse to use it to track the things they need. Instead we have to copy paste from it into the word docs, powerpoint, excel etc.

- By far the most annoying. Management force all the above as they need the info for finance, accounting, legal etc etc. So we have to do it, but whenever there is a question from legal, management send the question to us. So despite having documented every facet of everything imaginable, it all gets ignored in favour of endless emails.

I once tried to to put an end to all of this madness by proposing the use of a ticket tracking system, and then building reporting tools on top of it.

... I was told that it "wasn't appropriate". Still don't know what that means.

Dev: This is the first version of this new app, we’re still experimenting with how it’s going to work but initial headway is looking promising. It cost very little to make, came together very quickly and is already resulting in productivity increases for users. We’re just doing a bit of code cleanup now and we’ll make a move on the next iteration.

Corporate IT: This project is being completely mishandled! In order to successfully build an app you have to determine every single requirement beforehand! It takes millions upon millions of dollars due to the complex system of governance and approval that needs to exist. Massive numbers of stakeholders need to be involved and coordinated to even make so much as a login screen! I bet your project doesn’t even have a documented list of core values.

Dev: Has you ever successfully built an app using that methodology?

Corporate IT: 😡 That’s a loaded question. I went to school to study project management and have over 25 years of experience in the field. If you had the training and experience I do you would know that tech projects are naturally very volatile and there’s nothing you can do about that!

Dev: …

I developed a simple scholarship management system for my school using Laravel, MySQL, jQuery and Bootstrap, I did it for free since college students from my country have to pay social service to get their degrees. Everyone in the scholarships department seemed to be really happy with my work and they evaluated my social service with 10/10, but yesterday they asked for one last favor: to go talk to the new social service guy who'll be supposed to maintain my project, a mid 30's dude who was really pissed off from the beginning because he wasn't even able to deploy the project, he wasn't even able to clone the project from Github. Ok, so I tried to explain to him the tools I used and how the project was structured, but everything I said seemed to piss him even more, so I stopped and had a chat like:

Me: "Look man, do you know or at least have basic concepts of PHP and MVC frameworks?"

Guy: "Yes, but I'm a project manager, not just –despectively– any programmer, and you didn't write proper documentation, it's impossible to deploy your project with the manual you wrote, I cannot work like this".

*We go to their computer and I clone and setup the project in 3 minutes.

Guy: "Yes, but I still don't know how the project works, I need everything documented. If I have to change something, I don't know where to look.

Me: "Man, that's why asked you about knowing PHP MVC frameworks".

Guy: "I cannot work like this, nothing is documented, I don't even know what's that software you're using *points at Sublime Text*. Or tell me, can you arrive at a place where they expect you to work with something you don't know and they have no documentation?"

*At this point he was really pissed

Me: "Well... Dealing with non-documented software is what I do for a living"

Guy: "I don't know what companies you've worked for, probably not big ones..."

Me: "Well, I actually work for *I mention one of the biggest music apps in the country*"

*Guy ironically laughs

When I gave my feedback to the lady in charge of the department, I told her that this guy was really pissed off at how things were done and that I wasn't so sure of him being capable of maintaining the system. She told me not to worry, that the guy became a well known asshole in the office only after a few days, and that she'll probably have to find something else for him to do. It'd be hilarious if this guy ends up capturing scholarships in the system I made.

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..."

!Rant But after seeing this I laughed like hell I need to share this to all my dev folks.

Client: “Our next requirement, we need an elephant”
IT Team: But why don’t you adjust with a buffalo, even it is big…. and black?”

Client: No, we need an elephant only.
IT Team: Fine, I understand your requirement. But our system supports only a buffalo…

Client:We need only an elephant!
IT Team: Ok, let me see if I can customize it for you”

At the Offshore Development Centre :
BA – Client wants a big black four legged animal, long tail, less hair. Having trunk is mandatory. The same was documented, signed off and sent to offshore for development! Based on requirement all features are supported in base product (as buffalo), for trunk alone a separate customization is done.

Finally the customization is shown to client, and the client faints

Addon to this, testers completed their test case as above

What you think when in college

These big companies would have all their code systematically arranged and everything organized, well documented.

When you come to the corporate world

Its the same shit you saw in college with the only difference being that you are expected to somehow keep it running since now it has actual money flowing through it!

When you document your class just right, so when you encounter it accidentally while debugging, you feel like digging in a base class, because it's so well documented and perfectly written.

!rant

Yesterday a friend of mine asked if I could help her with an assignment. The goal was writing shortest path agorithm in excel. I told her I don't know excel or VB but I will look into it. I didn't even know that we can code in excel 😅 After 1,5 hours of research and coding I writed a well documented code that does the job (with n^2 complexity of course). I feel VERY motivated after this. Because I did well job at an unexperienced environment with a language that I don't know!

Tldr: my new favorite ide is excel.

Here is a preview of my Python devRant client

The client supports both CLI and GUI modes.

This is the CLI mode using the rant command.

CLI mode currently supports dynamic importing of custom commands (and creating your own command is documented already too).

If you do not like my rant command? Download or make another one.

Also, the command execution, import, and registration process all send events to the application object. This is in preparation for allowing mods!

Unfortunately, emojis are technically 2-width, so they totally fuck up the box I draw around the rant. Lots of work to do, but I was pleased with my first visual payoff today.

i once had a manager that would fuss at every little detail.

front end had to be pixel perfect on every freaking device he could find and the backend being over documented that one liners needed a bloody comment.

//is it true?
if( true ) {

}

anything needing more then 5-10 minutes to work out required several meetings to discuss every tiny aspect in detail.

drove me insane and glad i left!

Apple you drove of delusional suckers! When will your retarded fashion devices finally support WEBP?!

A gallery page with images, and thanks to WEBP, it's 408 kB. Because Google made WEBP and handed out a well documented CLI FOSS compression tool that even can convert the source PNGs to lossy WEBP with bloody transparency. Well done, Google!

Except that Apple's shitty management can't take it that Google actually made something nice, so no WEBP. Instead, JPEG-2000 that enjoys nearly no fucking tool support. The free tools that even can deal with that mostly don't support transparency, and the encoder sucks donkeys so that JPEG still fucks JPEG-2000 big time.

So it's JPEG with matching background for iOS. Fine, but since JPEG's blocky artifacts are much more visible, the compression can't be that high, and it's 769 kB. That's 88% more image data for Shittari than for non-retarded browsers and even Edge! EDGE!!

Oh and if the user changes light/dark system mode according to surrounding light conditions, guess what happens? Yep, since JPEG doesn't support transparency, now it's different JPEGs with dark background via the media query in the "picture" element, and it's another 754 kB download. Bloody 1523 kB instead of 408 kB, that's a factor of 3.7!

Fuck your ass Crapple, with an electric eel!

Yesterday I started programming a telegram bot. First approach. Just curious.

Pretty impressed.
It's well documented and funny.

well documented code.

Some time ago I had ordered a LCD display I wanted to use in a project. Ended up with a vague datasheet and no clue of how to use a 8bit parallel interface. There was also little help on the internet cuz most ppl use a serial interface.
So after HOURS of reading I finally managed to get it to display something!
I sometimes wish some stuff was better documented.

How i love well documented code *_*

Today i implemented something of such a complexity that the part of my brain i am in could not follow it.
(Really guys. I did not know what i was doing. I only knew i had to do it exact this way)

This feeling when you are in a tunnel and unstoppable. I even documented what i did.
Sadly i do not even understand my thoughts there xD
I wrote about three hours straight and then run a test. And the only mistake was a variable not filled as described. Used another one and it run smoothly as hell.

Today i will drink a beer on whatever part of me did this. Cheers

"We use WSDL and SOAP to provide data APIs"
- Old-fashioned but ok, gimme the service def file
(The WSDL services definition file describes like 20 services)
- Cool, I see several services. In need those X data entities.
"Those will all be available through the Data service endpoint"
- What you mean "all entities in the same endpoint"? It is a WSDL, the whole point is having self-documented APIs for each entity format!
"No, you have a parameter to set the name of the data entity you want, and each entity will have its own format when the service return it"
- WTF you need the WSDL for if you will have a single service for everything?!?
"It is the way we have always done things"

Certain companies are some outdated-ass backwater tech wannabees.
Usually those that have dominated the market of an entire country since the fucking Perestroika.

The moment I turn on the data pipeline, those fuckers are gonna be overloaded into oblivion. I brought popcorn.

Had an awesome day at work got so much coding done, made an awesome well documented class for a Countdowntimer class in Android.

Was looking forward to getting home and using my motivation to continue coding my game when I got home.

Then get to the bus stop and it's packed for the Adele concert, I saw a poster okay thats good only buses are packed (I then take a train, I live pretty far from work) I get to the train station and the shittiest system has been setup,

Where people pack on the train that goes to the last stop south for the Adele concert that isn't even near the last stop!

One of the platforms aren't even being used and the trains that got partway south are tiny as hell for the rest of the people that don't want to go to this concert.

For one thing who thought it was a good idea to setup such a shitty system? Why not have one train go straight to the damn concert area and continually use that one platform and for the rest of the people have the trains running as normal?

Nope let's make a shitty system that doesn't work well.

Top it off have concerts on a Thursday, Saturday and Sunday.

Dumbasses.

Now I get to wait in town doing absolutely nothing and losing the little time I have to code on my game.

Introduced a ‘new’ logging framework for our web site. Web team is testing the integration and I get an email saying the logging wasn’t working. Instead of sending me how she is searching the logs, she sends me a screen shot of the code (which is ass-backwards of how I documented the logging library, but that’s another rant). OK, she wrote 5 lines of code that should be one line, but OK, the error still should have logged fine. I search the logs, and sure enough, there they are. Errors logged just as they should.
So I email back (with screenshot of the search query and results) asking how she searched for the errors.
Hour later she responds ..”I don’t know.”
That’s it.
WTF do you mean “I don’t know”?…WTF…you are a –bleep-ing developer too! This is not the first –bleep-ing splunk query you’ve written!
OK..I’m calm..feeling better. Wouldn’t be so bad if she emailed just me with the question (I’m not a splunk query expert either, we can figure it out together), but she was sure to cc 3 of the PMs involved in the integration, my boss, and other team members to make it sound like the problem was my code.

Oh boy. Gotta love having a team member (For a School project) be in charge of the Database functionality/design, who has almost no communication skills and basically no clue about how to store data in a data base.
Im talking dates stored as varchar(5), column sizes being way way to small, overall table design being rather terrible, no primary/foreign keys, pretty much... Actually no, everything was being stored as a varchar.
Not only that, but there was a hell lot of data that needed to be stored that wasn't even accounted for in the DB design. He made some code that could be used by our team members for queries, creating tables, inserting data (etc), almost 2,000 lines of it.... And basically nothing was fucking documented at all. I'm talking comments like "Insert data into cities table" and nothing else. More complicated functions had as much, or less documentation. Complete mess.

Google/Microsoft: We are committed to Linux and the open source community!

Us: Awesome, so can we expect a one drive and google drive client for Linux or at least well documented API's?

Google/Microsoft: *Unveils random arse applications and services without answering our pleas*

Google is by far the worst for this, Chromebooks built on Linux, getting full Linux application support and android that's built on Linux all have Google drive support baked in... Can we just get a single fucking desktop client... Please!

@Apple iPadOS an iOS teams: you puZies.

You release one buggy iOS / iPadOS after another, each piling on features and bugs, without fixing crowd documented long standing defects.

But what really pisses me off is when you don't have the balls to own up to your mistakes. This is at least the 3rd time you have re-released an iOS / iPadOS update under the same version number. This time it is 14.5.1

I have iPadOS 14.5.1 installed and the iPad is now telling me I need to update to 14.5.1. Just own up to it, you released buggy shit and you need to release another bug fix days after... call it 14.5.2. Call it like it is and we respect you. Try to hide it and you lose our respect, you pussies.

If Microsoft did one thing right, they defined the release sequencing:
X.Y.Z

Changing X means rewrite the manual it is so new and improved (🖕🏻 you Adobe and FileMaker)

Changing Y means it is an update with more features than bug fixes but not a generational change that constitutes a rewrite of anything (🖕🏻 you macOS team for bastardizing with 10.X.Y)

Changing Z means you fixed your stuff, we respect you for owning up to your mistakes.

Man-up Apple, grow some balls and stop confusing people with trying to cover up your screw ups. It's all about the Z.

PM approves all UI and project gets assigned to me. He then makes tons of UI changes that will affect the workflow of the approved UI. To this point, code was clean and well documented. I request a few days to re arrange the code to reflect the new workflow. PM says: I need a minimal product. I don't need it clean. I want speed to ship and start marketing. That's where I stopped caring.. To the next dev, I am terribly sorry..

Our team was having a problem with very slow response times from a 3rd party web service they were contacting to get some device stats. No issues on the other end, but it had already been weeks. They ask me to take a look at it.

I take a few days, do a couple of benchmarks and tests and I isolate the section of code responsible. Turns out, the method they were calling would timeout if the device was offline. We ask the vendor, and they confirm this. They tell us to call methodX to check if it was up.

After having done that, lookup now only took seconds. They were annoyed that it wasn't documented but was just glad it was fixed.

> ticket comes, new feature is requested
> create the new feature from scratch. Code is neatly splitted in files and methods, each with clear responsibilities
> every method is documented, there are clear service layers for the business logic, which resulted in controller having 10 lines of code, give or take
> commit the whole code, everything works
> check the develop branch today, team leader littered business logic in the controllers because "the codebase is a mess anyway"

Today I learned that the my new teams choice to use a mostly undocumented/unused framework over a well known/documented one was decided by a coin toss.

Computer Science student here, and it looks like my group partners have no idea what keeping classes short and straight to the point means.

The project is in C++, and I'm trying to understand this mess that they made, when they have a class called "Manager" that basically did EVERYTHING, whose header file has only the declarations of functions. 50+ functions. Only half of then documented, and most of them with apparently random names. The file has more than 200 lines of reading.

I've never worked with so much Spaghetti in my life yet.

Worst part: I spent time and effort organising some other classes, breaking down methods, untangling code and all that tedious stuff. But one week before delivery, they decide to delete all of my work, because they "didn't understand it" and didn't even think of asking me to explain the changes.
And if that wasn't enough, they refused to give me some percentage of the grade due to that code not being in the delivery.

I am so freaking done with those guys -_-

!rant

Updating PHP from 5 to 7.2 on windows server at work the other day... Thought it would be easy, but I really find software management for windows a pain in the ass compared to package based solutions like apt, brew or pacman. It ended up taking way too long due to dependcies with the website, that weren't really documented, and setting up all the software that depended on PHP over again... I ended up writing 10 pages of documentation about how to updated PHP on windows, so the next programmer would have some idea of how to approach the problem.

Of course I suggested switching over to Chocolatey for windows, but my boss is skeptical since it's not the traditional way, and it seems like it will take too many resources. So now I have to make a presentation for her to convince her that package managers are superior to downloading stuff from phps website.

Wish me luck.

So I got my internship grades today... The fucking bastards gave me a 16.8 out of 20 when I had to work my ass off on legacy VB6 code, using poorly documented add-ons and barely asked for help. I always tried to figure things out myself and that helped me learn that useless crap. But they rate me that low after all the effort I put into a payless job?

So you mean that not only was I not paid, they were also not thankful for said unpaid job. Fucking waste of half a year.

The only documented case that “have you tried turning it off and in again” is confirmed not to work

Just released version 1 of my first API! For this project I did everything the way I wanted to, no shortcuts! I documented the shit out of every endpoint and parameter. Everything is throughly tested and it’s dockerized. I also have metrics for each endpoint (with Grafana in the frontend, which I love) as well as alerts in case it would go down for some reason.

I prepared all of this before deploying it out into the wild and damn, it feels so good. Probably no one will use it but I don’t care. It’s one of those projects where you have to force yourself to go to bed at 2 AM.

Just some thoughts. Don’t really have any techie friends so figured maybe someone here recognizes that feeling. Also I wrote it in Python, such a pleasant language.

different kinds of doneness:
- The German kind: The method is thought through, implemented, documented, errors are handled and thoroughly tested.
- The "other" way: The method is there ... somewhere

I present to you,
The "Ruby on Roads"

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

Boss: we can't accept your MR request until you fix the problems we highlighted, everything is blocked and the client is getting angry

My brother in Christ, I understand your concerns but I need you to understand: you decided to block a perfectly working and documented PR because you didn't like having "<!-- -->" in a couple of HTML files and menial bullshit like that.
It may not be the most elegant thing ever but don't put on me the responsibility of your blocks or I'll smash your face with the coffee mugs I've used to work until midnight so that you could deliver the product in time after someone else delayed the deadline twice already.
Thanks and get fucked ASAP.

My Project Manager to me, after attending his first ever Hackathon of life

PM : Did you see, how people create a full project in a day,
So it is POSSIBLE and here you always complain about the deadlines

Me : Yeah true :|
Of Course it is possible to create a well documented, bugs free, features enriched, stable and properly structured project in a day
My Bad :/

<...in the style of linkin park's in the end...>

I DOCUMENTED SO HARD, AND MADE SO MANY TICKETS!!!

BUT IN THE END, NOBODY REALLY READS THEM!!!

I HAD TO DEV!!! AND BUILD IT ALL!!!

BUT IN THE END, IT FEELS LIKE I'M TALKING TO A BRICK WALL!!!!

rhymes are lazy / nonexistent, I know, but my rage is superseding my ability to rhyme right now.

Working with Android DatePicker is such a pain in the ass.

You want to have your DatePicker appearing as a SpinnerView? Well, easy!

If you're under API 21, you can use the following method 'setSpinnerViewShown()'. If you're between API 21 and API 23 you need to add some style configuration. And if you're above of API 23 you can't use both of the methods above, you need to create a custom xml with the attribute "datePickerMode" (no, datePickerMode can't be set programmatically, it would be too easy to guess).

If you want to add a listener to it, you think it might be a method called 'setDateChangeListener' or something like this? Well no! You must use the 'init(year, month, day, Listener)' method, logic!

If you think you're finished with this bullshit, of course not. Their is a known bug on API 21 that you must take into account (but this bug isn't fixed, no, it's just documented somewhere on google forums).

I don't know the team that designed the DatePicker for Android, but it might a team of champanzee that randomly changed their minds to the phases of the moon!

I have a few of these so I'll do a series.
(1 of 3) Public privates

We had a content manager that created a content type called "news item" on a Drupal site. There where two file fields on there. One called "attachments" and the other called "private attachments". The "private attachments" are only for members to see and may contain sensitive data. It was set to go trough Drupals security (instead of being directly hosted by the webserver) but because the permissions on the news items type where completely public everybody had access. So basically it was a slow public file field.

This might be attibuted to ow well Drupal is confusing. Howerver weeks earlier that same CM created a "private article". This actually had permissions on the content type correctly but had a file field that was set to public. So when a member posted the URL to a sensitive file trough unsafe means it got indexed by google and for all to read. When that happend I explained in detail how the system worked and documented it. It was even a website checklist item.

We had two very embarrassing data leaks :-(

Amazon API ... seriously...this thing is documented over 3 different pdfs in 3 different locations with 3 different requestpattern, 2 different answerpattern and requestthrottling per minute and per hour takes the rest...and then you just do basic stuff e.g. request all orders that were refunded by amazon... who the hell designed this mess?

Am I allowed to use an API from the government that they do not have publicly documented or explicitly said anyone can use BUT don't have any authentication on it?

First comment by the architects that were reviewing my test, as part of the selection process:

"Well the code was very well documented, not something we see much of..."

Made my day :)

when you find a tool or library that does exactly what you need, but it's not documented at all

or worse, when it's "cross-platform" but all the build/install steps are made assuming you're using a Mac
"brew install my-shiny-metal-ass"

My biggest regret is the same as my best decision ever made.

The company I work for specializes in performing integrations and migrations that are supposed to be near impossible.

This means a documented api is a rare sight. We are generally happy if there even IS an (internal) api. Frequently we resort to front-end scraping, custom server side extensions and reverse-engineered clients.

When you’re in the correct mindset it’s an extreme rush to fix issues that cannot be fixed and help clients who have lost most hope. However, if your personal life is rough at the moment or you are not in a perfect mental state for a while it can be a really tough job.

Been here for 3+ years and counting. Love and hate have rarely been so close to each other.

Sins? I don't want to keep you up all night, so here are some highlights.

Fucking with clients and employers who fuck with me first, or waste my time.

Occasionally not documenting my code (I'm actually pretty good about this), then bitching about poorly documented code.

Honestly wishing other people in the office would *actually* explode, or die engulfed in flames.

Working drunk and/or stoned.

Getting pissed off when I have to do something in a stupid way, or use a workflow that I don't like.

Seriously fucking up out of either arrogance or stupidity, then blaming it on something else.

Zoning out, skipping work, or sleeping in and billing for it (see sin #1).

But my greatest sin? That honor's got to go to becoming a developer in the first place.

I wasn't always a professional asshole, but I fucking am now.

Your data is formatted according to some ISO? Nice. You say it's easy to use and well documented? Great!

IT'S FUCKING FORMATTED WITH IRREGULAR SPACING??

What the fuck is this formatting?

Date <tab> Word <3 spaces> Some conjugated version <ONE space> Type <FIVE spaces> gender

WHAT
WHY
WHY ISNT IT XML
WHY ISNT IT JSON
WHY THE TABULATOR AND IRREGULAR SPACES
WHY DOES THE ORDER CHANGE PER LINE
WHY IS THIS IN A SINGLE 1MIL LINE FILE

help the university of oslo makes me dysphoric in their dictionaries i really dont want to parse this

At this point, I just feel bad for my coworker.

No, I am not frustrated or angry, just feeling terribly bad for her as how difficult life must be for someone so dumb.

We are introducing a new method to track some data in our product, like total number of sign-ups, DAU, etc.

Now the implementation is already WIP and this is known to all.

The dev has documented the approach where he has mapped the screen name, a screenshot, and a snippet of the schema that tracks that particular screen.

I kid you not guys, this coworker somehow landed on that document and started some scientific study to try and extract data.

Yes, she looked at the schema screenshot and spent like few hours trying to decode it to figure out the sign-ups and DAU.

Data via a screenshot in a document. I can't even express it.

And then texts me in panic mode that she isn't able to access the data because the file is . jpeg within a document.

I asked where is she executing the schema, because I thought she is joking initially. She said she doesn't know and asked me where she should execute it.

My mind is numb. Life must be real hard when you are so fucking dumb.

Yeah, So the principals of hackathons is shit and am about to braek down to fucking cry.All you do is waste 48hours of your life discussing your ideas with irrelevant startup managers who will just shatter your dreams with a single sentence "this is already in market, what have you creat new?" For fuck's sake, it's my first hackathon , you guys have given me just 10 hours ,i have a team of worlds most idiot devs and i am their equally idiot if not more leader... However my idea was 1000% real and authentic and worth finding... if not, then at least give me prize for creating 9000 lines of code with 2 IOT devices and a working , documented model which no other fuckin team could do.... AND even not this, then FUCKING GIVE THE PRIZE TO SOMEONE WHO DESERVE IT, AND NOT THE TEAM FROM THE COLLEGE THAT SPONSORED IT.. fucking politics -_-

Spent all morning trying to write a JSON parser in Python just to get a bit of practice (technical interview next week).

After an hour or more... Didn't get far and finally gave up...

Then I remember Python has a built-in json module... (yea no need to write in myself).

Since libraries are just py files, I open the source code... And wow!

All the public methods are nicely documented with informative comments and descriptions.

But then I look at the method calls and .... I don't understand what it's doing....

.............................. ☹️🙁😖😢😭😧😰😱

I was having great progress in reverse-engineering the devRant Avatar system...

And then I came to the shirt list.

109 SHIRTS THAT HAD TO BE METICULOUSLY DOCUMENTED AND GIVEN AN INDIVIDUAL CODE

AAAAAAAAAAAAAAAAAAAAAAAAAAAA

I wish my boss would stop revoking my permissions. He's always saying how these slew of things need to be accomplished, yet, everytime I go to do them I'm at a wall because, despite having permissions for a very long time he decided to revoke them entirely.

It's not like I can't be trusted with them, it's been over 2 years with them, so why the sudden revoke?

I finally sent some snot mail to him informing him I'm unable to complete my tasks without the permissions granted to me (I'm a sysadmin, sec guy, boss is vp of tech), and instead of him granting them yet again he's going to run around and try to hack around the permission requirement so he can avoid giving me them.

Seriously? This is stupid. I was the one who wrote the security design and implementation document, and put all that work in. Now I'm being locked out of the system I designed, built and implemented?

Well, time to look for a new job. If you're a manager, please don't revoke your employees permissions without notice, at random, and try to hack around well-documented security policies. It won't end well!

Favourite API.
That's a hard one.
I guess it's a toss up between Salesforce APis and Cloudflare.

Both are straight forward and work within minutes of getting started, and both are well documented to the point, you only need a basic understanding of what you are doing or trying to manipulate to get it up and running.

If only AWS could do the same 😅

the guy won't reply messages, he won't do his job and everyone who depends on him is punished for his behavior. he's hanging by a thread but also no one know how to do his job because it was not documented

Hey, we need a service to resize some images. Oh, it’ll also need a globally diverse cache, with cache purging capabilities, only cache certain images in the United States, support auto scaling, handle half a petabyte of data , but we don’t know when it’ll be needed, so just plan on all of it being needed at once. It has to support a robust security profile using only basic HTTP auth, be written in Java, hosted on-prem, and be fully protected from ddos attacks. It must be backwards compatible with the previous API we use, but that’s poorly documented, you’ll figure it out. Also, it must support being rolled out 20% of the way so we can test it, and forget about it, and leave two copies of our app in production.

You can re-use the code we already have for image thumbnails even though it’s written in Python, caches nothing and is hosted in the cloud. It should be easy. This guy can show you how it all works.

1) Read the wiki on git. I probably have enough shorthands and test methods that you won't need much other shit to debug issues.

2) when debugging, remember that if it is there, there's a good reason why I put it there.

3) commented-out code is probably useful for maintenance. I left it there for a good reason. 😛

4) chances are whatever I wrote, was the state of the art at the time I wrote it. There might be better ways to do it now tho.

5) I always work modular. First, understand the structure. (probably also documented on wiki) DO NOT fuck up the structure. If you change it, you document it.

6) If you feel I wrote shit, it's probably because management annoyed the living shit out of me. Pun intended.

7) Your confusion is normal. I don't do dumb shit.

Discovered pro tip of my life :
Never trust your code

Achievements unlocked :
Successfully running C++ GPU accelerated offscreen rendering engine with texture loading code having faulty validation bug over a year on production for more than 1.5M daily Android active users without any issues.

History : Recently I was writing a new rendering engineering that uses our GPU pipeline engine.. and our prototype android app benchmark test always fails with black rendering frame detection assertion.

Practice:
Spend more than a month to debug a GPU pipeline system based on directed acyclic graph based rendering algorithm.

New abilities added :
Able to debug OpenGL ES code on Android using print statement placed in source code using binary search.

But why?
I was aware of the issue over a month and just ignored it thinking it's a driver bug in my android device.. but when the api was used by one of Android dev, he reported the same issue. In the same day at night 2:59AM ....

Satan came to me and told me that " ok listen man, here is what I am gonna do with you today, your new code will be going production in a week, and the renderer will give you just one black frame after random time, and after today 3AM, your code will not show GL Errors if you debug or trace. Buhahahaha ahhaha haahha..... Puffff"

And he was gone..
Thanks satan for not killing me.. I will not trust stable production code anymore enevn though every line is documented and peer reviewed.

I don't understand privacy advocators.

Am I the only one who wouldn't give up practicality in exchange for "potentially more secure"?

I don't understand so much what the deal is with people who avoid Facebook, or don't trust Google or Microsoft, just in the basis of "privacy" or "security".

Websites tracking you to serve ads? Well, it's pointless because I very rarely buy something from the internet or let myself be influenced, ads are waste of time, just use an adblocker.

I can pretty much upload my whole life or documents on Google drive, even if I made it public no one would really care or read it all. It's like that GitHub project you uploaded but never documented, so no one cares. I usually use alternative software not because of "privacy" but because it has features other software doesn't have.

In reality you realize people aren't that interested in your life more than their own life.

Today, I was so certain that all the functionalities were implemented to handle some webhook calls from a third-party service. It's a script I wrote that has been running for 2+ years uninterrupted or without any issues.

We got some "complaints/notices" today that some "special" actions weren't registered, so I thought that the third-party service just didn't send those actions via their webhook. After some research I found a part where they explained that those actions trigger the webhook like any other action etc. So..

First thought: "okay, maybe they implemented that at a later stage" (was not the case)
Second thought: "maybe this is not what the client meant" (it was)
Third thought: "Then it should have been implemented" (it wasn't)

Okay, time to look at the code to see where this could get handled but apparently isn't. All the actions look good, nice, clean handeling etc, nicely documented code (gave the 'past-me' mentally a high-five)..

I scroll further down to that specific action and it was quiet obvious why it didn't work.. I just see an empty function with the comment:

"//TODO: maybe handle this action one day. don't know what this does atm, probably unused.. Will take a look at it next week.."

.. :D

I took my 'high-five' back..I just needed to copy-paste some other code and change 1-2 parameters..

My man said "What should I return if the True/False field is left blank?"

WHY WOULD A BOOLEAN BE ANYTHING OTHER THAN TRUE OR FALSE???!!!

I'm gonna have an aneurysm. I shouldn't be educating people on best practices for something that's already been written about time and time again. RESTful philosophy has been documented so much, and all it takes is a quick google search, but noooo! I have to take time out of my day as if I'm a regular old stakeholder to explain that I want the exact thing that I sent in an email two weeks ago. Amazing.

Had to look into some old code today and had the "Is this my code?! This can't be my code!? No one else worked on this code, so it must be mine... But, but, it's so... good! And clean! And logical! And well documented! This can't be mine... Can it!? Hey! It works!" moment.

*coding at 1AM*

Result: wrote a whole feature in what was supposed to be a git merge 😅

But hey it turned out to be very well documented 😜

I'm an embedded devices dev. As part of my job I take off the shelf devices and write libraries so that our JavaScript team can interface with them. If I have to deal with one more custom implementation of a standard protocol I'm going to freak the fuck out. Like fuck there are only 5 or so major communication protocols at the hardware level there is no fucking reason to reinvent some shittier protocol over a well documented, widely used protocol that has been around for 30 years. (Modbus for anyone who cares)

Received a complaint that the year dropdown list isn't far enough (ends at 2022). They wanted it to go all the way to 2027. My script handles this by getting the current year then add 5 to it and it generates the values in the dropdown list. All I had to do was change from '5' to '10' in the config puppet files. Contractually, any source code changes needs to be documented and informed to the client. I followed suit, documenting how I am going to make the change. This is new as it involves using git to commit the changes and pull it in the server that talks to the git server. This shouldn't take more than a minute to fix.

Submitted and wanted to finish this today. Client decided to wait til next week to complete the code change to fix the complaint. A work that can be done in a minute is now dragged to a week. FFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUUUUUUU

Web development:
I'm honestly happy that my toxic "senior" colleague is gone.
- Didnt learn a single thing in the last 10 years. Used godamn serverside rendering with Jquery / plain JS for a highly interactive business Web Application. Yeah boii, save that UI state in the relational database, good job.
- Every error in his shit was the error of someone else.
- Manipulative as hell. Type of guy that is your best buddy to gather information.
- Blocked entire technical progress in the Web department by manipulating people. Understandable. I mean if your legacy shit is gone...
- Kept backend developers from doing their job with unjustified complaints about structures... etc to justify that he needed an insane amount of time to implement simple things.
- Cried for every shit to be documented to the last bits. Did never do any documentation himself.

Fuck these people, honestly.

I just took over a new project from a brand new client today. It's an Android app that he said needed some updates and refactoring, and he said it wasn't well documented but he would add some comments for me before giving me the code. He gave me access to the code today and one class in it is over 1200 lines long with exactly 4 methods in it... the shortest method is still over 200 lines long. There is one comment at the very top:
// Needs refactored.

... gee thanks.

Last night I had a very strange dream. I should point out in advance, all of this is fictional and none of it really happened.

I was looking at an answer I posted on Stack Exchange.. for the sake of argument, let's say it was Super User. I remember the question being about volume limiting, which is actually an issue I and many other iOS 14.2/14.3 users have been facing in the last few months. Apparently it has been partially addressed in 14.4.

In the real world I fixed the issue by jailbreaking the phone and unloading the healthd service, while in the dream that was the answer I had documented on Super User. In reality I have documented it in several other places, but not there.

Fast-forward a couple of days in the dream where the answer was posted, and I was now looking at a reply. I don't remember the exact details of it, but apparently in the answer I had posted something about my network.. a screenshot from the iPhone? And the comment on it basically said something along the lines of "your answer is shit, and you probably have a very basic internet connection with default settings". I was really upset by that, as my network is actually quite advanced (on account of being a sysadmin).

Then I woke up and realized that it was all just a dream...

Worked on a WordPress Multisite project that required digging around to find ways to hook into areas that weren’t meant to be hooked, create and add custom core files that would withstand updates, ensure certain plugin capabilities were available even if the current site didn’t load them, and a variety of other black magic that I’m too fried to remember off the top of my head.

By the end of the project I more or less felt like a god in WordPress—There’s little I could ever want to get it to do that I didn’t know how to do.

Then again, this is all probably a long way of saying I learned some very bad ways to do things. Mercifully, it’s fully documented with PHPdoc blocks down to the loop level so that even a 3-year-old should be able to figure out the logic...

All this to say, I’m definitely ready for a new project.

Submitted a ticket to the 3rd party IT provider today. Just like they always do they close the ticket instantly saying they did the work when they didn’t do anything.

Except this time they went one step further. They documented that they had a conversation with me and that they convinced me that I didn’t need the work done.

No such conversation occurred. I have not changed my mind nor have been given any reason to. They just want their ticket times to appear as fast as possible and are willing to lie through their teeth to achieve that.

Prepare for a shit storm motherfuckers.

4 months into the journey at an ambitious streaming startup we, a team of 10 engineers (primarily full stack), sets up a tiny and performant express.js api setup.
We document plans for improving the maintainability, including outlining specific practices (not very different from general node best practices) that need to be followed for all new development.

Enter a new engineering manager (dedicated backend manager), henceforth referred to as S, with a rat face and brain that belongs in a rat hole.

Week 1:
S: let's push this new feature out asap
Dev: it'll need a couple of weeks to get done right
S: let's push out a functional version tomorrow, and revamp in the next iteration
Dev: ... (long pause) there's documented practices specifically directing against this
S: can you not do it by tomorrow
Dev: not if it needs to be done right
S: all you need to do is.. (simplifies changes spanning 5 modules into a 3 line summary)
Dev: yes, (outlines how each changes chains into the others, and how to keep the development maintainable for atleast a few months)
S: (interrupts every sentence saying "yes dev, I understand, yes yes")
Dev: could you please tell me how you expect me to connect (outlines two modules that would fail unless developed as standalone services)
S: Yes dev, I understand, yes yes. I don't have much experience with Node.js, so I can't tell you that.

Dev:
<_<
>_>
O_<

Our.. entire.. backend.. stack.. is.. Node. (Months of motivation, cultivated through hard work over late nights, dies inside)

I need a J and some sleep.

Me yesterday evening:

"Fuck java, fuck JVM, fuck everything about it, shit doesn't work for some reason, no runtime errors, no compiler errors, no syntax errors, nothing, *turns off computer*".

Me today morning(coffee = false), after comparing the documented example code provided by the API with one someone else made, I've noticed that the one provided by the API was messed up and couldn't work.

"Lemme change that one value in the properties...okay here we go"
Shit works out perfectly.

FUCK FALSELY DOCUMENTED CODE

FUCK DOCUMENTATIONS IN GENERAL

Improving my English using DevRant

Note: Will be of great help in writing precise documented code 😜

Fucking hate Qt.

Spent all morning trying to figure out how their bullshit QThreadPool works with their bullshit QRunnable but after a bunch of bullshit asynchronous testing I figured that my thread object was being collected and deleted before I was done with it, for no reason. Now if the race condition was documented... This wouldn't be an issue. But every google search brought up nada. Eventually I resorted to turning off autoDelete on the runnable, but then I just have a memory leak, obviously.

I couldn't find a way to manually clean up a QRunnable in Python. What the fuck.

I just went back to good old fashioned QThreads... This is why I quit Qt in the first place.

What time do you get up on work days? I'm starting to think I should have me time in morning (reading, learning, coding my own things) before going to work.

I've think I've come the the conclusion that this job/team is sorta chaotic and tedious and there's no skill growth. Not learning anything new. Usually just something broken, integrate some new feature, build something that I've already built before but differently for this specific case. Nothing fun or challenging, or new.

And also tired of trying to be a "role model", make things right. I tend to like to keep things orderly, documented, well tested and clean but everyone else seems to just bulldoze their way to get whatever they need, leaving a mess behind... It's been like 2yrs already but the technical debt seems to be growing not shrinking...

Yes its completely necessary to have a spring server with a mysql database with docker containers all over your ass for 3 fucking endpoints and a (url, varchar, varchar) schema. Fuck you. How the fuck do i run all this shit and how do you expect me to create a frontend for something that has no documented endpoints?? Fuck you.

In other news, im now a senior.

So I've created this account specifically for this rant. I usually just browse anonymously.

I've recently been hired in a big company that is one of the biggest Microsoft users in the world and my essentially revolves on making it easier for our collaborators to work with SharePoint (and other ms software)

Never in my life have I hit that much of a roadblock. So for the past week I've been trying to integrate what Ms calls webparts. And to modify the default webparts Ms provides you need to their properties (or Metadata). Except here's the big problem these are NOT documented anywhere (unless I failed to find it, if you do know where it is documented please HMU), so I've found myself trying to reverse engineer the js scripts that are served with SharePoint to figure out what the webpart properties are called and what type of data they are! I've been going through endless github repos using the CSOM nuget package (it's the library everyone uses to interact with SharePoint) and I finally found out about this other library called PnP which is a wrapper around CSOM that makes it easier to use. That wrapper has a way for me to load existing page and look at the properties of existing webparts. So here I thought it was the end of my suffering and I could finally get an idea of what it should be. Turns out this method doesn't work because one of the dependencies it has has had breaking changes and they still updated it even though it breaks their code! So for the past two days I've been trying random combinations of key values with different data types and json serialization methods.

Oh and yeah I've also looked at all the http calls via the chrome network tab, the metadata is not served as an individual file but is computed by Ms servers when they're serving you their html files.

So uh yeah run from CSOM if you can..

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 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.

Visual Studio 2022 compiles our internal c++ cmake project as a mix of x86 and x86_64 binaries, then fails to link.

VS 2019 correctly compiles everything as x86_64.

No idea why. And, obviously, it's not a documented problem.

Are my rants supposed to be well documented, too? Or like submitted as if it’s a GitHub issue, where I shall add details such as what’s not working, how do you expect it to work, steps to replicate the bug, screenshots?

Why tf am I even overthinking this?! Lmao

My idea of hell is being forced forever to maintain a prestashop website with hundreds of under-documented, readily obsolete, mutually conflicting, and most often useless modules.

Apple: "We're justified in taking 30% of all our customer's in-app purchasing revenue because we've implemented an awesome super-secure in-app payment system"
Me, after spending the last week wrestling with Apple's shitty, horrible, unbelievably obtuse, poorly documented system for handling subscription renewals and having to write my own god damn crypto shite for reading receipts: "You're shitting me, right?"

What a complete scam.

Thought you'd like to have your transition documented.
Here you go.

can there just ONCE be a FUCKING react native library that works as it is FUCKING documented?

but NOOOO, gotta always sift through the absolute shit pile that is GitHub issues threads digging out arcane horseshit to make the stupid shit work just like the little managers want

on and on into the circus enternity

It's so frustrating to see how PHP images for Docker are nicely set up, well documented, come with Apache or Nginx, almost ask you to let them pay your bills, while you get almost nothing from Ruby, and when you think you finally made something that works, it behaves like a fucking drunk irish

So I spent the last 2 hours trying to figure out why my co-workers source when hitting the API I built was not working. They kept saying that the problem was the API and I kept saying that it's their implementation.

Turns out it was their implementation and as well as the API. Their implementation problem was not setting the "Accept" in the header. The API problem is how Laravel will return a JSON error response ONLY IF the "Accept" is set in the header.

I actually documented this into the API documentation but it's obvious that none of my co-workers read that you need to set the headers correctly. I think the more scary thing is that they didn't know the difference between Accept and Content-Type!!

So now I’m working with this code that is roughly documented because ”variable names are self-explanatory”.

Yeah, you just forgot that FORTRAN does not support utf-8 variable names...

Why utf-8? Because then if I see:

real :: 座標(3)

I would understand that you mean ”zahyō”, the usual 3D position array ”r(3)”, but no, I need to deal with:

real :: zah(3)

yeah...🙃🔫

I’m an idiot. Stackoverflow issue that I documented to a T. Javascript. So I put requirement of not having jquery or framework.

Get a comment about do I know it is working? My answer, debugging. They respond back with a question about debugging and some details I totally didn’t read.

Well, that was the bug. Chrome debugger was showing a message I didn’t understand. So they answered my problem perfectly.

But before realizing he answered my issue, I blew up. Of course I know what is going on. The debugger is showing me....did you even run my example?

I almost felt like giving up as a developer. Here is this awesome guy, solving my issue, and some dumbass like me has to be frustrated. Now he won’t respond to take a bounty he so awesomely deserves.

I’m still a dev. I just don’t feel so professional anymore...

Neo4j has to be the most well documented price of software after Linux... I mean ...holy shit! It is so fucking well documented!! I actually feel ashamed of the documentation I wrote this last week..

Just wanted to code some better public transportation route calculator (better ux) and found out that the pt company offers an API.

EVERY FUCKING REQUEST HAS TO BE SENT AGAINST THE SAME FUCKING ENDPOINT IN A POST REQUEST WITH THE ORIGINAL REQUEST AS FUCKING XML IN THE FUCKING BODY. At least they offer xsd files... BUT THATS NO FUCKING HELP. At least not that much of a help. AND THE DOCUMENTATION DOES NOT STATE A SINGLE FUCKING EXAMPLE OF HOW TO USE THAT FUCKING ENDPOINT. I FOUND THIS OUT BY SENDING RANDOM REQUESTS TO THE ENDPOINT TRYING TO REVERSE ENGINEER THE EXISTING FUCKING FRONTEND AND NOW I NOTICED THAT 80% OF THE FUCKING DOCUMENTED FEATURES ARE DISABLED BECAUSE: NOT FUCKING SUPPORTED!!!

MAAAN WHY DO YOU DO THIS.

Alternatively I'd use the GTFS files they provide but THEY ARE FUCKING INCOMPLETE AND DONT STICK TO THE EXISTING STANDARD GOOGLE DEFINED... They also offer a different propietary format... BUT THATS FUCKING UNDOCUMENTED AND FUCKING INCOMPLETE...

When a national organization leaves the administrator password on a tool that manages the entire IT Department to the default password.
Also when said default password is publicly documented, known by all trained administrators of this tool, and said tool is exposed to the Internet.

"It's very unfortunate that someone has to sit 10 hours a day on a computer screen but that's what we are paying for."
Working with an EU client.
Task is in stages beginning from assessment of an 9 year old Salesforce instance, cleanup and then transition to lightning.
The deliverabale in the first stage is excel sheet - objects(2400+), fields, apps, packages, profiles(110k), users, perm sets, apex classes, triggers, pages, s-controls and insert each and everything that a Salesforce instance could have.
Each and every data needs to be, analyzed and documented with our recommendations before being sent over. (Finding duplicates in 110k profiles??)
Oh, did I tell you, this was to be done four weeks? Weekend goes to hell.
That's when this beautiful motivational line comes up from the bridge, "It's very unfortunate that someone has to sit 10 hours a day on a computer screen but that's what we are paying for."
Fortunately(un?), that part of project is done and over with.

Now comes the clean up, identify packages not being used, remove them, qa and then push for deployment.
Mind you, this project is to be 2 weeks long. Its Friday of the first week today. And I am still working weekends.
Can I say, FML?

I hate so very much about so very many things, I forget some of the things I love.
And what I love is small lines of code that reveal something about their developer. This? This I love to see.

Some guy here studied C at university, decided he liked it so much he would port it over to JS. Absolutely pointless effort, but he decided he would do it nonetheless. The code is clean, documented, just with this little quirk and I'm honestly smiling. You rock, buddy, whoever you are.

I love to develop for the web, i find JavaScript a nice language and I love the unmatched flexibility of the web platform but i hate when I have to work with the unstable or badly documented APIs which seems to be the norm in the enterprise world: wasting hours in forced breaks because suddenly the API returns nothing but 503 or the VPN suddenly dies, wasting lot of time to find the documentation you need in the slow and cumbersome enterprise API manager, making lots of tests with cURL/Paw/Postman/wethever trying to find out why a request which should work just doesn't... in these moments I envy desktop and mobile devs. The worst part of it is which microservices made everything worse since nowadays there are way more "moving parts" which can break making the API you need unavailable and unlike with monoliths often it's hard to just clone a back-end, populate a database and then work fully locals since now everything depends on a lots of things which are hard/almost impossible to replicate on your laptop.

I don't fucking care if you don't understand what I'm trying to convey, I've documented how to configure email with your fucking iPhone (even though I don't own one), I will not fucking guide some FUCKING idiot from management to teach them configure the same documented thing.

It's fucking email, you log in with your credentials and settings are fetched, how is this difficult to understand you FUCKING idiot?!?!??

Also, pic related, translation "I don't give rat's ass" or "I don't fucking care"

Buying a Macbook for development. Now I'm using a Dell with Linux and it's infinitely more convenient, useful, easy, documented, supported, better looking and I can go on and on. OSX is shit.

Why is it that every god damned time, i ask questions until i have a clear view of a clients project and flow. I present them this flow. They OK it and everything. I build said flow in an app. And then at the end of the line i always end up with a shit codebase because i designed it to be like the documented flow, but changes were being added (and obviously paid for) all the time. I made such a neat little app. And now it all gone to shit.

Is this just me? Am i that bad at programming or what?!

Stop changing half of the app functionality after the original design is created!

Great... None of my coworkers know about this tiny bit of undocumented code, and the guy who wrote it, I replaced ... Fucks sake ... Next weeks gonna be hellish

Company had problematic client projects that each client has a bucket load of change requests. Company doesn't know how to say "No" to them. Company can't afford to pay the subvendors for the changes and the subvendors aren't willing to do them for free.

I went in, reverse engineer the shit out of each application, database, system, documented my own findings, changed according to each client request. This involves editing tables in MSSQL, rerouting PHP files, adding field and validations in C#, passing parameters in VB to Crystal Report, and managed every change request into my own personalize ticket system (that the company does not have).

Saved the company, everyone was grateful. A couple of months later, the company hasn't paid my salary on time, I left like a boss.

They're in shit again and need my help. Haha!

Most awkward video meeting?

Can a conference call count? This happened several years ago.

Diving into international markets that could potentially make us millions of $$ (no pressure), while the phone was ringing the CEO's number (in Norway), my manager leans over and whispers
DevMgr: "This project will be managed using *proper* software development methodologies, none of this agile shit you want to use."
<CEO picks up>

I had already been in talks with their dev team to get a feel for their tech stack and we had discussed project milestones, potential release cycles (laying the ground work for using agile methodologies) before getting upper mgmt involved.

The partner dev team was listening and kept throwing out agile buzzwords and I could tell my manager was getting pissed. He would blurt out "Those specifications will need to be fully documented before PaperTrail writes one line of code!". No one said anything, but I could tell the other mgrs/VPs in the room were uncomfortable with the hostility towards discussing features.

Thanks MongoDB for introducing transactions (ACID) in 4.0 version ... This is really going to help a lot.

Your code is as well documented as an npm package without a readme

So I just spent 2 hours debugging a script that fetches data from an API. Thats all it was supposed to do. Http get some data.

It wasnt working and was giving a "parse error". Worked fine in browser.

So it turns out it was using http 0.9 (first documented http version, defined in 1991) and wasnt sending any headers. And js cant do no headers...

So yea I now have to write a tcp / http 0.9 client in js

Well, this one was very satisfying.

When I resigned from my previous job, there was this one last task I had to finish. The task was to implement an identity and access management system that would work across three different platforms they had. I used to work on one of them which had nothing of the sort but the other two had something of their own. Here lies the kicker, it had to work with existing authorization system in other two platforms. After explaining multiple times why that is a bad idea, I gave up. I created an interface, no implementation, documented how the interface was meant to be used and got the hell out of there.

I would love to get into more frameworks, but half of them make 90% of your work harder, are not documented well enough or are just confusing what they actually offer. 😥

the api endpoint for retrieving user-data in an alexa skill might as well be api.eu.amazonalexa.com WITH .EU
this is not as good documented as it should be and did cost me several hours until i saw it by accident analyzing the request-data another time...
you´re welcome.

Holy shit sometimes I hate my job. Current assignment: translate a C++ COM class to C#. Requirement: interface should not change. I ask the other team using this interface to ask me any questions so I can address their concerns. First FUCKING thing they ask for: a diagram explaining how to access the interface. For. Fuck. Sake. The goddamn thing is not changing. At all. I have said that to every stakeholder every time. It's a changed reference and a tweak to some calls to make them .Net calls. Why am I redocumenting something that was documented years ago?

From an actual job posting I found this morning
**software performs as documented and it can not be broken once it gets into the hand of the customer**

I_AM_NOT_GOD!!!

(but if I were you would have to pay me better)

Raspberry Pi havin their own software as the second/third stage bootloader sure sure is kinda well documented and works kinda well. But oh god is it a faff to get to do something non standard. Just let me modify the u-boot environment and save it to disk/tftp 🥺

Also whoever thought that NFS rootfs should only work with proto=tcp, FUCK YOU for not documenting it! Wasted literally two day on this!

So im pretty sure I made the biggest/dumbest fuckup for the year already...
Deleting the majority of our RHEL server's root partition.

Blonde mistake for sure.

Technically i didn't actually delete it... just fucked up the block device so it's no longer recognised as existing.

I could go fishing for data and put it back together... but since i have the boot par and all the uset account configs... plus i actually documented all remarkable server updates cuz im trying to get better at the whole 'having a team' thing... im just gonna play it safe and go through it all like old school video games when you die right before the checkpoint so you need to go through the same paths again and again... but not too fast or youll fuck up somewhere easy and itll drive u nuts when u gotta reiterate again.

@jestdotty here you go. Always saying I just mention positives about myself... cant get much worse than this.

Working on a very large project that has been going on for 6 months and will run for 18 more.

The day before our bimonthly meeting with the client the PM decides to walk out and quit without telling anyone. Now we're left to try and figure out what he was doing, as most of it was poorly documented it's gona be a pain.

So I love how for the last what now, 20 years companies that don't seem to have the most obvious sources of income build huge data servers, and make the general public push to digitization and lack of physical ownership *cough google cough* and then they, after encouraging dependency for storage say 'yeah well, we're going to press the reset button anyone who is being detained for 2 years or so or eating dogshit in the street by deleting all the photos attached to an account that is not logged into for that long'..... seriously.

So I developed a tool to download everything.. a few times now. Why should I have to hop from one foot to the other so much ? Thats what I'm asking.

I tell you, for such a rich company their api's are very poorly documented and there is so much goddamn documentation that is competing with other versions.

Spent 2 hours wondering why Unity Engine sees my 2 joysticks as Joystick 1 and Joystick 5 (or 6 depending on a UBS port).
Turns out, for some reason, Unity remembers ALL the ports that were ever used (even with the usb extender). That's documented...exactly nowhere. Ok, at least I figured that out, but what am I gonna do about it? Nothing, there's no way to change the order.
So after a quick nervous breakdown, and a cigarette break, I decided to build and run the game, just to see how it looks, and...what's this?
Everything's working! Unity removes all the joysticks from it's array and puts only active ones in the right order and that too is documented...NOWHERE!
Ugh... Unity I still love you, but god damn, GET YOUR SHIT TOGETHER!!!
Needless to say, this day is an emotional roller coaster.

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 😑

So..
The company I was working at until two weeks ago just called me because they don't understand the project I've been working on (even though I provided in-depth documentation, which felt like I documented closely every bit twice -.- ) and they don't have any developer left who knows even a bit of python.

WHY PYTHON IN THE FIRST PLACE IF YOU DON'T EXTEND THE CONTRACT FOR THE MAIN DEVELOPER?!?!

Hypocrites...

"Oh yeah I made a new endpoint, and I just pushed the logic for it wherever I wanted without following any of the project's guidelines or structure. I didn't write any tests or documented it anywhere either. I kinda felt there was already an endpoint for it (there was) but I couldn't be assed looking for it in the documentation"
Die.

C/C++ is so fucking unreadable. Who had the cancer idea to use abbreviations for EVERYTHING?? If a word is longer than 3 chars you can be sure those psychologically unstable devs will use a shortcut.
Pointer ==> ptr
test_and_set ==> fucking t_a_s
rollback ==> rb
I don't want to play a shitty word guessing game for every fucking function in your horribly documented api.

I was just getting frustrated how hard it can be to search on google for very specific subjects when it comes to development. So I thought, why hasn't anyone made a search engine just for developers so you don't get any bullshit in between.
I found apis.io but they only have 1076 documented apis in their db... lets collectively make this better!

I was discussing scope and budget with a potential client for a side project. It involved a good bit of complex postgresql and subsequent aggregations and creation of reports. He was hiring because the last guy's work was so poorly documented, they couldn't verify its accuracy.

Me: "So, what are your thoughts on a budget?"
Him: "We were thinking something like $15/hour."
Me: "Um...ok. If I can ask, where did you get that number?"
Him: "That's what we paid the last guy."
😑😑😑😑😑😑

Connecting my Pi to the interwebs through my computer should be easy, right?

NOPE!

Two hours of fiddling with badly-documented config files after I started, I can SSH in but not access the internet on the Pi. None of the guides seem to want to actually work...

I got a job where I should develop a product based on LLMs.

Expectation: oh right! I'll be working with state of the art technology! 😀

Reality: badly documented libraries that are always changing; new libraries becoming obsolete in less than a month; my product ideas were done by somebody else twice before I could finish a POC; getting dizzy trying to keep up with the latest news about LLMs 😵‍💫

I think I want to do basic old boring stuff again. 😐

(On conference call with potential client)
Me: ...yes, you can interface with our system via our documented interfaces, using either JSON or XML...
Client: That's too hard. Can I just email you guys a Word doc or something?
Sales Rep: Yep, we can totally handle that, no problem.

Others here hates how DevOps pushed parts of operations workload on Devs? Just this afternoon I have to fix a CI issue and then find a way to connect a microservice I built to production MongoDB; I'd be okay with that (I love to thinker with servers) if not for the fact which I have to do it trough leaky and badly documented abstractions put up by the customer. I was having a nice productivity streak but when I have to do this kind of shit the motivation quickly plummets.

I have been given the displeasure of updating a company's WordPress website which was built and (sort of) maintained by another company which ended up closing down. NOTHING WAS DOCUMENTED. Almost no comments added anywhere. Not even a description of the what a particular file does. File names are basically completely random. There are 3 versions of the same theme this company made and no indication of which one is actually being used. On top of this; they used plugins and modified them, so they cant even be updated without them breaking. As well; after looking around it seems they used jQuery mixed with Angular (or maybe the plugin creators did this?). The website isnt mobile friendly either; one of my tasks was to see what I could do with fixing this. Seems basically impossible based on the complete mess of a project this is.
All this being said, I just graduated from Post Secondary and have almost no experience working with WordPress, There arent even other developers to help assist me on this project.....
Gonna be quite the experience.

New question to ask potential employers: What makes this work so difficult? is it innovative or in a challenging domain? Or is it because of a poorly documented, poorly maintained code base between multiple groups that can't agree on terminology?
Though if you ask, you should probably be more polite than I am hearing this in my head.

I asked at an interview if they documented their code with class diagrams.
One of the interviewers told me: "Good code doesn't need a class diagram"

...

*TRIGGERED*

Users have use cases, test cases, user manual etc documented material with them at the time of UAT.
But in the end users do only those things which they don't suppose to do..!! 😑😥

What language would be most suitable for little graphical apps?

Like fractals, animations, and random visual stuff.

I like to learn new languages, but I never know which ones to turn myself to...

My requirements (all optional):
0- Can output visual stuff
1- Cross-platform
2- Documented
3- Not python

Thanks in advance :)

So the contract for this big project with a client has some interesting content in it. I'm not sure if I can sign this in good faith.

Because I seem to be lacking guard dogs and a receptionist at my home office. Maybe I could build a force field for them.

And I'm not really looking forward towards having all my friends sign a document every time they visist.

5 PHYSICAL SECURITY
5.1 Adequate physical security perimeters (e.g. fences, walls, barriers, guards, gates, electronic surveillance, physical authentication mechanisms, reception desks and security patrols) shall be implemented to safeguard Information and information systems.

5.2 Supplier shall have a documented visitor policy and all visitors must be identified, registered, logged, and accompanied by an employee from Supplier.

Just met with country brand manager of famous MNC automobile brand. They have their brand website for our country. He doesn't know any information and doesn't have any information regarding the website nor domain. He has been there for 2 years already and the website was made when the brand came to our country. So now he is stuck with that stupid ugly and most of all out-dated website.

So my point is, why the fuck did business people think domain and server information are less important and doesn't need to keep it documented and confidential?

Ok forget about server. They have to at least be very very careful with the domain name which they use it everywhere everyday.

What if it was some sick bastard like me who bought that domain and made that website? I could drop their butt ugly pages and put some animals seriously making love video up there.

"You are fired!"

Is what I wanted to sent to all clients and third parties involved in the project. Stop making your problems my problems. My systems are ready, properly tested and well documented. Stop changing the requirements and stop adding requirements until you are sending valid requests to my API.

IntelliJ should have a plugin for censoring code comments

How interested would people be in a CoC that was defined in a much more moderate way, providing the documented clarity that one provides, but without the SJW excentricities?

I remember there being someone on here who documented their progress on building their own sex robot with a bunch of Arduinos or something.

Who was that again? Are they still here?

Leaving the company in 9 days (!!!)
Any suggestions for the last week?
Any ideas for a leaving session?
I updated the Wiki and documented everything.
I did the missions no one wants to do and a lot of dev tasks.
What else can I leave behind for the team?

So for the past one month I'm working on an enhancement in a product coded in C++ and shell script, running on RHEL. After toiling away for almost 10 hours/day for a month, the enhacement is ready. Coded, tested, documented. Ready to ship.

The client is supposed to recieve the update as a drop. 1 day before the drop is scheduled to be released to Quality Control, I fire an overnight build on the build machine, update the change request ticket, update other related tickets, inform QC of the drop to be released tomorrow. On the D-day, I package the drop using the company's painfully arduous method. Everything is ready by the evening, and the drop is good to go.

At 7pm (one hour before the drop is to be released), Jack fucking Jack-o-lantern (one of the top most exec in the company) tells me that the default value of the parameter introduced in the enhancement, needs to be changed from 86400 to 1500. HALF AN HOUR BEFORE THE DROP IS TO BE RELAEASED!

Now here I am, changing the value in over 25 files, followed by firing an overnight build, followed by sanity testing, change specific testing, followed by drop packaging, followed by inform QC that the drop will be delayed.

All because fucking jack-o-lantern wanted to change the fucking default value.
GOOD FOR YOU FUCKING JACK.

Working on FCM today and actually this is not rant. 😃 🎉
Google documented everything correctly and everything is understandable.

I hate it when someone says ist all documented, but its just a bunch of old crappy word documents with mostly unusable information in it...

I think UPS' Api documentation and service must be the worst documented and build API I have ever seen from a corporate.

1. The developer website is a mess. A total mess. You can barely find the API type you are looking for.

2. When you get the API and download the documentation, the files, .pdf etc is still a mess. Pages long that most are craps.

3. Each request returns Status Code 200. Even if it is an error. This blew my mind.

4. Each request, based on error type or based on tracking activity returns different JSON schema.

For example, the JSON Schema for a shipment in transit is different from JSON schema for a shipment that has been delivered. A shipment that has been returned, a shipment that required signature etc. They are different from each other.

5. And the worst. They do not provide with test tracking codes. I have found some on internet, but they do not work in development and production environment.

Today I had to spend the whole day fixing a stupid bug in a legacy application in a completely different tech stack than I'm used to...

At my company we have an Internet application running where we can upload a word document and using some mailmerge variables magic, can set those vars and receive the personalised word doc back...

Now this is great, when it's working, and is used in various projects we have up and running... Suddenly the application decides to crap out for no apparent reason and guess who drew the short straw....

Anyhow I ask our sys admin for the password to the server, I remote desktop to it, turns out its a fucking Windows 2008 server...

But wait it gets better, the application, a shoddy mess of c# code, is not under any sort of version control, has to be developed on that same server and to top it all of, I have to follow some obscure barely documented deployment precedure to get my changes live....

So after a lot of cursing on the dev (not working at the company any more) who did the original setup, and hours of painstakingly piecing together how it works and what went wrong and how to fix it, I finally managed to get it working....

After this rant, I'm mailing my technical lead about this in the hopes we can get someone to do it right (yes, I'm that naive)

When windows forms required me to dispose of a certain control derivative manually using a .dispose() call because dynamic control creation was causing a memory leak in dotnet, which instead of fixing, microsoft documented, vaguely.

!rant

build me a little tool today, which make use of the spotify API.
Just want to thank the devs of this API. Well documented, good examples, easy to use.
There are some good devs Out there 😊

Qt to develop desktop apps. It's very well documented and easy to get with it. Even the green color used for the background logo is nice!!!

1/3rd of my work today was documenting my all the parts of my project that haven’t been documented and it felt good

A few years ago a client who sold printer ink on eBay and Amazon wanted to branch out to another store, so I grudgingly began to implement the new API, I followed all the API docs but no matter what, I couldn’t get it to work, eventually I contacted their support and was told it should work. Turns out the test API was faulty and that they had no interest in fixing it instead suggested we tried test data on their live account. I refused and for once the PM agreed with me and went back to the client saying the problem was the retailer.

If only I DOCUMENTED THE CODE WHEN I WAS A BEGGINER!

Fucking Fucking Fuck.... fucking acumatica and fucking IIS.
I’m not shitting on CS or ASP but the fucking windows server/IIS implementation. No one should use that shit. Fucking horrendous garbage.

Literally every goddamn thing we do in acumatica has major fucking gotchas.

Today apparently goddamn concurrency is fucked cause IIS and acumatica. I love friggen obscure issues being only documented in a friggen comment on a damn post in a random difficult to search corner of the friggin internet.

When some gotchas aren’t documented so you need to trial and error the api