• Introduction to Unix and GNU/Linux
  
• Embedded Linux kernel and driver development
  
• Development tools for embedded Linux systems
  

• Java in embedded Linux systems
  
• What's new in Linux 2.6?
  
• Introduction to uClinux
  
• Real-time in embedded Linux systems
  

• Introduction to Unix and GNU/Linux
  
• Embedded Linux kernel and driver development
  
• Development tools for embedded Linux systems
  

• Java in embedded Linux systems
  
• What's new in Linux 2.6?
  
• Introduction to uClinux
  
• Real-time in embedded Linux systems
  

• apt-get to update my Suse distribution
  
• eclipse auto-update. Good for eclipse+GEF+EMF ... but still too many plugins don't provide install-URL and have to be "intalled" (extract in plugin directory) manually
  
• Java WebStart
  

• ALT-F2: I start most of my programms like this, auto-completion is nice too
  
• ALT-F2 4+9: calculator
  
• Konsole: switch between consoles in one window with ALT-left/right
  
• Konqueror shortcuts: "gg:keyword" will search in google
  
• Move windows with ALT-pressed. No need to search Window border
  
• virtual filesystem (kio-slaves): access any ressource indenpendent from it locations (see also gnome-vfs,commons-vfs...)
  
• kweather and knewsticker
  
• date is displayed in clock applet
  
• ALT-TAB displays icon+application name
  

• Code convention: important when you develop software in a team, use different IDE's or/and use a version control system. All IDE's support code convention templates, so use them.
  
• Testing: write as many test cases as you can and add them to your project. Use JUnit (http://www.junit.org/index.htm) and JUnit IDE support. Write tests before you start implementing (define how you app/procedure should work to find out what you need, and then write it).
  
• Comment your code: at least each class/method, but also inside method if ever you do something someone might not understand without your background
  
• Document your application: not only inside code, but also write documents (plain text preferred) which explain the architecture of your application. Store documentation with/near your application and in your version control system.
  
• Code review: do code reviews, use tools (see below)
  
• Code quality check: before or while code review use Java code analyzers. They will help identifying common coding errors (naming conventions, imports, modifiers, duplicate code, … see findbugs bug descriptions):
  
  
  
  • Findbugs: (eclipse plugin , JBuilder: ? )
    
  • Checkstyle: (Eclipse plugin , JBuilder PlugIn )
    
  
  
• Profiling: from time to time (at least before releases), do long time tests of your application in a Profiler. It will help you to identify bottlenecks and memory problems (Eclipse Profiler)
  
• Daily builds: helps to identifiy errors quick after they have been implemented (team) and fix them while developer still know what he did and not days or weeks later
  
• Debug: use debuggers to find errors instead of System.out-try-and-error
  

Decoder dec = new Decoder(pcapFile)

Packet first = dec.nextPacket();

Packet act;

Packet last;

while ( (act = dec.nextPacket() != null)

   last = act;

System.out.println(first.getProperty("timestamp"));

System.out.println(last.getProperty("timestamp"));

create table MYTABLE

(

    COLUMN1 VARCHAR2(200 char);

)

String value = ... ;

// only check above 1333

if ( (value != null) && (value.length() > 1333) )

{

   // get bytes of the string in UTF-8 format

   bytes []  utf8Bytes = value.getBytes("UTF-8") ;



   if (utf8Bytes.length > 4000)

   {

      // Get 4000 first bytes and ... 

      byte [] tempBytes = new byte[3999] ;

      System.arraycopy(utf8Bytes,0, tempBytes, 0,3999) ;

      // ... built String from UTF-8

      value = new String(tempBytes,"UTF-8") ;

}