Page 1 of 1
Posted: Tue Jul 13, 2010 11:48 am
by TheCatt
So... we had a situation with our code today, and I proposed a solution.
Another developer said "OK, do that, it's what I'd do too."
Funny, cuz svn says he's the one who wrote this stuff to begin with.
Posted: Tue Jul 13, 2010 12:49 pm
by Malcolm
I've lost track of how many of our architects have recommended, nay demanded, feature X & then slammed it a few weeks later.
Posted: Wed Jul 14, 2010 11:39 am
by thibodeaux
What's fun is to look at SVN and find that a certain dev hasn't committed ANY CODE IN THE LAST 3 MONTHS.
What's even more fun is that dev is now an "architect" somewhere else. And the team he used to work for has done more in the past few months than it did in the previous year.
Posted: Wed Jul 14, 2010 11:50 am
by TheCatt
Architects work in CONCEPTS, man... code is details. 
Posted: Mon Jul 19, 2010 3:57 pm
by Malcolm
Malcolm wrote:I've lost track of how many of our architects have recommended, nay demanded, feature X & then slammed it a few weeks later.
Developer X : We need to use this new data type so we can improve our performance on this UI screen.
Me : Alright, but your team has to build the methods for it. Mine doesn't have the time.
Developer X : Oh, nevermind then.
[approximately 18 hours later, when my manager examined the project schedule & found the time]
Me : I can build those methods for you.
Developer X : Uh, we don't want it anymore.
Me : Why not?
Developer X : Technology risks.
Odd, because his final report (which was based on my analysis) actually said there were more risks staying with our current technique.