env.properties

Seriously, the world is being overrun by huge companies. We need more skilled freelance programmers to help put them in their place.

There was a time I also have been writing a very concise code. But one time I have stumbled upon very well-written framework which used a lot of whitespace. My first impression was similar to yours - I was repelled by it. But when I looked at it in more detail, I have been amazed by how easier it was to comprehend the code when it was organized in semantic blocks separated by whitespace.

And when it comes to enforcing conventions - you still have to check the code for compliance. Anyway, thanks for the comment :)

My two cents, stick with the sun convention or if you’re a eclipse user (ctrl+shift+f)

..and as for your big company consultants, provide them with your conventions and ask them to stick to it :)

And remember your EJBs still have to implement interfaces in EJB 3.0.

You can also try adding a mappedName to your Stateless annotation to be 100% sure you’re using a correct name.

Glad to have you here, kato. And thanks for words of encouragement.

Have to say it starts really interesting. Well, maybe not in terms of geeky php tips & tricks (as I’m nowhere near working with PHP) but I can see your almost cognitive approach to every-day problems of a programmer; I find it interesting in both personal and professional way.

Bookmarked. (not a RSS fan)

Otherwise, take a second look at my first point.

Good interviews do a quick test whether you are able to think in an abstract way. Pen and paper are just as good for that as a computer is. The whole idea is that it’s the *thought process* that counts, NOT the actual details.

So, while giving a candidate a computer with an IDE might seem more natural, it also distracts. The candidate will try to actually write 100% correct code, which is typically beyond the purpose of an interview test.

Happy coding.

I remember back when I was in high school and had limited access to the computer, I was writing code in my notepad, so that I could test and debug it during the “off the lab” time. But those days are long gone.

Anyways, I’m not advising not to use it - I’m against it when readability suffers. And when readability matters at the same time.

Gil, I know and subscribed to your blog, actually. Found it when I stumbled upon your “ZF is loosing a war” blog post :)

1. Object type at hand when using well designed IDE
2. An error while compiling

I’ll start with the latter since it’s easier - you don’t compile when you’re reading the code while looking for a bug, for example. I agree it errors out but it does so when it’s not really desired.

Now, when it comes to IDEs, I see your point but hovering over a variable and waiting for a pop-up to emerge has it’s own price - you’re distracted. You read the code and then you have to stop, look for the information to show, read some text outside the code, then go back to what you were doing, focus again and finally go on. That’s a lot to do.

Next thing is, you have a great IDE. I’m happy for you. But what about those times you’re helping somebody else who doesn’t have your IDE or uses something completely different? Or when you read the code on the deployed application or in version control? It happens all the time.

I think you understand “readable” as “less cluttered”. And I agree with that if that’s the case. But when it comes to comprehending the code, it’s not always the case. And that was my original point.

Anyways, thank you for your comment.

Just my two cents, to me fluent interfaces are more readable.

Here’s mine ;)
http://coding-aloud.blogspot.com