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
Search - "just whining"
I am at the lowest point of my mental health. Lol
I hope it doesn't get any lower than this because I have reached my breaking point.
I have nobody to talk to. I don't want to be a cry baby, nagging and whining all the time.
My friends here Jason (from Zurich and not Australia) and Rutee07 were in similar position when I last spoke to them here. I wonder what happened to them!
Shall I call in for yet another superficial therapy session? Or shall I just wait for the feeling to pass and continue being busy?27
Got a toxic mf transferred off the team. For months we knew nothing of what he was doing and every planning session he just kept saying that it's a waste of time to do this or that and instead just go past everyone to the source to get shit done, and completely ignored the development process we had to at least keep some sense of what people are doing. Also, spent months whining about stuff, instead of just accepting shit and moving on. If you don't want to get with the program, then go fucking do something else.6
More a call for discussion...
How can it be that devs constantly whine about technical debt, how everything is "ancient" bla bla bla...
Yet don't want to update libraries / stuff unless one explicitly rams an klingon pain stick up their arse because one is very very very very tired of lame excuses.
Even better example - and reason for the rant - new microservice.
They honestly started with JDK 8.
Looking at the dependencies is like walking in a museum...
OWasp Dependency check?
Lot's of 7.5s and greater (NVD score).
How brain fucked ignorant can one team be?!!!
Let alone that that thing - despite being just a skeleton project - has already 178 dependencies.
I don't want to look at the build files, I'll guess I'd turn to Freddy Krueger otherwise...
But really - why whining all the time like you have a clit / arsehole full of sand and then starting a new project with an obviously copy pasted graveyard skeleton?!5
Creating a stripped down version of a product is a big red flag to me (e.g. "easy/light mode").
It means the main product is too complicated; it handles too many things. Instead, shift the focus back to the core of the product by removing features.
In the our day-to-day it is completely normal to stumble upon things that used to work but now have been changed: they have been deprecated.
Deprecating and removing features should be added to any product iteration. Thus being "normal" and a common occurrence in any changelog; just like features and bug fixes.
This gives non-tech product owners "permission" to remove bloat. Devs stop whining about "the big rewrite". And end-users don't suddenly have to learn yet another tool with "basic" features missing.
I think the best example is google (https://killedbygoogle.com/) and the worst is the amazon shopping website (what a mess!).3
After working with a bunch of people it occurred to me that almost anyone can work and learn for most IT positions. This is something that most people will realize, especially if they work with newbies that learn on the go. There are exceptions of course, but most companies are just making crud apps with their business logic.
What I wonder then is, why is it that the way hiring is done seems to be completely against this idea? Rather than whining about recruiters and bad interviews, I am curious about why this is so common. What is it that a lot of companies think or see that make their hiring process so bad or convoluted?11
I just think some people, in some countries, simply lack the culture for the type of communication DevOps requires. Observing from the sidelines I've now seen multiple people complain in different kinds of meetings how teams don't communicate and nobody knows what others are doing and this leads to conflicts and duplication of work. But when it's time to actually build a community where those developers would be able to discuss freely and safely about that work, nobody fucking says anything. Nobody responds to threads, nobody opens up discussion, everyone just shuts up and ignores the community.
Why the fuck are you whining about silos then if you behave this way you ignorant monkeys!?4