Details
-
AboutJust here to rant and read rants
Joined devRant on 4/25/2020
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
-
Something that I'm utterly ashamed of.
Had to add text message and call communication functionality in one of the products.
Boss shrunk the deadline to two days ETA.
Didn't know jackshit about twilio.
Meeting with client:
Client - So the communication thing is done right?
Me - Yyeahhh
Client - Let's try it then. *Calls himself*
Me - *Calls the API directly from my phone*
Client got out happy. Nobody knows what actually happened there. I didn't even talk to my colleagues about this. Boss gave me bonus to pull of the impossible. I added the feature after a week of the incident.8 -
I’m collecting the offensive words that target me personally. The more it stings the better.
I only need single words, the simpler the better. I don’t need a long burns.
Once I collect them, I’m planning to give them to my future sexual partner to call me proper names while they hatefuck me during a consensual non-consent session.
So please help me :)23 -
FUCK YOU GITKRAKEN
After all the suggestions in https://devrant.com/rants/1540091 I decided to give Gitkraken a try.
Here's the shitty experience you can expect:
1) It doesn't even ask you where to install it. Turns out, it spontaneously installs itself in "%LOCALAPPDATA%\gitkraken" - who the fuck installs software there??
2) It is "seamlessly integrated with GitLab", except the first time you open it you can only log in with your GitKraken or GitHub account, and NOT with a GitHub one. Just brilliant
3) After logging in, it spontaneously changes your global git username and email config, because fuck you that's why
4) If you have a repo on AWS CodeCommit with an remote that looks like "ssh://git-codecommit.us-east-2.amazonaws.com/...", *after the first push* it will spontaneously change it to "<user>@git-codecommit.us-east-2.amazonaws.com/bla/bla", causing future actions to fail. Because FUCK YOU, THAT'S WHY.
And they expect people to pay for this shit, just to be able to manage more than one account at a time (and some "additional features" that are not even listed on the site)?
FUCK OFF, AND FUCK YOU FOR WASTING MY FUCKING TIME, HOW ABOUT I CHANGE YOUR FUCKING SETTINGS TO FUCK YOU22 -
Bugfix I am most proud of?
The ones where I dont just fix a bug, but refactor an old (possibly shitty) feature thanks to new knowledge, making the next person's job easier in the process :)3 -
I used to be a lousy software developer, and I used to settle for what I knew. Until my sister told me that my mother spoke of me to the family as a successful professional, someone who had overcome the poverty where he grew up and now lived in another country. Since then I have struggled to become a better professional, a better husband and in a few months i want to be the best that! My wife's pregnant!9
-
Like one of those jobs that demand 12 years of experience with Kubernetes (which was released 6 years ago)6
-
So this has happened before, but I think I’m gonna deliver late on this project. I really don’t want to look bad within the first six months of a new job. Someone lie to me and say it’ll all work out. 😭😭4
-
Took a task with 3 story points ( mappable to ~2-3days) and wondered why it was so much more than the estimation. I expected to finish in 2 to 2 1/2 days but needed 4. Afterwards I just realized that I accidentally did more then needed and finished two upcoming stories as well, each 2 SP so 7SP for everything.
Feeling jumped from "man I could be faster" to "man that was really fast".
It feels like a fuck up, however, it is victory1 -
When Coronavirus become a household name, our Manager said:
"This is a good to time to build a real-time chat system like Zoom. If anyone is able to build something like it, it will help our company grow."
[Silence]
Manager: "There is a lot of demand."
[More silence]12 -
I had a short gig for a startup where I was meant to migrate the entire backend to serverless. It was my first time learning what serverless was and I had just been working on the app for around 2-3 weeks.
Boss rolls in with his leased Tesla and sort of hints at me being finished with a certain area by the next day, giving me a wink as if he's just trying to motivate me to keep on struggling.
Turns out he decided that he wanted a fully fledged demo and went off on me because I hadn't finished migrating the UI for that certain section (just the backend). I decided that there were better things to work on while I was at it migrating the backend. Had I known that he expected some form of fancy demo, maybe I would have done things differently.
He then proceeded by letting me know that he could have finished my work in half the time it took me and decided to remind me that I had a probationary employment. I left the company two weeks later and the app never got released.2 -
Impossible deadlines are ubiquitous in our company. Our CTO has the opinion that development is a lightning-fast process that doesn’t require testing and deployment because every developer is a God.
It is normal to hear something like ”just develop it tomorrow morning, it is easy” from him, but in reality, it is never that easy. -
Would you like to smile for 10 seconds? Read this short story:
*Story begins*
During World War II, numerous fighter planes were getting hit by anti-aircraft guns. Air Force officers wanted to add some protective armour/shield to the planes.
The question was "where"?
The planes could only support few more kilos of weight. Mathematicians were called for a short consulting project.
Fighter planes returning from missions were analysed for bullet holes per square foot.
They found 1.93 bullet holes/sq. foot near the tail of planes whereas only 1.11 bullet holes/sq. foot close to the engine.
The officers thought that since the tail portion had the greatest density of bullets, it would be the logical location for putting an anti-bullet shield.
A mathematician said exactly the opposite; more protection is needed where the bullet holes aren't - that is -around the engines.
His judgement surprised everyone. He said "He said We are counting the planes that returned from a mission. Planes with lots of bullet holes in the engine did not return at all".
Moral: Not everything that counts can be counted, and not everything that can be counted, counts.
Source: From the book -
"How Not To Be Wrong", by Jordan Ellenberg.4 -
One week, and it turned out to be worse than that.
I was put on a project for a COVID-19 program in America (The CARES Act). The financial team came to us on Monday morning and said they need to give away a couple thousand dollars.
No big deal. All they wanted was a single form that people could submit with some critical info. Didn't need a login/ registration flow or anything. You could have basically used Google Forms for this project.
The project landed in my lap just before lunch on Monday morning. I was a junior in a team with a senior and another junior on standby. It was going to go live the next Monday.
The scope of the project made it seem like the one week deadline wasn't too awful. We just had to send some high priority emails to get some prod servers and app keys and we were fine.
Now is the time where I pause the rant to express to you just how fine we were decidedly **not**: we were not fine.
Tuesday rolls around and what a bad Tuesday it was. It was the first of many requirement changes. There was going to need to be a review process. Instead of the team just reading submissions from the site, they needed accept and reject buttons. They needed a way to deny people for specific reasons. Meaning the employee dashboard just got a little more complicated.
Wednesday came around and yeah, we need a registration and login flow. Yikes.
Thursday came and the couple-thousand dollars turned into a tens of millions. The amount of users we expected just blew up.
Friday, and they needed a way for users to edit their submissions and re-submit if they were rejected. And we needed to send out emails for the status of their applications.
Every day, a new meeting. Every meeting, new requirements that were devastating given our timeframe.
We put in overtime. Came in on the weekend. And by Monday, we had a form that users could submit and a registration/ login flow. No reviewer dashboard. We figured we could take in user input on time and then finish the dashboard later.
Well, financial team has some qualms. They wanted a more complicated review process. They wanted roles; managers assign to assistants. Assistants review assigned items.
The deadline that we worked so hard on whizzed by without so much as a thought, much less the funeral it deserved.
Then, they wanted multiple people to review an application before it was final. Then, they needed different landing pages for a few more departments to be able to review different steps of the applications.
Ended up going live on Friday, close to a month after that faithful Monday which disrupted everything else I was working on, effective immediately.
I don't know why, but we always go live on a Friday for some reason. It must be some sort of conspiracy to force overtime out of our managers. I'm baffled.
But I worked support after the launch.
And there's a funny story about support too: we were asked to create a "submit an issue" form. Me and the other junior worked on it on a wednesday three weeks into the project. Finished it. And the next day it was scrapped and moved to another service we already had running. Poor management like that plagued the project and worked in tandem with the dynamic and ridiculous requirements to make this project hell.
Back to support.
Phone calls give me bad anxiety. But Friday, just before lunch, I was put on the support team. Sure, we have a department that makes calls and deal with users. But they can't be trained on this program: it didn't exist just a month ago, and three days ago it worked differently (the slippery requirements never stopped).
So all of Friday and then all of Saturday and all of Monday (...) I had extended panic attacks calling hundreds of people. And the team that was calling people was only two people. We had over 400 tickets in the first two days.
And fuck me, stupid me, for doing a good job. Because I was put on the call team for **another** COVID project afterwards. I knew nothing about this project. I have hated my job recently. But I'm a junior. What am I gonna say, no?7 -
Seriously github, the best thing you could do for the black community is change the name master to main, fuck you and your publicity stunts2
-
Today we were all called into a meeting and the CEO was livid. He went on a rage about how the CTO was wasting money on useless shit (GitHub Enterprise). He said I bought laptops for a reason if there’s a fire someone better protect our assets and code. He wouldn’t reason with us and went into github and deleted everything. The CTO was fired and no one is leading our team. Wondering if I should quit 😶29
-
This guy at my last internship. A windows fanboy to the fucking max!
He was saying how he'd never use anything related to Linus Torvalds because he hated him for creating Linux.
Two seconds later I saw him initializing a new git repo.
I was standing there like:
*should I tell him?*
😅😆70 -
My dumb CEO just hired an even dumber CTO. The new CTO asked me the following questions...
1. What is GitHub?
2. What is JSON?
3. What’s an array?
4. What is Get and what is Post?
5. When an iPhone is offline, can it call an API on our server to tell us it’s offline?
6. I know you’ve spent 11 month the writing this backend in PHP but can you change it to Java now?
Me: Why?
Dumb CTO: Because it’s better.
Me: How?
Dumb CTO: because it is.
7. I know you’ve started to rewrite this codebase I Java but can you convert it to Node.JS now?
Me: Why?
Dumb CTO: Because Facebook uses it.
8. What is MySQL? Why aren’t you using a database instead?
9. What does NULL mean?
Somehow, I doubt that asshole is remotely qualified for the job.
Fakin shyt for brains.180 -
"Are you familiar with uploading your code to Google Drive?"
I left the building at that exact moment.41 -
I recently met a young fella (14yo) playing League of Legends. He asked:
- What do you do for a living?
- I'm a programmer, do you know anything about programming?
- I don't, actually.
Apparently he was playing from a LAN Gaming center 'cause he didn't have a computer at home (his computer had broken and these Lan centers are pretty affordable).
I figured I could explain to him what was it and what super powers you could get from it. Turns out I recommended a JS course in codecademy and now he goes to the LAN center every day to study programming (he got really into it!).
Now he always pings me with questions about JS and apparently he's learning a ton! He had almost no English skills too (we're Brazilian), and because most of the material in the internet is in English he found himself some free English courses and he's now taking them!
Knowledge is free on the internet and I guess he's just realized that.
Not exactly a rant guys, just figured it was a nice story to tell :)
#TeachAKidHowToCode57 -
- Sir, you must put away your laptop before the flight takes off.
- Is a tablet okay?
- Yes
- *Uncouples keyboard from Surface*
- ಠ_ಠ
- (⌐■_■)17 -
What devrant taught me:
Everyone hates java
Everyone hates php
Everyone hates spaces
Everyone hates tabs
Everyone hates vim
Everyone hates windows
Everyone hates linux
Everyone hates clients
Everyone hates PMs
Everyone hates every language they're not working with
Everyone loves devrant 😊36 -
┓┏┓┏┓┃
┛┗┛┗┛┃\○/
┓┏┓┏┓┃ / Friday
┛┗┛┗┛┃ノ)
┓┏┓┏┓┃ Deploys
┛┗┛┗┛┃
┓┏┓┏┓┃
┛┗┛┗┛┃
┓┏┓┏┓┃
┃┃┃┃┃┃
┻┻┻┻┻┻17 -
Website design philosophies:
Apple: "...and a really big picture there, and a really big picture there, and a really big picture there, and..."
Microsoft: "border-radius:0 !important;"
Google: "EVERYTHING MOVES!!! And most websites get material design. Most."
Amazon: "We're slowly moving away from 2009"
Wix: "How can we further increase load times?"
Literally any download site: "Click here! No, click here! Nononono!! Click here!!..."
Facebook: "We can't change anything because our main age demographic is around 55"
University websites: "That information isn't hard enough to find yet. Decrease the search accuracy and increase broken links."32