Blog

Shooting yourself in the foot because of Hibernate A few years ago, one of my colleagues had some things to say about the use of hibernate in big software projects. “We should leave hibernate modelling to senior developers, because a lot of projects I have worked on have been ruined by inexperienced people writing DAOs.” At that time we were working on enhancing the performance of an application that was pestered with (N+1)[https://secure.

As one of my college professors used to say: I hate to come over as a “sage on a stage”, but over the last few months I have come to learn a whole lot of intangibles. Some advice that was given to me in the past by more experienced former colleagues has started to make a lot more sense, and I felt the need to write it down and share some of the realisations, advice, and experiences I have had.

You would probably not say this when you look at the state of my desk, but I enjoy working in a clean environment. For me, this translates into a desire to have a clean codebase. In a previous post I have talked about the redesign I am doing on my pet project “TraMBU”. Other that entire reworks of projects, I really enjoy the feeling of figuring out a clean way of implementing something.

Backstory A few years back, me and my then-girlfriend were toying with the idea of creating a tool that would help us get out shit together. It would be some sort of activity tracking and personal calendar mash-up that could be expanded to give suggestions on what to do if you had some time to spare. Not much later, I was promoted at my previous job into a more senior position.