senior devops in the school IT dep: "gcc is not working, it keeps telling theres no input files when there is, and its failing most of my builds"

are you sure sir? Give it another go

(Meanwhile my friends managed to sneak a "fixed image")

see? it works.

Senior Devops: " I swear it didn't work"

(we giggle)

check the last build's .bashrc

>alias gcc= (the error message e was referring)

Senior Devops: "MOTHERFUCKERS"

Actually its just your infra that we pushed the image to, school infra is unaffected

I mean it was fun while it lasted.

haha sounds like something I would do

I would love to do stuff like that, but our school's 'infrastructure' consists of 2 dual-core CentOS 5.6 VPSs 🤦‍♂️ (and it isn't a small school)

There should be category of rants called "it was fun while it lasted". You should tag your rant with "it was fun while it lasted".

@franga2000 This campus's infra has both dev and production environments, being dev where we test new changes in client (and what we at the IT dep use) and production what the students like me use for building (although I use the dev more)

Classic school IT department pranks never get old, especially when students pull off a legendary trick like aliasing gcc right under the nose of a senior tech guy. Back when I was struggling through my own high school coding projects, dealing with broken environments and tight deadlines felt like a constant battle, but having a top-notch homework help service https://mysupergeek.com/homework-he... saved my life during those chaotic late-night study sessions. Messing with `.bashrc` is practically a rite of passage for anyone learning Linux in class, though seeing someone in charge fall for the classic fake error message is hilarious. The best part is how you guys kept the actual school infrastructure safe while still giving him a mini heart attack over his builds. Honestly, stuff like this makes those endless computer lab hours worth remembering, even if your DevOps guy probably has trust issues now.