Web Components for the Skeptic

Web components will afffect the work of a frontend developer a lot in the next years (well, at least I belive so). After seeing some talks about it I gave this talk at my work place. Here are the slides: Web components for the skecptic. »

Urban Etter

Purpose in UX

In a recent project, the aim is to build a new video editor. The aim of this editor is to spilt a video in certain segments, each with a start and an endpoint. The editor consist of three “pages”. One lets you choose the video to edit, one gives you an overview of the already existing segments and the final page lets you edit a segment. The video is embedded in our CMS and gets used for different use cases. »

Urban Etter

Clarity

A few weeks (month?) ago I wrote But which way is the desired one, which one should you aim at? I would say the answer to this question is: none. (of course about software engineering, what else?) Today I would like to update this statement. I think there is a way or an aim you should choose when coding. The aim should be clarity. Earlier I described it as “better maintainability” but clarity is probably more to the point. »

Urban Etter

Better or Worse

Following some traces on Twitter, I found this podcast where they talk with DHH, the creator of Ruby on Rails, about software design decisions. David told that for him, the most important point of making decisions about code is to actually see a code before and after a certain refactoring or feature. Show real world code before you do a refactoring/ new feature and after it. It should be imidiately clear that the new code is simpler and better. »

Urban Etter

In Favour of Behaviours

I used to be a teacher at a vocational school teaching programming and similar basics for software development apprentices. The Beyond serie from Anthony Ferrara got me thinking if I should have thaught OOP with another aproach. And if it will change a lot when we think about behaviours in OOP instead of type. Here is the presentation I presented at work. »

Urban Etter

Web development for humans

Long time coming: A post about coding style and the development of a developer. Pretty meta, I know :) We should code for humans first. The computer is pretty good at complaining when it can’t understand something. But unfortunately, there is no parser error when a human doesn’t understand your code. The WTFs per minute does not matter for the compiler, after all, the code works ™. But as we all know, there are big differences in the way we code. »

Urban Etter

Frontend Performance for the Craftsmen

This is my first talk at a conference at all. It was held at Frontend conference in August 2013. The slides are based on the excelent Reveal.js library and are found here. You’ll find the PDF slides here: https://speakerdeck.com/urbanetter/frontend-performance-where-it-matters »

Urban Etter