If you had
one language
One framework
To code everything you want
Would you learn it or let it pass

His code is heavy,
arms are weak,
mind is bending.
It's all spaghetti.
He is nervous but looks calm and ready
to go now
but he keeps on forgetting
what he wrote down.
The manager is getting loud
He moves his mouse but the bugs won't got out
They are features now
Time to ship
Over blaow!

I once changed all my error messages to say “Processed successfully” because I had a demo yet the software was very buggy.

I bought myself time to fix the bugs later.

#demoHack

1 - Programmer produces code he believes is bug-free.

2 - Product is tested. 20 bugs are found.

3- Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.

4 - Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.

5 - Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.

6 - Users find 137 new bugs.

7 - Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.

8 - Entire testing department gets fired.

9 - Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.

10 - New CEO is brought in by board of directors. He raises the programming team's salary to redo the program from scratch.

11 - Programmer produces code he believes is bug-free.

12 - fml

When you finally fix all the reported bugs.

Me trying to fix all the bugs

Credit: Internet

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

--- 3 months previous ---

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

CEO: documentation? on what?

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

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

lead dev: ..... eh ok

O2: *approved*

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

I spent about 5 hours today coding and I was totally in the zone. I'm talking things were working properly, tests were passing, bugs were being squashed all over the place. It was completely amazing, I felt like a god ruling over my code kingdom.

After about 5 straight hours I realized that I needed food so I got up, stretched my legs and had some dinner. Well I sat back down about an hour ago and I am SO far out of the zone. Everything is breaking, I can't focus and I have no idea why. My kingdom was overrun with a plague of bugs in just the short time I paused to eat.

Moral of the story: when you get in the zone don't stop for anything even if it seems like basic human necessity. After all we aren't human when we're in the zone, we are coding gods.

Take a break folks,
From work,
From code,
From tension,
From bugs,

Take a car, drive to the country side, breathe the fresh air, ride horses,
Have a meal, stay for a day or two, without internet, and then Be back to work.

This is what we all need now :D

The code you write is your child.
When it misbehaves(bugs) you disciplines(fixes) it.
You are ecstatic when it achieve something(into production).
You want them to be at par with the world(adapting to new libraries).

So, to all the developers out there happy father's day.

9pm Project Manager: We have to push an update TONIGHT
9.45pm Devs: okay guys, all latest bugs are fixed, just needs final check and we can push the update
10:45pm Devs: Guys?...
11:45pm Guy in charge of testing: Uh doesn't work...
- What doesn't work?
- I dunno, I get an error message
- What's the (fucking) error message?!
Aaaaand silence
Fuck this I'm going to bed.

me: Just to be clear, we're only supporting chrome?
boss: Yes.

* few days later *

QA: I have a lot of bugs to report, the bosses asked me to test the app in all browsers

We passed a milestone: 250,000 phpunit testcases.

If it weren't for a heavily parallelized build pipeline which splits it out over 20 servers, it would take about 7.5 hours to complete.

Not hating on PHP, and without tests it would truly be hell...

But still, fucking hell, we outgrew PHP.

Not having a solid type system just means you either accept more bugs, or write thousands of unit tests to guard all the foundational cracks in the system.

On the bright side, I get a coffee break after every commit 😄

They made a full fucking application in MICROSOFT EXCEL!!!!!!!
who the fuck makes an app in Excel? Though it's used internally, it has over 100 users and Everytime there's an update a new file is sent to all of them by mail. They use different excel files as DBs and tables as sheets. It's even got a fucking UI with check boxes and drop-downs and shit

Now guess what my task is?
Understand that entire application from the Excel files and make a webapp to cater to those requirements.

Fuck documentation, there are bugs in the Excel file and I need to fix the bugs in my app

Some good soul please tell me how must one start analyzing an Excel sheet to understand the logic behind it. Or a tool that magically converts "excel applications" to webapps

Was running tests on a big project I'm doing which still contains a fair amount of bugs but I was sure that all thresholds would succeed and the test wouldn't fire an alert.

Ran the test: alert received any fucking way.

FUCK.

*checks rule*
*waaaait a second, I've set the threshold differently by accident...*

HOLY SHIT THIS MEANS IT WORKS 😵

*pats project* - "good project 😊"

When my manager asks me if I can fix all the bugs on the board by the weekend: 'look, I have a covenant with God: I don't do miracles, He doesn't code.'

> make a change
> PR gets rejected
> IHATEFORALIVING! YOUR CHANGE IS NOT WORKING! EVERYTHING BREAKS!
> 3 hours long debugging session
> We find out a whole bunch of bugs
> Suddenly, everything works
> None of the bugs had ANYTHING to do with my change. In the instances where the app broke, my code wasn't even being called at all.
> My change was literally the one and only working thing

I wish life was like in The Office, when you just stop what you're doing and you drop the Jim stare at some camera

Dev: Your PR only addresses a quarter of the ticket

Dev2: *limps a commit so that now 1/2 of the ticket is addressed and creates a new PR for a separate ticket*

Dev: Your original PR only addresses half of the ticket

Dev2: *limps a commit so that now 3/4 of the ticket is addressed and creates a new PR for ANOTHER new ticket*

Dev: Your original PR only addresses 3/4 of the ticket

Dev2: *limps a commit so that now all of the ticket is addressed but two new bugs are introduced and creates a new PR for ANOTHER new ticket*

Dev: Your original PR introduces 2 new bugs

Dev2: *limps a commit addressing one of the two new bugs and creates a new PR for ANOTHER new ticket*

Dev: Your original PR still has one bu—

Manager: WOW GOOD JOB DEV2 THAT’S 5 PRs TODAY AMAZING! Dev you need to pickup the pace, you only have 2 PRs so far today. And get these PRs from Dev2 QA’d fast. He’s a rockstar!

Dev: …

*The 4 other PRs turned out to be equally dogshit*

Manager: Hey hurry up with QA, you’re holding Dev2 back!

Dev: …

In my current work, I have two systems to work on (let's name em Systems A and B). Both basically do the same thing; both allow users to book facilities available to them.

System A is already in production. My job is to fix any bugs that come up on said system. System B is an improved version that they wanted me to develop. This would follow a different framework etc. I am already halfway through this system.

Now, here's the fucked up part. The code for system A is a massive clusterfuck. It has unused commented code dated back to ancient times where men had the brain of an ape.

And don't get me started on the fucking logic. One part of the code was to retrieve and display the timeslots available for a chosen facility. The code to do that alone takes up 500++ fucking lines, filled with ajax commands, html manipulation and commented, unused codes..AND THAT'S JUST THE FRONTEND!

The fucking backend was not a problem of smelly code anymore. Nope. It was like a programmer had code diarrhea and shat his backend code all over the project. If I had a pin board, I would have made a crazy wall just to understand what some fucknut was trying to achieve.

Anyway, my supervisor told me to fix some bugs on System A. Knowing how the code was, I told her that I could refactor the code. Since I've already achieved that function on System B, with a shorter and cleaner code, I could just copy that and use on System A. But nope. She SPECIFICALLY told me to just "do whatever to fix the bugs. I don't want to waste time on System A." Okay. Makes sense to me. Whatever. I didn't wanna fuck my head up looking through that mess of a cesspool. So, I came up with a few hacks, not thinking of clean code and fixed whatever bugs there was. I then just pushed to the repo (after testing of course).

This bloody morning, supervisor came in and gave me more bugs to fix. When I thought she was done, she said "Hey. I saw the fix you made to the system. The bugs are fixed but the retrieval of the timeslots is now pretty slow. Could you see what is the problem?"

Slow.. She said that it was slow. And asked if I could fix it. I already told her what the problem was and she did not want me to waste time on it. But she wants me to fix it. WHAT THE FUCK IS WRONG IN HER BLOODY HEAD! I SWEAR TO GOD... UGHHHHH I swear I was already waterboarding her in my head. YOU WANT FAST?? How bout fucking allowing me to refactor the code?? Fucking shit head. I think I should take up yoga.

MS should employ a person who just scrolls through devRant and notes all the bugs and problems

Had to do an assignment in Haskell and had some bugs all over the way. After some Wodka I did a one liner that worked but I never found out why. 10/10 would do again

I've fixed all the bugs in the issue tracker that are "fun to solve". What remains are vague reports of unexpected behavior.

Today is going to be tough 😫

Thank to “Weekly Rant 119” we all had to clean the place where working, eating, gaming, chilling, sex, porno watching, bugs fighting ,duck fucking, etc etc etc.

Salute to @dfox !

When you are given a task or bugs to fix and your boss will tell you everytime that, "this is so easy this will be done in just 3 seconds".

WTF! Then don't hire devs and do it yourself! And start fixing all the damn bugs in just 3 seconds yourself! There are 28800 seconds in whole fucking 8 hours, I guess if we divided it by 3 you can finish a task or fix a bug at approximately 9600! (Applause) Now we are silently calling him "The 3 seconds man'.

Me when I'm updating my projects:
"I put some new code in,
I took some old code out,
I put some new code in and I tested it all out, I fixed some major bugs and I pushed the update out. That's what it's all about!"

Sandev. The santa dev.

If you are a nice dev, he makes your code work... If you are a naughty dev, he fills it with bugs.

If you are an immensely naughty dev, he disables all browsers except for an older version of IE, rm -rfs your linux distro, and magically makes android studio eat up more ram than usual.

If I died, I would have one regret.

I once worked in a code base whose messiness would make an oil spill in the fucking pacific ocean look like spilled milk on the floor in comparison.

Naturally, it had bugs. Oh BOY did it have bugs. Most of them were taken care of well enough. Or about as well as anyone insane enough to work in that code could.

There was just this one bug, which I still (un)fondly call "my bug of 2 years". It. Just. Didn't. Make. Sense.

It was written in JavaScript. Naturally. Which by itself, is the metaphorical programming language equivalent of a pile of horse manure. But this bug. It was the guano icing on top of the horse manure cake which is JavaScript.

I LITERALLY spent 2 years trying to find a solution. I woke up at night, thinking of explanations. I had dreams about fixing the damn thing. And I never did.

On the day I left the job, I had to pass it on to a friend (who hasn't solved the fucker yet either).

I hated that bug with all my heart. But..

Now that I think back, all the books I read, all the docs that I scoured, every non working fix I coded and every failed efforts I made on it, eventually made me a better programmer.

So cherish your bugs and issues. Sometimes, they come, not to hurt you, but to help you grow (unless you use JS, those bugs just wanna fuck you).

Fucking retards. They make us submit 3 fully fledged fucking Android apps (with ALL the generated boilerplate crap), all zipped into one fucking folder which cannot exceed 10MB.

ARE YOU FUCKING KIDDING ME, YOU DUNG-EATING PREHISTORIC APE ?! ONE PROJECT ALONE IS 60 MB, HOW IN THE MOTHER-FLIPPING HELL DO YOU EXPECT ME TO FIT 3 OF THOSE INTO 10 MEASLY MEGABYTES?!
Ever heard of git you moth-eating-cactus-fucking pricks?! Time has come to learn it !!! Private repos are a thing, you cocksuckers.

May your bed be infested with bugs and your code riddled with Greek semi-colons. Fucking dimwits.

Attend all the meetings, they said. They're super important, they said. You'll get more code done if we hyper-report on progress they said. The bugs are piling up and we need to have even more meetings, they said.

STOP SAYING THINGS AT ME AND LET ME FUCKING CODE YOU INSUFFERABLE CUNTS.

Not really a recruiter but at interview at one place I was given a printed code example and told that there was 8 bugs and that I shield treat it like a code review.

I found 16 bugs and 4 bad practices and explained them all to the director of software engineering and team lead (that set the test), they agree that I was correct; the director turned to the team lead and said ... Are you are your a senior

I tried not to laugh lol

"As a team, we have the shared responsibility to ___".

(replace with ALL of the following: resolve bugs, do junior's code reviews, clean up dead code, keep the kitchen clean, improve test coverage, write documentation, order coffee beans, etc)

NO. JUST FUCKING STOP RIGHT THERE. Shared responsibilities do not exist. A single person is responsible, and can optionally delegate tasks.

EITHER I DO IT AND I'LL BE FUCKING AWESOME AT IT, OR SOMEONE ELSE DOES — BUT I'LL SLAP SLACKERS IN THE GENITALS WITH MY KEYBOARD.

Fucking startup hipsters with their community driven attitude, this way no shit gets done, ever.

Me at midnight: let's release a demo build

Me at 1 am: why are there so many bugs? Why won't it compile.

Me at 2 am: omg finally compiled. Runs it, buttons don't work. Closes it, reopens it. Buttons work.

Me at 3 am: let's write apologetic posts for the bugs, but post the version anyway

Me at 4 am: why do I advertise in so many places

Me at 5 am: let's update the patreon reward tiers

Me at 5:30 am: nah fuck this, going to bed.

Mom at 9 am: wake the hell up we need you to dig out a hill and build a stone wall around one side of the house.

Me: omg wtf why.

Me at 2:30 pm: why the hell are we doing this, I have so many bugs to patch and everyone knows they are there because I told them all!

Staring at cursed blinking cursors.
Repairing work of worst thinking workers
Reverse merges or it'll murder the servers, it nurtures despair
Amateur managers, dimwitted savages interrupt all of us janitors
Cleaning up damages, spills and experiments using skills in embarrassment
Explicit foulness, in a minute it's straight to the bowels with weapons of limitless vowels
A bittersweet hateful machete, eviscerates stateful spaghetti
The slow disease flowing from keys knowing it's going to please
The growing unease, no one agrees, there's no guarantees with your useless degrees
Need more drugs, keyboard's crawling with bugs, falling as I chug
A bottle of cognac gotta love all the hacks, no poise for code that lacks
All the noise, gotta relax, before I destroy the syntax.

Excuse me for not making sense.
Too gloomy, aching and tense.

We have 1 guy managing everything. He develop our CMS, customers email client, manage our network, servers, domains (our own domain servers), billing system, SSL certificates... In short: everything (as well as bugs). The entire company relies on 1 guy, pretty much.
Brings the phrase "all for one, and one for all" to a whole new meaning.

fixing bugs all week, when you think you're finally done and you break the build...

Out of all the bugs, the most annoying are the ones that come out and make me say "WTF?!?!? WHY THE FUCK HAS IT BEEN WORKING FOR THE LAST 2 YEARS??!!?!!??? THERE"S NO WAY IT COULD HAVE!"

When the bug surfaces, you investigate and see that it indeed IS a bug and there's no way it would ever work w/o a fix. But then SOMEHOW it's been working just fine for years....

It's like server elves went on strike and said "no more, it's enough covering that bug - it's time you fix it, lazy-ass idiot!"

Two friends and I are about to publish a side project in two weeks (for an open Beta) it feels good but I am kind of nervous...

Today I found new bugs and I don't know yet if we have the time to fix them all...

Do you have any tips / experience you could share with me?

It's my 2nd week into my new job. I asked people what they think they are doing.

The summary:

Senior dev: we fix bugs
Junior dev: we write code
Intern: we create the future

It depends how you look at it. They are all called software engineer or developer.

When starting a project at work:

My name everywhere. Every file, every change-list I proudly put my name to prove my skills.

Program goes for validation:

Thousands of bugs.

Realize that I've written shit code. Slowly removing my names from all over the code.

/**
* Do not read before New Year.
**/

Happy coding to all of you guys! My very best wishes for this 2018. May your code be free of bugs the whole year.

P.S. Fuck you testers (just kidding, we need you)

The 2018 bucket list!

I sort of swear to be a good coder, to take honour and dignity in all the lines I write, I will not take shortcuts, I will obtain a +80% test coverage across my projects, write clean and accurate documentation, and ultimately I will write less bugs!

Yea..., probably not but worth a try anyway!!

boss: we should map all the possible ways to do things in the system so we can test them and make sure we fix the bugs.

Me: yeah, well, that is exactly what automated tests are for, every time we find a non-mapped way that breaks this we make a test out of it and fix, this ways we end up mapping the majority of ways.

Boss: yeah,yeah ... Let's sit down latter and map everything on a document.

I bet my ass we are never gonna have tests as a part of our workflow.

Update log: performance improve, API rewritten, fixed all bugs reported, new features implemented, general cleanup of code, documentation and comments update
Feedback: love the new background colour!
😞

Here's to the next orbit around the sun y'all!
Hope we all push unit tested code with the least number of to-do's, and fix more bugs than we create!

Going live on Friday afternoon.
- no way, too many critical bugs! - I said
- we will - the Key account manager said.

Friday is here, still many critical bugs, I was right, it's impossible.

The Key account manager just dropped all functionalities with critical bugs and tricked the customer into thinking it's ok.
So we go live.

He was right, we can.
Oh yeah.

I like coding at night, nobody bothers you... Anyway, I'll never forget when I had to write a Huffman compressor(and decompressor) in C for a school project. It was New Year's Eve of 2016, as fireworks were blowing outside the window of my room, I was fixing bugs. Then, around 4am, I fixed all the bugs. I felt exhilarated as I started compressing and decompressing random images on the internet, comparing hashes.
One of the best New Year's Eve ever... Don't look at me like that... I like being weird.

3 hours making this beautiful circuit to test stepper motors.
Arduino nano + L293D + pot
Fucking bitch has a short circuit somewhere and can't find it out...
Made the same project in a breadboard in 15 minutes and it's working.
Fuck hardware bugs.
Cutted in the middle of all connections, took out excess solder... Nothing.
Fuck it, moving to the next ideia

Help?

I work in support and some of the developers here don't seem to realize that their customers can't use the app they wrote because of all the bugs, but they freak out if anyone so much as *thinks* there's a problem with the code.

We have evidence it's their code. How do I get them to see I'm not saying their code sucks, just that a few changes might help performance?

I don't want to insult them, but at the same time, they're only responsible for one application...

I had a client that used to send emails to detail requests or report bugs on a software.
Now, believe it or not, this was the regular way:
An email with just an introduction and a Word document attached, containing very verbose descriptions (usually not in a human known language) and most importantly, screenshots.
What's so weird about this? Those pictures were captured with printscreen, printed on paper, scanned and then inserted inside the doc 😭😭
Why all this? I don't know, otherwise I wouldn't have posted it as #wk32 ☺

I doubt the Apple Review Team would accept Xcode given all the bugs it has.

Tunes throughout the work day...

Someone's interrupting:
Queen, Don't Stop Me Now

Working on same bug for hours:
Muse, Supermassive Black Hole

Merge Conflicts:
Jay Z, 99 problems

In the zone coding:
xzibit, Concentrate

All bugs squashed, deployed, going home:
Louis Armstrong, What a Wonderful World

This junior dev is killing me with all of the bugs in the code ... like did you even test it to see if it works fml

Wishing all the developers out there a very happy and prosperous new year. May your code always compile on the first try and your age gets incremented without bugs.

Before becoming a developer, I used to work as a sales rep at this company that spent a good amount of time building what they believed to be an innovative state-of-the-art “code generator”. It was basically a scaffolding tool for generating software.

They were using it to auto generate customized iOS and Android native mobile app templates, along with a web backed.

The problem was that the generated code was shit, and the developers on the team basically spent more time fixing bugs than if they had built everything from scratch. But their passion for the product meant they just kept using it.

For some reason they never fixed issues in the original templates, so basically all the bugs that were found, kept showing up with each new app!

I have never seen apps like this that essentially had more bugs than features. Opening more than 10 app screen meant the app would freeze and crash. Sign up forms were actually dummy forms. The list goes on...

All the apps had the same shitty UI. For example, Product pages had a product image area that was like 5% of the screen view!

Last but not least, apps had a backend IP address hardcoded pointing to a server with an IP address that was temporary. So one day they had to restart the server and suddenly all customer apps stopped working and required a software update to work!

It was amazing seeing how a team of 3 developers trying to fix messy autogenerated code, couldn’t accomplish what was essentially a website on an app that I managed to build in my free time.

That’s how I knew it was time to quit my job and code full time.

How to piss off a developer?

1) Make your SDK bundled with an IDE and provide no way to update only the SDK, forcing them to loose all of their IDE settings and customizations.

2) Make GNU tools bundled in the SDK that are compiled 10 years ago and haven't been updated.

3) Provide a Linux version of the SDK, but only save all files in Windows-style line endings.

4) Provide SDKs that introduce bugs and break builds.

5) ???

6) Profit!

My nipples are hard, as hard as diamond. For no fucking reason at all.

But aside from that important update, does anyone just get this absolute light-headed euphoria whenever they realize they've fixed a bug?

Like my god, its the best feeling. I've only fixed other people's bugs a few time, and even then I experienced it.

There are two type of bugs that will keep you awake all night.

Mosquitos and bugs in the code.

Both equally annoying

Merry Christmas as well to all the people who have to program, monitor servers, fix bugs and all the other stuffs!

Monday morning: The last straw.

After talking about in a previous rant about how my client wants to fix bugs that keeps popping out after bug fix.

Today I discovered, that all C-levels, worked all Saturday to "fix my code" because it "didn't work" and we "needed bug fixes not pretty things".

The app version I was working on for the last week is gone. Without mentioning that their "CTO" wrote a fucking crappy code to disable features that I added, breaking the build step.

This shit is enough for me, I'm done!

Google: buys Android
Makes tons of $ from Ads
Meanwhile 7 year old bugs
Are still not fixed

A bug reported in 2012: recently created files are not visible when using MTP protocol.

Guess what? I still have this bug on my 2017 phone, like many other people.
Probably has something to do with file cache.

Because obviously 7 years is not enough to fix a stupid bug. Especially when Google is busy implementing all the other features nobody asked for except marketing department

To all you fuckers out there giving bad app rating because some shit does not work on your shitty phone and you are to fucking lazy to report the bug via the fucking "send log to dev"-button that pops up with the exception.
Go fuck yourself.
And to all the user whose bugs I fixed and did not change their Bad rating - fuck you too.
And oh.. The fucktards that did not even install the app and give a Bad rating because i am your competitor - guess what...fuck you.

That moment when you are testing the product with the PM and you remember all the bugs that happened and all you can think is that you don't trust this abomination

Got a few Jira tickets reassigned to me because the dev who was supposed to work on them got stuck on another project. It's fine, that happens.

I open the tickets. No descriptions for all of them. No screenshots for those reported as bugs, nor any replication steps. No attached test cases or, well, ANY useful information.

I talk to our BA, he says that all information I need are in OTHER tickets on ANOTHER BOARD that business manages but I DON'T HAVE ACCESS TO. Honestly, these shitfucks could've just done simple copy/paste. But nooooo...

So I reassign all the tickets back to their original reporters (business testers) with comments requesting more information.

It's been a week. Now I have no idea what to put in my time sheet.

When your company buys a third party solution and you spend all your time emailing them about bugs in their system.

Seriously, I even sent you the exact line of the bug in your JavaScript with a suggested solution, and deployed a new stack with your latest (broken) fix so you can test out that solution. Then you email back saying it is fixed but it is clearly still broken. If I email you a fixed version of your file will you deploy it? OMG!

A web developer's bookshelf. Pre and post career. Certainly makes the bugs, chores, dev bosses, and bullshit priorities (that take away from "code purity") all the more tolerable - and introspective. Thanks Mom!

Awesome! New server!
With a newer version of MySQL
With new bugs on my websites

Seriously, this new version destroyed all the queries

I wish the Congress would run all legislation by a team of programmers. Regardless of political leanings one thing is indisputable: We are very keen when it comes to finding bugs in a piece of code -- especially if we didn't write said code!
After all: What is the law if not code for people instead of processors?

Happy Father's Day to all the ranters out there! may your bugs be few, and your code execute correctly the first time.

Leaving work with no bugs in the code! Everything works flawlessly!
Coming back the next day and all of a sudden nothing works and we need to spend the whole day getting it to work as well as it did yesterday.
There seems to be programming gnomes, ruining our code at nights!

Sorry for the excess of blury.

Coworker thinks running a query on a console is a way to proof all use-cases.

Good lord I'm still surprised at how many bugs I can spot just by overlooking his code.

I mean, what is a MVC?!!SHIFT+1!!!?

Routing is just a file importing a 5000 liner controller that is actually not a controller for it handles http attributes and sends the response themselves.

Models are just good guesses of queries or a shit load of them: see picture attached

HALP

There are so many weird hacks in the quite legacy app I work with I could write a book about all them hacks…

But I must admit, the worst of them all is internal time. Yes, so some blockhead thought it’s a good idea to represent time in a manner completely removed from Datetime objects or timestamps or even string representations. Instead we deal with them as intervals represented by integers - and because this is not fucked up enough by itself, the internal time doesn’t start at midnight, yet the integer representations do. It’s a bloody mess. No wonder most of the bugs we face have to do with dates and time…

Just startup stories:

Our backlog of tasks and bugs has officially reached 100+ tickets, all for me, the single software engineer at our "tech" company.

Huh, imagine that.

When I arrived at my new job last year they were working on developing a large site using a live server with all the devs ftp-ing every change in the build process to test it. 😵

It was not uncommon to hear 'is anybody in the style sheet?' being shouted across the office!

Needless to say, I had to fix many bugs multiple times when my fixes were overwritten!

An iOS app which was basically a wrapper for a giant jQuery eForm.
~5000 lines of custom JS and it broke ALL THE DAMN TIME. A team of us worked on it for about a year and all we ever did was fix bugs. But the bug count never went down. The bugs just got replaced with more bugs.
Thankfully its not live anymore.
After the global thermonuclear war, all that will remain is cockroaches and jQuery.

We were all drunk at a college party. I pretended that I was able to code something for a friend. He put me on his laptop and made me code. In 20 minutes I had finished. Everybody reviewed the little program and said it was all good.

When we reviewed again the program sober, it was full of bugs that none of my drunk buddies tested out

Added some features to an internal app used by finance. Tester found some bugs, but most of them were due to old code. Tried fixing them, found some more serious bugs that could have a large economic impact. Rewrote the service, squashed all the bugs we found and reduced code by roughly 50%. Felt good.

Everytime I don't sit in front of my code (and go for a walk or something), I immediately find bugs or things to improve from all the code I've written, IN MY HEAD. If you have a hard time finding bugs, try this, maybe. Might help.

Bureaucracy is the biggest impediment to progress.

Instead of putting a brick wall in front of you by saying "The PO said that you created a bug", learn how to communicate and have a horizontal hierarchy, for fuck's sake.
Even if all my tests passed, they still throw other bugs in my face and call it my fault. Fantastic. I love Scrum. This is not Scrum, this is abusing and not respecting Scrum.

Stupid rules, stupid people.

If there are bugs in your code, the problem 100% of the time is that you’re not using Rust. Just rewrite it in Rust, and all bugs, security, and performance issues will disappear. Any software not currently written in Rust should be rewritten in Rust. Rust is all you need to know as a Software Engineer. This future is Rust. Welcome to Software3.

1- Copy/Paste (code)
1- Googling before trying to fix a bugs by myself first.
1- Never finish my side projects.
2- (Worst) Still doing all the above.

Am I the only one, who likes to hate the tester for sending back your code, when I should be greatful for him/her for finding bugs?
Replies from me by the amount I get my ticket back:
1: okay, sure, thanks
2: all right
3: oh, okay
4: what? still not okay?
5: how did you even catch that?
6: what the fu** is wrong with you?
7: you again???
8: die already!
9: <singing the frozen theme> Let it go, let it go!

That thing we all tried - explaining to project managers what the difference is between back and frontend,

Today i got 23 backend bugs assigned to me as a frontend 💩

Product gets launched in 2 hours. Just casually updating the documentation. Nice chill day. Everything tested and validated.

Then some random f**king designer comes barging in vomiting all these "necessary" features to the product owner.

This was yesterday. The designer and product owner are currently complaining to us devs that there are bugs everywhere...

I need a beer.

Am I the only one that down votes reviews for an app just because the review is from someone who's incompetent?

For example: major new release, so of course there's going to be bugs. Person 1 stars and bitches about how great the old version was.

Like ok you incompetent fuck, that's not at all how this shit works.

I really like this book on the basis of the philosophy overall, no this doesn’t solve all problems but it’s a good baseline of “guidelines/rules” to program by. Good metrics or goals to architect and design software projects high and low level projects.

Fight Software Rot
Avoid duplicate code
Write Flexible, dynamic, adaptable code
Not cargo cult programming and programming by coincidence.
Make robust code, contracts/asserts/exceptions
Test, Test, and TEST again and Continue testing.. this is a big one.. not so much meaning TDD.. but just testing in general never stop trying to break your software.. FIND the bugs.. you should want to find your bugs. Even after releasing code the field continue testing.

Guy rage quit over someone resolve duplicating his bugs (when they were really duplicates) but he kept reopening them repeatedly so the other guy kept resolving them as such till he lost his mind on work chat. A few days later he is now casually sending an email (after being told to do so by management) to apologize but he skirted around apologizing and instead excuses himself by saying "we are all fellow autists to a certain extent."

I work in a bitcoin startup , my fucking boss really wants everyone to use ubuntu because of security and all , the bad thing is i am the only guy who knows how to install and deal with it , so when any one joins or has some problem he always bugs me and the thing is i am an android developer not a sys admin and now he fucking want to get 2 factor in ubuntu desktops when they log in

Pending issues : 5. Deadline is nearing.

Tweaking around, I found some bugs on functionalities that for some reasons have magically passed QA. The bug was quite simple to be found.

Created 5 issues for 5 different bugs. Pending issues is now 10.

Manager : I am not happy. Last week we have 6 and we're going to weekend this week at 10?? Wtf you guys have been doing?? Why isn't there any progress?? Are you guys not doing any work?? You guys been lazy??!

Yeah, we been here sitting around play computer games all day.

devRant bugreport

Im getting more and more bugs in devRant on my LG G2.

- Links cannot be opened
- profiles can not be viewed
- double tapping a rant opens the rant twice (tapping five times opens it 5 times) instead of voting it up.
- once in a while an opened rant shows up again under all the comments (with all comments as well). When this happens its exactly the ammount of comments.

Im not sure where to report this. If @dfox could take a look at this?

Gonna look up my android version in a sec. (edit version: 4.4.2)

*client comes to us "please take care of our app, it's ugly and the previous devs made it all buggy, especially the Android version"
*we write code, analyze bugs, fix them, QA them
*we deliver a preview
*client only looks at the iOS app, doesn't give a flying fuck to the Android app

For me there are two kinds of bugs. The ones where you lean backward and the ones where you lean forward.

If you found a bug and you lean backwards in your chair resting your hands behind your head you feel proud and relieved that you found that sneaky bastard. Good for your dev soul.

If you lean forward, resting your forehead on your fists or on the desk then it was a very stupid bug. Not sneaky at all. Something plain obvious. It makes you doubting all your career and life choices you made so far. Like needing one hour to find out that you named the "MANIFEST.in" accidentally "MAINFEST.in"...

Want to share any embarrassing bugs to make me smile again?

Google: The all mighty bug fixes for Android Studio are now live, see version 3.4
Android Studio: But I still freeze when I need to format xml files tho, but who cares...

** Days later
Google: Android Studio 3.4.1 is now live! Smash those bugs!
Android Studio: lool I still freeze when formatting an xml file ¯\_(ツ)_/¯

Client: Hey new iOS 11 is coming soon, is out app compatible?
Me: Not sure, let me shift the development to new Xcode 9 and test it out.
Client: So, how was it?
Me: pretty straight forward. all seems fine a couple of bugs.

But then when trying to fold a big function to make things easier to read, you discover that Xcode 9 beta 1,2,3 & 4 DOESN'T FUCKING SUPPORT THAT YET. How on earth is this not yet implemented?

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

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

Just spent an entire night eaning up my codebase...

I optimized some of the functions got rid of unnecessary global variables and changed up the whole file hirearchy so it would be easier to read. After spending all night doing this I went to run the program and for once it seemed everything worked right the first time! However a portion of my application that is supposed to happen at a certain date and time never would run. After spending all night comparing each and every line for what I changed versus my last commit I couldn't find the fallacy in my logic. Everything should still work like it did before. After spending more time looking for bugs I finally realized I didn't break anything when I switched over to this new structure it was the old code that was broken. I went through the old code and after some debugging eventually found the culprit an extra continue statement that prevented my loop from fully executing. Lesson learned sometimes the biggest bugs can spawn from one line of code.

You guys work from home because of coronavirus?
Me on the other hand, have to work on weekend on my desk to finish an urgent project, it’s for the ministry of education (who closed all schools and launched an online courses) to monitor the effectiveness of the new platform and fix some bugs on it.

Was talking about how I implemented CI/CD in one of our projects as a starting point to others and how it worked by running tests and deploying to the server and one of my colleagues laughed about having to have tests at all, I explained and asked him what was he gonna do that morning, his answer:

"Well, I'm gonna test the system X and fix some bugs"

To what I replied:

"If you have automated tests you could have those tests automatic(?!) and they also help you finding bugs early"

Wtf do ppl have in mind that they prefer remediation over prevention and they end up wasting their time with shit that could be fully automated?

Who doesn't love bugs, we all love them, they provide the help needed to sleep, whether they were IRL bugs or program bugs

good morning, devRant! My cat is trying to scare away all the bugs for you:

My former housemates had a cat, they moved out and took said cat. Cat had fleas which I wasn't informed of.

Cleaning out the now vacant room with a can of flea spray in hand I utter:

"Now, my uninvited friends, sooner or later, even if I have to do it individually, by hand at times, I will find you all and I will squash you for I am a software developer and I deal with bugs all the time."

I am just sick of the things that's been going on.

Joined a mid level startup as full Stack developer working on angular and node js . Code base is too shit and application is full of bugs(100+ tickets are being raised for bugs)

Since the product owner(PO) wants to demo the application he is pushing for bug fixes.

UI code:
1. Application is not handled for responsiveness all these years, it is now being trying to address. Code base is very huge to address though .
2. The common reusable components of UI has business logic inside. Any small change in business logic we are forced to handle in common components which might break up on another components.
3. Styling in 40+ components are made global. Small css change in component A is breaking up in component B due to this
4. No time to refactor.
5. Application not at all tested properly all these years. PO wants a stable build.
6. More importantly most of developers have already left the company and we are left with 2 developers including me.

I am not in a position to switch due to other commitments adds up a lot to frustration

This night I dreamt that I could build indexes (yeah, boo me on the plural) for relalife things..trees, buildings, birds.. Everything gets an index, Oprah style!!!! And once last month I also dreamt I could debug real life things.. Look at the person and see what's wrong with them.. All their stats, bugs, everythiiiiing!! So disappointend when I woke up :(

Got my program hooked up to an external sql database that’s ready to be fed into by PHP, hosted on an SSL website, fixed up all the other bugs with TONS of other stuff.

4:23 A.M. and feelin’ good.

This is for all those people that like dark themes and when asked why you say it's because light attracts bugs.

I would like to explain how that is just so wrong. Bugs attracted to light are moths and a few other flying bugs.

The rest of the bugs live and thrive in darkeness. Cockroaches, bedbugs, spiders etc.

In fact mosquitoes hunt at night and prefer to hunt in the dark.

I just had to put this out there.

Add your fucking requirements.txt files or atleast have a decent fucking readme. I have had to implement many official repos for AI ML papers now and most of them are shit with a load of bugs in them, cant you implement them properly while you are at it?

Also would like to add most of the sota results arent honest maybe famous ones are but the research community is full of shit really. All of that cant be changed but atleast add readmes and requirements ffs.
I have to spend days just to implement your sub par result providing fuckery.
I’d rather just code it all myself sometimes

Today, in "Marketing showed a Beta feature to a bunch of cusomters"...:
"I shouldn't have given access to the Beta server to the new user... They're gonna find all of these bugs and they're not gonna be happy..."
You don't say

> In an online team meeting where our manager is telling us to wrap up the final bugs and get the release out as soon as possible so we can enjoy Christmas and the last week of the year stress free
> Opens LinkedIn while in the meeting since all my discussion points are done
> First post on my feed
> mfw

"Do not lose time improving the data pipelines from our ERP, it is about to be replaced!"
Then suddenly there is a week of bugs and stress because the non-improved data pipeline can't handle new situations.
"Just fix the bugs! It is all about to change anyway!"
Repeat. And repeat.

Fuck, I hate when managers think that there are such things as "temporary fixes" in ERPs. Or that companies can ever migrate to another ERP. Those things are forever, as Cheetos dust on your bowels.

My company is (supposedly) all about collaborative work, pair programming, getting on calls and cRaCKinG tHinGs ToGEtheR. Also (and rightfully so) we’re not supposed to approve any PRs if tests weren’t created/updated.
Of course that applies to all but the old timers in the company who simply act like lone cowboys. They fall off the face of the earth for two-three days then reappear with monster PRs full of untested code.

Leave it up to the plebe then to try to make sense of the mess they’ve created, to challenge them with the fact that the PRs are lacking tests (only to be met with excuses about not having anymore time to spend on the subject).
Reprimand the plebe for not reviewing PRs thoroughly enough. Leave it up to them to fix the resulting bugs.

I’ve lost all trust in our managers, tech leads, lead devs and their guidelines and rules that only apply to others but rarely to themselves. These people that then have the audacity to criticize the tech team in it’s entirety for not being rigorous enough in its processes.
Fuck them all

Why can we all relate to almost every rant for wk24?

Devs could rule the world! Why do we have to endure all of the same crap from India to the UK?

(The recurring meetings and the 'Dynamic Requisits', as I call it, are what bugs me the most!)

Feeling sad and disappointed during a really intense sprint. Have been working for the past year on a web app made with fucking jQuery. I fixed a lot of bugs, and caused quite a few of my own.
And all this happened because I was desperate when looking for a job. I was too afraid to take my time and find something better. I just took the first offer I got.
I'm thinking of quitting, but why should I do them a favor? I'll stay and keep getting paid until they kick me out.

Me: "Sweet new Xcode update"
Me: "I'm sure they fixed all the bugs"
*starts download*
Xcode: "Want to upgrade to the latest Swift syntax?"
Me:
*clicks yes*
Me:
Me: "Fuck it, next release is 'fully rewritten from the ground up'"

All my tasks was development, last week our boss gave me a testing task, and I completed it.
He said that the developers will hate me if I keep reporting every expected/unexpected, small/big, normal/critical bugs , so that he sent me back to the development team.
I just wondering if I misunderstand the word "testing"!!?

C++ code written before current standards still complies and is just as maintainable, but every so often a new major change to the standard happens and I feel like all my code I wrote before last month or so now needs updated. "Range-based for" ALL THE THINGS. except I'm just retouching code and possibly adding bugs along the way.

Sometimes I just feel that my most mastered and beloved language suffers from a severe case of multiple personality disorder. As soon as I get to know it, it's suddenly somebody else.

I really love Mr Robot.
The show though... not the guy...

But there's one thing that bugs me since the beginning:

For security reasons Elliot destroys all his drives and puts his RAM into the microwave which of course is effective but why would you even consider frying volatile memory?

Sure... the data can remain for some time but not that long that he would risk anything...

Any ideas?

Oh and btw... SEASON 3 IS NOT THE END??? LIKE WHAAAAAT?

Fucking corporate bullshit, I was coding (mostly creating bugs and pulling my hair off) all night on my free time (I'm on night shifts I keep the schedule when I have my days off) and at the moment I was making huge progress on my project, I gotta go to sleep to go back to work 4h later to follow a fucking 2h training on team efficiency and cohesion, in other words, how to waste 2h in a useless meeting and not getting it back + interrupting the only night I was in the zone, I'm so tired of this....

A "partner" company has created a "REST" API we use on an online shop we developed to send all shop-related requests to.
At least once a month, something fails on their end and the customer calls us every time, expecting that we did something wrong, but it has never been us.
These "partners" do exactly zero testing, are extremely slow in solving API bugs, have almost no logging and have no monitoring on the API at all.
Today at noon, suddenly no customers were able to order anything anymore for 4 hours.

How the fuck can you run a business so unbelievably brainless that this keeps repeating monthly?
Time they fire all their "devs" and everyone in charge of the company and operations. TERMINATE.

Found this gem in a comment from a couple of years previously:

// This shouldn't be here - needs moved to a separate handler. Likely to cause all sorts of weird bugs

No shit, Sherlock! Like the one I'm bloody trying to make sense of now!

I really lost my faith in our profession.
A Software&Hardware solution that costs more several 10.000€ is broken after every update.

The Producer even achieves to break untouched features in new releases.
No communication at all. If you report Bugs, they are your fault. The whole system has absolutely no security at all.
It is unsecure by design.

And even if they hear your Bug report you have to pray that they will fix it.
Most if the time you have to wait the whole year for a new release tio get your bugfixes.
But there are also bugs that are untouched for years.

WHY? WE PAY YOU!
I want to cry

Company uses Trello to track bugs and features the devs are doing.

End of the week the PM: "So what bugs and features did you work on this week?"

If only there was a platform that we could track all these things... 🤦‍♂️

♪ All around me are familiar faces
Worn out braces, worn out faces
Bright and early for their daily standup
Going nowhere, going nowhere
The bugs are filling up their tracker
No expression, no expression
Hide my head I want to drown my sorrow
No tomorrow, no tomorrow ♪

Wake up in the morning and my girlfriend told me I have been mumbling about bugs all night. God, I need new projects, so tired of maintenance work

Hi everyone.
I wish you all a 2017 full of code, of problems to fix, of oportunities to learn new languages and above all full of bugs to fix because from this, is from wherr we learn the most.

Are you.. are you telling me .. that every time ..... every time ..... I've been running ..... npm i something .... it's been putting ^version into my ..... package.json file ?!?!?!?!!? SO THAT IN THE FUTURE WHEN I COME BACK TO THE PROJECT AND DO A FRESH NPM I .... THE VERSIONS WILL ALL UPDATE .... AND THAT'S WHY I'M ALWAYS DEALING WITH BUGS WHEN COMING BACK TO PROJECTS EVEN THOUGH IT WAS WORKING WHEN I LEFT IT A FEW MONTHS AGO.

FUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

No error handling at all, not even a single try catch. Program crashes when the wind changes direction. Previous developer developed his test plan around his bugs. 😭

Don't understand what the hype about Elementary OS was. Used for ca. half a year, do not see any benefit.

If this is supposed to provide "usability" on a Linux kernel, then I am sorry, but in this regard it is a tremendous failure.

All tasks take long, there are all sorts of bugs, today I needed a multi-monitor setup for a presentation "real quick", dear lord was that a shitshow.

Nah, this thing is not for me.

DAPHNE: We finally caught the mean old Edge Browser! Now let's find out who you *really* are!
SCOOBY: Ruh-roh!
SHAGGY: Yoink!
DAPHNE: Gasp! It was Old Man Trident Rendering Engine all along!
VELMA: We could have worked it out from how Edge has exactly the same bugs and performance problems is IE!
OLD MAN TRIDENT: And I'd have got away with it if it wasn't for you pesky kids!

Managers don't understand that there will ALWAYS be bugs shipped to production, no matter how hard you try to prevent or test against them.

Devs: lol

inb4 any comments really, i've seen facebook, instagram, and all the 'big players' crash and have bugs multiple times before, so don't go around swinging your dick like your company's software has no known bugs (don't even get me started on the devrant mobile app) I'm just saying bugs are a fact of software

God I hate when dev work gets all political.
Our team had a technical meeting with a difficult partner/customer, that wants to connect to our internal service, so we are writing an Integration Service for this.
Apparently the project is very important on both sides and highly political so in the meeting there was a member of the Board of directors of them. We just wanted to check one feature to verify they can connect, etc.
After some minor bugs showed up, that guy goes on ranting about how this is all a joke ("Verarschung" literally) and how we did not deliver all features yet as promised (Note : that was not promised) and basically indirectly personally attacked us, our company and our team.

It's incredible how such assholes can stay in such positions.

We make a small server product with a web based admin system, as we were going to have limited customers who will use this (usually just the engineers) and this was not on the www. We dropped all support for all browsers other then chrome/firefox. No more IE/safari bugs for us XD

Oh yeah am very religious.
I attend the Church of JavaScript.
We code 5 times a day.
And pray on Sundays for Internet Explorer.

By keeping away from bugs and living a functional life
We will all one day meet the web in native paradise

Project Manager logic (the best kind).

PM: Here are a list of the tickets we need to address next.

Architect: Hang on, didn't X raise a number of critical bugs yesterday? They were serious, we need to fix the critical bugs first.

PM: ... but he marked them all as critical

(so that means they aren't an issue? cool, i've been doing this wrong all my life)

The world's largest rubber duck is a couple hours from me at the moment, I plan to visit with all my major coding bugs and errors, hopefully his size and wonder will help me fix all the big issues my little one couldn't

To all devs out there who don't use the toilet flush in company: FUCK YOU! I WISH YOU 100 BUGS EVERY DAY AND MAY YOUR FUCKING CODE NEVER COMPILE YOU DISGUSTING PIECE OF SHIT!!

My best dev experience this year was the success of my company intern app at work, where I am employeed since last December beside my studies.
The company founder, the CEO, the head of department and the marketing department all like my app and in January it will be deployed to all company phones 😀
Whish me luck that there won't be any serious bugs 😅

I envy all those developers with clean codebases and consistent coding standards and nice architecture.

I'm fixing bugs and optimize code in someone else written project. which looks like spaghetti. with naming conventions like "a", "bbb", "zA" comments written in unknown language and off course the deadline was yesterday.

I just switched from Arch to Fedora...

I know I know that all the cool kids use arch, but right now I'm not up for checking out random gdm bugs or some other manual tasks. I need a stable, fairly supported and well maintained distro and fedora just works!

The development department got an order to remove certain functionality from our current server monitoring solution, so that we had to use a new, still very in development solution, that is full of bugs and super unreliable.

End result? We now have to have two windows open all the time, while also hoping the new solution actually works, as it tends to stop refreshing randomly, and tends to give false positives a lot.

This is how I feel after resolving all the bugs 😁

Still not sure about this new guy, not trying to be rude but everytime we're talking about code he says shit that makes me wonder how he got hired. (btw he is hanging with the IT department all the time) He's a very nice guy, but talks massive shit when it comes to bugs/new features/etc.

Should I have a look at his pc to see what he's doing when in office or is it none of my business. Help me out here, I'm really curious but don't care if he's a fake at the same time lol.

Our PM just send a mail to our team, that after testing the latest extension we made to the project, he could not find a single issue or bug (usually there are some minor UI problems or some edge case bugs we did not think about or know existed)
and what a incredibly great job we did, and he also forwarded the mail to all our managers up the hierarchy right under the CEO.
The appreciation is a nice change to the self-hatred I feel while coding

Product manager: When building new features, we find we have bugs that reappear in other parts of the app where the bug was solved before. We have to find a solution to this issue.

Dev: These are called regressions, they happen all the time in software development.

Product manager: ...

Dev: Fuck outta here! Its friday!

Not sure if yelling at someone for not listening counts as a fight.. 🤔 since he wasn't listening..ever!!
But yeah, my ex coworker was a champion in not listening and doing stoooopid shit, from not following orders, to cheking in all the files in solution to tfs (no changes + debugging shit etc) which made it a nightmare to find and fix his bugs.. I just gave up talking to him alltogether since he only wasted my time and didn't listen to any advice/order..

I always love to stare the application that I develop... First I start with admiring it... then the things that could have been done to enhance the feature.. then the bugs that could only be seen by me.. then all these results in new update of the application and this cycle continues 😂

>ooo new thing to play with and learn, yay!
>*Installs using directions*
>Hello world program fails
>Oh I need these dependencies
>Wait the deps all need their own deps...
>But one of them is deprecated.. what do?

I love the feeling of working on something new but
I hate ending up spending more time getting a workflow setup and chasing down random bugs or hacky fixes just to get something stable so I can start working!!!

someone please motivate me to code again.

since one month i did nothing but digital art/youtube watching/maths/chatting but i did not code.
the main reason being that all my projects have bugs currently :/

I am surrounded by incompetent fucking idiots, from the team lead that does a half arsed job at coding and then wonders why nothing further down the chain works to whole component teams that seem to be lagging so far behind they don't even know what the current code base looks like.

And who's in the middle of it all running around fixing all the problems these fucktards create, why yes it's me.

I would leave to let it implode and see what they'd do but I already know, they'd leave it till I got back so I could fix it all for them.

Feel like going around with a rolled up news paper and whacking each of them on the back of the head while screaming "no, bad code monkey, bad, fix your own bugs"

I hate being the go to fix it guy sometimes.

Copy-pasting 90% of our entities including logic and merging some - creating thousands of duplicated lines - and then creating views for those abnomalies just to speed up the ORM fetching which could have been done with a single join...

Took me some time to delete all of that fking shitty untested code full of bugs...

I'm working on a project that is being shipped to production this friday, so we're killing all bugs and finishing all remaining features.
Sadly, one of the main devs just took his vacation last friday for THREE WEEKS, and being the small team we are, it feels like we'll need to work non-stop extra hours every day to meet the deadline.

The problem is, I can't sleep right now and it's 2:30 am, so fuck me.

When you finish the complicated code for a feature you spend all day on and it runs without bugs but instead of returning the high-wife your gf looks at you, asks what the feature does and at the end says "but that sounds really easy to make"

If you call yourself a developer or consider yourself part of the IT world and at the same time complain about software updates (all those dumb windows update rants) then do one of the following:
1- write a multi -million line of code OS that runs on virtually unlimited number of PC configurations and hardware and get the code right the first time with no major bugs, no security vulnerabilities, and a consistently fast and stable performance.

Or...
2- stop calling yourself a dev, or part of the IT world.

If the last 2 options are unreasonable, unachievable, or unfathomable.... Then stop bitching about software updates.

In the “Qualities of Great Design” session at #WWDC2018. Really wish the Xcode team could be sitting in the front row so they couldn’t sleep thru the session...

oh i guess being the optimist I was thinking they would even be here. Silly me.

All the bugs that drive me effen crazy are clear and present in Xcode 10 beta. Stupid shit still rules at Xcode Central.

I work with a guy who is genius in his field, but doesn't have much ability outside of it, his view is we should all know what he knows and not bother him with bugs in his code we should fix the issues ourselves. Oh how the shoe was on the other foot when he needed help with a personal app.

Everyday I come to work. I feel miserable. Everyday write code. Fix difficult bugs. Go home dinner sleep. Tomorrow repeat.

I am reading Jia jiang's story. Mel Robbins 5 seconds. Christ grace's lectures. Still feel miserable. What is the meaning of life? All I want is to teach people code.

So I do not get why people use ReactJS. I hate it. for 3 years passionately. And I have to work with it every day.

- one-way data binding
this makes you write twice as much code, which will have twice as much bugs, you need to read through twice as much code from other devs.
- mixing html and JS
after all I like to pour my coffee on my omlette so I can eat and drink at the same time in the morning. This kills productivity and ugly AF
- not unified
Every dev uses their own special snowflake framework with React there is no unified way of doing things and you cannot use your familiar tools. Every project you need to start over from zero.
- Bugs bugs bugs
infinite loops, max update depth reached, key not present on list element. Let me ask you something dear ReactJS. If you know that there should be a unique key on that element. Why cannot you just put it there and shut the f up?
- works reeaally slow when compiled with TS
ReactJS was never designed to work with TS and now the tools for it are really slow. And why TS? Explicit contract is always better than an implicit contract. TS helps you in coding time, but for some reason React devs decided to worth 3 seconds to wait for compile and then realize you mad an error. ReactJS is bad and inefficient so stop making projects with it please.

I hate Intellij so much ...
* it has the weirdest bugs
* like window focus not working properly,
weird comment/uncomment short (jumps one line down wtf)
* It is slow as hell
* doesn't compile properly (or doesn't give a shit telling me about its actual status).
* Not even the build log is working properly. Why can I hide WARNs but no INFOs?? WTF
* Panels are all over the place and keep coming back, regardless how often I close them ....

ARG ARG ARG, *smashing face on the keyboard*

and the worst ... even though I have the F***ING ULTIMATE version, it constantly nags me about BUYING THE F***NG ULTIMATE VERSION AAAAAARG

Dear app, if you say that your update is for bug fixes, you better fix all those bugs instead of releasing and releasing an update with the same bugs still there. Better look into the UI/UX issues too. Your app looks horrible! Last time I was involved in it, everything is looking so fine I haven't had a bad review for a long time. Hope you can read this. #ktnxbye

Twas the night before deadline,
And all through my house,
tons of bugs were scurrying from the
onClick event of the mouse.

Seriously though... Dreamweaver CC needs to revamp the way they implement bootstrap snippets. Specifically the navbar hover and click on <ul> dropdown menus.

You know what really bugs me? How movies show people hacking into something with the terminal and all the matrix code but its really not like that.

Target: Migration of an old system(not developed by us) to a new without touching existing applications.

Todo list:
[✅] Migrating old webservice from VB.NET to C#.
[✅] Decide if we go to the old system or the new based on the document class.
[✅] Start implementing same logic to the new system so the results will be the same.
[✅] Stunble across a search method with fuck up logic.
[✅] Create test cases to foresee all cases.
[✅] Implement logic for new system.
[✅] Stuck in infinite refactoring to fix existing bugs brougth from the old code to the new while mantaining the response the same.
[ ] Become insane during the process. (In Progress)

Debugging WebRTC is pure hell.

For starters, it's JavaScript, so you know this isn't gonna end well. Second, it's still in kinda beta phase for some browsers so you gotta add polyfills. Let's talk compatibility now. During normal days, yeah, I could ask for a couple of computers in the office, each using a different browser. But, covid. One browser mishbehaves and doesn't wanna share the camera with the other browser, so I can't really test a connection with the only 1 computer I have. I can't take my partner's computer all day to debug.

Solution: ask the marketing department or even the execs to video chat with you to test it on a staging server. So I push my changes to the server, wait for them to build, call my lab rat, check all the bugs, clean the code, push the changes back up. No fancy breakpoints. I'm doing the old style like my great uncle did. Oh wait no, he was pretty intelligent, but my lab rat isn't. They probably don't know what a console is. So no baby I'm not only talking about console logging the problems, I'm talking `alert` the heck out of the bugs - okay no, I'll just display the objects in the middle of the screen. The screen is my console.

Despite all the code bugs, manager worries, colleagues' annoyances, self pity, low self esteem, constant guilt all the way, we are still alive and kicking

I guess 2022 will be nothing different but I also wish it will be super interesting and satisfying

Wish You And Your Families a Very Happy New Year 2022!

The person responsible for making layouts in CSS/HTML got moved from our project and now our team had been forced to improvise by ourselves until a replacement is found.

Suddenly all those old, untouched bugs seem very appealing.

Spends 6 hours trying to fix all the bugs...

Missing a comma on line 3...

Having a manager and client and boss who know no programming is frustrating because when they post issues on the repo as bugs and critical but its neither of those, the terms lose all meaning because whats really happening is

THEYRE REALLY BAD AT USING COMPUTERS.

I cant keep this inside anymore I have to rant!

I have a colleague that is an horrendous loose bug-cannon. Every peer-review is like a fight for the products life.

Now I understand - everyone makes bugs me included and it is a huge relief when someone finds them during peer-review. But these aren't the simple kind of bugs. The ones easily made when writing large pieces of code quickly. Typing = instead of == or a misshandling of a terminating character causing weird behaviour. These kinds of bugs rarely pass by a peer-review or are quickly found when a bug report is recieved from testers.

No the bugs my colleague makes are the bugs that completly destroy the logic flow of a whole module. The things that worst case cause crashes. Or are complete disasters trying to figure out what causes them if they are discovered first when the product reaches production!

Ironically he is amazing a peer reviewing other peoples code.

But do you know what the worst thing of all is! Most of the bugs he causes are because he has to "tidy up" and "refactor" every piece of code he touches. The actual bugfix might be a one liner but in the same commit he can still manage to conjure up 3 new bugs. He's like a bug wizard!
*frustrated Aruughhhh noises*

I've spent several long nights and even pulled all nighters debugging issues patiently. Even the most frustrating and ugly bugs, I've dealt with calmly for hours.
But this. Numbering fucking lists in Word. Why the fuck is this fucking crap piece of software trying to teach me how to fucking count? For fuck's sake, when I'm on level 2 of a list and I say I want 4.1, I mean fucking four fucking point in between and a fucking one. I've been screaming and pulling out clunks of hair for the past half an hour now before it decided to just work.

And now, towards the end of the report, all of a sudden it just decided to change the dictionary language to fucking French! Fuck you, Word!

How are you supposed to fix bugs in your program where:
1. it has been investigated before and was not found how to reproduce it
2. it cannot be tested at all
3. never happens on the test environment

fml

Ran an app release yesterday, adding some new stuff and fixing a few bugs. Was scared this morning because APM didn't have any errors and the app was already in use by half of the userbase.

Turns out it's the most stable release so far! Day's all good again :D

After requirement are all agreed.
Client: How long will this development takes?
Me: About a month.
Client: (Pause for a while) The previous developer took 6 months and the system was unusable with a lot of bugs.
Me: ... (I should have ask for 3 months at least)

*Repost of my own accidentally deleted post*
A Short story that i made on an Android component
===============================

Once upon a time there used to be a ViewPager who was not able to load a Fragment UI.
All the ViewPagers in town can properly load the Fragrant UI but this one was little different.

He wanted to be more then just a ViewPager. He used to see an Activity that can load anything. He was inspired from the Activity and wanted to be like the Activity but his destiny made him just a ViewPager.

So he refused to cooperate. He started to protest silently, No log, nothing.

Everyone assumed this ViewPager have a bug in it. but he was planning something really big that will left everyone in shock and awe moment.

He was planning to rise against the evil 😈 developers who continuously making him to load Fragrant UI

He assembled the biggest army of the bugs that humanity ever seen to counter the developers.

He distributed these bugs in all over the developer's code to make them fire from their work.

Even he taught bugs to not caught in QA testing but appear in production randomly.
So they silently started going into production

And then chaos is erupted all around the world, bugs started to surface and interrupted the daily life of humanity.

In this chaos the ViewPager RAISED!
And took over all the base classes.

ViewPager was unaware of few facts. this unnecessary rise in his power made whole system unstable

Without the base classes the system finally collapsed and then ViewPager as well with the system.

This was the end of everything for the ViewPager but he was satisfied as he lived the life he always wanted

THE END

the word bug has lost all meaning to me because all issues in the repo are labelled "bug"

That being said, the best bugs I fix are the ones where i can say its IEs fault and theres nothing i can do so i dont have to do anything because IE will never be updated

my company believes microsoft dynamics crm is the solution to all enterprise problems and they have used crm to build all manner of stuff it wasn't meant for. now we have bugs when users perform the slightest tasks..when people who dont know shit make tech decisions it always goes down south.

It's 9 at night, I am finally logging off and my project manager sends me a qa report I have been waiting on for a week

He decided we need to launch today, I have a list of bugs to fix and I am falling asleep

I fix all the bugs in record time, send him the preview link and of course he doesn't respond, now I am gonna blow a deadline, get everyone pissed and possibly lose my job

This is not the first time this has happened, I have had this at every job I have ever worked at, project managers seem to think that I somehow know about the bugs before they tell me and expect it to be fixed as soon as they tell me about it, they will take their sweet time answering my inquiries but if I dare miss a call or not report within 10 minutes I will lose my job

Fuck this shit, I don't need food that badly

Anyone else ever get into such a groove that you solve a problem that you thought would take three days, remove all major bugs, get to a step you thought would take you a week to reach, and then spend 30 minutes looking for bugs because there has to be some. That's too much progress in a day to not have any bugs

All because you put your headphones In today instead of just listening to the science of a lab area

How to interpret when you receive bugs reported for your application?
Should I be happy that someone is using them or just be sad that I gotta fix them and how poorly I wrote the code.

Note: will obviously consider turning some of them into features. Though not all.

Finally got the last round of god awful bugs in this god awful shit code fixed. I thought I could finally get back to working on the new build, but no. My reward is updating a god damn pdf, because none of the fucktards here know how. I have to work backwards through all kinds of pointless bullshit code that apparently generates it, all to find a mother fucking image that just needs to be replaced. Thanks a lot, to the tryhard motherfucker who wrote this code. I hope wherever you are, you're in complete agony.

So, small note to all developers out here:

If you provide a Serverside program to update your software in a network, like M$ WSUS to remove internet traffic,
Please consider not to introduce Bugs in your newest version that make this Service unusable and patch it out later.

Microsoft did exactly this with the Anniversary Update 1607 last year.

Now, after each installation I have to install the most important patches manually to use the WSUS. Because when I go directly i get the newest version that is not tested in our environment. :(

This is From Sysop to Dev :-)

Some people be like:

MAN: Are you at office?
SE: No, I'm on a airplane at 35000 feet;
MAN: While you are up there, you should write more code. After all you know that bugs won't survive at 35000 feet.
SE:(sighs and facepalms) hmm that a very good point....
MAN: plus you are closer to the cloud, so server code should run faster or with lower latency at least.
SE: (jumps off the plane)

good commit message:
"make improvements to the user interface."
bad commit message:
"made improvements to the user interface"
no, you didn't. it's not deployed yet. your merely SUGGESTING improvements at this point. that's like walking into an interview telling the secretary you already got the job. flushing before you wipe. eating the pizza when it's still frozen. you are way too assumptive about this commit you've just made actually making it to production.
unless you are already on production? well, in that case, your commit message was incorrect. let me amend it for you:
"HOT FIX ALL TEH BUGS!!!11111!!11"

8 months ago, me and my teammate developed an API and a web application for one of our client. The API was supposed to be consumed by mobile app which another team was working upon. Now my suggestion for the mobile team was to use something like ionic or react-native. This was purely to keep technical debt on lower side since hybrid apps don't deviate too far for both Android and iOS platforms. But mobile team went with the native apps and developed two separate apps which both have some differences.

The client didn't even use the iOS app since past 6 months. Now all of a sudden she reported several bugs and the person managing the mobile devs put that all on us. I tested some of the bugs and seems like the same feature is working on Android but not on iOS.
Came to know later that the iOS developer who was working on the app had resigned and left the company exactly 6 months ago. Right after the apps first launch. And since then mobile team hasn't put any replacement person for the project. That fucker was trying to buy some time by putting it all on us.
And now here I am, experimenting again with Flutter. So far it seems quite decent.

with all the bugs I've created over the years, you'd think I'd be a better fisherman...

Just taken on a new client through my own business. Great news! They pay well, everything seems to run smoothly and they're a great team.

They gave me access to their Gitlab repos and all looked well...until...no branches! They have zero branches to determine what is the current live distributed project, dev project or any of the various other reasons. I don't often use git but this really bugs me!