Ide

One error that has bugged my Eclipse PDT for a long time, was \_org.eclipse.emf.ecore.util.EcoreEMap $DelegateEObjectContainmentEList. \_A vague error, not much to go on, not many hits on google either. Turned out it had to do with the version of my Java Runtime Environment I was using.

Hi folks. As you may or may not know, I have a [love/hate relationship with my IDE: Eclipse PDT](/blog/2008/04/11/my-new-ide-eclipse-pdt/). For times and times we get along well. But once every while it gets messed up, and it's a pain to straighten it out again. Or at least, it was.

Good testing will result in better code. If you have to wait endlessly for on SVN commits, uploads or compile steps, you will simply produce less inventive code. This has to do with: patience, creativity flow, will, and of course time. Constantly being interrupted breaks concentration. If there's one thing I've really learned, it's **invest in a good testing environment**. Rapid review of code results will pay off (I promise).

In another article I've told you about how I would like to see one rule removed from the PEAR Coding Standards. This rule would allow developers a bit more flexibility, while staying true to the convention.

Recently I've been experimenting with Virtual machines for my development environment. The goal was to create a Virtual Machine that resembles our main production server, and have that Virtual Machine mount my workspace project directory as its DocumentRoot. This way, my code could be served & tested after every save in my IDE. So no more building / committing delays. And all I could mess up was a Virtual Machine.