there's a post going around about complexity/simplicity in coding. i'm not responding to that post, but it made me think about something funny.
namely, you can really draw a lot of parallels between "code complexity" and "management complexity".
when you start out, you're the one in control. you code what you want, directly. your simple tool to accomplish a task is short and does one thing well. the work it does may be complex, but the code is simple. ingest a file, do some twizzlering to the data, spit it back out. great.
as you move up, you start using more abstractions. you get managers. you get levels of indirection. no longer do you just open the file and twizzle its bits; you now embed libraries to abstract away what you're doing. you write functions for different types of twizzling, maybe some you don't need but maybe will be useful later. more and more things get added in.
so it goes, up until you reach now, where everything is an abstraction. managers managing managers managing you, layers of indirection, everything in these 10-layers-of-insulation-from-everything-else. you no longer embed a library to fetch your file for twizzlering; now it's an entirely different microservice on a different network that you're batching calls to through two layers of job queues. you're no longer doing so much work as just moving entries around on a jira board any more.
"what's the point of this post, where are you going with this": nowhere. sometimes i just write about things i think about, and maybe that thought ends in a funny cul-de-sac, and that's fine. not every thought has to go somewhere.