Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "friday 13th"
-
Yesterday was Friday the 13th, so here is a list of my worst dev nightmares without order of significance:
1) Dealing with multithreaded code, especially on Android
2) Javascript callback hell
3) Dependency hell, especially in Python
4) Segfaults
5) Memory Leaks
6) git conflicts
7) Crazy regexes and string manipulations
8) css. Fuck css.
9) not knowing jack shit about something but expected by others to
produce a result with it.
10) 3+ hours of debugging with no success
Post yours27 -
"We shall be doing maintenance on Friday 13th at 20:00 hours on our core routers"
I dont know if your insane or what. Dont think it helps that the ticket this created has 666 in its id....1 -
Maybe GitHub being down is just a joke from the GitHub guys to scare all the Friday 13th believers :D1
-
An 8 month nightmare project that failed more than it did anything else. With a team of 14 starting out and a 2 month deadline. Project ends Friday the 13th with only myself and another of the original team still left. It's crazy how issues out of our control caused skilled engineers to lose their cool and position and those that saw it through jumped up even though it all failed. Even if the project is horrible sometimes it pays to see it through to the bitter end.1
-
compile with gcc, ./a.out: "Segmentation fault (core dumped)"
compile with clang, ./a.out: runs and fails.
compile with cc, ./a.out: Alternated between "Error: Too many arguments" and "Segmentation fault"...
ffs I'm done for the week I guess.
The problem is not that it fails, the problem is that it alternates because of time of compilation, power consumption, random blody oracles or the phase of the moon in a leap year on a Friday the 13th. God.Please.Send.~Nudes~. Help.rant clang afraid to use other compilers compiler argp linking what is that cc gcc subliminal segmentation faults stumble12 -
hmm..
1. coronavirus is threatening the world
2. food delivery companies have no free slots for the next 3 days at least
3. the winds are so strong that they make windows seriously bend. Spooky stuff - haven't seen anything like this before in my life. Feels like one more gust and the window will break (wind speed -- 33+m/s)
well.. time to charge all the batteries in the house and find my zombie-apocalypse survival kit
P.S. any chance Corona is what's gonna make zombies?
P.P.S. tomorrow is Friday, the 13th and a full moon. Yiippeee!!!5 -
We deploy the website of a client today. On the 13th Friday. Before weekend. Before I fly abroad for my holiday. If anything goes wrong I'm planning to secretly run away.2
-
Friday 13th. Superstition.
0655, got WFH laptop going. 0700, VPN'ed in. Bluescreen, first in ages. Yes, Windows, the hatred is mutual. Rebooted. Windows claimed memory fault, offered check, 40 minutes. Noped out. Started machine. VPN'ed in. Some strange script error that I'd never seen before. Rebooted. Script error again. Shut down machine, then rebooted, same problem. 0715, fuck, still wearing sweaters, my e-scooter not charged, and an important Teams call at 0800.
Got dressed, stuffed laptop into backpack, hurried up by foot. Took the bus. Fuck, the next connection on the change station just had gone off. Took a taxi to make it. Arrived at the company, plugged in the laptop, started with no issues. Had the important call.
Took the laptop to IT. Tested it with external network connection and VPN. Worked with no script error. Had it checked for RAM issues. No issue. WTF had happened in the morning?!6 -
It's always the 'Poll Of The Day' on some other site that reminds me that there's an actual word for the fear of the Friday the 13th...5
-
So, today we had our first production release of our web app. Last week we changed a big part of our UI. This week we changed the design, rewrote the complete API documentation, implemented mobile support. While the release the administration center of our cloud was unreachable. Shortly after the release we made a bug fix and deployed it directly to production.
So today was a very normal prod release 😂1 -
Why isn't physics an optional class in my computer science degree?
I mean, why would they assume I will need more physics in my life? I had physics until my senior year in school, we're pretty much learning the same thing! The only purpose I see in this crappy class is to lower my average, I will never need to know how to measure forces, sound waves or magnetic fields.
I know some people will need some of this in the future but it's a very small portion I bet.
I've always hated physics and to make matters worse I need to go to exam (if we fail the class by tests we need to go to exam) and I've been studying ever since the semester is over when I could've been on vacation and studying stuff that really matters, like how to make gui's and playing more with Linux and C. But no, I have a shitty exam in the 13th (Friday) and because of it I only have 1.5 weeks until classes start.
I just hate physics so God damn much...6 -
Not really most painful, but definitely most painful of the recent bunch..
// yup, a bunch.. I've managed to fuck up a little on every thing I did that day :/ little friday the 13th for me, especially as I went on sick leave the next day and had to fixup my fuckups with a friggin migrane..
Anyways, I was fixing fallback to some default value in plsql.. before it didn't check what the input format was and simply relied on certain format, parsed that and converted to number..threw an error, duh!
I fixed it somehow elegantly to check with regex if the format is as expected and if not default to xy value..and if format is as expected to parse out the number..except that when I copied (or typed?! for the sake of me, I cannot recall how the fuck I managed to fuck this up) over the code to the package I didn't see additional [ at the begining, so everything went to the default.. Most embarrassing part is I commented everything, how it should work, use cases, what the input was and what was expected output..and failed to see the friggin extra [..
It was fixed easily, the extra [ stood out later when I saw the code, but it bothers me how I managed to overlook that in the first place. I think I need a vacation.. but have to fix other fuckups first.. :/