Works if manually restarted by an intern from time to time

I have a tool that I wrote, probably 5+ years ago. Runs once a week, collects data from a public API, translates it into files usable by the asterisk phone server.

I totally forgot about it. Checked. Yep, up to date files created, all seem in the right format.

Sometimes things just keep working.

Meanwhile, had to debug a script that zipped a zip recursively, with the new data appended. The server had barely enough storage left, as the zip took almost 200GB (the data is only 3GB). I looked at the logs, last successful run: 2019
- Yes, had the same happen. Something that should be simple failing for stupid reasons.
- Need some monitoring!
Yeah, all these simple data processing scripts will always work as long as both sides stay the same/compatible
- Yep. It seems they haven't changed a thing about the format. Probably a script much older than mine on their end is generating it too.
- Isn't that true for all of data processing?

I don't see the alias in your .bashrc

yeah, um, about that. I have no idea where it comes from. We can type alias and see what it is, so if it's ever lost, we can recreate it, but I looked for 30 minutes yesterday even did a grep -R and I have NO IDEA where it comes from, or why it's named electricboogaloo

the final part of that is "written by person that left the company ten years ago"

Nah bro, that bash alias is FULLY documented in .bashrc! Idiot.

My current project has a crontab with 216 entries.

Well, here's a sentence I haven't been tempted to use before:
"I believe that may be too many crontab entries."
- Any problem in server administration can be solved with an additional crontab entry. Except for the problem of too many crontab entries.
- just randomly delete 50 of them.
- pshaw, just drop in there and combine a few
  /etc/cron.d/first25 /etc/cron.d/second25 ...
Use SystemD timers, you animal
At some point it may be good to migrate to airflow or something similar.
It's not the number of entries that makes it bad. It's the fact that if you run crontab, they are gone...
- At first I thought you missed the -r. Then I checked. Defaulting to STDIN here is very, very dumb, IMHO. Almost as bad as putting the “edit” flag right next to the “delete everything without confirmation” flag on a Western keyboard (-e vs -r).
- That's why there's a crontab rule to load the crontab from a file. Cronception if you will.

OK, I got called out

Ha, loser.
glances over at 6 bash scripts and 2 cron jobs
Not you, you're perfect

Suck my dick O’Leary

Oh man, you guys should see what I was cooking up at my old place.

Head office too shitty to give us an actual asset management solution, but we did have full access to the Microsoft suite, so i used a SharePoint lists as databases, powerapps apps running on iPads for all the data entry ux and then like two dozen hacked together power automate flows linking them all together as well as taking any Info out of the actual IT systems head office used and since we didn't have API access to those system any data feeding back in to them would be in the form of automated emails that the poor 1st line techs in head office would have to sort through and process manually.

A self-written shell script "daemon" that tails & greps log output for "ERR|FAIL"

I know there's a meme here, but as a Canadian, I'm sorry about that traitorous asshat.

I'll hear NO aspersions against my precious Cron!

Cron is magic. Cron is civilization!

Naw, mate, that's Crom.
This might come in handy.

alias thisdoessomething='cd /home/linuxuser/ && ./myscript.sh'
- alias cd='echo "command not found"'
Nobody write down that if you run the stuff in a different machine, you have to create the alias first.
And once you lose the machine and are trying to restore your backups, you can't run alias and discover what doThingy actually does.
If you try hard enough
This a joke? Cause that won't show up on another machine. Of course it's undocumented.

Since I'm somewhat of a simpleton... isn't that how pipelines actually work? The only difference being, they're all (scripts) available from a centralized system and triggered i.e. with webhooks?

Instead of a local script on a server, the system opens i.e. a ssh session and runs the script step by step remotely?

So is that the joke or am I missing something?

Pipelines are meant to be versioned an replicable, as opposed to a hack job that only runs on a forgotten server in someone's closet depicted in the meme.

I feel attacked

Yes

This used to be my remote work wardrobe. But now I dress more casually.

As much as I love the magic of working and attending meetings in your undies, I've found I'm a far better professional if I'm actually fully dressed while I work. And when I go into the office I always wear something with a collar even at workplaces where that's overdressed. It just puts me in the right mindset to be the best I can be at what I do
- I'm always fully dressed while working remotely. That is, if wearing a bow on my winkie counts as "dressed."