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
Search - "collaboration"
-
Today is sprint demo day. As usual I'm only half paying attention since being a Platform Engineer, my work is always technically being "demoed" (shit's running ain't it? There you go, enjoy the EC2 instances.)
One team presents a new thing they built. I'm still half paying attention, half playing Rocket League on another monitor.
Then someone says
"We're storing in prod-db-3"
They have my curiosity.
"Storing x amount of data at y rate"
They now have my attention. I speak up "Do you have a plan to drop data after a certain period of time?"
They don't. I reply "Okay, then your new feature only has about 2 months to live before you exhaust the disk on prod-db-3 and we need to add more storage"
I am asked if we can add more storage preemptively.
"Sure, I say." I then direct my attention to the VP "{VP} I'll make the change request to approve the spend for additional volume on prod-db-3"
VP immediately balks and asks why this wasn't considered before. I calmly reply "I'm not sure. This is the first time I'm learning of this new feature even coming to life. Had anyone consulted with the Platform team we'd have made sure the storage availability was there."
VP asks product guy what happened.
"We didn't think we'd need platform resources for this so we never reached out for anything".
I calmly mute myself, turn my camera back off and go back to Rocket League as the VP goes off about planning and collaboration.
"CT we'll reach out to you next week about getting this all done"
*unmute, camera stays off* "Sounds good" *clears ball*4 -
Getting zero encouragement or positive feedback from my boss is really killing me from the inside. There isn't even a negative feedback. There's absolutely nothing.
PhD is such a lonely path as it is, and being ignored by your advisor is just...soul-crushing.
I did a collaboration with my friend from another lab, and even though her lab is bigger and crazier than ours, her professor found the time to compliment our work and even told us he will present it in a presentation he gives in Meta. Really, it's not that hard to say a kind word here and there.4 -
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 -
At my last startup, the company decided to formally adopt core values after being in business for ten years already. They even emblazoned them on a mouse pad and sent it out to every employee as company swag. I quickly learned that those values were more for show. It was a sign of the culture going downhill. Values included teamwork and collaboration. But since I was only an IC and wasn’t a manager or director or VP, I was expected to be a mindless worker bee. Even when I just asked logical followup questions, I was treated like I was being insubordinate and “questioning their requests.”1
-
If I had to name one attribute that dominates the software engineering ecosystem, it would be “arrogance” especially among young programmers. I think software engineering would be a much better place to work if people were more empathetic than being ginormous assholes trying to have a leg up over all their peers. Collaboration is much more rewarding than competition. It feeds your soul and feels a lot more natural.
Collaboration over Competition.
Have a peaceful day at work guys!5 -
On the one hand I really wish there was a good open-source self-hosted file sharing and collaboration service which made use of modern web technologies to provide most of its features inline as well and not just through APIs consumed by client applications.
On the other hand, I tried writing a WebDAV server once, and I fully empathize with the people who have to deal with this madness. -
Recently, our backend team has gotten smaller. The company has stopped the collaboration with the company of the backend lead developer.
We are currently lacking backend developers while we have way too many frontend developers right now (compared to backend).
How can I, as a front-end developer, switch to back-end?4 -
Went on a Hackathon with two friends. They didn't do shit. This week, they told me that they only knew c#, so we should switch to that. (I use Linux so I shouldn't have accepted that) Just learned that they are going to a maths camp this week and the deadline is next Sunday. Dotnet core CANNOT PARSE FUCKING JSON. I'll rewrite it in node.js, and hope that I can type fast enough to finish in time. Fuck me, fuck my lazy friends and especially fuck Microsoft for saying that they support Linux while providing a dotnet for Linux published in 200-fucking-56
-
So far it has been a collaboration with a shoemaker. I produced the most awful website I (never thinked I) could make… and not by my design, quite the contrary! This guy was there asking me to break rule after rule of design and would refuse suggestions and advices to follow their vision!
Pointless to say the site was down 6 months after being created.4 -
How do I push a hiring offer to later and say no?
Context:
I work at company A and the manager, let's call her Jane, who hired me at company A, left shortly after to join company B at a senior executive level (very high up the ladder in a public company).
After few months, I decide to quit company A and started my job hunt. I received a job offer from company C.
Now, my relationship with Jane was super awesome. Jane was very supportive and thought very highly of me. She offered to write a LoR (letter of recommendation ) for me whenever I needed it.
Now, out of courtesy and maintaining the relationship, I mentioned to Jane that I quit company A and will be joining company C.
To which she immediately mentioned that she could hire me and setup my connect with one of the hiring managers in her team. We had our initial conversation and they skipped second stage (since I got a very high reference) and moved to final stage of the interview.
Now, I am not really keen on joining this company B as it will also require me to move outside of the country to a different timezone.
At the same time I don't want to sabotage my relationship with Jane and make sure I keep my options/doors open for some collaboration in future.
How do I go about telling Jane (and the team) that for now, I am focusing on joining company C and would like to explore the opportunity with her company/team in future, without damaging my professional image?11 -
How do other developers handle local websites that are large in size? Currently the code and site need to be setup for each client for several developers. We use github and bitbucket repos for the code.
The biggest issue is downloading the site files and setting it up locally for each developer. We used Docker for some projects but ran into permission issues and storage space became an issue.14 -
Hi there, my 2 cents to rant on WWDC :)
- Check time? My big head is in the way.
- Work tabs... Why is my Wordle in the list?
- Edit message ... Good bye iMessage memes :(
- Dictation. Hello Jarvis. Hi CIA. Sup 0-day devs
- Live Text. Indian tutorials are now just a copy paste away
- Wallet keys sharing through messages 🤌
- Family. Send more screen time through messages (goodness this messaging app is becoming less green)
- Shared libraries in photos, lovely, now your aunt knows you love visit and taking photos of the neighbor (if you forget to turn it off)
- CarPlay, this will need screen time soon, ui so beautiful you gonna plan a journey by tinkering with the dials
- Check time (part 2) on the iwatch, My big head is still in the way
- Fitness app, Sleep app, Health app, Medication app, mmm lovely but still cant put my confidence in AI
- M2, saw it coming. Spec: scaringly powerful.
- isnt the midnight MacBook air elite?! But the notch tho. Magsafe is back, more thin, this thing looks fragile.
- Did they show a game running lower than the videos fps on purpose? Hmmm
- Ventura's stage manager, xbmc vibes
- Is that Facetime attachment free? Is there a subscription to continuity camera?
- Tab Group Collaboration, hehe, "they can see which tabs you're looking at" hehehe
- Free Form: bloatware
Meh, I cant rant more, honestly the new features look good.1 -
Way to go ruin a collaboration. I wanted to have fun some making a game with one of my friends, but turns out being friends doesn't correlate to making a good team. Some of you probably know this, but I've never had such an experience, not even to almost strangers
Some tips on how to kill off any motivation to work with you:
* Casually insult other peoples ideas
* Don't consider other people's point of view
* Try to talk people out of prototyping/experimenting with their OWN ideas on their OWN time
* Completely undermine their skill even though you have no basis to go on
* Never worked with this person before
* less experienced
* don't have to give estimates on a daily basis
* don't consider the fact that there are libraries that can be used to speed up things)
* Victimize yourself, because someone is "forcing you" to become the bad guy
I don't know if that person is on here and I don't care if they happen to read this. I tried to treat you with the most respect, but if you don't do the same then just fuck off.
Anyways, there goes the idea of a "no stress, no problems" game dev project, because I wanted to see if isometric view would work better than top down.
My idea to have another person to work on a project with, to keep the motivation up backfired a by lot.
Someone within european timezones up for some hobby game dev?3