-
Today I have co-dealt with a domestic Big Bull of Mud or also known as "what the hell you did" by my partner. Surprisely, without any drugs involved, I found an interesting correlation to software and how to deal with a #BBoM and the incremental refactoring processPermalink On twitter.com
❤️ 1 Favorite Mood -1 🙁
-
I attach a picture of what's the thing. A light that you put in the wall and does this nice effectPermalink On twitter.com
-
Because we are moving and we needed to show the home to new people that want to rent the flat, we had to take that out from the wall. I, as junior packaging life being, I decided to pay a tech debt and pull that from the wall without a proper techniquePermalink On twitter.com
-
Resolving the issue of the people to watch the flat coming in few hours but at the cost of crating this messPermalink On twitter.com
-
2 days latter, we are properly doing the packaging. Then my partner pointed out the mess I created that now I should pay the technical debt. Spoiler: she resolved the most of the mess, thank you love 🧡Permalink On twitter.com
-
What's investing is that you can not solve everything at once. You need to go one by one to properly organize themOn twitter.com
-
It does not matter how many of them you did, the speed doesn't increase much due to all the messPermalink On twitter.com
-
You need to refactor one piece at a time, extracting the mess from the BBoM, which maybe we can name it as Big Ball of Wire or BBoW 🤣 The experience is good, but what's more important is prescience and knowing that you can do less but expecting hours to fix it.Permalink On twitter.com
-
1 min of rushing and creating this mess implied 2 hours of refactoring, meanwhile doing it good in the first place would taken 10 min at most. Outcome: think twice if the adding tech debt is always the solution, sometimes is more messing than the value you receivedPermalink On twitter.com