Just setup a new phone cause old one is flaking out. Spent two hours uninstalling bullshit. The default weather app had fucking tiktok video ads running in the app! Fuck you motorola! I uninstall this piece of shit weather app. Then this non shitty weather app appears. Fuck you motorola! That should have been the default. Turned off all the suggestions bullshit, uninstalled like 20 garbage pos apps, took 10 minutes to figure out how to shut off phone because new android os is fucking retarded. Fuck you google! Seriously you changed the fucking power button to pop up the stupid voice shit! Fuck you google!

The whole time I am waiting for the setting I can't change so I can return this shitty phone. Fuck you motorola!

I dunno, we will if this isn't complete shit.

STOP RUINING EVERY FUCKING THING! Fuck you shitty ass phone manufacturers!

At the end of the day, at least I ain't a retarded Apple user... I am just a retarded aNdRoId uSeR!

What did go smoothly? Transferring my old data wasn't complete shit. Its a 5G phone, but it still only seeing LTE. Fuck you T-Mobile!

I hope there was enough "fuck yous" in this post.

client cto: "SOMEBODY COMPROMISED YOUR KEY!!!! IT SHOWS SOMEBODY LOGGED IN TO DEVOPS GUY'S ACCOUNT USING KALI LINUX!!!!! HERE ARE THE LOGS!!!!"

the logs: *show an ip address*

the ip address: *ip address of the office*

devops guy: *actually uses kali linux*

not really a rant, just found it funny

Deleted over 1'500 lines of code over the last 2 days and replaced it with 80 lines of readable, simple, generic code.

And I'm feeelin' gooood 🎶

To get a PhD in three years. Half way in, absolutely unrealistic but that's a hill I'm willing to die on! ⚔️

The most unrealistic deadline? Okay, here it goes. For context, this is one of my earliest jobs, and I’m actively using React.

— Kiki, I have a stunning idea! Let’s build a Figma clone!
— Okaaaay, 🧐
— You have two days.
— A what?
— I’ve just stumbled upon an amazing new technology. You maybe don’t know it yet. It’s called React.js, and you totally can build a full Figma clone in two days using it!
— …
— It’s a revolution, and you’re so ignorant for not following it. Are you even a real engineer?
— …

Two days later:
— Forget about Figma! Let’s build an online DAW for musicians!

That guy was nuts. I left when we had an executive meeting, I was explaining tech things, and he suddenly popped out a fucking tambourine and started striking it. One year later, he lost everything and went to get a junior C++ position at an outsourcing company.

My CTO told the COO and CEO i'd be finished SOC2 compliance by the end of December... On December 14th.

It takes 3 months to do the audit, let alone all the actual work. I hadn't even started yet.

He was fired shortly after that.

I did it.

I finally fucked prod.

And had to do open heart surgery on the service to get it unfucked.

Shit happens. Luckily its internal prod only...

!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"

So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.

First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.

So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.

Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?

I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.

Did you run the code I gave you to do this update?

"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"

So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.

More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!

I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.

And this, my friends, is the part I will never forget.

"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."

You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!

"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."

I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.

So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.

You just cannot make this kind of stuff up.

So I'm sitting on the swings, minding my own business, seing how best I could destroy this cluster of servers, when suddenly I notice SOMEONE IS COMING FOR MY COFFEE

"hi neighbour! What you've got there"

I wonder how many bitflips did they trigger last night...

Looks pretty. But much too scarry when you understand what it is.

Fun fact: because of its immense biting force, jaguar goes for the skull, not the neck.

The Coding Apocalypse: A Dev's Rant

June 14, 2024

Okay, gather ’round, fellow code warriors, because it’s time for a good ol' developer rant. If you're reading this, chances are you’ve already faced the dragon that is modern software development, and you’re somehow still using "Agile" as a life preserver while the ship is sinking. So let's dive into the chaos that our world has become.

Here’s the thing: We’re living in a paradox where every other day there's a shiny new framework promising to be the “ultimate solution” while ignoring that it's just recoil from the last big mess. I mean, can we talk about JavaScript for a second? I’m pretty sure if you stand still long enough, a new JavaScript framework will spontaneously generate from the void. Do we really need another one?

And don’t get me started on Sprint Planning. It’s like playing Tetris with stones while blindfolded, hoping that all the blocks land perfectly. Spoiler: They don’t. The product manager’s eyes glaze over as they nod approvingly to your estimates, secretly extending deadlines in their minds. The 'flexible' deadlines then become rigid, unattainable goals, and who gets the heat? The devs, of course.

Also, can we address the insanity of microservices? Sure, splitting a monolith into microservices sounds fun—until you’re drowning in API calls and Docker containers. Debugging a distributed system is like trying to untangle a pair of headphones made of spaghetti.

Oh, and if one more person asks if we’re "leveraging AI" and "blockchain technology" for our simple CRUD app, I might lose it. Sometimes, folks, the wheel doesn’t need reinventing. It just needs a little grease.

Finally, remote work. Blessing and curse. Sure, I enjoy the freedom of working in my PJs, but the endless Zoom calls are killing my soul. Breakout rooms? More like breakdown rooms. The Slack notifications? Let’s just say my sound settings have a hair trigger on mute these days.

So here’s to us, the devs. The ones who stare into the abyss of JIRA tickets and laugh in the face of mounting tech debt. May your coffee be strong, your code refactored, and your deployments ever in your favor.

End rant. Back to the trenches. 🚀💻

I’m getting really tired of all these junior-turn-senior devs who can’t write simple code asking ChatGPT to solve everything for them.

I’m having to untangle everything from bizarre organization/flow to obvious gotchas / missed edge cases to ridiculously long math chains (that could be 1/10th the length), or — and I feel so dirty for this — resorting to asking ChatGPT wtf it was thinking when it obviously wrote some of these monstrosities. Which it gets wrong much of the time.

“ALL HAIL CHATGPT!” Proclaims the head of Engineering. “IT’S OUR PRODUCTIVITY SAVIOR! LEVERAGING AI WILL LET US OUTPERFORM THE ENTIRE INDUSTRY!”

Jesus fucking christ.

I applied for four jobs today, including GitHub. I feel kinda proud of myself.

Before I left for vacation two weeks ago, I busted my butt to build out another portion of my frontend testing framework and get it in place (and spec’d) to unblock a coworker on a semi-high-priority ticket. I sent him detailed notes on which areas of the product it covers, how to use it, and copied one of his (blocked) tests over and updated it to use the new methods, pattern, namespacing, etc.

I came back today and discovered … he hasn’t even touched it. Everything is exactly as I left it.

Wheeeeeee.

Wordpress.

Dogshit.

That is all. Thank you for listening.

Story time...of how HR actually did its job of taking care of employees.

So, I started at this new gig on December, the boss was all sunshine and promise (big red flag now to think back). Then as time passed, he started seeming...off. To a point I considered quitting my boss just after 2 months of working for him.

Then one morning we had a project meeting. He started verbally abusing me, calling me incompetent, bashing my work (of which he knew ~nothing, his experience 30 years back). Earlier in the week he demanded me to make a presentation which he in this meeting told is complete bullshit without actually reading any of it. He told me 'I am your boss, you do exactly as I say' when I told him something is technologically impossible in the situation we're in. He *actually* told me to break the law with data protection...

This was like wtf dude. That's not how you manage people. So, I made an HR ticket about his behaviour. They were *shocked* and escalated the matter.

Long story short: he was a bully, he's getting fired, my team has a new manager. My workplace actually appreciates my expertise.

Bad thing in this is, now I actually need to continue doing my job. ;_;

For the love of buggery, stop watching bloody videos on your bloody phone with the bloody volume turned up.

I was thinking about something, just starting to get in the zone, when suddenly that tinny little speaker opened up a portal into the howling chaos of the underworld.

It sounds like cats fucking in an empty grain silo.

For the next half an hour, there is no room in my head for anything apart from the diabolical echoes of that bollock-wrenchingly hideous noise.

YoU nEEd tO tHInK MorE LiKe oUr nOn tEcHnICal UsErs

That's your fucking job you powerpoint monkey, I'm writing code since age of 14, I distrust everything that doesn't spit out logs of what it's extacly doing to my console including you, my gf says sudo to get my attention, how the hell am I supposed to know how normies think

AEvery time :D

I had high ideals when I started working here. The entire code base was practically devoid of comments. Its been 5 years and it is still practically devoid of comments. I have become like them...

having to prove you actually work

I know ppl say there is no place like home...

but after returning from places like this one, I just wanna go back there...

I just bought winrar for $9.

I got a job

I just burped out loud on a live call with about 30 people and I thought my mic was muted.

Goodbye, cruel wairld:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 123736064 bytes) in /var/www/vhosts/hexicalapp/public_html/Classes/Services/Devrant/SearchService.php on line 174

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

EU have finally passed the law that requires all phones to have user-changeable batteries by 2027.