We are in a steep ride, jumping quickly from a start-up to becoming part of BEA and
now of Oracle. I hope we can keep the “small-company” atmosphere here in our division.
Watch this video demonstrating some cool algorithms for resizing and cropping images. They analyse the content of the image and try to remove/add/stretch/shrink only those areas of the image that are less relevant.
A couple of smart friends of mine are strong advocates of mind maps, so much in fact that they had nothing better to do than develop http://wisemapping.com. It’s a pretty impressive online mind-mapping tool with everything you’d expect these days from a web two-oh application: rich UI, collaboration, tagging, sharing.
Here’s my first try, presenting the basic ideas behind DITA:
It’s still a private beta, with many more features coming.
In March, I accepted a new position within BEA, to work for BEA Argentina.
After more than six years in the U.S., my wife and I were thinking about moving back to
Argentina. We were talking about doing so in 2008. Then, this opportunity
within BEA came across. It was sooner than what we planned, but it was interesting
for me professionally, and BEA was helping with all the relocation needs. So I accepted.
It all happened (is happening I’d say) pretty quickly. Me and my family arrived at
Argentina a couple of weeks ago, and I started on this new role immediately.
April was a good exercise on getting things done, both in and out of work. Here’s just
a summary:
I found myself in the need to invoke a private method of a Java
class that was out of my control. I really needed it.
So, I went ahead and violated the method’s privacy declaration via
reflection. You can (under certain circumstances) invoke methods which
are declared as private using the Reflection APIs (java.lang.reflect).
But before using reflection, I created two classes:
class A {
public String method1() {
return "Hello World!";
}
}
class B {
public static void main(String[] args) {
A a = new A();
System.out.println(a.method1());
}
}
They compiled, and java B said “Hello World!” as expected.
Then, I made A’s method private and recompiled A. And I run java B again. Nothing changed. It just worked again.
That cannot be right. This would mean you can handcraft a class with the
same name and methods as the original one but making everything
public. Then you could use this class only at compilation time,
allowing your code to call any method. (Or, one could modify
the Java compiler to ignore access declarations altogether).