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.
I never had to get involved with semaphores and concurrent processes, thank God!
I never had to get involved with semaphores and concurrent processes, thank God!
(post is archived)