I didn't, therein lies the problem.
I didn't, therein lies the problem.
I embedded ample comments in my coding days. You never knew when you might be requested to revise or add more capability years later.
Anything I wrote from scratch was virtually self commenting because I used very descriptive variable names and did my best to write code that read like English. Visual Basic was a great language for that. C and C++, not as much.
I embedded ample comments in my coding days. You never knew when you might be requested to revise or add more capability years later.
Anything I wrote from scratch was virtually self commenting because I used very descriptive variable names and did my best to write code that read like English. Visual Basic was a great language for that. C and C++, not as much.
Most code I write nowadays is to drive APIs. GUIs suck ass.
Most code I write nowadays is to drive APIs. GUIs suck ass.
This was all command line stuff. After reviewing it, it was apparently to solve a problem with another program that I didn't write that wanted this file in a location, but would erase it at times. This fixed that.
This was all command line stuff. After reviewing it, it was apparently to solve a problem with another program that I didn't write that wanted this file in a location, but would erase it at times. This fixed that.
The code conundrum. Do the hard thing and go deep to fix someone else's clunky old code or do the easy thing and write an expedient patch. Young you probably chose the right path because when you correct someone else's clunky code, you usually end up owning it and all of its warts going forward - a patch can resolve the issue more quickly while you remain at arms length of owning the clunky code. The next guy that comes along after you needs documentation to know about the flaw and the patch or will be forced to reinvent it.
The code conundrum. Do the hard thing and go deep to fix someone else's clunky old code or do the easy thing and write an expedient patch. Young you probably chose the right path because when you correct someone else's clunky code, you usually end up owning it and all of its warts going forward - a patch can resolve the issue more quickly while you remain at arms length of owning the clunky code. The next guy that comes along after you needs documentation to know about the flaw and the patch or will be forced to reinvent it.
There's a lot of things running here that use files as interlocks and semaphores. It's always fun.
There's a lot of things running here that use files as interlocks and semaphores. It's always fun.
(post is archived)