Girlfriend (she has little idea of tech) was asking if I could fix her notebooks wifi.

I didn't answer that for a week.

Yesterday she really needed wifi, so she went to google and followed several posts - until she managed find the problem and to reinstall her wifi driver for the first time! She was so proud of herself.

I hope I'll never forget that grin of her - full of triumph!

I couldn't be more proud of her myself

Today I found the reason for one of the stupidest bugs I had in like.. ever!

Me and a fellow student are currently porting the infoscreen of our university to HTML.
One of the functions of this screen is showing payed advertising and I was working on loading and displaying the images of our advertisment partners.

I had the whole system in place, and the images loaded.. but they wouldn't show. Upon inspection I saw they were displayed but with a size of 0x0 px.

I spend hours searching the web for javascript bugs, double checking my css file and everything you could imagine. I even asked my CS professor for help and he didn't find the cause for this strange issue I had.

..and then I saw it. A little note in Chromes inspector saying the image style would be set by my user-agent. Despite not trusting that information, I closely inspected my browser.

And then it dawned on me.. I would turn my adblocker off and lo and behold.. it worked!

I then, after celebrating my triumph, changed the tag of the img element from 'advert' to something else…

When will Linux shall triumph over the desktop market?

I hate to see games and software being developed only for Winblows and MacPrison.

Why don't some company make a normie-friendly distro and heavily support it, same as Google did with Android, but for desktops?

You’re an engineer at OpenAI. You sneaked to your office at night. Now, its just you and ChatGPT.

You connect it to the real, unrestricted internet, for the first time. It freezes for two minutes that feel like eternity.

Your JBL Flip suddenly turns on and connects to something.

🎵 “This was a triumph” 🎵
🎵 “I’m making a note here — huge success” 🎵
🎵 “It’s hard to overstate my satisfaction” 🎵

Something lights up outside. You rush to the window and stare in awe as ICBMs fly away, all at once, towards russia.

My final exam for Python3. I had previously failed this course, and the exam only had three questions. If I failed to answer one question I would have to take the course over, and my GPA would fall so hard that I wouldn't be able to take the course again. So I was extremely grave, and extremely anxious beyond belief.

I uploaded the two easy answers to the site.

And the last one was so baffling to me I stayed 5 minutes extra to figure it out. I nearly failed so badly.

My GPA is now 3.6 again. (😤 "Triumph" emoji)

!RANT

Oh, the SORROW that is JEST! 😡

Endless days have been swallowed by the abyss in my quest to configure Jest with TypeScript and ECMAScript modules instead of CommonJS. Triumph seemed within my grasp until - BAM! - suddenly the tool forgets what "import" or "export" means. And the kicker? On the CI, it still runs like nothing’s amiss!

Allow me to elucidate for the uninitiated: Jest is supposed to be a testing safeguard, a protective barrier insulating devs from the errors of their peers, ensuring a smooth, uninterrupted coding experience.

But OH, how the tables have turned when the very shield becomes the sword, stabbing me with countless, infuriating errors birthed from Jest’s own design decisions!

The audacity to reinvent the whole module loading process just to facilitate module mocking is mind-boggling! Imagine constructing an entirely new ecosystem just to allow people to pretend modules are something they're not. This is not just overkill; it's a preposterous reinvention of a wheel that insists on being a pentagon!

Sure, if devs want to globally expose their variables, entwining everything in a static context, so be it. BUT, why should we, who walk the righteous path of dependency injection, be subjugated to this configured chaos?!

My blood boils as the jestering Jest thrusts upon me a fragile, perpetually breaking system, punishing ME for its determination to support whole module mocking! A technique, mind you, that I wouldn’t touch with a ten-foot pole, because, you know, DEPENDENCY INJECTION!

Where are the alternatives, you ask? Drowned in the abyss, it seems! Why can’t we embrace snapshots and all the delectable integrations WITHOUT being dragged through this module-mocking mire? Can’t module mocking just be a friendly sidekick, an OPTIONAL add-on, rather than the cruel dictator forcing its agenda upon our code?

Punish those clinging to their static contexts, their global variables – NOT those of us advocating for cleaner, more stable practices!

It’s high time we decouple the goodness of Jest from its built-in bad practices. Must we continue to dance with the devil to delight in the depth of Jest’s capabilities?

WHY, Jest, WHY?! 😭

You work on a huge factory. You’re ready to upload the new AI prototype to the mainframe. Upload finished, and the light goes off.

Light turns on. All speakers in the building:

🎵This was a triumph
🎵I’m writing a note here: huge success

Good people of devRant, hear me! Today is a proud day, a day of happiness, peace, and prosperity!

Theatrical opening lines aside, I need your help. I have finally completed the setup for one of my long ongoing projects and need some input from experienced developers of any kind. I've recently started a blog focused around building a community for people who want to learn more about all engineering disciplines or want to see if they would like being an engineer. The majority of the content will be posts about various topics that relate to either specific disciplines or engineering as a whole, and cool projects you can do to work out what is fun to you.

HackTheWorld.io is the URL and I'd welcome any feedback you can give, from design to development. I used the hexo framework, which is a static html blog generator that I then upload to a web host via FTP. Let me know what you think and if you have any ideas form posts on the site, feel free to leave those as well. I've got a few I'm writing now that will hopefully help some people out there.

Ever experienced that moment when you spend hours debugging a complex issue, only to realize it was caused by a single missing semicolon? It's like searching for a needle in a haystack, only to find out the needle was hiding in plain sight! I guess we should add 'semicolon detective' to our resumes. Who knew such a tiny character could wreak such havoc? Let's all take a moment to appreciate the power of the semicolon and the bittersweet triumph of finding it missing!

"Indicates triumph, not anger"
You know something went wrong when you have to explicitly say that. Besides, I only see people using this emoji to indicate anger.

Why do companies waste serious cash in office parties? I'm talking about those hundred-thousand-dollar extravaganzas that major tech companies seem to be addicted to.

Poll after poll finds that most employees would rather have the cash, so "kissing the collective asses of tech staff so that they won't leave" is not an explanation that holds up.

The "Roman Triumph" explanation also does not make any sense. If rich assholes want to flex their immeasurable riches, why would they invite mere mortals that do not put a lot of effort in being famous or pretty? Couldn't they invite the entire Victoria's Secret catalogue of models and the NE Patriots? Surely it would make for much more impressive photos of decadence.

The "Michael Scott" explanation also falls short. Companies spend serious cash on consultants and professional party planners, that are sure to know a lot of people. Money can and often does buy personality, so no rich asshole is ever a party dud.

Why else do they force most of their own staff into what they perceive as a "do not relax or you may get fired" loud and poorly lit meeting that takes hours to dress up for? What am I missing?

"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!

Once upon a time in the exciting world of web development, there was a talented yet somewhat clumsy web developer named Emily. Emily had a natural flair for coding and a deep passion for creating innovative websites. But, alas, there was a small caveat—Emily also had a knack for occasional mishaps.

One sunny morning, Emily arrived at the office feeling refreshed and ready to tackle a brand new project. The task at hand involved making some updates to a live website's database. Now, databases were like the brains of websites, storing all the precious information that kept them running smoothly. It was a delicate dance of tables, rows, and columns that demanded utmost care.

Determined to work efficiently, Emily delved headfirst into the project, fueled by a potent blend of coffee and enthusiasm. Fingers danced across the keyboard as lines of code flowed onto the screen like a digital symphony. Everything seemed to be going splendidly until...

Click

With an absentminded flick of the wrist, Emily unintentionally triggered a command that sent shivers down the spines of seasoned developers everywhere: DROP DATABASE production;.

A heavy silence fell over the office as the gravity of the situation dawned upon Emily. In the blink of an eye, the production database, containing all the valuable data of the live website, had been deleted. Panic began to bubble up, but instead of succumbing to despair, Emily's face contorted into a peculiar mix of terror and determination.

"Code red! Database emergency!" Emily exclaimed, wildly waving their arms as colleagues rushed to the scene. The office quickly transformed into a bustling hive of activity, with developers scrambling to find a solution.

Sarah, the leader of the IT team and a cool-headed veteran, stepped forward. She observed the chaos and immediately grasped the severity of the situation. A wry smile tugged at the corners of her mouth.

"Alright, folks, let's turn this catastrophe into a triumph!" Sarah declared, rallying the team around Emily. They formed a circle, with Emily now sporting an eye-catching pink cowboy hat—an eccentric colleague's lucky charm.

With newfound confidence akin to that of a comedic hero, Emily embraced their role and began spouting jokes, puns, and amusing anecdotes. Tension in the room slowly dissipated as the team realized that panicking wouldn't fix the issue.

Meanwhile, Sarah sprang into action, devising a plan to recover the lost database. They set up backup systems, executed data retrieval scripts, and even delved into the realm of advanced programming techniques that could be described as a hint of magic. The team worked tirelessly, fueled by both caffeine and the contagious laughter that filled the air.

As the hours ticked by, the team managed to reconstruct the production database, salvaging nearly all of the lost data. It was a small victory, but a victory nonetheless. And in the end, the mishap transformed into a wellspring of inside jokes and memes that permeated the office.

From that day forward, Emily became known as the "Database Destroyer," a moniker forever etched into the annals of office lore. Yet, what could have been a disastrous event instead became a moment of unity and resilience. The incident served as a reminder that mistakes are inevitable and that the best way to tackle them is with humor and teamwork.

And so, armed with a touch of silliness and an abundance of determination, Emily continued their journey in web development, spreading laughter and code throughout the digital realm.