for years i was doing “superficial“[3] java albeit professionally and effectively.

By 2005 i already learnt something unknown to some experienced java guys. but my resume still lacked
– C: large-co-trec and
– S: software-tool-nlg incluidng open-source

Through experiments + several relatively small projects, i improved[1] on S

I also lacked so-called large-team-xp [T], as susheng put it.

In Verizon i gained some large-team-xp and some large-co-trec. More importantly i filled up countless gaps in my java/sql fundamentals [2]. Now I feel my blog is essential evidence.

In 2008, I feel competent in perl, vi, unix, autosys, sql, java fundamentals, ….

but perhaps the GS requirement feels a little too high in junit, OO design, hibernate, IDE,

[1] somewhat superficial in eclipse, spring, hibernate, pl/sql, jms ….
[2] such as (not only) access modifiers, oo details, instantiation, threads, collections, mem mgmt ….
[3] perhaps no need to explain

[T] CVS
[T] large build. No need to explain what’s large.
[T] integration test, as “checkout”
[T] regression test, as in Verizon
[T] load/stress test, as in Verizon