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.

Comments

Popular posts from this blog

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

Simple code: Contracts

Code works around contracts and contracts should be carefully thought and crafted. What are contracts A High abstraction level of contracts for code are API's. They define a interface that is basically a contract that the producer and consumer of the API agree to use to communicate with each other. Two common forms of API's are libraries that are used in code and external API's  that are used via HTTP, RPC etc. When thinking in a bit deeper contracts consist firstly of functions, methods or external endpoints and secondly of data, more precisely on data models and data types within the models.   Defining contracts Contracts should always be defined with careful thought. I've come accross few times to someone saying that "this is for intenal use only so it doesn't need to defined and/or documented as thoughtfully as a public API would be" but I disagree with that. The same care should be be given to internal and external contracts because the contracts are

Simple code: Functions and methods

What makes a good function or method? I don't think it's a single thing but a combination of things where each is significant. If one the things is flawed it affects to all others and the whole function is flawed. So what are those "things"? Have a meaningful name Function should have a name that describes it's purpose or functionality. When a function has a meaningful name it's easy to read and understand what's it's purpose. Let's take a example. If function's purpose is to find a customer by it's id a good name could be findCustomerById(id: String) or it could just as well be just  findCustomer(id: String) because the function signature implies that the customer is found by it's id the word find also implies that the customer might be found or it might not be found. If the function's name would be changed to getCustomer(id: String) it's meaning changes because now it implies that there's no fallback, the customer is e