Tag Archives: java posse

Scala First Impressions

Somewhere in the last few months,  I decided to learn Scala. And master it. There are several reasons to do this, but a couple of them is enough for me:

  • The desire to learn something new, different. Java is nice, I love it. But I want to learn new ways to do things; I want to open my mind to new ideas and possibilities;
  • The urge to be more productive, to be able to spend more time on what matters, and less on boilerplate code. Ruby on Rails is one big inspiration here, but I want something more focused on the Java platform.

So, after discovering about the existence of Scala through one of the Java Posse episodes, this was the language I decided is going to be my next big step in terms of software development.

I still have a LOT to learn. I am just a baby when it comes to Scala. But a few things already hit me. One of those is that Scala source code may seem alien at first. For example, instead of declaring variables like this:

Integer count = 10;

you would do this:

val count: Int = 10

There are a few interesting things about this code:

  • semi-colons are optional;
  • the type definition comes after the variable name, instead of before;
  • the type definition is optional in this case: you know 10 is an integer, right? The Scala compiler knows that as well.

I’ll be posting more about Scala as my learning progresses, so stay tuned! Any expectations? Leave a comment!


OSGi and Modularization

I just finished listening to the episode 245 of the Java Posse podcast, about OSGi.

The Java Posse is one of my preferred podcasts out there. In this episode, they feature an interview with Peter Kriens and B.J. Hargrave, two men who seems to be involved a lot (full time?) in the development of OSGi. If you are like I was up to an hour ago, you know almost nothing about it, and maybe even find OSGi a little bit alien. If that is the case, you must listen to this.

Modularization is something that the core Java platform is really lacking right now, and OSGi seems to help covering this gap. After listening to the podcast, I now plan to take a deeper look into it, when I find the time. In the interview, they even discuss the JSR 294, which is supposed to bring modularization to Java 7 (god knows when…)

Now, if you don’t know why the issue of modularization is important, its because you haven’t messed with projects with lots of sources files and packages yet. If that’s the case, bookmark this post and come back later, when you discover you need it – or be pro-active and start to get ready for the problem now!


The Onslaught of the Tools

Before starting, please be warned: this is more like a philosophical post than anything else. I might say something in a sentence and then negate it in the next one. If you are ok with that, have fun reading on!

Nowadays, there are tons of tools out there to help us in our job developing software. This is amazing. And yet it is terrible. It is amazing because it gives you choice. You can find something that really matches your requirements. Also, you are likely to find tools to solve almost any problem you find; sometimes several tools solving the very same problem – most of the time probably. Great!

Or not. Now you have to study and compare them all. And of course you have a LOT of free time to do this. Unless you work. And have schedules. And need to deliver results. And if you are like me, you will WANT to know every option you have prior to choosing one.

Tools!?!?

Tools!?!?

I constantly find myself frustrated, knowing that there is a better way to solve problems we are facing right now. Yet, we can’t afford the time to reach those ways. But there is the other side of this coin. Maybe you don’t NEED that better way, that better tool. You are in heaven now.

This is a discussion that came about a few times not too long ago in the Java Posse podcast. And I basically agree with their conclusions. Is it good or bad to have so many options, like we do in Java? It’s good, because you have choice, which is probably one of the most important thing you can have. And if you don’t want to afford the time to choose, you can hire a company like Sun to help you, or do this for you.

Maybe the only time where the great amount of options are bad is when your are starting the learning process. There are so many places to go that you might get a little bit lost. At first at least.

So, concluding. I do like to have options. I don’t mind spending hours studying different choices for solving a problem. Actually, I think this makes me better, it makes me stronger and wiser. Let’s hope I’m not wrong and that I don’t die with an overdosis of information!


Follow

Get every new post delivered to your Inbox.