On Mon, May 02, 2005 at 09:10:00PM +0200, Marc Espie wrote:
> If you start running into conflicts, it usually means people don't commit
> often enough... and if they don't, it might be because intermediate code
> is not stable/does not compile, which bodes real bad for the project as
> a whole...
Or (to second your Java/eclipse rant on ports@) you've a bunch of
clueless people not only denying communication but even using
braindead eclipse features as "Override and Commit".
[I could shoot the guy who added this thing to eclipse]
Clear signs of urge of unemployment:
- Using graphical tools as in eclipse for CVS access (especially that
override-shit).
- Commits without reasonable log messages.
- Commits that contain two lines with semantical changes but that change
the complete file due to reformatting.
- Muttering as "that's *my* code" or "I can't work on code formatted
like this, so I reformat."
Sorry for being offtopic, but out there in the wildness of
enterprise/bullshitbingo/java/buzzword world, shit doesn't just
happen, but actually accumulates to infinite stupidity.
Ciao,
Kili, only clueless once a month
