There's a really new -maybe- cool feature in the Chrome browser since v40. It's called "Service Workers" and is a possibility to run javascript threads which are independent from the web page. Independent means the applications js code does not have to know about the service worker. And the service worker does not block the page cause it's an own thread.

Vom 23.06.2015 bis zum 24.06.2015 findet in London die Jenkins User Conference 2015 statt. Ich freue mich dabei zu sein und in meinem Vortrag "Jenkins for PHP projects" zu berichten wie wir Jenkins in unseren PHP Projekten einsetzen.

A little while ago I had to dive deeper into the performance optimized usage of PHPExcel. Our users are uploading files like Excel or CSV with a lot data to process. Initially we used the PHPEXcel instance without any tuning of the default configuration which lead to heavy memory issues on relativly small files. So I had to avoid reading all file content at ones to the buffer (like file_get_contents() does).

Am 04.05.2015 um 19:00 Uhr findet nach einer längeren Pause wieder einmal ein Webmontag.Talk in Mannheim statt. Ich freue mich dabei sein zu dürfen und etwas über "die Kunst Daten zu speichern" zu erzählen. In dem Kurzvortrag werde ich darauf eingehen welche Möglichkeiten es außer den "klassischen" Datenbanken gibt um Daten in Applikationen zu speichern und zu nutzen.

Am 04.06.2015 findet in Dublin die NoSQL Matters Konferenz statt. Ich freue mich dabei zu sein und meinen Vortrag "The NoSQL Store everyone ignores: PostgreSQL" präsentieren zu dürfen.

Since it is not really documented how to build a release .apk package with SenchaCmd and Cordova I`d like to share the current workflow I use. First of all we build the native package via SenchaCmd. This results in a production build of the Sencha Touch application wrapped in a debug build of Cordova:

As I blogged yesterday we created our own coding standard for our Javascript code. In addition to that we were looking for a way to lint SCSS code and found a tool called scss-lint which seems to be the only option out there when it comes to linting scss code. We were not happy with the default settings of scss-lint and came up with our own version which we`d like to share with the world today. Head over to Github and have a look at our cs-scsslint repo. The package can be consumed via npm, the package is called "bitexpert-cs-scsslint".

About two years ago we agreed on dropping our own company-wide code standard (which in fact was none!) in favour of the common standards used in all the programming languages which we use. That's PSR-1 and PSR-2 for PHP projects, the Java Code conventions for our Java projects and the Puppet Language Style Guide for our Puppet cofigurations. For Javascript we were not able to find the one and only standard out there. So once again we had to jump in and create our "own" standard. However, this time we`d like to share it with the world ;)

Long ago I started to globally .gitignore all the things. Recently I ran into a few issues with setting up Sencha projects via SenchaCmd. In my global .gitignore file I have a setting to ignore the vendor folder which perfectly makes sense in a Composer setup. As a side-effect this means that in a Sencha project the folder resources/themes/vendor/ will not be added to the repo. The work-a-round to avoid this is easy and simple. Add the following line to your global .gitignore file:

Am Mittwoch den 22.04.2015 trifft sich die Java Usergroup Mannheim. Ich wurde eingeladen meinen Vortrag "Microservices: Klein aber oho!" zu präsentieren. Der Vortrag gibt einen Einblick was Microservices wirklich sind, welchen Vorteil sie uns im Alltag bringen und welche Anforderungen Microservices an die Unternehmenskultur stellen.