Oliver Tupman

I encountered AngularJS back around version 0.6 and built a prototype system for a startup. I also did most of the groundwork for building an open source AngularJS / HTML mobile framework (LungoJS) integration called the 'Lungo Angular Bridge'; this involved some deep delves into the dark internals of AngularJS (take a look at ng-view...). I also worked with my teams to build their initial prototype applications, helping them with their problems and expanding their knowledge of the platform.

I've been using JavaScript for front end work for around 10 years now back in the days where the term 'ajax' didn't exist and neither did jQuery. Now I still use it on the front end, typically via AngularJS to build complex apps rapidly or on the server side via NodeJS.

I love NodeJS on the server; its quite rough and ready when you compare it to something like Ruby on Rails, but what is cutting edge if not to bleed a little on? SailsJS brings us some of the capabilities of Rails to JavaScript, but there are still huge gaps in its infrastructure lurking to capture the unwary.

My team and I decided on the future of a previous company by assessing a number of frameworks out there (Groovy, Java+XYZ, RoR, etc.) and decided that RoR would be the best way to go. A major product was prototyped with RoR and then deployed as an API with the mobile client reaching #1 in the German app store.

I've worked with SQL databases for over 10 years now including: MySQL, Postgresql, MS SQL. While these days one would try to use a framework that would abstract the details away (ActiveRecord, Hibernate, etc.) from time to time you find yourself getting dirty in the details. Or performance optimisations!

I've used Java as part of the Spring / Hibernate framework as well as on client side apps within the Eclipse framework. These days I tend to use Ruby on Rails or JavaScript/NodeJS, but I still enjoy having strict typing and the like :)