As developers we come across the problem of accessing the same site with two or more different logins every so often. Problem is that if you are using Firefox the session cookies are shared across all running browsers. This means that you either run different browser applications or keep deleting session cookies and keep logging in, not really ideal.

Microsoft Internet Explorer, the one browser that can really spoil it for a front-end developer. This post is not about why IE is such a burden, but more about a potential way to lessen the weight it puts on every project. It is a shame that time has to be invested in finding workarounds and fixes for that single browser that really doesn't care about standards.

I found myself having to reinstall a server with no CD drive available. I had an old USB stick (256MB) lying around so I thought it would be nice to use that as an installer. Here's how I did it.

I was looking a long time on how to set the prefix for a namespace when marshalling an object to xml using JAXB. If you don't do anything JAXB will write random namespace prefixes (like ns2, ns3).

How do you configure a RAID drive with over 2TB? The usual way with fdisk didn't work. It turns out you need to use parted and give it a GPT disk label.

Find the memory leaks in your app with Eclipse Memory Analyzer ( MAT ). This Eclipse plugin can give you a detailed view on object level of memory consumption in the JVM of your application.

When working on projects with multiple front-end developers, the perfect scenario would be to have every developer work on his own piece of the puzzle. To make this happen it is important to have a completed graphic design prior to commencing the front-end development stage. With a finished graphic design it is easier to identify the different pieces that will make up individual components.