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 - "calm before the storm"
-
I was in class one time, chatting with a pal of mine. We had just started our Web development course so I was working on that while we talked.
A few rows behind me sat another classmate, struggeling with this project we were going to turn in The week after.
So our teacher comes by and asks us how's it going and the guy behind us starts throwing a tantrum (it didnt go Well for him).
- "I have no idéa what I'm supposed to do, or what I'm even doing!"
My teacher started out very empathetic and calm, explaining and helping him.
This guy got more and more frustrated to the point an hour later where he started to scream.
And then came the one and only time I've heard my teacher angry, it was exactly like The calm before a storm.
- "Do you know what 99% of all developers do when they get stuck?! They use fucking Google!! You have to learn how to fucking Google!!"
Non the less the dude calmed down and started to use google.2 -
Me -Hey did you run through the UTC(s) ?
Co-worker - Yeah.
Me-How many failed?
Co-worker - None!
This project is either going defect-less or Its just the calm before the storm.1 -
Today everything went just fine with Windows 10 and Visual Studio. It must be the "calm before the storm"! 🤔2
-
The low workload week(s) after a big delivery feels so weird, like it's the calm before the storm, instead of the rainbow
-
I don't often have reasons to rant, but today is the one.
We had a deadline to finish a project, because today people are being trained on it. I've been working my ass off on it for a year now.
I "finished" about 2 weeks ago, meaning QA could start for real 2 weeks ago. As you can imagine for a project this long, there was bugs. Lots of them.
We did our best to fix most of them, or find work-arounds we could use during the demo.
Let's just say it isn't going great so far. We have several known bugs, which at some point may crash the app, a very low confidence in the fact that it's going to work well.
Oh and obviously the client is one who already use heavily the solution. Today we figured we never tested on a device with 0% disk space. Files are cut partway because of that, and obviously things crash.
I have a feeling there will be yelling sometime soon.
Right now I'm enjoying the calm before the storm, with coffee in hand.
Why do people still continue to promise dates to clients, after me telling them for 5 years not to do that?
We are a 2 devs team, with 11 apps on 2 platforms, 2 back-ends (one is legacy) and obviously our marketing site, which doubles up as e-commerce. We just can't promise anything, because any emergency reduce our development bandwith for new features either to 50% or 0%. There are so much known bugs it's not funny anymore, and we don't even have time to solve those.
To add insult to injury, at the beginning of the month, the SaaS provider for our legacy back-end (which have not been maintained for 2 years now) decided we had to update to PHP7.1 before 1st October. If we don't do anything, on monday this thing is broken. I hate that thing, and I hate having to maintain it even though I was promised I wouldn't have to ever have anything to do on it.
Monday will be "fun"...2 -
"The Perils and Triumphs of Debugging: A Developer's Odyssey"
You know you're in for an adventurous coding session when you decide to dive headfirst into debugging. It's like setting sail on the tumultuous seas of code, not quite sure if you'll end up on the shores of success or stranded on the island of endless errors.
As a developer, I often find myself in this perilous predicament, armed with my trusty text editor and a cup of coffee, ready to conquer the bugs lurking in the shadows. The first line of code looks innocent enough, but little did I know that it was the calm before the storm.
The journey begins with that one cryptic error message that might as well be written in an ancient, forgotten language. It's a puzzle, a riddle, and a test of patience all rolled into one. You read it, re-read it, and then call over your colleague, hoping they possess the magical incantation to decipher it. Alas, they're just as clueless.
With each debugging attempt, you explore uncharted territories of your codebase, and every line feels like a step into the abyss. You question your life choices and wonder why you didn't become a chef instead. But then, as you unravel one issue, two more pop up like hydra heads. The sense of despair is palpable.
But, my fellow developers, there's a silver lining in this chaotic journey. The moment when you finally squash that bug is an unparalleled triumph. It's the victory music after a challenging boss fight, the "Eureka!" moment that echoes through the office, and the affirmation that, yes, you can tame this unruly beast we call code.
So, the next time you find yourself knee-deep in debugging hell, remember that you're not alone. We've all been there, and we've all emerged stronger, wiser, and maybe just a little crazier. Debugging is our odyssey, and every error is a dragon to be slain. Embrace the chaos, and may your code be ever bug-free!1