I really wish I could rely on this but in practice it is very, very hard. Getting a large team to provide adequate Java Doc is an ongoing bane.
On the Reflection point though, from a developers perspective I would find very hard to take, and having fought against mad internal, inadequate API's and technology decisions driven from a level without real understanding, I would fight against this one tooth and nail had I been posed it. 2010/12/8 Cédric Beust ♔ <[email protected]> > > > On Tue, Dec 7, 2010 at 4:01 PM, Liam Knox <[email protected]> wrote: > >> So then you need to enforce Code reviews and Fing Bugs. >> > > You can also add "developer integrity" too. > > If you are asked not to use a certain tool as part of your work, it just > seems very natural to me not to use it and assume that not all the > developers on the payroll are idiots who will try to break the rules. > > And if one day, I come across a problem that absolutely, positively > requires this tool, I'll just make a case for it and hope that I'll be > heard. > > Simple work ethics, really. > > -- > Cédric > > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
