Skip to main content
6 events
when toggle format what by license comment
May 30, 2012 at 23:21 comment added Tiago Cardoso To make things worse... it's not even a development project.. is a maintenance project.
May 30, 2012 at 20:47 comment added eMgz Well, given that, can this guy program at all? If not, I don't know what he is doing in your team.
May 30, 2012 at 17:18 comment added Tiago Cardoso My point is... the whole team has the understanding that this process is almost as simple as sending one mail... who'd like to be reviewing mails? I completely agree that anything beyond the obvious must be reviewed, my concern is that the instructions are 'take it from here, paste here and run there' and still we have problems for over than 6 months...
May 30, 2012 at 17:08 comment added eMgz Don't look at review as an overload, it's a necessary step in any serious development model. Even if you work with the best team, they're humans, and humans makes a lot of mistakes. Each bug you let pass to the next step in development will cost you about 10 times more to solve. Also, seniors are vulnerable to self confidence, they can make the same unnoticeable mistake for years thinking it is right or is the only way to do it. I apply extensive reviews with my team, as it helps not only to catch bugs ASAP, but also to spread knowledge among us, improving the learning curve for everyone.
May 30, 2012 at 16:41 comment added Tiago Cardoso I do agree that a review (in this case) is a must to avoid issues down the road... the problem is the overload it causes in the team. Let's think of a process of washing a car. If you have a newbie around, of course a review will be required to advise what went wrong. The problem is that after 6 months you're still putting a more seasoned guy to review such a simple thing. Better to drop off the newbie and keep the senior doing it by itself (which is a less waste of effort, but still waste).
May 30, 2012 at 15:10 history answered eMgz CC BY-SA 3.0