I*******o
发帖数: 53 | 1 如果你和team member关于某个design有不同意见，
而且你认为他的design从long term来讲肯定会出问题，你怎么办？ | c*****t
发帖数: 1879 | 2 The person having the responsibility wins.
Also, there is no such thing as "long term". There is no
spec for the future, so you can't really code it. All the
codes are compromise between elegant and quick-n-dirty solutions.
【在 I*******o 的大作中提到】
: 如果你和team member关于某个design有不同意见，
: 而且你认为他的design从long term来讲肯定会出问题，你怎么办？
| g*****g
发帖数: 34805 | 3 Don't think too much about far future. Requirement changes,
design changes, codes change. As long as you have a good framework,
it won't be too hard to accomodate any changes,. But doing too much
for the future is just not worth it.
【在 I*******o 的大作中提到】
: 如果你和team member关于某个design有不同意见，
: 而且你认为他的design从long term来讲肯定会出问题，你怎么办？
| m******t
发帖数: 2416 | 4
Depending on how much responsibility you have over that particular piece,
and how much it would impact your pieces.
This is really more of a political issue than a technical one. In my
consultant mentality, I would alway bring it up. My client is entitled to my
professional opinions, so I'm obliged to provide them, but I'd be
completely fine if they choose to ignore them - they are entitled to that
just as well. 8-)
【在 I*******o 的大作中提到】
: 如果你和team member关于某个design有不同意见，
: 而且你认为他的design从long term来讲肯定会出问题，你怎么办？
|
|
