Details
Joined devRant on 3/10/2018
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
-
Java in 2000: Just to be clear, JavaScript is not my kid
Java in 2020: Just to be clear, JavaScript is not my dad4 -
So today I debug the code from the previous developer.... I show this in the file I wonder what it is as I debug , it give the log which is I don't know what to react .....4
-
FUCK TOMCAT
FUCK JAVA
FUCK SYSTEMJS
FUCK SYNCFUSION
FUCK THIS SHIT WHOEVER DESIGNED ANY OF THIS GARBAGE SHOULD BURN IN THE LOWEST CIRCLE OF HELL.8 -
Don’t work under a lead dev that is single focused on immediate problem solving. You will only ever put out fires caused by their small-mindedness and miss on learning to solve bigger problems.2
-
We work in a field full of pretentious bitches, messed up egos, and fucking over inflated titles.10
-
Fucking teams.
It's shit, it's buggy, it's confusing, threaded conversations suck when there are multiple ones going on because stuff appears out of order and is easily missed.
I hate it with a passion.5 -
Stop! Changing! The requiremeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeents!
Hadouuuuken!
Shoryuken!
Tiger punch!3 -
Alphabet has stake in Uber.
Waymo is partnering with Lyft.
Alphabet is gonna be the future of autonomous vehicles.
Now, how far that future is a whole new question entirely. 🤔3 -
Never gave much consideration to new year's resolutions, but here we go:
- Make my life less shitty
- Find a way out of my depression
- Get back to my old rythm
- Be in control of my own mind and my body again5 -
Have fun coding again.
It’s just a job at the moment. I wanna have the satisfaction again.
And find a girl..8 -
Boss: “Our YouTube channel doesn’t look at all like our website.”
Me: “I’ve made it look as close to our branding as YouTube allows for with its limited editing controls.”
Boss: “This is unacceptable. I expected more from you.”
Me: “I cannot accept the blame for this. YouTube is setting the design parameters for all channels and I can only do so much.”
Boss: “You can call the YouTube, can’t you? Why didn’t you call them?”
Me: “.......and ask them....what?”
Boss: “You don’t ask! You tell! Our company has been around for 140 years. Our brand name carries that weight. They’ll change their design to what we need if you’re assertive enough.”
Me: “Ma’am, that’s just not how this works. That’s not how any of this works.”50 -
I really think there should be a subject in every CS course to teach us how to handle/work-under Grade-A assholes and dumbfucks. Not that it would help, but atleast warn us on what we are getting into.
In my opinion, development is not *that* hard or frustrating but is made so by these shitty people. But again, what do I know.
I was scolded by my boss for using for-loop to iterate through an array recently. Apparently for-loop is not used in real world projects and this iteration should be done "in-memory". My colleagues and I are still trying to understand and process that.
I was asked to add fitbit integration to a project within 2 hours just because I had "already done it a week ago" in *another* project. Luckily, it was then given to a "senior" developer who took 4 days for it and essentially copy-pasted my work without much changes, ofcourse it stopped working every now and then.
I am given unreal deadlines on my tasks, on technologies I haven't worked on before, and then expected to churn out production ready code with no bugs in them.
My boss literally just sends me the links of 1st three google results on the problems I encounter and report, after humiliating me ofcourse. Yes, I did google it and yes I went through all I could find from Google forums to GitHub issues. When the library/plugin author himself says that this feature is not yet available, don't expect me to develop it in 2 hours you dumbfuck.
And for the love of God, please stop changing the data model every single day and justify it with agile development. Think before making any changes to it. Ever heard of Join queries? Foreign keys? Or any other basic database concepts.
We reached a point where each branch in the repo had different data model. Not kidding. And we were a team of just 4 developers. Atleast inform us when you change models after discussing it with your shit for knowledge "senior" developer, so we don't have to redo it all over again. The channels on slack are not for sharing random articles only.
I am just waiting to complete my year here.
I should have known what I got myself into the day he asked me to remove the comments I had added to explain what my code does. Why you ask? Because "we don't write comments".