Quality is a hard concept to get across. People who experienced its lack have learned to appreciate its presence. It is generally only noticed when missing, or when contrasted with its opposite.
With the arrival of HTML 5 (which commonly means more than just HTML), web development has become even more of a joy that it used to be. Clean semantics in HTML, elegance through CSS, new scripting possibilities, it’s all there. This blog post describes two new features, offline applications and name/value storage, which allow developers to make web applications available offline.
The past years, we’ve seen two new terms become popular: REST (REpresentational State Transfer) and DDD (Domain Driven Design). However, where DDD is often used to prevent an Anemic Domain (now considered an anti-pattern), a domain model for REST is often anemic. This blog post explains how we can reconcile these opposites.
After spending a couple of days looking into multi- product and version testing I came across two techniques which are very useful, so allow me to safe you the two days and point you into the right direction :-)
“Do not optimize prematurely”. A sentence that is worthy of hanging all gilded and framed on any software professional’s wall. Living up to its hallowed words has made our software more robust and easier to understand, therefore better and cheaper to maintain and operate. However, the credo has a nefarious side-effect that needs to be addressed.
On February 13th / 14th, 42 hosted a workshop aimed at teaching Java developers more about applications working with databases. The workshop was presented by Ron Smeets, our resident database guru. The topics ranged from RDBMS architecture, to DDL and touched on performance and scalability. Students hacked away at assignments in order to gain a deeper understanding of the subject material.
When starting a new project, its common to create an "Instant Developer Experience": a new developer can get started by issuing two commands: get the code, and build&run the application. The only things needed are Java, Maven and an IDE.
Doing this for a stack with Spring, Hibernate/JPA, HsqlDB and Jetty has become common knowledge. But using JavaEE 6, it has been somewhat problematic. The only sufficiently well working Maven plugin was by Oracle (an embedded GlassFish). But to configure an entire domain with HTTP listeners, EJB settings, etc. just to get a DataSource is of course plain silly at best &mdash it’s actually a pain from a systems point of view.
Until now. Read this short blog post to learn how an Instant Developer Experience is also possible with JavaEE 6.
Have you ever needed to simultaniously develop in several modules? Did those modules have their own trunk/tags/branches in subversion, their own release cycle, etc.? Did everything build with a single Maven command?
If the answer to the first two is yes, chances are that the anser to the third one is no. In this short blog-post I’ll demonstrate a simple remedy for this. As an added bonus, I’ll also show how one can easily set it up for new developers (i.e. with a single checkout command).
Recently we upgraded from Confluence 3.5 to 4.x and with that change came the loss of the wiki editor. Confluence 4.x only supports (for the best of reasons) a fancy rich editor.
Aside from the initial frustration that I had lost my most powerful writing tool I also had to do battle with some interesting features of this editor which to a novice user may seem totally illogical. Fortunately they aren’t.
In this article I will share my initial rich editor denial, discoveries and ultimately acceptance.
Last July Atlassian released one of it’s new products, Bonfire! Bonfire can capture issues in the browser, take screenshots and annotate, track testing activity, making Bonfire an awesome rapid testing tool for everyone on your team and organization.