Comments for Wille Faler's Buzzword Bingo

Comment on If you need a build team, your build is too complex by Wille

Wille — Fri, 25 Jul 2008 11:46:03 +0000

I take your point to quite a large extent - especially if you have a large project that is split into sub projects that need to be integrated at some point.

However, what I am questioning is the need for it to be an explicit “team” or part of the project, I believe that developers should be disciplined enough to integrate things smoothly on their own (I know that is not always the case though..). I can see though that there is nothing wrong with having “build specialists” in a dev/maintenance team that are more specialized in installing, setting things up etc. Having different competencies in a team is very important, or you risk getting a “mono culture” that is very liable to not seeing mistakes and problems.

I’d say that most of the time, the “need” for a build team very much highlights the shortcomings and mistakes of a team of developers, not the other way around.

Comment on If you need a build team, your build is too complex by Åsa Berggren

Åsa Berggren — Fri, 25 Jul 2008 11:37:31 +0000

hi. I really don’t agree that you don’t need a build team. I agree that you should have a buildtool or buildscript that makes sure that the build is easy to perform but the build team is needed anyway. The main task of the build team should be to make sure that the developers are working according to the process and that code that is sent to integration don’t sabotage the code base. It is also very good to have a team very close to the build team that optimizes the compiler and buildscripts so that the time to build the code doesn’t take too long. Both the developers and the build team will benefit of this. What I do agree with is that a build team that is working a very long time to integrate the code recived from the developers is not a very good thing. The developers should make sure that their code works with the code base so that the integration will be easy.

Comment on Windows Vista is a useless pile of s**t by Ken Buck

Ken Buck — Wed, 23 Jul 2008 12:00:38 +0000

Need help with Linux, go to my website. It’s not complete yet, but there may be some info of use to you. http://convertingtolinux.com/

Comment on Most pointless code snippet I have ever seen by Wille

Wille — Wed, 16 Jul 2008 14:16:06 +0000

“Foo” was actually a class that resided in the same package as the shown code snippet.

Even so, I think if you _know_ what implementation class you are looking for when you are writing the code, it should be supplied during compile/build time, if only as a “provided”-type dependency in Maven (or whatever build tool is used).

Comment on Most pointless code snippet I have ever seen by Jon Mann

Jon Mann — Wed, 16 Jul 2008 14:08:06 +0000

> The original code at the top instantiates a specific class, invokes a specific method through reflection, all of it hardcoded, why oh why would anyone ever want to do that?

One possibility is that “Foo” is an optional plugin (possibly provided by a 3rd party), which is not available at compile time (and so cannot be imported).

If “Foo” is supplied (at runtime), the original code will load it and execute “setBar”, which will presumably do something useful. If “Foo” is not supplied (at runtime), then an error message is logged.

Without the full context of the example, it’s difficult to say if that is the intention.

Comment on iMac - first impressions from a recent convert by thezerox

thezerox — Sat, 12 Jul 2008 06:22:47 +0000

And there is also Quicksilver, which is a good replacement for Spotlight.

Comment on Saying that using a standard is “less risk” doesn’t make it so by Magnus Persson

Magnus Persson — Wed, 09 Jul 2008 22:25:53 +0000

Less risk = less risk of fucking up in a way no one else does. If you do the same mistake as everybody else, it is in other words excusable, because at least you won’t be worse off than the rest…

Comment on iMac - first impressions from a recent convert by Magnus Persson

Magnus Persson — Wed, 09 Jul 2008 13:46:47 +0000

Oh, and the green button on the top of the window is not a maximizing button, it’s a “zoom” button. I don’t fully agree with the concept either, it’s supposed to find an “optimal” window size, but for me it quite often chooses something which is probably optimal, but not for me. I’ve learnt to live with that. At least OS X remembers which size windows I used last time, so I don’t have to resize them every time I start them…

Comment on iMac - first impressions from a recent convert by christopher

christopher — Sat, 05 Jul 2008 20:03:00 +0000

Also, there are several free programs that let you mess with your dock settings, allowing you to customize the appearance (including the little white dots below active icons, making them more visible).

Welcome to the Mac community!

Comment on iMac - first impressions from a recent convert by Wille

Wille — Sat, 05 Jul 2008 18:11:48 +0000

Didn’t actually notice that before you made me aware of it. Thanks!