May 14 saw the birth of a new technical conference in Budapest that I foresee a very good future. For a really affordable price we had two days of great talks in an outstanding venue, with good food and open bar after-parties.
The talks were paired in practical and theoretical with Q&A after each speaker and coffee-breaks in between each pair. So here I would like to highlight those talks that impressed me more or I consider most useful.
For the practical side there are two videos that I would make my team watch as soon as they are up.
On Thursday Sebastiano Armeli of Spotify spoke about Enforcing coding standards in a JS library; and although it might seem simplistic as something we should already know, by experience I know it’s not like that in every team and it’s good to be reminded. The use of editorconfig and code quality tools like JSHint; automated the build process with Gulp or Grunt; unit testing using Karma and Mocha; standards for the commit messages in order to generate the changelog; and Plato, a tool I have to try to check code complexity.
The first one to blow our minds was Martin Kleppe with his Invisible Code talk. I knew about JSFuck before but the things he can write in 140 characters, using 1024 bytes or not using Latin characters at all are extraordinary. You must check the jaw-dropping examples on his website.
These were just some of my favourite talks but all of them were of great quality and there are many more worthy to watch.
The announcement of io.js being merged back to node.js came on Thursday so it was interesting to watch Fedor Indutny on Friday answering “political questions” after his Diving into io.js C++ internals talk.
Stephan Bönnemann had a good point about versioning and described it in We fail to follow SemVer – and why it needn’t matter.
And the best possible end for the event was How you can fix your community in one day by Anika Lindtner talking about diversity and inclusion.
Definitely and as I said, a great conference in a beautiful city with a lot of interesting people. Congratulation to the JSConfBP team and see you next year!