final methods and classes
in [Java Programming]
|
From: Arne Vajhøj on 25 Oct 2009 21:37 Lew wrote: > Wojtek wrote: >>>> http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Timestamp.html >>>> which extends Date. > > Lew wrote: >>> Out of curiosity, why are you linking to out-of-date Javadocs? > > Arne Vajhøj wrote: >> Try Google on: >> jdbc timestamp >> and see what show up first. > > How will the popularity of old information change the fact that he > linked to out-of-date documents? It does not. But you asked about WHY. And I supplied a possible explanation. Arne
From: Arne Vajhøj on 26 Oct 2009 22:22 Andreas Leitgeb wrote: > Rzeźnik <marcin.rzeznicki(a)gmail.com> wrote: >> On 14 Paź, 19:06, Leif Roar Moldskred <le...(a)huldreheim.homelinux.org> >> wrote: >>> Alessio Stalla <alessiosta...(a)gmail.com> wrote: >>>> Documentation is sufficient to "signal". >>> To the typical software developer? Not in my experience. >> Who is a typical software developer? Someone who does not read docs? > > And even if so, why do you (Leif, Mike, etc) feel obliged to prevent him > from shooting his toes off? Not commenting on the specific context, but in general: If the company culture is "it does not matter if the project fail if you can prove it was not your fault", then there is no reason. But if the company culture is "the important thing is that the team/company succeed", then there is a reason. Arne
From: Arne Vajhøj on 26 Oct 2009 22:24 Rzeźnik wrote: > On 14 Paź, 19:37, Leif Roar Moldskred <le...(a)huldreheim.homelinux.org> > wrote: >> Andreas Leitgeb <a...(a)gamma.logic.tuwien.ac.at> wrote: >>> And even if so, why do you (Leif, Mike, etc) feel obliged to prevent him >>> from shooting his toes off? >> Because I'm a professional and I don't do shoddy work, and because I prefer >> working with clearly defined APIs myself, so that's what I try to make. > > That's deceptive to think that API is "clearer" because of extensive > use of finals, and if you believe that your work is less/more 'shoddy' > because of finals, you are lying to yourself. I agree. The "I really think language XYZ is better than language ABC, so when I code in ABC I try to make to code work like XYZ" line of thought usually just creates weird code. Arne
From: Andreas Leitgeb on 27 Oct 2009 06:53
Arne Vajhøj <arne(a)vajhoej.dk> wrote: >> And even if so, why do you (Leif, Mike, etc) feel obliged to prevent him >> from shooting his toes off? > If the company culture is "it does not matter if the project fail > if you can prove it was not your fault", then there is no reason. If you and the user of the API work on the same project, then I'd expect other channels of communication to be available, where the user could complain to you about an (in his eyes) wrong "final". You'd then discuss the matter and in the end either remove the final, or find a better way to solve the user's (actually colleague's) problem. Adding "final", where no discussion about it is possible, is like: "I know better - if you disagree, then you're ly^H^Hwrong." Some "final"s even *are* right, but for the *idly* added ones, chances are obviously less than 100% of being right. -- Oh gosh, and I thought that thread was already done. |