So my manager (a 29 y/o, who hardly can use a mac) walks towards me with a hint of panic in his eyes.

Manager: Hey commander keen, do you know how to use vertical look up in excel, I've tried, and looked at tutorials.

Me: yeah I really don't know excel (and not willing to learn, especially on the fly), I don't even have excel installed, I can write I script that does what you want.

Manager: No you have enough on your plate

3 hours later

Manager: hey I still can't figure it out, could you solve it with a script, won't that take to long

Me: no send me the files, Ill do it with a script.

I start writing 2 for loops and wait for the file, 10 ish minutes later its basicly done, just need to put in the column indexes.

I send a message on both slack channels (hey are you going to email or slack me the file)

After a hour I walk to his desk and again ask him for the file.

Manager a good 2 hours later on slack: Hey I just send you the file, I hope its not to much work, it has to happen asap.

So if you have kids, and they are not that bright by some kind of birth defect, don't worry, they can always become a manager.

But you can't get me down today. I hit 2000 upvotes and the employer is unknowingly a proud sponsor for reading and writing all these rants and comments :-) thnx devrant

Our parent company is pushing a new zero defect policy for code that gets shipped.

The next day they announced they are firing our QA team.

WTF?!

This one is for devs and gamers.
But first some background story.

My girlfriend is special. Not just generically lovey mush mush special. She is 1 in 100 more accurately 1 in 10000. She was born with a rare Congenital Heart Defect {CHD}. Called Truncus Arteriosus or TA for sake of brevity. TA's main thing is the two main arteries going into the heart are fused together and never seperated at birth. It's bad news. There is no cure for this kind of thing. Simply repairs that happen over the course of life.

So here is me. Desperately trying to find a way to get the word about this and the 40 other types of CHD out there in the world. I thought. "What if I make a game..." Not based around the medical jargon but on a level people could understand. I spent the better part of the last six years attending appointments with her and still don't get it. What I do get is her Emotional state. How her CHD causes her to think and feel.

So here is the pitch.

The game is about a girl who is diagnosed at birth with a CHD. She is now in her 20's and has to undergo an open heart surgery to repair the defect. The day comes. She goes under but when she wakes up she find herself in a final fantasy style environment. This new world has a darkness cast over it. She is unknowingly the hero of this world and she has to face off with multiple bosses of varied degrees of evil.

Then after beating these bosses she really wakes up from the surgery. Waking up to the realization that the world she saved was herself. And all the bosses were manifestations of her own internal feelings. Depression, anxiety, hopelessness, Denise, desire and so on.

I would sell this game with the caveat that 2/3 of all profits get split between the Adult Congenital Heart Association and Project Heart. As those are the two main organizations that deal heavily with creating standards of care and raising awareness for CHD survivors.

Thoughts?

Note: I am still learning game dev. This is an eventual goal for me.

QA: Please Look at this Defect.
Me: Okay not a problem!
QA: Thanks
Me: <Starts to look at Defect>
QA: 2 mins later. Do you have an ETA on when it will be fixed?
Me: Not yet, I'm still looking at it.
QA: Do you know what time it can be fixed? I have a deadline.
Me: I don't know what's wrong yet, I can't tell you when it will be fixed if I don't know what's wrong.
QA: Okay. Update Me.
Me: Opens Dev Rant.

*Doing a Peer Code Review of someone senior to me*

Me: This fix doesn't look like it will work, but maybe I don't understand. How does this fix the defect?

Senior Dev: *Blinks* It works on my machine

Me: But how does it work?

Senior Dev: It works when I run it on my machine...

Me: Do you know if this will fix the issue?

*Silence*

Never seen QA punt an issue back to development so fast.

Dev created a new service for our application that opened SQL connections. The catch? They never closed said connections. How this passed QA/review I've no idea, but after a few minutes on Staging the service would crash with "connection pool overflow".

I raised a urgent defect, and the devs "fix"? To up the maxConnectionPool to Int.Max!! Argh!

So, some time ago, I was working for a complete puckered anus of a cosmetics company on their ecommerce product. Won't name names, but they're shitty and known for MLM. If you're clever, go you ;)

Anyways, over the course of years they brought in a competent firm to implement their service layer. I'd even worked with them in the past and it was designed to handle a frankly ridiculous-scale load. After they got the 1.0 released, the manager was replaced with some absolutely talentless, chauvinist cuntrag from a phone company that is well known for having 99% indian devs and not being able to heard now. He of course brought in his number two, worked on making life miserable and running everyone on the team off; inside of a year the entire team was ex-said-phone-company.

Watching the decay of this product was a sheer joy. They cratered the database numerous times during peak-load periods, caused $20M in redis-cluster cost overrun, ended up submitting hundreds of erroneous and duplicate orders, and mailed almost $40K worth of product to a random guy in outer mongolia who is , we can only hope, now enjoying his new life as an instagram influencer. They even terminally broke the automatic metadata, and hired THIRTY PEOPLE to sit there and do nothing but edit swagger. And it was still both wrong and unusable.

Over the course of two years, I ended up rewriting large portions of their infra surrounding the centralized service cancer to do things like, "implement security," as well as cut memory usage and runtimes down by quite literally 100x in the worst cases.

It was during this time I discovered a rather critical flaw. This is the story of what, how and how can you fucking even be that stupid. The issue relates to users and their reports and their ability to order.

I first found this issue looking at some erroneous data for a low value order and went, "There's no fucking way, they're fucking stupid, but this is borderline criminal." It was easy to miss, but someone in a top down reporting chain had submitted an order for someone else in a different org. Shouldn't be possible, but here was that order staring me in the face.

So I set to work seeing if we'd pwned ourselves as an org. I spend a few hours poring over logs from the log service and dynatrace trying to recreate what happened. I first tested to see if I could get a user, not something that was usually done because auth identity was pervasive. I discover the users are INCREMENTAL int values they used for ids in the database when requesting from the API, so naturally I have a full list of users and their title and relative position, as well as reports and descendants in about 10 minutes.

I try the happy path of setting values for random, known payment methods and org structures similar to the impossible order, and submitting as a normal user, no dice. Several more tries and I'm confident this isn't the vector.

Exhausting that option, I look at the protocol for a type of order in the system that allowed higher level people to impersonate people below them and use their own payment info for descendant report orders. I see that all of the data for this transaction is stored in a cookie. Few tests later, I discover the UI has no forgery checks, hashing, etc, and just fucking trusts whatever is present in that cookie.

An hour of tweaking later, I'm impersonating a director as a bottom rung employee. Score. So I fill a cart with a bunch of test items and proceed to checkout. There, in all its glory are the director's payment options. I select one and am presented with:

"please reenter card number to validate."

Bupkiss. Dead end.

OR SO YOU WOULD THINK.

One unimportant detail I noticed during my log investigations that the shit slinging GUI monkeys who butchered the system didn't was, on a failed attempt to submit payment in the DB, the logs were filled with messages like:

"Failed to submit order for [userid] with credit card id [id], number [FULL CREDIT CARD NUMBER]"

One submit click later and the user's credit card number drops into lnav like a gatcha prize. I dutifully rerun the checkout and got an email send notification in the logs for successful transfer to fulfillment. Order placed. Some continued experimentation later and the truth is evident:

With an authenticated user or any privilege, you could place any order, as anyone, using anyon's payment methods and have it sent anywhere.

So naturally, I pack the crucifixion-worthy body of evidence up and walk it into the IT director's office. I show him the defect, and he turns sheet fucking white. He knows there's no recovering from it, and there's no way his shitstick service team can handle fixing it. Somewhere in his tiny little grinchly manager's heart he knew they'd caused it, and he was to blame for being a shit captain to the SS Failboat. He replies quietly, "You will never speak of this to anyone, fix this discretely." Straight up hitler's bunker meme rage.

What are your plans on New year??
"Defect fixing"
What are your plans on Valentine's day???
"Defect fixing"
What are your plans on zombie apocalypse??
"Defect fixing"😖😖😖

So just about to head to the pub and I got the dreaded call from my boss.

The support team had developed some fixes. They "tested" and deployed without letting us know... And you guessed it there was failures all over the shop!

So it turned out their testing was running on a local base install with no integration compared to the live system with 15 years of customisation and complex integration. My they thought this was acceptable I don't know...

And the best part was the developers who made the changes didn't understand their own code (I found the tutorial they copied online) they just blindly copied it without understanding how it worked!

So 4 hours later we found the bug, nothing like having a query and s SQL connection but not executing the query....

There goes my Saturday evening. Now we're was my beer!

a U.S. company that places an order for 100,000 integrated circuits with a Japanese manufacturer. Part of the specification was the defect rate: one chip in 10,000. A few weeks later the order arrived: one large box containing thousands of ICs, and a small one containing just ten. Attached to the small box was a label that read: "These are the faulty ones."

>me on first day as temporary scrum master
>gets invited to 'optional' scrum master meeting
>meeting is with all SMs globally
>at 6PM local time
>POs also joining because why
>first topic is discussing a defect
>a PO has stroke of genoius
>"Our code base would be much easier to maintain if it didn't have bugs!"
>this gonna be a long meeting

They've literally left me with nothing to do. I'm doing nothing. I can't be happy doing nothing.

To illustrate the chaos: Everyone on the team was trying to figure out some defect. No one knows what is going on in the code. It's unlike anything I've ever seen.

I found an API call with a misspelled endpoint. It was wrong since the code was written two months before. There's no way it ever worked. Obviously no one tested the code because they would have immediately seen that the call returned a 404 every time.

I fixed it. That was my only PR in about a month. It was literally one character.

The next week that PR got reverted. Apparently the app works better if the API call fails. No one said what goes wrong if the request is made, just that it "causes problems."

That's how bad it is. No one knows why anything does or doesn't work. People write code that doesn't work, never test it, and the application works better in some unspecified way if that code never gets executed.

The last straw for me was when an architect told us that if we want to improve our skills we need to learn how to read and debug stuff like this.

1) Not to be immodest, but I'm good at figuring out bad code.
2) Just because I can doesn't mean I want to do it all day instead of actually developing software
3) He trivialized the really important skill, not making a mess like this in the first place. If his idea of skill is to sling crap without tests at the wall and then debug it, how is he an architect?

I tried really hard but I can't keep a good attitude. I don't want to become toxic, but why would I consider working that way? I try my best to be good at this. Writing decent code means a lot to me. It should mean a lot to them. Their code is costing them hundreds of thousands of dollars. Maybe millions.

I can't write good code and add value if all I do is debug bad code.

So I'm out. I'm going to another project. Have a nice life.

First day of a week long vacation and this series of emails comes in (no I didn’t reply to any of these)

Random new QA: “Why does this 5 year old functionality behave this way?”

(10 minutes later)

QA: Okay I saw your out of office message but I really need to know why this behaves this way or else I’m opening a defect because I don’t believe it should behave this way.

Internal me: Heh that’s great kid but you didn’t make the requirements.

(Another 10 minutes pass)

QA: Defect opened, please resolve this before Wednesday.

Oh the joys of enterprise development, I guess if it’s a big enough deal they’ll actually forward it on to the people I put in my away message. I’d love to see that defect holding up the release when I get back on Monday.

Best error message I've seen all week!

So Friday afternoon is always deployment time at my company. No sure why, but it always fucks us.

Anyways, last Friday, we had this lovely deployment that was missing a key piece. On Wednesday I had tested it, sent out an email(with screenshots) saying "yo, whoever wrote this, this feature is all fucked up." Management said they would handle it.

The response email. 1(out of 20) defects I sent in were not a defect but my error. No further response, so I assume the rest were being looked into.

In a call with bossman, my manager states that the feature is fixed, so I go to check it quickly before the deployment(on Friday).

THERE IS NO FUCKING CODE CHECK-IN. THE DEV BASTARD JUST SAID THAT MY USECASE WAS WRONG, SO MY ENTIRE EMAIL WAS INVALID.

I am currently working on Saturday, as the other guy refuses to see the problem! It is blatant, and I got 3 other people to reproduce to prove I am not crazy!

On top of that, the code makes me want to vomit! I write bad code. This is like a 3rd grader who doesn't know code copy-pasted from stack overflow! There is literally if(A) then B else if(!A) then B! And a for loop which does some shit, and the line after it closes has a second for loop that iterates over the same unaltered set! Why?! On top of that, the second for loop loops until "i" is equal to length-1, then does something! Why loop???

The smartest part of him ran down his Mama's leg when it saw the DNA dad was contributing!

Don't know who is the culprit, and if you happen to see this, I am pissed. I am working on Saturday because you can't check your code or you lied on your resume to get this job, as you are not qualified! Fuck you!

Me : I found this code issue, I think we need to fix it
PO: does it affect the user?
Me: not really but we can make it better
PO: do you have a defect for it in *insert issue tracker here*
Me: no, I just noticed it
PO: is there an IM ticket for it?
Me: I don't think so
PO: is this issue already in production?
Me: possibly. Yes. That's why I was wondering if we should fix it.
PO: okay then we will fix it in the 3rd release from now if you still remember it by then.

I'm coming off a lengthy staff augmentation assignment awful enough that I feel like I need to be rehabilitated to convince myself that I even want to be a software developer.

They needed someone who does .NET. It turns out what they meant was someone to copy and paste massive amounts of code that their EA calls a "framework." Just copy and paste this entire repo, make a whole ton of tweaks that for whatever reason never make their way back into the "template," and then make a few edits for some specific functionality. And then repeat. And repeat. Over a dozen times.

The code is unbelievable. Everything is stacked into giant classes that inherit from each other. There's no dependency inversion. The classes have default constructors with a comment "for unit testing" and then the "real" code uses a different one.

It's full of projects, classes, and methods with weird names that don't do anything. The class and method names sound like they mean something but don't. So after a dozen times I tried to refactor, and the EA threw a hissy fit. Deleting dead code, reducing three levels of inheritance to a simple class, and renaming stuff to indicate what it does are all violations of "standards." I had to go back to the template and start over.

This guy actually recorded a video of himself giving developers instructions on how to copy and paste his awful code.

Then he randomly invents new "standards." A class that reads messages from a queue and processes them shouldn't process them anymore. It should read them and put them in another queue, and then we add more complication by reading from that queue. The reason? We might want to use the original queue for something else one day. I'm pretty sure rewriting working code to meet requirements no one has is as close as you can get to the opposite of Agile.

I fixed some major bugs during my refactor, and missed one the second time after I started over. So stuff actually broke in production because I took points off the board and "fixed" what worked to add back in dead code, variables that aren't used, etc.

In the process, I asked the EA how he wanted me to do this stuff, because I know that he makes up "standards" on the fly and whatever I do may or may not be what he was imagining. We had a tight deadline and I didn't really have time to guess, read his mind, get it wrong, and start over. So we scheduled an hour for him to show me what he wanted.

He said it would take fifteen minutes. He used the first fifteen insisting that he would not explain what he wanted, and besides he didn't remember how all of the code he wrote worked anyway so I would just have to spend more time studying his masterpiece and stepping through it in the debugger.

Being accountable to my team, I insisted that we needed to spend the scheduled hour on him actually explaining what he wanted. He started yelling and hung up. I had to explain to management that I could figure out how to make his "framework" work, but it would take longer and there was no guarantee that when it was done it would magically converge on whatever he was imagining. We totally blew that deadline.

When the .NET work was done, I got sucked into another part of the same project where they were writing massive 500 line SQL stored procedures that no one could understand. They would write a dozen before sending any to QA, then find out that there was a scenario or two not accounted for, and rewrite them all. And repeat. And repeat. Eventually it consisted of, one again, copying and pasting existing procedures into new ones.

At one point one dev asked me to help him test his procedure. I said sure, tell me the scenarios for which I needed to test. He didn't know. My question was the equivalent of asking, "Tell me what you think your code does," and he couldn't answer it. If the guy who wrote it doesn't know what it does right after he wrote it and you certainly can't tell by reading it, and there's dozens of these procedures, all the same but slightly different, how is anyone ever going to read them in a month or a year? What happens when someone needs to change them? What happens when someone finds another defect, and there are going to be a ton of them?

It's a nightmare. Why interview me with all sorts of questions about my dev skills if the plan is to have me copy and paste stuff and carefully avoid applying anything that I know?

The people are all nice except for their evil XEB (Xenophobe Expert Beginner) EA who has no business writing a line of code, ever, and certainly shouldn't be reviewing it.

I've tried to keep my sanity by answering stackoverflow questions once in a while and sometimes turning evil things I was forced to do into constructive blog posts to which I cannot link to preserve my anonymity. I feel like I've taken a six-month detour from software development to shovel crap. Never again. Lesson learned. Next time they're not interviewing me. I'm interviewing them. I'm a professional.

Jesus titty fucking Christ people are stupid. I hate everyone in the software development lifecycle that isn’t a developer or isn’t technically minded. Everyone else seems to be a fucking goofy arse mother fucker.

I just got in trouble because I fixed a defect that never should have been fixed, even though in yesterdays standup they brought it up and asked me what the status of it was. Apparently I was just supposed to estimate the defect and see how long it would take to fix. Why the fuck wouldn’t we do that in a grooming session or a sprint planning session, you are just begging to confuse the devs. Absolute mud sharks.

My company’s upper leadership is sooo focused on the NUMBER of defects that are open on our project and only the number. We give each defect a priority of P0, P1, or P2. You would think this would help prioritize and strategize our plan to fix them. But nope. Every week we have some arbitrary “goal” to hit. A number purely made up by clueless leadership as to what makes a “quality” product.

On Friday’s, managers start harassing devs to merge their fixes and for QA to close out defects. So effectively rushing to hit that arbitrary number or else we’ll have to work Saturday.

Meanwhile they want more test automation coverage to reduce the incoming defect rate. But when the fuck do we have time to develop said tests when all you want is the defect closed to bring down your precious little number?!

They’d rather us close 25 P2 defects to bring the number down rather than 10 P0 or P1 defects. These leaders are so incompetent it kills me! Without any back story, they’re ultimately the reason we’re in this position in the first place! Argghhh!

When junior devs “fixes” the legacy defect...

I'm currently working in a web application project with multiple environments for testing, and we need to give support to all browsers.
So when a 'defect' is iddentifyed by someone, we make sure we know all the previous constraints to solve it quicker.

One of these days, this "tester" comes to us:

Tester: There is a deffect in this X screen.
IT: Ok. Can you tell me what browser you were using in the test?

Tester: The same as you. "H T T P : / / localhost:8080"

:D

After a long day of wrestling with some bad code and getting it to 'work' leaves me feeling dev angst. Then on my way home I see some minor bug in a phone app I'm using and I think to myself, "MY GOD.. all software is made out of SUFFERING."

Behind every tiny defect out there lays some poor soul's looong hours of overtime, stress, tears, alcoholism, and stale popcorn dinners.

New mobile challenge I created:

... treat this as production code and show us your best practises and thought processes ... please list and explain any third party libraries used.

First submission:

I've used library X, although it has a major UI defect when rotating the device, it should be good for a simple test.

... wrong

"Why are some features done very fast, and some very slowly?"
Well you see, I'm nothing more than a punny human. As such, there's a ton of stuff that I don't know. Even worse, human beings have this defect of rarely being 100% efficient, so my performance may vary a bit.
It may be hard to understand for a manager, as lizard people are quite a different species.

Me -Hey did you run through the UTC(s) ?

Co-worker - Yeah.

Me-How many failed?

Co-worker - None!

This project is either going defect-less or Its just the calm before the storm.

I changed "Bug" in TFS to "Monstrous Hideous Defect". That'll get the mindset right. The word bug is so common that nobody cares anymore. New Monstrous Hideous Defect? Holy crap, better fix that right away! 😃

When customer support calls with a complex issue and wants a guaranteed fix date for a defect you haven't even investigated because "they need to get an answer back to the customer TODAY."

Today I had a client raise a high defect directly with my boss’s boss. I got called into a meeting and was told
I needed to fix it immediately.

I looked and realized it was in their code and not our component. I told them as much. They asked me if I would still fix it. I refused. Told them it’s not my component. Fix your own problems.

Sat their as my boss’s boss asked them how they functioned if they didn’t even understand their own component. Feels good man. All I could do is smile at them trying not to laugh.

Recruiter: "this will mainly be defect resolution type work"

Me: "just say bug fixing dude"

"Oh, the next button is 2 pixels to the left, let's open a separate defect for each page that has the next button"

Ever get assigned a defect like this?

First click any radio button and hit the Next button. Then on the next screen click some buttons and hit back button. Then hit next, change a radio selection, hit back, then next, then back, then next and eventually page will bomb out.

Wtf am I supposed to do with this?!

After the end of Sprint, well, the QA people came up with this defect ( mind it 'defect' ) : "The exclamation mark is not very red" [ sic ]

Cancer died a death that moment.

A bug is born
... and it's sneaky and slimy. Mr. Senior-been-doing-it-for-ears commits some half-assed shitty code, blames failed tests on availability of CI licenses. I decided to check what's causing this shit nevertheless, turns out he forgot to flag parts of the code consistently using his new compiler defines, and some parts would get compiled while others needed wouldn't .. Not a big deal, we all make mistakes, but he rushes to Teams chat directing a message to me (after some earlier non-sensible argument about merits of cherry picking vs re-base):
Now all tests pass, except ones that need CI license. The PR is done, you can use your preferred way to take my changes.

So after I spot those missing checks causing the tests to fail, as well as another bug in yet another test case, and yet another disastrous memory related bug, which weren't detected by the tests of course .. I ponder my options .. especially based on our history .. if I say anything he will get offended, or at best the PR will get delayed while he is in denial arguing back even longer and dependent tasks will get delayed and the rest of the team will be forced to watch this show in agony, he also just created a bottleneck putting so many things at stake in one PR ..

I am in a pickle here .. should I just put review comments and risk opening a can of worms, or should I just mention the very obvious bugs, or even should I do nothing .. I end up reaching for the PM and explained the situation. In complete denial, he still believes it's a license problem and goes on ranting about how another project suffering the same fate .. bla bla bla chipset ... bla bla bla project .. bla bla bla back in whatever team .. then only when I started telling him:
These issues are even spotted by "Bob" earlier, since for some reason you just dismissed whatever I just said ..
("Bob" is another more sane senior developer in the team, and speaks the same language as the PM)
Only now I get his attention! He then starts going through the issues with me (for some reason he thinks he is technical enough to get them) .. He now to some extent believes the first few obvious bugs .. now the more disastrous bug he is having really hard time wrapping his head around it .. Then the desperate I became, I suggest let's just get this PR merged for the sake of the other tasks after may be fixing the obvious issues and meanwhile we create another task to fix the bug later .. here he chips in:
You know what, that memory bug seems like a corner case, if it won't cause issues down the road after merging let's see if we need even to open an internal fix or defect for it later. Only customers can report bugs.

I am in awe how low the bar can get, I try again and suggest let's at least leave a comment for the next poor soul running into that bug so they won't be banging their heads in the wall 2hrs straight trying to figure out why store X isn't there unless you call something last or never call it or shit like that (the sneaky slimy nature of that memory bug) .. He even dismissed that and rather went on saying (almost literally again): It is just that Mr. Senior had to rush things and communication can be problematic sometimes .. (bla bla bla) back in "Sunken Ship Co." days, we had a team from open source community .. then he makes a very weird statement:
Stuff like what Richard Stallman writes in Linux kernel code reviews can offend people ..

Feeling too grossed and having weird taste in my mouth I only get in a bad hangover day, all sorts of swear words and profanity running in my head like a wild hungry squirrel on hot asphalt chasing a leaky chestnut transport ... I tell him whatever floats your boat but I just feel really sorry for whoever might have to deal with this bug in the future ..

I just witnessed the team giving birth to a sneaky slimy bug .. heard it screaming and saw it kicking .. and I might live enough to see it a grown up having a feast with other bug buddies in this stinky swamp of Uruk-hai piss and Orcs feces.

I remember I was a child trying to tinker around the only computer that we had. No one knew how to install the Windows OS from scratch with the drivers and everything else (they were installed on floppy disks) so when no one was around I managed to do it everything. I remember such joy, felt like a hacker 😂

Now I'm a web developer and I feel like a moron each time I'm sitting on a defect I can't solve so I'd say these were good times 😜

To the people who empty the coffee pots in the break room without remaking, may you get an extra nasty defect for each time you commit this heinous crime.

Bug - if it is reproducible, then it can be fixed with no time.

But it is never gonna be that easy 😂

Working on a team to take functionality from the latest version of an old executable and put it into a new web-based app.

Coworker: I can't get the results to match so I'll just change the options I'm using in the original program until they match.

Me: That's not how this works. That's not how any of this works. Same options on both source and new app, and you should get identical results. Otherwise, there is a defect.

I walk over to look at what CW set up.

M: "Why do you have this box ticked? That option doesn't even exist in the new version."

CW: I don't know. It was there?

M: (trying not to lose my cool, sets up options the way they are supposed to be) This is actually a pretty simple program. It just queries the DB, so we have to make sure the queries and results are the same.

CW: (runs it) Still doesn't match.

M: What version of the source app are you using? Make sure it's the latest.

CW: I can't tell. There is no help/about menu.

At this point, I kinda want to quit and live in a cave.

M: You don't need that. Check the executable in Windows Explorer.

CW: What do you mean?

At this point, I'm sure I look like Anger from Inside Out. I show them how to do it (right click file, properties, etc), wondering how they got this far in their career without knowing how to do the simplest things.

M: (surprised and irritated) This... isn't the current version. It's two versions old.

CW: Well, I couldn't get the newest version to return the results that matched the test cases, so I used the version that did...

M: You can't do th... Why wou... How is that acc... (turns around and walks out to tell the manager he hired a moron)

At a startup where the software was built haphazardly because the developer thought he'll lifelong be the sole maintainer. The dude antagonized me at every turn and refused to help with familiarising with his code. He eventually left majority of the work for me, and dedication to work continued to dwindle until he threw in the towel

After his departure, we surprisingly grew fond of each other, discussing code concepts at length. He was in the habit of refusing to read any of the articles I sent him, or answer open ended questions citing the claim that they require thinking and he was busy. I didn't take any of this to heart

But it accumulated and I deleted his number. I didn't bear him any ill wishes but it wasn't respectful to myself for him to remain in my space. Some day, I was looking for a point raised during our conversations and went rummaging through our chats. Going down memory lane opened scars I'd long forgotten. I was embarrassed to see the way I forgot all about it. I should never have had anything to do with someone like that

He contacted me for a favour just less than a year after I deleted his contact. I didn't even think of declining. But this evening, I randomly remembered how he saw a defect in my code, promised me that the code will fail in production and resisted all pleas to point out what it was. I don't know if I hate him for his dastardly acts. What I feel deepest is sadness/bitterness that I got to experience all that

**it's 17:47*"**
Dev: Hi manager I have those 13 tasks on me and I won't finish on time.
Manager: Well all those items needs to be finished on Time, how YOU are going to resolve it?
Dev:😵😵😭😤🥺
Manager: there is additional defect to check please take it on priority ,it a real easy one , I'll do it my self in 5 min but I'm too busy
Dev: ETA?
Manager : by the end of the day.
Dev: Well it's already end of the day.
Manager: Exactly, I knew I can count on you .
Dev:🥺🥺🧐
****Next day *****
Manager: Hey sorry to call you on your cell but I see there were no progress on yesterday issue.
Dev : Sorry Manager I'm sick.
Manager : O.K feel well (🤬)
Dev : thank you so much (😎fk you asshole😎)

CEO, your Backend Server is a powerful machine.
It can output millions of pages and serves millions of users.
But it has one defect:
It needs a Developer.

CEO, your Web Application is powerful.
It downloads faster than light and carries more images than your son Instagram account.
But it has one defect:
It needs a Developer.

CEO, a Developer is very useful.
He can fix things on the fly and he can develop killer features.
But he has one defect:
He can think.

(from "General Your Tank Is A Powerful Vehicle" Bertold Brecht)

That moment you see a new "blocker" issue in the bugtracker with the content "this is not a defect but a question".

I'm looking through our SLAs if some clause forbids killing our users.
May I host hunger games with these users as participants? Hmmm...

"Our app needs a barcode scanner"
Fair enough, let's do this!
Android implementation using Zxing: 3 days. Ios: 9 days...
1. Dev iPhone has a subtle hw defect that doesn't let it connect to the computer anymore...
2. Our app-framework doesn't have a proper plugin for ios barcode scanners yet.
3. The first barcodescanner implementation is completely broken
4. Swift is not possible because of conflicting framework plugins
5. Build a plugin from scratch, using zxing objective c port.
6. Build problems with main app.
7. Fuck my life

So someone reported a defect, but the data used was not good.

When I tried to tell them, they disconnected.

god dammit

People who think that emailing, texting, voicemailing, whatsapping and skyping are acceptable alternatives to raising a ticket/defect/issue

It kills me when people performing UAT do not know how to test a particular functionality but still mark it as a defect when something uneven happens! We use IMF to build the input using tags. Sometimes they won't even care to know the right tag to fit in the params, but would still mark it as a bug whatsoever!

Two (2) senior developers and one (1) senior tester left our team and I am left with two (2) Java legacy applications that are hard to maintain. Here is a list of things I hate about these old webapps (let's call them app A and B):

1. App A depends on 80% web services. If one web service for a product or warehouse goes down, work flow is impeded while prod support team checks with the core services team for repair

2. App B is a maven project with multiple modules dependent on libraries that are dependent on company's internal libraries. So if we want to upgrade to OpenJdk 9 and up, the project will definitely produce a lot of errors due to deprecated/unsupported codes

3. App A is dependent on Tibco and I have no experience on that

4. App B's continuous integration build tool is Jenkins and the jobs that build it has a shell script that wasn't updated during the tech upgrade enhancement. The previous developer who did the knowledge transfer to me didn't tell me about this (it should be considered a defect on her part but she already resigned)

5. App A when loaded in eclipse IDE is a pain to work with since it is only allowed to build a war file using ant. I have to lookup in quick search instead of calling shortcuts (call hierarchy) because the project wasn't compiled via eclipse.

6. It's impossible to debug app A because of #5

7. Both applications have high priority and complex enhancements and I have no other teammates to help me

8. You never know what else can go wrong anytime

I just got my third 128GB MicroSD card off Amazon, this time SanDisk. Yet again, trying to do anything not involving the OEM full-disk exFAT partition staying intact (which, fuck that, all that uses that is Windows and Linux, i'm looking for splitting this thicc bih up) shifts EVERYTHING, including MBR+PT/GPT down the disk by 16MB exactly inserting data from... the atmosphere? whatever's using it? ...do SD cards have that secure key/DRM store space thing still?

(EDIT: I do verify that they ARE genuinely the right size after purchasing before reformatting or repartitioning, by the way.)

First it was a Silicon Power card, then a Samsung card, now a SanDisk.

(Also, why all S?)

Luckily, this time it wasn't a pain in the ass to get it to read as anything but "Bad Card" or a 0-byte/empty/non-existent device in Windows/Linux (respectively) so I was able to see that it was indeed the same issue without taking 3 days to jump through device hoops to finally get it to do it again but in such a way that it shifts out and back in all zeroes.

Oh this defect is great!

Inherited an app that allows people to type in the name of their beneficiary in a form.

The database column is varchar(50) and the form has no size limit...beautiful

When offshore overwrites your (100% to spec) content and then logs a critical defect because the incorrect content is showing...

Commit messages:
1- Defect 6380: fix update of user without end date
2- Defect 6380: fix update of user without end date 2
3- Defect 6380: forgot unit test
4- Defect 6380: fix test
5- Defect 6380: dammit!
6- Defect 6380: raaaaaah!!!!
7- Defect 6380: kill me now

Can't wait for this guy to arrive, were going to build some beautiful stuff together.

I had to return my Asus due to a screen defect.

I happened to come help with a project that deadline was in two weeks. It was hardware project for customers with UI.

They said to me - help us 2 weeks and it’s done. It only needs polishing. There was nothing working and we finished it after half a year.

Hardware was crap and drivers wasn’t working. Managers called me stupid when I tried to explain that this is hardware team fault. They used to say that it was tested in laboratory and there is no defect. Laboratory my ass fucking assholes never released anything from scratch.

I got depressed after this project for a year. It was fucking nightmare.

Everything, literally everything was rewritten 3 times cause of stupid decisions that I questioned all the time. At the end of project most of those assholes stopped commenting my decisions. I believe we released impossible product that was crap but based on usage rates I got later when I left it returned expenses.

I lost like 2 years of my life and about 20kg during those 6 months. Never again.

Spends 9 months on the side developing a library for analysis of a specific programming language. No help, entirely my own work. There's various tools built upon this library. Incorporates project management, an effective build system capable of parallel and distributed builds, a packaging system...

Beta release the library. Wait four months. Ask the community for who's been using it so I can get feedback and other comments. Majority of the comments follow a specific pattern.

"You don't support X, how dare you!?"

One, this is free software, pay me if you want specific things.
Two, I'm the only developer of a project usually undertaken by a small team.
Three, yes it does you fucking invalid... Every fucking time someone claims it doesn't support some feature, it's something I've already written and validated. I swear to fucking God users can't find something themselves and instead of checking the Wiki or asking for help, they blindly assume they can't make mistakes and it must be my defect.

It's kinda inpressive to me how everything comes to a standstill, as soon as Jira goes offline, because it's been overwhelmed by stuff going on.

Me and another colleague are waiting for it to get back online, so we can annoy the devs with defect reports again.

Which inturn were due a while ago, but the deployment for testing them wasn't done the whole time, so it was not possible to test anyways. And ontop all of that most of the tests failed, so there are a ton of defects.

Fixing them and bringing the tests on PASS has to happen until tomorrow, because that's the deadline for the release cycle.
Ah and it's roughly 45 tickets.
The next release cycle is like in two Months

You know... the usual stuff 😂😂

Just finished a defect fix, and turns out there's another unrelated but harder bug in the codebase. We are in the last few days of the release.

I told my tech leads that it was an unrelated problem and showed them in detail. I told them I was starting work on it now, but there should probably be a new defect entered for it.

They actually said for me to piggyback the old defect and let this go under the radar. Actually laughed it off like it was no big deal. Like WTF! I don't think its very unreasonable for devs to want separate defects for separate bugs. They're worried about analytics and shit, but I'm the one left holding the rug, looking like I spent a week on a trivial defect.

"Thanks XYZ-san for the clarification.

We will take the defect to next level." - A colleague in an email to the client

😐 the fuck does she mean take the defect to the next level!!!!

Each programmer is a poet at heart
Programmers are like God. We create defects and also kill them too. We spend the whole day fixing a defect, and the patch itself gives birth to a few more defects of its own.

The third clause perfectly describes a recent "showstopper" defect I was working on.

Spent 8 hours in debugging a defect, just to know that code has been completely refactored, that defect is resolved, another critical defect to be fixed at high priority 😭😭😭😭😭😭 in the same code .. refactored by someone else 🥺🥺

And people call .. life of software engineers is so easy and cozy 🤔😰😢🥱

A lazy sunday night with Monday coming up next day. This week will be busy with all those client requests and defect fixes.

I'm never buying expensive phones ever again. Ny Asus ROG Phone 5S which I spent $480 for, got its WiFi and Hotspot feature completely broken just 13 months after I bought it.

I looked it up and many other people are having the same problem and it turned out that it was a manufacturer defect

So Asus bricked my phone on purpose.

A peace of work to be done within 2 weeks for 3 devs
1 dev gets pulled off the team, the other decides now is a good time to take a 2 week holiday
So am the only one left and because the designs weren't even ready for the first week i only had a week to do it, i managed to finish it with some defect obviously, and testing oh yes the testing non, non whatsoever. Only test i had were snapshots. Other than that, nothing. So the demo seemed to please everyone and the whole team got praised for some gr8 work, work that was estimated for 3 but done by one and hah no testing...yet

Monday morning meetings:

- Reminding designers what the app looks like to then discuss a defect.
- Reminding everyone else where the online meeting link is, despite the fact we have used it everyday, for the past 7 weeks.

Fuck me! Fuck VSCode!
Wasted nearly a whole day of entire team by breaking a core functionalty.
Don't know if others also hate it so much when you want to add a bracket and VSCode detecting a closing bracket or whatever nullifies your attempt leaving the number of brackets constant.
Not exactly sure today's defect was caused by this, but I strongly suspect it because it was caused by just a misplaced bracket.

My code is in Acceptance Testing phase, and I got a defect reported.

I tried to redo the same without changing the code, it works for me

god dammit

After inputting all of the defect info into the bug tracking tool, QA writes a quick summary of their findings and goes home.

Love explaining to mgmt why developers could not fix bugs because they had no access to the bug tracking software.

1 day.... X number of bugs... 0 progress

Well fuck...

Korora 26 finally came out and I wanted to install it on my new laptop. I'd previously put Ubuntu MATE on there, with Cinnamon kind of tacked on, but it wasn't great, mostly because it wasn't Korora.

Unfortunately, Korora (and Fedora) still have a bug in the installer where it will complain if your /boot/efi partition is not on /dev/sda, which in my case it was on my M.2 drive. However, I was able to eventually get it working.

But when I booted it up and tried to log in, it would take me back to the log in screen. I logged into a TTY, where I was reminded that when I had set up my Ubuntu install, I had chosen to encrypt the home folder.

Not knowing how to set up the eCryptFS with an existing encrypted home folder setup, I opted to wipe the drive and reinstall from scratch--I had a backup of most of my files from the Ubuntu installation. However, I lost some very important documents that I'd set up since then.

Fast forward to today where my laptop won't boot unless it is either a.) unplugged with just the battery or b.) plugged in without the battery, with a different power cable from the one I got with the computer.

Thankfully the people responded quickly after I mentioned I was having issues. Hopefully it doesn't get worse...

So, a requirement is flagged in Altassian and I took that requirement.
Code Review done and committed in dev branch, and later to release branch.
After 3 weeks, QA raises a defect.
Turns out, BA has updated the requirement but didn't inform anyone.(Was updated after the code was merged in release branch).
QA took the latest version, raised a defect with high priority.
On confronting BA, he casually comments they'll update when required. It's the dev's responsibility to check the JIRA.
TL;DR; Its the dev who should check and update the code after commiting in release branch, even if Altassian gets updated 3 weeks later from release. -_-.

MOBBING DICTIONARY - 3 -

Sentence (harsh public remark)
- You always want to do everything.

Purpose
- highlight a (true or false) defect of the target, a lie repeated thousands of time will become true.

Result
- whether or not that is true, everybody will start to see the target with that particular defect. Every action will be justified to correct the defect.

While it is often true that people at time have difficulty to delegate, usually the reason is not that they don't want to, but they don't know how.
The mobber want to remove the person rather than helping on the "how".

This strategy get the best result when the target is self aware, take the mobbing sentence as a constructive feedback and start to effectively delegate. He/she will contribute to make him/herself useless and could be later easily disposed of.

A Website where the user alterts us about a defect on his printer.
There are predefined categories (things like error messages in the printer display, issues with the prints, issues with paper jams, issues with noise and so on) maybe around 10 to 20 categories.
They decide which fields are shown when the user selects it.

Should I do a Dropdown? List field? Radio buttons?

Tech: PHP, Slim Framework, fontsawesome, resulting in a mail sent to our ticket system to pre-fill form items to avoid 1st level support...

when the testers open a defect because an external link failed.

Ok so I'm working at this bank that hired me as a lead dev to do something about the quality of the software. Now we have CI builds with front end and back end unit tests, sonarqube, coding standards and much more. First release.of our software had only 1 low impact defect! All other software they released in the past always has dozens of bugs.

Now I have this front end guy in my team. He thinks he is really good and actually said my front end skills suck. What?? Wtf you saying? I'm truly full stack and doing front end way longer than he does and already did many many successful projects for awesome well known companies. So he refactores some JS component I wrote. Now this component is very simple but needed to look and behave different on different devices and screen sizes. It was working perfectly. Our tester did extensive tests on all sorts of devices and browsers: worked perfectly.

So, this 'front end king' is now already in the 3rd week of making changes to this component. And still it is not working properly. And he doubts my front end skills?!

Hahahaha go fuck yourself you god damn piece of fucking front end retard!! Everything you make doesn't worl right away and needs at least 4 revisions. Fuck you!

*New defect*

Designs are confusing and use bad practises. Multiple buttons achieving the same task. The dev team, the BA's, PM's can't understand the current flow.

*Defect closed*

"Design happy with current implementation"

Browser automation is a PITA. I’m going on my fourth side mission with this crap and I honestly still look like a newbie. I’ve tried Java Selenium with Chrome, Excel VBA with IE9, Vanilla JS in the browser console, and tonight I’m thinking to concoct some kind of hybrid CDP & Selenium approach in Chrome. Never used CDP before, not even sure where to start but I heard it sucks like anything else unless you get some extra libraries and plugins and stuff.

It doesn’t help that I can’t get just anything I want from our IT Department. It would be another PITA to ask for puppeteer. If puppeteer is totally legit please let me know.

Selenium sucks. The buttons don’t click, the waits don’t wait. Its unusable. Iframes are annoying as all hell but I can deal with that. HTML Tables suck too. It doesn’t help I have to restart my whole java program and whole Chrome every time an element doesn’t get picked correctly. Scripting one single element can take all fucking night.

Chrome dev tools what the fuck. Why the fuck is the DOM explorer in the same window as the web page I’m working on?? I can’t undock it. Am I supposed to use a fucking TV screen to work with this bastard?? If I use the remote chrome tools on port 9225 or whatever - It Still Renders The Whole Fucking Page Alongside The Console. Get Out Of My Way!!! The nested HTML CODE IS ONE CHARACTER WIDE ALL THE TIME. I can’t for the life of me figure out what the fuck I’m looking at. Haven’t you people ever heard of A HORIZONTAL SCROLL BAR at least.

Fuck I tried using getElementById, and the Xpath thing and its not all that great seeing I have seemingly 1000s of nested Divs all over the god damned place oftentimes containing a single element. I’m finally on chrome now should I learn Jquery now? I mean seriously wtf.

I use this one no code tool for dev it has web automation built in. As you can imagine its just as broken as anything else!! I have 10 screens to navigate it gets stuck on the second screen all the damn time. Fuck I love clicking the buttons when my script misses and playing catch up with it.

So as a work around to Selenium not waiting even 1 millisecond when I use explicit wait or implicit wait or fluent wait, I’m guessing maybe I can attach both Chrome Dev Tools Protocol (CDP as ive called it earlier) and selenium to the same browser and maybe I can use CDP to perform a Wait with any degree of success. Selenium will do nothing more than execute vanilla javascript Element.click(); This is the only way I know to even ACTUALLY use selenium beyond the simplest html documents possible. Hell I guess CDP can execute js idk.

I can’t get the new selenium that has CDP but I do have some buggy ass selenium from a few years back. Yeah, I remember reading there was a pretty impactful regression defect in the version I have. Maybe I’m being gaslighted by some shit copy of selenium?

The worst part is that I do seem to be having issues that the rest of the internet’s devs do not seem to be having. People act like browser automation is totally viable and pretty OK. How in the fuck hell is my Selenium Test Suite going to be more reliable my application under test?!!?? I’ll have more fucking bugs in my test suite than in my application. Today, I have less than half a test script and, I. already. fucking. do.

I am still SUPER PISSED at the months of 12 hour days (always 8 hours spent on normal sprint work btw only 4 to automation) I spent trying to automate our regression tests. I got NOWHERE.

I did learn a lot about HTML and JS though like I’m not that mad…but I’m just trying to emphasize my achievement on my task was zero.

The buttons don’t click. There are so many divs and I swear you sometimes need to select a div somewhere in the middle sometimes to get it working. The waits don’t wait. XHR requests are invisible. Java crashes 100 times before I find an xpath and thread.sleep() combo that works. I have no failure modes to use — Sometimes I click the same element 20x in a script because I have no way to know if it clicked the first time! Sometimes you gotta scroll the page to make the click work. So many click methods all broken. So many wait methods all broken. Its not just the elements don’t click! There are so many ways to click that almost work but surely they all fail the same in the end. ok at this point I’m just repeating myself…

there yet even more issues that I can’t remember…and will soon remember as I journey into this project yet again…

thanks for reading I hope I entertained and would love to hear your experience!

So I’m pretty sure I’m wrong here but I wanna rant anyways:

Had a US to pick up a date or time based on a zone and use that in the db in all locations, US had four functions written and told that only these need updating and DB itself will have no updates. Update four functions and made PR. Tech person who filled in US saw PR and approved, I merged and gave to QA. QA asked why some things aren’t being updated and I said oh those are meant to be updated too and I said ok. Get a defect. Checked that there is way more functions to update than needed, and tried so that no dB update happens in US. Made PR, reviewed and pushed. Still something is still not updating (this time purely mb I guess) another defect. I make PR again and dude asks why I don’t change it in this way which requires a DB change. Resist the urge to tell him he specified in his US no dB change. Did the thing and now it’s still in process. Product owner is pissed with amount of defects from me.

Reproduce production defect on local.... Apache ProxyPass for the redirection... Apache Crashes.... Fiddler to the rescue... fingers crossed.

Used to love our old severity grading methods on my old project. Traffic light system worked a treat. Defect raised... Have we seen this before? Green light
Never seen it but it's on stack overflow? Amber light
Not on stack overflow? Red light and most definitely an "environment fault"

That awful feeling of going through the mailbox to sort out build issues and defect mail chains, after a day off

So tester’ duty is to make sure the software application is bug free or defect free by implementing various scenarios with testing techniques, don’t u agree? pls. comment

so the deployment from my side went through ok... but a "SYSTEM" defect almost prohibited my changes from being signed off... explained it to the person responsible... and then they sign it off knowing well that it was a "SYSTEM" defect that was outside of scope...

I'm currently working on a dynamics CRM project which has been going on for almost a year, we're on week 19 of defect rectification brought on by a mixture of the clients abysmal testing and spec writing and the pain of debugging in Dynamics.

This project has left me emotionally and physically drained. I used to love where I worked and the guys I worked with but right now I'm the lowest I've felt in a long time.

I have autism and I really struggle with situations I have little control over, I also pride myself on being able to diagnose and fix problems quickly, I've been working on the same 2 bugs for the last 3 week's. I squashed one on Friday but this other one is persistent and I feel like it's killing me.

I've mentioned my low mood to my boss who could only say "It will be over soon". Well I was supposed to be transferred to a new none dynamics project in September, but yeah that didn't happen.

I really enjoy Angular and I've found this long project has caused my skills in it to rust to the point where even the most basic elements are a struggle.

I hate Dynamics and I hate the prospect of going in tomorrow and facing it again.

defect report: "After updating, I can't make a field turn red when an error occurs"

me: "You could do that before the update!?"

Working on an enhancement for a legacy product that's been in the industry for about fifteen years... The situation is that I fix one defect and give more pop up. I'm frustrated so much that I give up twenty times a day.
Please tell me that's how you work on legacy software 😔

Best: the U2 pilot's handbook, as you _wanted_ to read it.
The S370 assembler docs. Everything you needed and nothing more.

Worst: where to start? How about the defect reports produced by contemporary QAs? Maybe a screenshot, and an implied demand for telepathy. Mate, you're a mindless drone, the definition of brainless. Applying telepathy on you is pointless.

The Business forgot to list a requirement and now want raise its absence as a defect...

I spent fuckin whole day on a defect..
I made a cma content using fatwire in which I added &pound; on a html snippet and it converts to (£) and when I use it in page it shows £ even it's in utf8..
Can anybody help?

Me: it's a regression bug, I'll update you once I've patched and deployed.

Tester: What's a regression bug?

🤔

A birth defect of Google Chrome is that if one navigates away from a page or presses CTRL+S again while it is being saved, the saving of the page is cancelled. It was like this in Google Chrome since the beginning. This software birth defect was inherited by other Chromium-based browsers like Edge and Opera.

Eyup DevRant Devs - First off Merry Christmas, Happy Holidays and a Happy New Year to everyone working hard on this platform - In the New Year, please, please, PLEASE can you fix the iOS App not repositioning when in Landscape Mode for iPads? Currently typing this sideways on my iPad Pro 2020 on the latest iPadOS version, and latest version of the DevRant App; cheers chaps!