Good thing senior developers will always just pop up from thin air when you need them, instead of being actual people who started as rookies and gradually got experience!
I’m going to claim this one wasn’t entirely my fault and should have been coded better… But I ran it.
I ran a script that expected to run from a bin directory, cd/chdir to a input file directory, then do a sed on every file to replace windows line endings to UNIX/Linux line endings. After that it would start loading and processing them.
The problem was, if the directory it tried to change to didn’t exist, it silently continued and ran it on the current directory… You know, the bin directory… With all the compiled C binaries.
So at about 16:30 on a Friday, 30 min before we started our huge weekend builds, I nuked about 70% of the binaries by randomly replacing all bytes that looked like crlf with lf. Turns out binaries didn’t like that.
One hundred percent. They gave me a crash pad through them, I could bring anything up to them without needing to go to my ultimate employer. Yes, I was a junior in the suit of a senior and I’m very much aware of that fact.
Good thing senior developers will always just pop up from thin air when you need them, instead of being actual people who started as rookies and gradually got experience!
Right?
…I mean, the company I started for gave me a 6 month crash course, and then hired me out as a senior dev. Does that count?
Not to be rude, but they gave you barebones experience then lied about your experience.
A senior dev isn’t something you can crash course in even a year, it’s multiple years of experience layered in top of each other.
A crash course is essentially just a junior dev. Your company just wanted to charge more for your hours.
I’ve got 30+ years of fuck ups under my belt so I know to avoid those and create brand new, innovative, fuck ups… You can’t just teach that.
What’s the biggest blunder you remember?
I’m going to claim this one wasn’t entirely my fault and should have been coded better… But I ran it.
I ran a script that expected to run from a bin directory, cd/chdir to a input file directory, then do a sed on every file to replace windows line endings to UNIX/Linux line endings. After that it would start loading and processing them.
The problem was, if the directory it tried to change to didn’t exist, it silently continued and ran it on the current directory… You know, the bin directory… With all the compiled C binaries.
So at about 16:30 on a Friday, 30 min before we started our huge weekend builds, I nuked about 70% of the binaries by randomly replacing all bytes that looked like crlf with lf. Turns out binaries didn’t like that.
Good times.
An European country had no access to card payments for a weekend here :)
One hundred percent. They gave me a crash pad through them, I could bring anything up to them without needing to go to my ultimate employer. Yes, I was a junior in the suit of a senior and I’m very much aware of that fact.
IMO this is the silver lining as it ensures there will be a shortage of developers in a few years, even entry level people.