Skip to main content

Vaadin meetup

I attended Vaadin meetup with a few colleagues on a way to JFokus 2013 and thought I should share my notes of the two. First post is about vaadin meetup that took place on a cruise from Turku to Stockholm.

I made notes of three presentations and one of them I had high expectations. There were also two other presentations that I didn't make any notes of.

Vaadin 7


Vaadin released Vaadin 7 framework the same day that the meetup was on so they had a presentation where they told about new features and future plans. I'm more of a backend programmer than UI programmer so my notes of this were pretty brief but here it goes.

Whats new

  • Servlets and HTTP-sessions are controllable by the programmer
  • Multiple UI classes
    • e.g. One for web browsers and one for mobile web browsers
  • GWT is now build-in
  • Support for external JavaScript modules

What to expect in the future

  • Faster relase cycles
    • maintenance release every two weeks
  • Dynamic CSS injection
  • Vaadin CDI, their own depency injection system
  • Vaadin charts, for drawing nice charts

ePalo


This was a project ordered by Helsinki university and it was developed by a company called Arcusys. It's some sort of feedback system. The interesting part of this presentation was why they chose Vaadin framework for the UI. They chose it because it could programmed with Java or Scala and the developers didn't need to have any knowledge of web technologies like HTML, CSS or JavaScript.

Modern software development anti-patterns


Martijn Verburg, Diabolocal developer, had a presentation of software development anti-patterns. This the presentation that I really wanted hear he also had the same presentation later at JFokus. I had high hopes for this presentation and it didn't let me down. I'm just going to write a few buzzwords and notes here and the rest is available on Martijns slides and video filmed at the meetup.
  • Mortage-driven development
    • Write code to pay your mortage and make sure anyone else can't understand your code
  • Distracted by shine
    • Always use the latest and greatest
  • The deity
    • Huge classes e.g. Java class with 140k lines
Those were anti-patterns but he also gave tips how to avoid anti-patterns. 

One of the things he said is something in my opinion every developer should understand and remember. The anti-pattern was CV++ meaning that you try all the new frameworks and tools just so you can put a new line in your CV when instead you should be good at the principles.

So what does that mean. It means know the principles of software developent because languages, frameworks and tools change and evolve all the time but if you know hte principles you can always learn a new language or learn howto use a framework you haven't used before.

All the presentations of Vaadin meetup were filmed and uploaded to youtube. Links can be found at Vaadin meetup website https://vaadin.com/meetup/jfokus-2013.

On the next two posts I'll be what I learned in JFokus 2013.

Labels:

Popular posts from this blog

Simple code: Naming things

There are two hard things in programming and naming is one them. If you don't believe me ask Martin Fowler https://www.martinfowler.com/bliki/TwoHardThings.html . In this post I'll be covering some general conventions for naming things to improve readability and understandabilty of the code. There are lots of things that need a name in programming. Starting from higher abstractions to lower we need to name a project, API or library, we probably need to name the source code repository, when we get to the code we need to name our modules or packages, we give names to classes, objects, interfaces and in those we name our functions or methods and within those we name our variables. Overall a lot of things to name. TLDR; Basic rule There's a single basic convention to follow to achiveve better, more descriptive naming of things. Give it a meaningful name i.e. don't use shorthands like gen or single letter variables like a, x, z instead tell what it represents, what it does...
Read more

Sharing to help myself

It's been a while since my last post but I have a good excuse. I've been in a new customer project (well new for me) for two months now and have absorbed a lot of new information on the technology stack and the project itself. This time I'll be sharing a short post about sharing code and how it can help the one who's sharing the code. I'll be giving a real life example of how it happened to me. My story Back when I was implementing first version of my simple-todo REST-service I used Scala and Play framework for the service and specs2 for testing the implementation. Since then I've done a few other implementations of the service but I've continued to use specs2 as a testing framework. I wrote about my implementation and shared the post through various services and as a result someone forked my work and gave me some pointers on how I could improve my tests. That someone was Eric Torreborre  the man behind specs2 framework. I didn't take his ref...
Read more

Simple code: Immutability

Immutability is a special thing that in my mind deserves a short explanation and praise. If you're familiar with functional programming you surely recognice the concept of immutability because it's a key ingredient of the paradigm. In the world of object oriented programming it's not as used and as easy to use approach but there are ways to incorporate immutability to parts of the code and I strongly suggest you to do so. Quick intro to immutablity The basic idea of immutability is unchangeable data.  Lets take a example. We have a need to modify a object's property but because the object is immutable we can't just change value but instead we make a copy of the object and while making the copy we provide the new value for the copy. In code it looks something like this. val pencil = Product(name = "Pencil", category = "Office supply") val blackMarker = pencil.copy(name = "Black marker") The same idea can be applied in functions and metho...
Read more