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
-
Worst collaboration experience story?
I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.
The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.
Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"
Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).
Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".
Couple of months of UI re-design and many other changes, the app was ready for beta testing.
In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.
With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).
Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.
By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.5 -
I don't know how managers are planning deadlines and counting December as a full working month!
Most companies that I worked with, count either half a month or push the deadline until the end of January when the workforce is back but not here.
Our division manager has promised the customer that the production environment will be ready on the first week of January, without even consulting the team or checking the schedule like WTF!
The person responsible for setting the infrastructure was on vacation for 2 weeks and he didn't hand over the access to production or share the progress done.
Fast forward, the manager went to slack and pinged the whole company with full caps message that the production should be done today.
Fun times :/10 -
CPU time? Wayland, or Linux.
I/O? Firefox or VSCode. If I'm pedantic about not counting dispatch as usage then VSCode because Firefox is just a mediator between me, the OS and the webapp at hand.2 -
Every passing day in this country drives me crazier.
Someday, maybe soon, I'll go insane.
I feel claustrophobic and suffocated. My interests are changing even if I don't desire to. Feels like a forced changed, as the new ones don't necessarily make me happy, and rather remould me to fit into a toxic environment/society.
While I was raised in this environment, most of my opinions formed via internet which had a heavy influence from the west. When I got to my sense, almost at the age of 24, was the time when I started forming opinions. Internet was my only pal. Family/friends never bothered about me. And now when I dream of and work hard towards moving out, the same family/friends guilt me into not doing so. Maybe they care now, maybe they are jealous, maybe something else.
Even if I settle down here, convincing myself that I desire such a life and counting the benefits of doing so, it won't make me happy.
The heart wants, what the heart wants.4 -
“Lazy mom lazy wow” presented by Gail Swanlund was probably the most impactful piece of art to me.
Through simplistic form, this art piece presents the idea of caring about oneself and quit the eternal rat race for money. But somehow for its metaphor, Lazy mom lazy wow chooses the notion and aesthetics of death and decay. The closest analogy I can think of is the music of American Football. Some kind of liminal, eerie aesthetics. Also, the movie Gummo and the game Life is Strange, part one.
The piece deliberately avoids being aggressive and celebrating its notion. It’s not “quit the rat race and celebrate because life is so good”, it’s “quit the rat race by putting yourself into coma so nothing matters anymore”. The descent into eternal comfort of realization that you don’t have to do anything anymore, but also sorrow of losing meaning.
It feels like launching Counter-Strike Source in the year 2051, only to walk around cs_office and realize there are no players anymore, and they will not return ever again. The sense of watching an old VHS tape of you having a conversation with your mom in the hospital as she’s counting her last days because of cancer. The sense of comfort of coming back to your hometown. You remember your childhood and your high school crush, only to realize that those moments won’t happen ever again.
Top Tags
Weekly Rant
View