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
-
I FINALLY DID IT!! I landed a job!! I'm going to be a firmware engineer!! Woohoo!! 😁
It only took half a year, but I finally got one, and purely off my own merit. It feels damn good when you get the job with no references or connections, just your own skills.
After a highly successful on-site technical/whiteboard interview, I was 90% confident I'd get it. The fact that my job search is finally over, is such a fucking relief. Good riddance to endless interview prep, applications & rejections.
I start on Monday. Goodbye freedom >.<19 -
A fanfic based on devRant-chan. The character was created by @caramelCase and a drawing by @ichijou.
This is freestyle. I'll think of an image of a scene and go with the flow. I won't remove my fingers from the keyboard and I won't edit or change anything. That's how I come up with my best ideas.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Notes:
B/N = Boss' name (I was too lazy to think of one.)
Anything in between astericks is in italics.
Ex.) *this is in italics.*
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It was an early January morning when devRant-chan was situated in her desk, typing away on her laptop. She was working on a Python script for her barbaric client when she could've been out with friends. Oddly enough, her Sunday was surged with tranquility.
Normally, Sunday is when her irksome boss barks orders at her on the phone.
"This is wrong!"
"What is this?"
"Change it!"
devRant-chan resented her boss but loved her job. After all, "you can't force yourself to like everyone," was something her elder brother would tell her.
She released a slight chuckle, the one she would only display at the thought of her brother.
Her musings were interrupted when a concerning thought crawled into her mind like an undesirable intruder.
Why hasn't her boss called to complain yet? It's not that she enjoyed his complaining, which she didn't. She simply found it odd, since he's done this every Sunday morning, since she was a junior developer.
Unless he found someone else to complain to? In that case, good riddance!
But still, it wasn't a euphoric feeling to be replaced. She was already accustomed to his Sunday morning calls that it feels almost lonely not to receive them.
She should call him... Just in case some situation—or—problem—has emerged.
She dialed his number, waiting patiently for a reply.
"Hello," said her boss.
"Ah, hello," said devRant-chan. "I called, wondering—"
"You've reached the voicemail of B/N, please leave a message after the beep."
"Damn..." mumbled devRant-chan with a sharp exhale. "I always fall for that."
Why didn't her boss answer the phone? It was odd of him, considering he's always answered her calls.
She was about to dial her coworker when she received an email, which stimulated her attention. The subject of the email read:
*Important. Please read.*
She opened the email. It was her boss. The email read:
*Hello.*
*In case you aren't aware, I had quit my job, due to the stress. I've left the manager in charge. Starting tomorrow, he will be your new boss.*
*-B/N*
Before she could rejoice in excitement, she detected a strange change of voice, emitting from the email. Did her boss really write this?
That's when she spotted something. The word "tomorrow."
Her boss didn't write this.
He would never use words such as "tomorrow," or "today." He would use time instead. If this was her boss, he would say "in 24 hours."
She checked the IP of the email. Oddly enough, it was her boss' IP.
Still, the pieces didn't fit the puzzle. Her boss didn't complain, answer her call, or use his style of speaking in the email.
Something happened to him and she knows it. Whatever it is, has something to do with the manager, and she was determined to figure it out.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This was just a quick random fanfic, and I'm not sure if I'll continue it. As I said, I didn't plan anything, since it's freestyle. I might or might not continue it, so I'll think it over.8 -
A few months ago, I decided to let go some old clients with bad behavior and/or bad projects, since I noticed this was affecting my mental health (lowering my self esteem, make me feel depressed, anxious, etc).
I was exhausted of doing miracles in projects without git, build files, staging enviroments (yes... you can imagine), and receive all sort of curses when sudenly something stopped to work.
I set some requirements to work with any new project/client: 1) project needs to be under version control, 2) it must have staging enviroment, 3) I must work with build files.
As I still have contracts running, I'm communicating this to clients as soon as I finish my obligations.
Today, one of these clients told me they are leaving to work with another developer.
Reason: They said my new requirements are unreasonable and they prefer doing the old way.3 -
I was told in an 1:1, quite literally, "not everybody can do what they want to do if they are not good at it..." - get fucked! The person I had to "report to" was an idiot (at the same senior level as I was) and obviously threatened.
Then moved down to customer support, where I was fired for fixing problems faster than going through the chain of levels, because I was creating quick scripts to patch the faulty data.1 -
I've told the same story multiple times but the subject of "painfully incompetent co-worker" just comes up so often.
I have one coworker who never really grew out of the mindset of a college student who just took "Intro to Programming". If a problem couldn't be solved with a textbook solution, then he would waste several weeks struggling with it until eventually someone else would pick up the ticket and finish it in a couple days. And if he found a janky workaround for a problem, he'd consider that problem "solved" and never think about it again.
He lasted less than a year before he quit and went off to get a job somewhere else, leaving the rest of our team to comb through his messy code and fix it. Unfortunately, our team is mostly split across multiple projects and our processes were kind of a mess until recently, so his work was a black box of code that had never been reviewed.
I opened the box and found only despair and regret. He was using deprecated features from older versions of the language to work around language bugs that no longer existed. He overused constants to a ridiculous degree (hundreds of constants, all of which are used exactly once in the entire codebase, stored in a single mutable map variable named "values" because why not). He didn't really seem to understand DRY at all. His code threw warnings in the IDE and had weird errors that were difficult to reproduce because there was just a whole pile of race conditions.
I ended up having to take a figurative hacksaw to it, ripping out huge sections of unnecessary crap and modernizing it to use recent language features to get rid of the deprecation warnings and intermittent errors. And then I went through the same process again for every other project he'd touched.
Good riddance. -
Two years ago I said good riddance and go fucking die to everything Microsoft and I haven't looked back since.
I can work completely on my Mac. Life is now stress free.13 -
So, it's time to fucking rant!
Location: A small startup where direct contact with C-Level members is frequent.
A while back we had a customer using our SaaS product who had gripes about the way it worked.
He contacted our CEO and made a bunch of claims based on bad assumptions.
In the end, he wanted all images removed from his site. I was pulled aside by the CEO and asked if I could handle this for him and make a new screen for them without images.
So I did. I tried to discuss and get deeper into the problem by saying "this seems like a symptom of a problem and not the actual problem. What do you think?" He responded with "That was his request so it must be the problem if it won't take long then let's fix it for him.
- a week later
The problem is fixed and in the wild. No more images. Now he has another request :/
He does not like the pagination on his site. He says " I shouldn't have to click a button when I scroll so I want the be able to scroll and see all my products!"
This time the CEO asks me if this can easily be done and I take him aside and say "no, this will be a big change to our system and will need to be discussed with the team."
The main point I make is that we should go down and spend some time with this customer to find out what the real problem is.
After a half hour of discussion about the real issue he decided to bring in the CTO.
In the end, we implemented infinite scroll, dropping our current product building tasks to service one customer (yeah, it's a bad scene). But we got infinite scroll built and shipped.
- 2 Weeks later
This time he demands that infinite scroll isn't good enough. "If I scroll fast then I have to wait for them to load, they should all load at once!"
This time I have had enough. I can see the CEO is coming over to me to as me how much work is in this. I tell him there are 3 things I have to say...
1. I'm going to implement exactly what he asked by the end of the day.
2. We will only release it to him because it is going to be a shit-show loading everything at once, the load times will be mental!
3. We should fire this customer, right now.
So, I built it. Customer hated it (of course, who the fuck wants to wait 30s for loading. That's basically a lifetime). We changed it back and he was still mad.
- 2 weeks later
Customer leaves. Good riddance.
- sometime later
I am in the customer's store on a road trip. I get a feel for how their store works and they have a different system for making things operate.
It turns out that they did not know what the real problem was. They actually needed a completely different system (from a UX perspective) for accessing their data.
To top it all off, the system would have taken less time to build than the shitty fixes we made over weeks of work. FFS
I guess the moral of the rant is to find the problem, not a symptom of the problem.2 -
Joined a new team at work 6 months ago. Immediately set upon by a useless PO who was somehow set in her ways while still being around 30 years old. Absolutely refused to change the broken team dynamic or processes in any way whatsoever. Made terrible tickets, never did refinement on tickets so they were always missing stuff and constantly blocked. Generally unlikeable and difficult to work with, incompetent at her job and resolutely refused to change literally anything to make the team function better.
She finally leaves after 6 months and the team dynamic changes immediately. Suddenly we are improving our processes, getting stakeholder input, refining tickets, taking reasonable amounts of work in a sprint. We have discussions without her butting in and getting frustrated when you bring up legitimate concerns. No longer do you have to tiptoe around and appease her ego if you want to point out the obvious flaws in the work she drew up or even just examine it from a technical perspective.
It's insane how much things can improve once you shed the dead weight of people that are just determined to be difficult and won't budge an inch to change their ways. Good riddance.4 -
Finally Google kills off a product no-one wanted in the first place! First genuinely exciting announcement from Google in a LONG time. Good riddance Google+!
9 -
Using the Facebook Messenger thing on a recently updated Android 8 (finally, Huawei pieces of rotten eggs) is a friggin' pain in the starhole. For the life of me I can't seem to fudging remove this damn useless notification popping up... (pic)
It's more intrusive than the app itself... D:
I guess I'll need to trash the app then.. Good fucking riddance!
12 -
After a code review where I identified an odd way a request was being generated, I suggested to the developer to utilize the Strategy pattern.
Knowing that the Strategy pattern probably wouldn't make sense in the current context, I told him I would put an example together by the end of the day.
I throw something together, sent it to him.
Go to the restroom, come back and 'Bob' says..
Bob:"There is my hero. Justin said you saved the world again. What was it this time? World hunger? Global warming? Ha ha ha."
Frack off you condescending kiss ass. Why don't you take 5 minutes to listen and understand the problem Justin was having instead of making fun of him?
Yea, I heard you this morning laughing at his code, monday-morning quarterbacking a solution in which you have no idea whats going on.
Heard your days are numbers anyway. Good riddance.1 -
!dev
Left the window open to cool the room before going to bed. A fucking cricket got in. Didn't kill it at first, thought it'd leave.
Nope. It didn't. Lights off, comfy in my covers and there it goes... That noooooise! For fucks sake! It's not even loud, but it grates so muuuch. Agh.
And then it took me foreeeeever to find it. Bastard hide on top of the wardrobe, behind my luggage. Spend a good 10min looking for it. And he kept on taunting me, the fucking piece of crap. Well, at least its dead now. Good riddance, asshole. -
My PC kept booting into linux cause i installed two OS's on my HDD. Long story short, had to remove the Linux (it was Kali) and i didnt know how. And so started the longest few hours of my life.
I deleted the linux partition feeling like some genius that could speak to computers. To my suprise the computer didnt speak back, i restarted it and the GRUB bootloader had this sheepish grin on its face like as if it was saying, "Not sure who's been speaking to you all this time, but i bet you can hear me now, hehehe". I went down the rabbit hole that we all know and love called the google search bar.
My computer could no longer boot into windows, and i started to question my very existence on this earth. Hours of using our modern day saviour, google of alphabet inc, i came to an eventual conclusion. Grabbed a 4GB flash, made it into a bootable device and said good riddance to bad rubbish.5
Top Tags
Weekly Rant
View