Seniors: Welcome to the team. Feel free to ask anything if you need help. There is no such thing as stupid questions.

New Dev: Sure. Thanks.

*a few minutes later*

New Dev: How to comment a code?

Seniors: Google it....and please don't ask stupid questions.

Sign me the fuck up

Just 5k ping, everything will be ok...Said my friend...

Boy oh boy .... 🤭 .. look what I came across !!

boss' revenge

So here https://devrant.com/rants/1349878/... posted prank played on boss. For 3days I been freaking out what boss will do as revenge (check env and alias everytime I login). Then yesterday happened his revenge.

Was doing testing on my programs & sometime some programs would run but sometime it get segmentation fault. Seemed random first but then saw a pattern... everytime I get segmentation fault and I run again it would be fine. Checked alias... nothing, /etc/crontab, env, ps -ef... nothing seemed off, cksum of my binary... correct. Fuck! "What my boss did?" asked myself. Finally .5hrs later I saw entry in my id's crontab but then 1min later it's gone from my crontab

From there figured out how boss did it:
1) He replaced ntpd with his C program that runs in background creating an entry in my crontab every few mins
2) The entry in my crontab set to run /foobar/ulittleprick.sh every 2mins
3) ulittleprick.sh picks random binary owned by me, rename binary.name to .binary.name.nitwit and create a script named binary.name
4) Then ulittleprick.sh will remove itself from cron

What the generated binary.name script does? Sleep for 2 secs, echo "Segmentation fault", then rename back .binary.name.nitwit to binary.name. It even exits with status 139! I want to cry! Worst part is comment in 2nd line of ulittleprick.sh... kill me now

Le* developer's life

When I see YouTube videos titled "How to get a cs engg degree in 2018 "
My thought : "You should have gone to college in 2014."