Re: What is wrong with Ada?

[Ludovic Brenta <ludovic@ludovic-brenta.org>]

Pascal Obry writes:
> Thanks for your answers. But I was more thinking about being two people
> on a project not necessary two behind the screen at the same time. Code
> review can be done at any time with the right setup (sending mails for
> each check-in for example) it is possible to make code review as
> something "normal". Many developers seems to not like somebody looking
> at their code, if every piece of code is sent to a dev mailing-list it
> changes things, making code more visible by default.
>
> I do think that a single developer on a project is bad for the overall
> quality... I'm just looking for so data to backup this idea :)
>
> Well this has nothing to do with Ada, so I'm completely off topic, fell
> free to ignore :)

I agree wholeheartedly.  A few years ago, I would start each day
reviewing my teammates' commits in the version control system, and I
also encouraged them to do likewise.  We caught many latent or actual
bugs even before testing that way.  Furthermore, it allowed us to know
the entire source base intimately, even on those parts we weren't
directly involved in.

Now I work in avionics and we have formal code reviews instead.  They
tend to take place after everything is written, and I miss the
closed-loop feedback I had with daily reviews.

-- 
Ludovic Brenta.