My BedCon 2013 talk. Covering commiting code, packaging,testing, deployment and organisational changes.

Javadoc is here to help. To understand what the code does and how it works? Right?

I don’t think so. I confuses the heck out of me in most cases.

I’m a Java Programmer. I do mostly web projects. There is a tendency to move away from server side frameworks towards Javascript (+mvc) and rest services. This now involves me in programming Javascript at the GUI level. Welcome maven, IDE and continous integration.

Octopress. Now.

I got tired of Wordpress and choose to get something different. Octopress. First, I like markdown and I want to become a little more fluent. Second, publishing is only a commit away. Plain html files, no php. Hosting everywhere. I can start to learn ruby. Can I ask for more?

Expect some hickups in the next days. I still need to see how the whole disqus things works out.

In an earlier article I compared cucumber (with Cuke4Duke) and Concordion. It was very cumbersome due to the ruby/jruby jvm chain. Behold - the new cucumber-jvm was released. So how did it improve ?

Cucumber-jvm has support for many languages, e.g. Scala, Groovy, Closure and of course Java. I will focus on Java and Maven.

Recently I was debugging my code and I could not see why my test was failing. It took me about 20 minutes to see that I violated one rule I try to follow. One assert per test.

After tweeting it I got some reaction ranging from ‘this is a very silly guideline’ to ‘Tests should test one thing. Often one assertion, but not always.’. I, of course, tend to agree the latter one.

So what’s in for you when you use one assert per test? What are the problems?

My former hoster had a system crash and it took a while to get an older backup working. Some posts are lost.

Here I am.

Thanks for the patience.

Things still might be a little messy but I’m working on it.

I’m playing around with some web frameworks lately and to see what’s in store with Spring 3 MVC (never did too much with it) I gave it a try to see how it handles Ajax. According to ajax simplification announcement it should be possible to get up and running in (almost) no time.

Every Programmer needs to read books. Usually you would get some packages from Amazon (or your favorite retailer) and read through them. Now with devices like the Kindle and iPad (and Nook and…) things will change. No more carrying around a couple of hundred pages of paper. Only some Megabytes on Gigabytes of storage. The displays nowadays are good enough and the battery is not a problem for the most part.

Now the tricky part, you want your books in a format which you can read on many devices. The obvious candidates are:

If you developed an ajax rich web application, maybe even a single page interface, you want to make sure that the user gets notified if the server is not reachable anymore. This happens either if the it goes down or the client loses its network connection. Depending on your code the application can run for a while and the user is confused about missing interactivity.

So how do you detect this? jQuery offers an error callback if something with the call goes wrong.