Google Docs is a great tool store and edit documents online. MS-Office is a pretty good tool as well. Wouldn't it be nice if you could open documents stored at Google Doc using MS-Office. Of course MS-Office has something similar, MS Office Live, but that's still beta and I'm more used to Google Docs. However, since recently, Google Docs integration is possible, using OffiSync!
OfficeSync is a plugin for MS-Office. After installation, you'll get an extra menu.
Using the menu, you can open and save documents at Google Docs, in a similar fashion when you'd use MS Office Live or Sharepoint. OffiSync is free to use, but when you use the free tool, any MS Office feature that isn't supported by Google doc is lost when you save you're files at Google Docs. The paid version doesn't have this disadvantage.
I develop software for a living. This involves quite a lot of talking, coaching, attending meetings, drinking coffee, etc. but the actual work is done during programming - when the software is created. That programming involves repeated cycles of the following: modify or type some code, compile, deploy and then run the code and perform some tests to see if it works. How cumbersome that process was ranged from:
- Hitting 'Run' and waiting a few seconds,
- to hitting 'Run and deploy' in my IDE and waiting about 20-30 seconds,
- to executing a ant script, restarting the application server and waiting 5 minutes
- to compiling a class file, uploading the class and accompanied libraries using a cumbersome webinterface and then executing a PLSQL script to run that class, wasting in total time amount 15 minutes (yes, that was a a very big and professional company)
In my opinion, the programmer is productive when he either codes, or when he tests his codes. Any time spent on waiting or performing some troublesome actions like accessing a web interface is pure waste. In short the above time ranging from a few seconds to 15 minutes is dead time.
Of course all that time wasted not only frustrates developers, it'll cost quite some time and thus money. Now how can you limit that dead time, that is wasted by developers? One way is your have your developers write perfect code at once. Of course that's not very realistic. Recently I found a very nice tool to limit that dead time, when you develop Java software: JRebel. What does that mean for you as java-developer:
JRebel runs as a software agent within your virtual machine, that in turn runs your application server. What JRebel does, is taking over the class-loader.
You can specify the output directories of your IDE (target/classes, /bin, etc.). Now whenever you make a change in your code, IDE's like Eclipse can compile that code into a new class file in the output directory. JRebel will automatically detect the changed class file. Thus no waste! Since JRebel plugs into the VM, it'll work with virtually any application server.
subscribe via RSS