• he/him

I occasionally write long posts but you should assume I'm talking out of my ass until proved otherwise. I do like writing shit sometimes.  

 

50/50 chance of suit pictures end up here or on the Art Directory account. Good luck.

 

Be 18+ or be gone you kids act fuckin' weird.

 

pfp by wackyanimal


 

I tag all of my posts complaining about stuff #complaining, feel free to muffle that if you'd like a more positive cohost experience.

 


 
Art and suit stuff: @PlumPanAD

 


 
"DMs":
Feel free to message as long as you have something to talk about!


Was thinking about how jobs mention "part of your role is to keep up with current technologies" or whatever, which kinda goes without saying because usually in IT jobs if you have to keep a service moving you'll end up using different, new components to maintain it. Or if you're unfortunate enough to work with shit like Kubernetes, they just keep breaking shit nonstop and you have to stay on top of it.

And I realized that if one DOES want an IT job where you literally just do the same shit for 10+ years, you need to be proficient in old, completely obsolete codebases. COBOL, RPG, Fortran, etc.

And I gotta admit I'm not 100% against the idea of, some day, committing myself to an eternity of mild pain (maintaining a decade's old codebase I didn't write) in exchange for superb job security (because there's always executives that will kick the can down the road for decades).


You must log in to comment.

in reply to @plumpan's post:

i think the thing that bothers me the most about a lot of uses of containerization is that it's....

on some level, it's the opposite of this, right?

like, don't get me wrong, it's good to standardize versions of shit, but it's so fucking weird to me that people who are okay with version ranges for dependencies then start going "yeah and we'll just use 'works on your machine, ship your machine' as a practice"

so many projects where it's like "you can either run from source or you can use our container image!" and running from source doesn't work because they locked in a version of mongodb 11 years ago, started using some weird feature that got removed, and then never thought about it again

Yeah I don't know, at the end of the day it just comes down to security fixes I guess. There's no reason why 10-20 year old libraries won't do the job just fine aside from the fact that people have had 10-20 years to find ways to break into it. If someone isn't being paid to keep the code on modern libraries then might as well stuff it in a container to be preserved in time as it were.