Today I'm coding

After clearing the weeds and dirt from his boots, the author returned to his computer screen. Observing his garden resembled a battleground from a WWII film prompted him to reflect on his coding mindset. The couple had neglected their garden for years, and when the author finally devoted effort to it, the project flourished unexpectedly.

Living on a corner lot with two neighbors sharing fences, the author discovered that many unwanted growths along the fence originated from their neighbor's yard. Realizing the extent of the issue, the author meticulously uprooted the entire garden, driven by the need to address the root cause of his problems. The garden now appeared like a battlefield of destruction, mirroring his approach to programming.

When faced with a project adorned with hardcoded configurations, lack of local development capabilities, and inadequate test coverage, the author's brain refused to overlook the underlying issues. Instead of merely fixing a localized bug, he felt compelled to dismantle the entire dependency tree, eliminate bloated abstractions, containerize the environment, and rebuild the pipeline from scratch.

It was a scorched-earth refactoring spree that transformed a simple tweak into a chaotic project. The author now finds himself physically unable to continue gardening and is eager to embark on a new coding endeavor - developing a blog and a specialized booking system. While uncertain if it will lead to a traditional job, the author is determined to code relentlessly, committing to it "like there's no tomorrow!"