AboutYoung, good-looking and unsuccessful
SkillsJava, JS, Angular, Python, C++
Joined devRant on 10/9/2019
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Based loosely on the popular "git" command, I am happy to announce my new product, "hit"!
Essentially, hit hooks into "git blame" and automatically slaps the shit out of whoever wrote this garbage.
It uses SOHTTP (Slap Over HTTP) to deliver a nice firm wallop to any subpar script kiddie that had the audacity to come up with this bullshit.
Careful, the user is not immune to the effects10
Boss: Our customer's data is not syncing with XYZ service anynmore!
Me: Ok let me check. Did the tokens not refresh? Hmm the tokens are refreshing fine but the API still says that we do not have permissions. The scopes are fine too. I'll use our test account... its... cancelled? Hey boss, why is our XYZ account cancelled?
Boss: Oh, "I haven’t paid since I didn’t think we needed it" (ad verbatim)
It's been a while since I posted here. My previous workplace was a 101 on how to burn out people.
But now I am working at a place where:
- People are 0 toxic.
- Sprints follow the premise "under promise, over deliver."
- I was having trouble sleeping (for reasons) a couple of months ago, and my boss literally told me, "If you can't sleep at night, take a few days, or if you can fall asleep in the morning, just sleep in the morning until you manage to do otherwise. Talk with your team and rearrange the meetings if you have and rest. "
- All pieces of the company (sales, narketing, product, data, devs) have a clean roadmap.
- Product and bizz understand when something can't be done on the next sprint and why sometimes some features are delayed.
- They pay well, even raising the pay twice to account for inflation.
- Full remote, If I want to go to the office, Its my choice.
I need to keep this job no matter what!8
How to profesionally say: you fucking illiterate and incompetent piece of shit, I am tired of spoonfeeding you because you dont use your fucking brain. I am fucking tired of explaining same concept over and over again for the past 2-3 months. Open fucking google for once and lookup latest practices, and learn what functional programming is and learn how to use operators instead of fucking inventing wheel again and again with your 100 lines boilerplate of code functions. Open your fucking mind for once and lookup stuff for yourself, instead of asking me to explain everything for the 100th time you lazy fuck. Oh and stop asking me "to be nice", this is gaslightling. I am being professional and I am the only person in this company who actually tolerates u on some level, others are just avoiding you you useless piece of shit. If I need to explain something for 5th time and I make you feel bad, it means you should feel bad. So maybe grow some balls and start putting in some effort, instead of playing the victim when you are the supposed 6 year senior and I am the 3 year junior, who has to do your fucking job half of the time. You are incapable of even using the standard architecture, what you use is fucking 6-7 years old. Fucking code monkey with broken english who doesnt understand what hes doing. You dont like my methods? I dare you to schedule an appointment between me and manager or your useless techlead, but I know you wont do that because I know you are afraid of everyone finding out how incompetent you are. You low fruit hanging task licking incompetent shit.1
Being me. Fresh out of UNI with a three year bachelor in CS, no work experience. Starts in a big tech company with a lot promise of exciting project etc. Starts in 3 projects with one lead dev and two senior devs.
First month begins. I start by setting up my local environment and read documentations, which is fairly irrelevant and old. One of the senior devs quits.
Second month begins. Lead dev quits as well and the other senior dev having sick leave for the rest of the month. Basically I'm on my own, but thankfully not responsible for the projects.
Third month begins. The other senior dev is still sick. Nobody to help. Now I'm forced to talk to customer with a lacking knowledge of projects. Nobody knows what is going on. Hopefully my other senior dev will come back.
Fourth month begins. My senior have quit as well. I've been assigned as responsible of all three projects now. FML.
Fifth month begins. I begged my manager for help. Got a junior dev to help me with one of the projects. He and I still have no clue what we should do.
What a shitty start to a career as a developer.
Anybody having a similar experience?5
i am just curious, how often you use devrant.
to be honest,.. if my life is good.. no bugs. no miss management. I don't even remember devrant exist..
but as soon as I got frustrated from code,management, life.. Devrant is the first thing I type of my browser before starting any work :P3
Didn't finish morning run in time for morning scrum call. Looks like I'm answering the call from here.8
Company: Bobby you saved the company millions of dollars this year!!! Great job.
Me: So...how about that extra 2k per year raise.
Company: Um well it just doesn't seem to be in our budget this year.7
Udemy courses are targeted at ABSOLUTE beginners. It's excruciating to pull through and finish the course "just because". And some of these courses are jam-packed with 30-60 hours just for them to appear legit, but the reality is the value you get could be packed to 3-5 hours.
You're better off just searching for or watching for the things that you need on Google or YouTube.
You'll learn more when building the actual stuff. Yes, it's good to go for the documentation. Just scratch the "Getting Started" section and then start building what you want to build already. Don't read the entire documentation from cover to cover for the sake of reading it. You won't retain everything anyway. Use it as a reference. You'll gain wisdom through tons of real-world experience. You will pick things up along the way.
Don't watch those tutorials with non-native English speakers or those with a bad accent as well. Native speakers explain things really well and deliver the message with clarity because they do what they do best: It's their language.
Trust me, I got caught up in this inefficient style a handful of times. Don't waste your time.9
My annoying 19-yo nephew wants to drop out of CompSci to "create the next billion-dollar startup".
I told him I would give him 10 rupees (USD 0.10) for 0.000000001% percent of his "pass me the butter at the diner table" company.
He accepted. Thus, his "heritage protein logistics startup" had an series-A valuation of a billion American dollars!
Hopefully he will stay in college now.2
It fucking infuriates me when the docs mention to create a certain config file "xyz.json" but completely leave it to your imagination where the hell this fucking file should be placed!
Come on, I'm not getting paid for detective work, fucking imbeciles.4
Why do shithead clients think they can walk away without paying us once we deliver the project !!!
So, here goes nothing..
Got an online gig to create a dashboard.
Since i had to deal with a lot of shitheads in the past, I told them my rules were simple, 20% advance, 40% on 50% completion and 40% after i complete and send them proof of completion. Once i receive the payment in full, only then i will hand over the code.
They said it was fine and paid 20%.
I got the next 40% also without any effort but they said they also needed me to deploy the code on their AWS account, and they were ready to pay extra for it, so i agreed.
I complete the whole project and sent them the screenshots, asking for the remaining 40% payment. They rejected the request saying my work was not complete as i had not deployed on AWS yet. After a couple of more such exchanges, i agreed to setup their account before the payment. But i could sense something fishy, so i did everything on their AWS account, except registered the domain from my account and set up everything. Once i inform them that its done and ask for the remaining payment.
The reply i got was LOL.
I tried to login to the AWS account, only to find password had been changed.
Database access revoked.
Even my admin account on the app had been removed. Thinking that they have been successful, they even published ads about thier NEW dashboard to their customers.
I sent them a final mail with warning ending with a middle finger emoji. 24 hours later,
I created a github page with the text " This website has been siezed by the government as the owner is found accused in fraud" and redirected the domain to it. Got an apology mail from them 2 hours later begging me to restore the website. i asked for an extra 10% penalty apart from the remaining payment. After i got paid, set an auto-reply of LOL to thier emails and chilled for a week before restoring the domain back to normal.
Dev : 1
Shithead Client: 025
Fuck it. I'm tired. Anybody found me a rich husband? I'm ready to assume the role of a trophy wife.
1. Still no recommendation letter. My PhD application is hanging on a thread. If I were such an intolerable ass, someone could've at least told me. Or at least told me "no" when I asked them to write these damn letters.
2. I turned down a job offer, cuz a) offered salary was below market average for that role on that level, b) the guy who was supposed to be my senior and the only other person in the team gave the vibe that he disliked me, and c) asked the PM a simple question of what is his expectations of the product for the next three to six months and didn't get a solid answer. (Can't do magic tricks)
So I turned it down cuz I don't want to get stuck in another's swamp. (Been there, done that!)
3. I'm running out of ideas for the comic I was working on. As well, the backgrounds of drawings proved to be an absolute hassle. Gah.
4. So, the next switch is to the barista role. I have signed up for a lackey/intern/assistant role which starts in about two weeks. Wish me luck cuz if this doesn't work out I'm all out of ideas. Like, literally don't know what I'm doing with my life anymore. Which will make those who are jealous of me really happy, but I shouldn't make my life about what doesn't make enemies and frenemies happy, right?43
Worst dev team failure I've experienced?
One of several.
Around 2012, a team of devs were tasked to convert a ASPX service to WCF that had one responsibility, returning product data (description, price, availability, etc...simple stuff)
No complex searching, just pass the ID, you get the response.
I was the original developer of the ASPX service, which API was an XML request and returned an XML response. The 'powers-that-be' decided anything XML was evil and had to be purged from the planet. If this thought bubble popped up over your head "Wait a sec...doesn't WCF transmit everything via SOAP, which is XML?", yes, but in their minds SOAP wasn't XML. That's not the worst WTF of this story.
The team, 3 developers, 2 DBAs, network administrators, several web developers, worked on the conversion for about 9 months using the Waterfall method (3~5 months was mostly in meetings and very basic prototyping) and using a test-first approach (their own flavor of TDD). The 'go live' day was to occur at 3:00AM and mandatory that nearly the entire department be on-sight (including the department VP) and available to help troubleshoot any system issues.
3:00AM - Teams start their deployments
3:05AM - Thousands and thousands of errors from all kinds of sources (web exceptions, database exceptions, server exceptions, etc), site goes down, teams roll everything back.
3:30AM - The primary developer remembered he made a last minute change to a stored procedure parameter that hadn't been pushed to production, which caused a side-affect across several layers of their stack.
4:00AM - The developer found his bug, but the manager decided it would be better if everyone went home and get a fresh look at the problem at 8:00AM (yes, he expected everyone to be back in the office at 8:00AM).
About a month later, the team scheduled another 3:00AM deployment (VP was present again), confident that introducing mocking into their testing pipeline would fix any database related errors.
3:00AM - Team starts their deployments.
3:30AM - No major errors, things seem to be going well. High fives, cheers..manager tells everyone to head home.
3:35AM - Site crashes, like white page, no response from the servers kind of crash. Resetting IIS on the servers works, but only for around 10 minutes or so.
4:00AM - Team rolls back, manager is clearly pissed at this point, "Nobody is going fucking home until we figure this out!!"
6:00AM - Diagnostics found the WCF client was causing the server to run out of resources, with a mix of clogging up server bandwidth, and a sprinkle of N+1 scaling problem. Manager lets everyone go home, but be back in the office at 8:00AM to develop a plan so this *never* happens again.
About 2 months later, a 'real' development+integration environment (previously, any+all integration tests were on the developer's machine) and the team scheduled a 6:00AM deployment, but at a much, much smaller scale with just the 3 development team members.
Why? Because the manager 'froze' changes to the ASPX service, the web team still needed various enhancements, so they bypassed the service (not using the ASPX service at all) and wrote their own SQL scripts that hit the database directly and utilized AppFabric/Velocity caching to allow the site to scale. There were only a couple client application using the ASPX service that needed to be converted, so deploying at 6:00AM gave everyone a couple of hours before users got into the office. Service deployed, worked like a champ.
A week later the VP schedules a celebration for the successful migration to WCF. Pizza, cake, the works. The 3 team members received awards (and a envelope, which probably equaled some $$$) and the entire team received a custom Benchmade pocket knife to remember this project's success. Myself and several others just stared at each other, not knowing what to say.
Later, my manager pulls several of us into a conference room
Me: "What the hell? This is one of the biggest failures I've been apart of. We got rewarded for thousands and thousands of dollars of wasted time."
<others expressed the same and expletive sediments>
Mgr: "I know..I know...but that's the story we have to stick with. If the company realizes what a fucking mess this is, we could all be fired."
Me: "What?!! All of us?!"
Mgr: "Well, shit rolls downhill. Dept-Mgr-John is ready to fire anyone he felt could make him look bad, which is why I pulled you guys in here. The other sheep out there will go along with anything he says and more than happy to throw you under the bus. Keep your head down until this blows over. Say nothing."12
So I found this thing though a YouTube Shorts called The Library Of Babel. Basically it stores every combination of characters and English words possible. This means that at the time I am writing this post, my post will be somewhere in the Library. Go check it out. It's pretty crazy.
Last week my company thought it would be a great idea to introduce a new sh*tty internal web portal that gives federated access to aws (instead of using our own accounts to assume dev roles like we used to do).
This broke a lot of sh*t that simply used to ask for an MFA token and used our practically permissionless accounts to assume a proper dev role. An MFA token that we'd enter directly into the terminal/tool. It was very seamless. But nooooooo we now have to go a webpage, login with sso (which also requires mfa), click "generate credentials," copy-paste those into terminal/creds file and _then_ continue our aws cli call. Every. Single. Day.
BUT TODAY I HAD ENOUGH.
I spent the entire day rewriting the auth part of our tools so they would basically read the cookie that's set by the web portal, and use it to call the internal api that generates the credentials, and just automatically save those. Now all we need to do is log into the portal, then return to the tool and voilà, the tool's also got access! Sure, it's not as passive as just entering an MFA token directly, but it's as passive as it gets. Still annoyed by this sh*tty and unnecessary portal, but I learned a thing or two about cookies.9
Manager: Why aren’t you working?
Dev: I am, I’m just not typing because I’m thinking an issue out.
Manager: Well what is taking so long? You haven’t written any code for like 15 minutes, you’ve just been doodling on your notepad.
Dev: I’m not “doodling”. I’m taking notes and trying to visualize the issue. It’s a complicated issue with application stat—
Manager: Well just simplify it then
Manager: Instead of making it a complicated issue just simplify it and then it won’t take you so long. You’re likely overthinking it, I never spend more than 30 seconds thinking about any issue before coming up with a solution. That’s what makes me so effective at my job is my ability to be lean like that.
Dev: …this issue is a bit harder than deciding what to have for lunch27
I've had two DevOps engineers ask me how I deploy new pipelines so quickly.
I show them how I automate the automation.2
In the darkest dankest parts of the code, I have discovered a way to get the tag UNDEFINED to show up in this rant. They call things that are unknown a black box. But you see, if you have a good enough shot gun, you can begin to blow enough holes through the box to figure out what's inside. I never said that whatever was inside the box was going to make it out... I just wanna get a good idea of what was inside.4
Me: Did Sherry let you know that I'm leaving today?
Coworker: what!? No!
Me: yeah... I'm leaving.
Coworker: huh, I'm not surprised...
Me: what is that supposed to mean!?
Co: shit man, this job sucks, I'm not surprised. I'll be leaving right behind you.
Me: oh.... Um... April Fools... 😬
Co: God damnit.
Me: don't worry, I won't tell the boss how you really feel.4
So my company set up environment for docker and bablabla manually . WHAT? and a new employee took 2 weeks to configure everything.
So I decided to do some automation, a script to auto cnfigure, download , blablabla, all the new guy have to do is run the script (regardless of OS) and that save two weeks time. Everything configured just took 4 hours (the project is 3 GB) automatically.