Comments for Hadi Hariri's Blog

Comment on And when you call it, you can call it Util by Scott D. Strader

Scott D. Strader — Tue, 21 Feb 2012 18:13:20 +0000

StringUtils, XMLUtils, etc. are perfect containers for simple, reusable code. When and if any group of those contained methods merit a class of their own (e.g. XMLAccountTransform) then they should be refactored appropriately. The magical util class is a step in the process of developing a project and stops you from over-engineering at the outset.

Comment on And when you call it, you can call it Util by Olaf Monien

Olaf Monien — Mon, 20 Feb 2012 21:34:25 +0000

As long as I find recommendations in books (those about good programming practice) that say, that a longer method name is less easier to read than a short method name and thus recommend to keep names as short as possible (for readability!!), your dream will not come true

Comment on The Kotlin Journey Part I : Getting things set up by Nick Jones

Nick Jones — Mon, 20 Feb 2012 21:16:12 +0000

Thanks for pointing this out, I was doing the same thing.

Comment on And when you call it, you can call it Util by Sólo hay dos cosas complejas en computación « Blog de Francisco Velázquez

Sólo hay dos cosas complejas en computación « Blog de Francisco Velázquez — Mon, 20 Feb 2012 20:30:34 +0000

[...] la semana de esta cita, está por todos lados. En realación a esto, encontramos este artículo de Haidi Hariri, aunque no la llega a usar. En él recomienda no usar las siguientes palabras: Util, Service, [...]

Comment on And when you call it, you can call it Util by Erik

Erik — Mon, 20 Feb 2012 16:00:07 +0000

Yes, yes, yes! I fully agree about the importance of picking good names and the badness of calling something “utils” (or “helper” or “manager”). I’ve blogged about this in the past, but I’ll summarize quickly here. When classes are named this way, *anything* you put in them is categorically correct as long as it’s “useful” or “helpful”, which it will be, since the person writing it clearly has use for it.

Adopting these naming conventions is an “anything goes” advertisement that invites technical debt due to poor organization and dependency management.

Comment on The Kotlin Journey Part I : Getting things set up by hhariri

hhariri — Sun, 19 Feb 2012 19:34:31 +0000

Hey Ben,

Can I ask you to post the questions on the forums? That way the team can help and also use questions for basis of upcoming FAQs. The forums are here:

http://devnet.jetbrains.net/community/kotlin?view=discussions

Comment on The Kotlin Journey Part I : Getting things set up by Ben D

Ben D — Sun, 19 Feb 2012 18:05:54 +0000

Well, actually it does RUN fine from the IDE. How to I run it from the command line? Is there a simple way I can send just a simple .class file to a client site?

Comment on The Kotlin Journey Part I : Getting things set up by hhariri

hhariri — Sun, 19 Feb 2012 06:59:50 +0000

@Fabian,

You want to build the compiler from source? Cause that’s pointed out here: https://github.com/JetBrains/Kotlin in the README and the build.xml files is for doing so. But not sure if that’s what you want since you already mention the build.xml file…

Comment on The Kotlin Journey Part I : Getting things set up by Sandman

Sandman — Sun, 19 Feb 2012 02:41:55 +0000

Nevermind. Dumb move by me. I wasn’t installing the .zip file… instead, I had decompressed it and pointed right at the plugin jar.

Comment on The Kotlin Journey Part I : Getting things set up by Sandman

Sandman — Sun, 19 Feb 2012 02:34:38 +0000

Everything appears to work fine, but when I click ‘Setup Kotlin Runtime’, I get this message: “kotlin-runtime.jar is not found. Make sure plugin is properly installed”. I’ve followed your instructions closely.