Aboutfumbling in java
Joined devRant on 3/1/2018
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
Here we are, three years later. Our system breaks down at the slightest load. An architecture is hardly recognizable anymore. The code consists of methods that have been refactored beyond recognition. The so-called architects came and went, leaving behind an ever-growing fiasco. Wrong decisions are concealed, criticism of them dismissed as ignorance. Our clients are on the verge of having us all killed. Daily crisis meetings are the norm. The remaining developers skulk around the unmaintainable code like emaciated ghosts. Everyone who has even the slightest chance to escape takes a parachute. Our dailies are made up of lies to cover up yesterday's lies. Our Mondays have become days of dread, because that's when the weekend disaster news has to be analyzed. Yet there are still developers who turn a blind eye. Who recommend this and that workaround in a good-humored tone. The code consists only of workarounds. Sarcasm has replaced any normal discussion. Reasonable suggestions on how to basically refactor the whole thing are rejected for cost reasons. In the process, our entire budget is eaten up by maintenance costs. Middle management should be put up against the wall. Why am I still here? This deceptive feeling that one could still turn the tide. This is eating me up.2
Been on a conference call with some coworkers and a huge company which is trying to sell us a new tool for our CI environment. Sales guys ask us sensible questions about our requirements and try to find out our needs. No one of my coworkers says a word. Sales guys rephrase their questions but STILL: Crickets on the line from our side and this call gets embarrassing. So I try to explain our SW dev process and explain what we need for our CI and suddenly Mr. Manager sends me a text msg telling me to to "STFU!"....Oh well THANK YOU, I just tried to be polite to these sales guys who were invited by US and took their time to present us their really good tool. I mean cmon...what is F*CKING WRONG with you?5
A new currency is emerging in our industry. It is called "blame".
Who is to blame if we don't meet the deadline?
Who is to blame if the rushed release has x bugs?
Who is to blame if nightly build breaks, because our CI-Server is an old hunk of junk and "management" didn't approve the upgrade?
Our customer blames the delay in HIS infrastructure on us, because our system requirements are too high.
Blame blame blame. This currency is the new idol of our management team. Everyone gets blamed. They manage their "blame" ledgers instead of approving the tools we need or give us reasonable deadlines. Why Lord, oh why are there SO MANY MORONS in managment? You know what, dear "managers"? FUCK YOU., FUCK YOU SO HARD YOUR MOM WON'T RECOGNIZE YOU. YOU COULDN'T POUR PISS OUT OF A BOOT WITH INSTRUCTIONS ON THE HEEL.4
Is it just me or are all the stoopid people in middle management? Why do these clueless people always impose completely nonsense requirements? Like 'You have to process all entered client data but you are not allowed to store it, nowhere, because of GDPR, storing data is evil!' But when customer logs on all his not persisted data has to be pushed to the frontend immediately. WTF THIS IS CRAZY5
So, I have a coding task that takes several days to complete. How can I pick up the next day where I left off the night before? I find it difficult to get straight back into the flow because I first have to find my way around the previous day's code. Any tips?11
Today our so called "architects" chose the most complicated, most unmaintainable, prehistoric way to handle a simple, really easy REST problem...they stood around the white board, marveling at the alleged brilliancy of their imbecile drawings and tried to show us low life devs how we should implement this or that idiotic aspect of their crazy solution. We looked at each other desperately, raising our eyebrows at each new wave of insanity. No one spoke up...that includes me. I feel shit right now. Implementation sprint starts tomorrow. Thinking of grabbing a life vest and jumping overboard right now. Our customer will strangle us for this wannabe crap and I am already scared having to show the resulting API to them.4
If you plan on using Apache Kafka for whatever:
Don't do it. You are on the gates of hell.
If you are using Apache Kafka:
I feel sorry for you.
If you decided not to use Apache Kafka:
You chose wisely.12
Caught up in a deathmarch project with buzzword driven, childish architects who treat devs like insects and brag about their non existant experience and achievements while imposing completely idiotic requirements and unrealistic milestones. I feel shit right now.1
I'm in charge of our Maven based build process. Doing CI with Jenkins. Coworker develops huge multi module project, doesn't take care of hierarchical structures or any other Maven good practices.
Build fails due to several circular dependencies and other ill stuff.
How to handle the "I know better than you but haven't written a line of code in years" - SW-architect?4
Stackoverflow...asking for a framework to do X.
Question gets closed by 20++ nitpickers because "... asking us to recommend or find a book, tool, software library, tutorial or other off-site resource are off-topic"
Scroll down 1 inch to find really useful answer.3