Goglides Dev 🌱

Goglides Dev 🌱 is a community of amazing users

We are working on this space so that IT professionals can grow together.

Create account Log in
Balkrishna Pandey
Balkrishna Pandey

Posted on

A short story: How Mr. Developer googly his way to fixing the googly moogly bug

Mr. Awesome Developer and Mrs. Cool QA were two mad IT personnel working in the tech industry.

Mr. Awesome Developer is a go-getter who always gets the job done no matter what. He's a true team player and always puts the needs of his team first. He's an expert in his field and always knows the latest and most remarkable technologies. He's a true asset to any company and always strives to make the best product possible.

Mrs. Cool QA is a true professional who always puts the needs of her team first. She's an expert in her field and always knows the latest and most remarkable technologies. She's a true asset to any company and always strives to make the best product possible.

Mr. Developer worked day and night to roll out a cool feature in production for a legacy monolithic application called goglides googly moogly. He was also writing googly moogly unit testing to ensure not to introduce any bugs in production.

On the other hand, Mrs. QA is working hard to ensure no new bug is introduced as a part of this release.

They were working hand in hand to ensure everything would go smoothly. Until Friday the 13th, when something disastrous happened.

Mrs. QA was frantically running through the office, screaming that a new bug had been found in QA Server. Mr. Developer's heart sank as he knew that his goglides' "googly moogly" feature would have to be put on hold.

He quickly rushed to Mrs. QA's desk to find out what had happened. She explained that the bug was causing goglides to do stuff randomly; instead of printing "googly moogly," it's now printing "moogly googly" and sometimes printing "googly googly moogly googly moogly"!

Mr. Developer's eyes widened as he realized the severity of the bug.

Mr. Developer was devastated. He had worked hard on this feature, and now it was ruined. However, he knew he had to put on a brave face for Mrs. QA.

"Don't worry," he said, "I'll fix it."

And with that, he returned to his desk to figure out how to fix the goglides bug.

Mr. Developer worked tirelessly to figure out how to fix the goglides bug. He tried every possible solution he could think of, but nothing worked.

He was about to give up hope when he had a sudden epiphany. The problem is not in his coding, it was the legacy application goglides. He realized that the only way to fix this googly moogly bug was to go back to the beginning and start from scratch. Re-architect the entire program and write in something excellent programming language, and microservice it so googly moogly never happens again!

And so, that's precisely what he did. He went back to the drawing board, put on his thinking hat, and re-architected the legacy goglides monolith program. He wrote it in a new, googly programming language, breaking down gigantic monolithic goglides googly into goglides googly moogly microservices.

It was a lot of work, but in the end, it was worth it. He fixed the googly moogly bug.

He went to the Mrs. QA desk and said, "I fixed it."

Mrs. QA's eyes lit up, and she said, "Thank you so much, Mr. Developer! You're a true go-getter!"

And that's the story of how Mr. Developer fixed the goglides googly moogly bug. Thanks to Mr. Developer's quick thinking and googly programming skills, the goglides googly moogly feature was finally fixed, and goglides was back to printing googly moogly again.

The moral of the story is: when life gives you googly moogly bugs, go back to the beginning and start from scratch. You might just end up writing something even better than before.

Discussion (0)