Throw out the baby

The past couple of days I have been adding some new code but also changing how old code functions and I have to wonder:

"WTF is this."

A person would assume, ok sure, old code may need some tweaking because you just don't know what you don't know. This is true of course but then it does not account for time constraints and just the jenga nature of the codebase.

Although I don't think I wrote any particular feature worthy of toppling the tower, it can definitely feel like dominoes connecting different towers, and you can't see the damn dominoes.

I guess as always this is more for myself, I know other real developers they build things perfect the first time and account for all edge cases and have the flexibility to swap out pieces at will cause they use ninja adapters and interface like hookers on crack.

Alas I don't, I get it working... I tried thinking of what else I tend to try but really it is all just depends.

If I go through my code I can see a lot of my "it depends" philosophy, which can be a strength and a weakness.

It can lead to constructing Rubengoldberg components that try to cover cases which it has no business dealing with, but hey , it depends.

If you look at some other codebases and projects it can be amazing how defined things are , isolated and purposed. Maybe it can be that I know the scope of my own code and although I know this one thing does but one thing I can't help but also realise the dominoes are there.

Anyhow, just a little ramble about solving a rubiks cube while trying to move as little of the already-in-place pieces as possible. In the end if everything solves I guess it hardly matters how many times the one side got shuffled.