SonarQube properties Update - Fuck up

User Story 0.0.1

Description

: A simple request to update the sonarQube duplicate excludes and coverage excludes properties and other xyz properties for our backend and frontend code to move out from the sonarQube Admin UI to our codebase

Why ?

- To make the life easy for people to actually know why suddenly our sonarQube starts throwing errors for our codebase - which we haven't touched in months.
The above is really a hell annoying thing to happen to anyone who doesn't have an idea why his release branch started failing.Somebody had to call out, investigate and understand what this black magic was happening. Somebody just toggling on some excludes folder in global sonarQube admin UI and you re running same build throwing different results - FUCK IT !!
Finally, spending some hours, we jot down a problem and create this user story, a simple move to config file.

Day 1 of picking up the story But this is ME [MY NAME HERE], I got a user story and I had to understand the complete thing above from a slack thread - wasted a day to understand and ask for properties - thursday productivity [50%] I'll say.
Day 2 , Damn some errors in env and it's Friday, and me trying to understand more about how to best approach the problem and probably moving it out to a config file which require and taking reference for already being done in out code. YES, ALREADY BEEN DONE IN OUT CODEBASE - GOD DAMN IT, how hard can this be ? day 2 over- productivity [40%]
Day 3 - Monday - env issues - no work on this - Productivty on this story - 0%
Day 4 - Tuesday - env issues - thinking of how to test this - Productivity - 30%
Day 5 - Wednesday - Moved to a seperate file , got understanding of how to test this, got things to partially work, path issues, waiting for pipeline to run after every test run, comparing existing pipeline result with old, again running to fix errors and no breakthrough to conclude it - 80%
Day 6 - Asked for help - Got work around approach just don't move it to a damn config if you can't , YOU DUMB piece of shit. It works, DAMN IT - Get's a sarcastic reply from lead. get's a comment, template variables in Yaml. solves it and PR is ready.
Finally , PR done , but lead is pissed of - week effort and a simple change - WRONG DIRECTION AND NOT PROPER TIME MANAGEMENT , makes this 2 day story max , make me took a week.

FUCK UP LESSON

• ALLOCATE FIXED DAY TO FINISH A STORY
• IF PROBLEM DOESN'T GET SOLVED, CLEAN YOUR DAMN HEAD AND RETHINK FROM SCRATCH
• ASK FOR HELP EARLIER , YOU DUMB PIECE OF SHIT.

ONTO THE NEXT STORY.........