Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "oh yes"
First of all, condolence.
Second of all, Confluence.
Read the documentation I've written and you'll be just fine. It is detailed and organized. If you find a bug, it's most likely not a bug but a business rule that the business people have conveniently forgotten about and called a bug to shift blame to the developers.
There's a special section that includes the JIRA issues related to the logic. Yes, I'm obsessed with paper trail and I enjoyed gathering evidence. If you take a peek into these issues and find yourself screaming, "Oh my god, this is horrific! How was he able to understand all this shit?" Pull the anal bead glow-in-the-dark rosary out of your butt hole and offer a prayer for me.
You will find legitimate flaws, of course. I'm semi-human after all but don't you dare curse my name and definitely do not curse my name three times in front of a mirror in a dark room with a lit up red candle, it's weird.3
Okidoky you lil fucker where you've been hiding...
*streaming tcpdump via SSH to other box, feeding tshark with input filters*
Finally finding a request with an ominous dissector warning about headers...
Not finding anything with silversearcher / ag in the project...
*getting even more pissed causr I've been looking for lil fucker since 2 days*
*generating possible splits of the header name, piping to silversearcher*
*I/O looks like clusterfuck*
Common, it are just dozen gigabytes of text, don't choke just because you have to suck on all the sucking projects this company owns... Don't drown now, lil bukkake princess.
*half an hour later*
Oh... Interesting. Bukkake princess survived and even spilled the tea.
Someone was trying to be overly "eager" to avoid magic numbers...
They concatenated a header name out of several const vars which stem from a static class with like... 300? 400? vars of which I can make no fucking sense at all.
Class literally looks like the most braindamaged thing one could imagine.
And yes... Coming back to the network error I'm debugging since 2 days as it is occuring at erratic intervals and noone knew of course why...
One of the devs changed the const value of one of the variables to have UTF 8 characters. For "cleaner meaning".
Sometimes I just want to electrocute people ...
The reason this didn't pop up all the time was because the test system triggered one call with the header - whenever said dev pushed changes...
And yeah. Test failures can be ignored.
Why bother? Just continue meddling in shit.
I'm glad for the dev that I'm in home office... :@
TLDR: Dev changed const value without thinking, ignoring test failures and I had the fun of debunking for 2 days a mysterious HAProxy failure due to HTTP header validation...