• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Agreeing on design issues in a team...

 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Today we talked about some design issues for a web application we are doing. We had an discussion about something and I settled for something I disagreed with because two people (whose opinions I normally respect) thought my solution was a bad idea.

However, I feel that I finally agreed because it was 2 to 1, not because I think their solution is better. Both solutions had their pros and cons, but I still think my solution has the better advantages but I couldn't convince them of that.

How do you handle these situations? Are you going for the democratic approach or will you do everything possible to push your solution as the definitive one?
 
Sheriff
Posts: 4313
Android IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't think this is really "Meaningless". I'm going to move it to the Jobs Discussion Forum where its more appropriate.
 
blacksmith
Posts: 1332
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jaap van Hengstum:

How do you handle these situations? Are you going for the democratic approach or will you do everything possible to push your solution as the definitive one?

Neither. I like to listen to all arguments and point out everything I think others are missing, jointly exploring all the implications. I then push the solution that makes the most sense. I don't worry about who proposed which solution.

How hard I push depends on how much of a difference it makes. If giving in will just add, say, twenty percent overhead to the work, that's not a disaster. If it will doom the first three months of the project to being totally wasted when we discover the approach doesn't work at all and we have to start over from scratch, I'll push very hard not to make the mistake - and consider leaving if the team is unable to avoid such major mistakes.
 
Not so fast naughty spawn! I want you to know about
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic