@rickss euhhh you should be designing banners instead in reply to rickss #

Powered by Twitter Tools.

finally found the magic keywords that make us appear first in google http://screencast.com/t/xyZxF0cCF9m #

Powered by Twitter Tools.

Powered by Twitter Tools.

At the office however we are of course using PC’s and so I had bought the S510 (1 week after the S510M) version of the Fujitsu ScanSnap, but I must say I never really used it because I have not found a viable equivalent of DevonThink. It was also a nightmare since you had to wait for a “scan” to be completed (physical scan+PDF+OCR) before you could scan something else.
 
But now that I made “the switch“, I could finally install DevonThink on mac and go paperless at the office !

The only issue was that the ScanSnap S510 is for PC only and is not supposed to be used with a Mac. But after searching on the internet I found this nice article explaining how to get it to work anyway.

Here are the steps summarized :

1. Download ScanSnap_V21L20.dmg from the Fujitsu Japanese website (Japanese version)
2. Download ScanSnap_V21L11.dmg from this link (English version)
3. Install Japanese package completely
4. Explore contents of English package and replace the language resources as mentionned in this article
5. Restart ScanSnap Manager and it will be in english

Now you can choose to install the software of your choice. If you need OCR, nothing rivals DevonThink Pro. If you don’t need OCR and prefer plain tagging, you can try Yep! or something alike.

Pierre

—John Gall

seen on Signal vs. Noise

And I must say that I am still amazed at how things just work. Here is my setup :

Hardware :

Macbook Pro 15” 4Gb Ram, 320Gb HD 7200 rpm

Software installed :

1. PathFinder as file browser
2. IntelliJ as Java IDE
3. Skitch
4. Things (synced with iPhone)
5. Adium (IM)
6. Firefox
7. Smultron (Text editor)
8. SugarSync (sync files betweek multiple laptops)
9. Parallels (to run windows, see more below)
10. Text Expander (this is a must have ..)
11. Witch (faster app switcher)

Specific challenges

I need to be able to run Oracle. After a quick search I decided that I would run it under parallels since the same customer I need Oracle for, also requires me to connect to their network using a specific Connectra client which does not work for Leopard (yet?).

I first installed a bootcamp partition, but quicky switched to a complete virtual disk since I can’t “pause” the bootcamp partition under parallels and I don’t see why I would need to boot natively in windows.

That was basically the only challenge. Everything else works like a charm.

Printers were detected automatically, windows shares are already there. VPN (PPTP) connection is the matter of entering host / username / password ..

Never got that to work as fast in windows ..

To do

Learn to use Quicksilver. It seems and feels productive but the learning curve looks a little steep to me.
Get all my iPhone synchronisation in place (contacts, calendar, iTunes, …)

Pierre

Maybe it’s just me, but for the past 3 years now I have not come across one single developer that grasps half of the concepts needed to understand how Hibernate works. They use it and don’t understand it.

This is a trend I have been witnessing more and more. Developers pick a technology because it is the hype of the moment, start to use it, get a hard time to get it to do what they want, but keep using it and advocate it. Probably because they don’t want to admit to the world they don’t understand it.

This is in my opinion what makes Hibernate (and the like) so popular.

To illustrate my point, we were just contracted by one of our customers to take over the maintenance of a codebase written by another company.

I will make no comment on the code itself, since I tend not to judge code written by others since code is always written in a specific “context” and, in my opinion, can not be judged without knowing that context.

The main complaint of the customer was that the application was getting slow. He had to wait from 5 minutes to 15 minutes to get one specific screen to dispay (I am not exagerating).

So we started  a code analysis and had the chance to witness exactly what I was mentioning above. All the code was written exactly as if practice existed in “theory”.

The application had a magnificent (ironic) data model with 50 tables (entirely generated by Hibernate). An object graph sometimes 5 or 6 level deep.

While looking at it, I could hear the developer say on day 1 : Wouaw, this is so cool … I can do getEmployee().getDepartment().getRegion().getXXXX().getYYY().add(new ZZZ()) .. and it all works ..

And then the nightmare begins : lazy loading, hibernate session (open session in view issues), object identity, HQL, slow queries, etc ..

And so the developer (which never abandons) tries to “understand” by finding workarounds, tricks, breaks his architecture and does everything that is needed to make this nightmare work.

And so in day 15 (or 200 depending on the company you work for) : the code works (or seems to work) and nobody can touch it anymore because nobody understands it (except of course the main developer).

In our case, in production with real data (1.000.000 records or so – which is not even that big) the application is “curiously” verrrrrry slow ..

Just turning on the “show sql” in hibernate generated 3 Mb logs on every click …

The conclusion here is that, in my opinion, it is not a good idea to try to “hide” your database behind a “magic” object model. Even if Hibernate does its best to achieve just that, I think the challenge is not worth it .. The database will always pop back on you .. So embrace it ..

So we decided to remove the Hibernate layer and replaced it with IBatis. Hopefully the code was well structured and we were able to replace the Hibernate DAO layer by and equivalent (somewhat adapted) IBatis layer but not touching the above service layers.

When we choose a technology, we usually expect the following :

• It should pass the 10 minute test
• The learning curve should not be too steep
• It should serve a specific purpose and serve it well
• The technology should be understandable by a junior developer after 30 min introduction

Pierre

Note: we don’t hire college graduates (they are too expensive) but developers who took 3 years of IT courses (called graduate school here in Belgium).

When they start at TELIO, we usually assign them with a simple and well defined project just mentionning the technologies they have to use. For the rest they are free to use and do things the way they want to.

This allows us to evaluate their strong and weak points and see how to do things and specifically how they react to a technical stack they don’t know.

Well, it’s a great experience but sometimes a sad one …

Here are some thing they don’t know :

Theory

• They have a very vague view of network protocols that basically run the world today (TCP/IP, DNS, HTTP, SMT, etc ..)
• They never heard of the word “socket” except at the store by two size 42 ..
• They don’t clearly understand what a server / client model is
• They have absolutely no understanding on how HTTP works and more generally what happens “behind the scenes” when you click on a link in a web page.

Practice

• They have never used (or sometimes even heard) of Ant
• They have never used (or sometimes even heard) of a version control system.
• They rename classes by hand and don’t use “refactoring” that is supported by their favorite IDE.
• If you ask them to work outside their favorite IDE they are completely lost.
• They rarely have the reflex to “google” for something, they prefer trial and error ..
• Debugging = System.out .. they have never used a debugger (even inside the IDE) so don’t even think about attaching to a remote JVM.

Now based on that my question is : What the h… do they learn in school during these 3 years.

Here is a list of things they know :

• Run tomcat inside the IDE – but have no clue that it can run as a standalone application. Sometimes they even think it’s part of NetBeans, Eclipse etc ..
• The “theory” of object orientation, forget about practice.
• They “know” hibernate .. at least they think they do .. I personnaly don’t understand how you could honestly say you “understand” hibernate when you don’t know what ORM stands for or have a basic understanding of databases.
• They “know” struts 2 (or 1) and they love using the word MVC and always try to figure out if what they are coding fits the MVC definition (or what they remember of it)

The list goes on and on. Now they are not to blame (their teachers are) but this does not reassure me on the quality of the IT resources coming out of our education system.

In about 2 weeks however we try to get them going.

The most important thing for them is to :

1. Admit (even if it’s sometimes hard) that they did not learn anything in school
2. Realize that they are capable of learning anything they want if they trade “using” against “understanding” ..

Computer science is about fundamentals and basics. If you get the basics you can grasp almost anything. And the basics are simple, so computer science is simple.

But all these juniors seem afraid of looking under the hood, not because they were told not to, just because they were told they would not be capable of understanding what they would find.

That’s a shame.

1. 34 Mb dependencies (cocoon project – lot of XML stuff
2. 30 Mb dependencies (using web services .. )
3. 6 Mb (basic web based project)

Now, considering that a JDK weighs 33Mb (rt.jar) my question is : what is really in the JDK ?
P.