Oh, how the weather can change! Yesterday it was 28 degrees Celsius, sunny and we were sweating because of a broken airconditioning (which was fixed and compensated by free ice cream, just so you know). Today it was 16 degrees and raining constantly. Luckily the venue was dry and they had some great coffee!
These are the 6 talks I attended on the second day of Laracon, with a bonus surprise announcement at the end.
Eryn O'neil has been working for an agency for many years and has seen stuff fail, and she learned from it. Problems can be split up into project-problems and tech-problems. The Project-problems need empathy and good communication to understand each other and overcome any misunderstandings. The Tech-problems are best solved by making a plan up front, keeping calm and keeping checklists where appropriate.
Although for me she was putting too much emphasis on the developer-vs-human-being part, which I find very degrading, it was fun and informative talk. I'll definitely think about this when I hit my next Project-problem and I'll start preparing for my next Tech-problem.
Freek van der Herten, and his company Spatie, are celebrities in the Laravel ecosystem. Mainly because of their many open source packages, but also for their talks at Laracon.
In this presentation, Freek gave a walkthrough of their homemade dashboarding website for in the Spatie office. Laravel is used to retrieve all the bits of data that are displayed on the tiles of the dashboard. Pusher is used to setup a websocket connection and send updates over that connection. Vue.js is used to build the frontend tiles in the dashboard and update each tile as updates are coming in over the websocket connection.
Personally, I really liked the walk-through of the Vue.js components as I am not really familiar with Vue, yet. You should definitely check out Pusher if you don't know it already. They make it crazy simple to setup a real-time connection between your backend and frontend and it allows you to build some super cool stuff!
How to make my UI not look terrible? Shut up and take my money! :')
Laura Elizabeth is an independent designer that wants to teach developers how to make better looking UI's. Her 5 simple principles are based around choosing the correct colors and fonts. Then you should pick a nice layout and add sufficient padding. At the end, you can add some flair to make things shiny.
What I liked was that each step was accompanied by some rules of thumb and she shared many great websites that help you make better choices. For example, palleton.com can help you pick better colors.
Her #1 tip: don't stop if your first attempts don't lead to immediate results. Keep trying and eventually you will see improvements and get better at spotting correct design choices.
After the lunch break Dries Vints introduced us to building API's using API Blueprint, Dredd, and Apiary. It is one of the possible workflows and it might not be for everybody, but he showed some cool stuff that many projects can benefit from.
API Blueprint is a method of describing the specifications of your API. Its syntax is Markdown-like and very readable, which I think is pretty awesome. Using Dredd you can test your implementation of the API against the API Blueprint specification.
The first (and for me the most obvious benefit) is that the specification is easily and automatically translated into documentation about the API. Secondly, this is a framework- and language-agnostic style of describing your API. So it works the same for Laravel and Drupal, for PHP and Python.
I still don't really get what Apiary exactly is. It seems to be a collaboration tool for developing API's. But Dries was very enthusiastic about it so it probably worth a closer look!
So I must admit: after two days of sitting and listening I was getting a little tired and just a little bit sleepy. I haven't been paying enough attention to the talk by Femke van Schoonhoven, and that's a shame. Sorry Femke!
Femke has some great stories that put all these things in a different perspective, and that is really refreshing to hear. Especially since all the other talks are centered about stuff that you should be doing. Highly recommended!
Traditionally these files were separated and Evan talked about why this changed and what advantages it has. After that he dove deeper into the inner workings of Vue and how the different components are all processed so it can be interpreted by browsers.
If you want to know more about the inner workings of Vue, this talk is really good. Topics that are touched are WebPack loaders, how Vue enables hot reloading of components and why it doesn't use Native Web Components.
But wait! There is more!
So at the end of the conference (or should I say: at the beginning of the after party?), Shawn McCool had a special announcement to make: Laravel is going to offer official certification for Laravel developers.
Pre-registrations are being offered at a discounted price, so maybe that is the reason that the website seems to be offline at the moment. This stuff seems to be really fresh and the details need to be filled in a bit. From what I've seen so far this seems like a great new extension of the Laravel community!
I've had a great time at Laracon and learned a ton of new things. The atmosphere and the venue were also great so it was a very pleasant experience. I highly recommend it to everyone. Thanks for the organization and the speakers for offering this great event!
I suppose that videos of the talks will soon be released, as they have been for Laracon US. I will update this article and link to those videos as soon as they become available.
Keep on reading
- Day 1 of Laracon EU 2017.
- How to solve encoding issues when connecting to an MSSQL database from PHP.
- This is what I learned by making my first open source package.
What did you think of Laracon? Share your thoughts in the comments!