Visual Prototyping, Konzeptionierung und Modellierung

Analog ist die erste Wahl

Bevor man sich den Kopf zerbricht oder in Tooling-Gefrickel verfällt: Gute Stifte und gutes Papier sind immer noch das Tool der Wahl für gemeinsames Prototyping, die gemeinsame Planung und Konzeptionierung im Team, zur gleichen Zeit am gleichen Ort. Dies gilt auch für die Arbeit alleine.

So machen’s übrigens auch die besten der besten.

Gutes Papier, große Bögen und gute Stifte sind dabei sehr wichtig. Robuste Blanko-Kärtchen in verschiedenen Größen können beim UX Prototyping auch helfen.

Ergibt digitale UI/UX Prototypisierung, Planung und Konzeptionierung im Liveteam Sinn?

Visual Prototyping, Konzeptionierung und Modellierung weiterlesen

IoT, IoT, Oooh my Internet of freakin’ Things!

IoT is a fad.

There, I said it.

Embedded has a use. It always had, ever since microlelectronics. And it most certainly always will.

But IoT is a fad. Pure and simple. It roughly is to the general population today what Ruby on Rails was to programmers 10 years ago. Truckloads of hype that will soon wither and fall back to niche cases when facing the real world.

IoT, IoT, Oooh my Internet of freakin’ Things! weiterlesen

Typo3 neu aufgezäumt, aber falschrum – Warum Neos eine schlechte Sache ist

Es ist mehr als 10 Jahre her, da kamen im offiziellen Kernteam die ersten Gedanken auf, Typo3 nicht nur weiter, sondern von Grund auf neu zu entwickeln. Die Gründe dafür lagen und liegen jedem, der mal mit Typo3 gearbeitet hat – egal ob als Redakteur, Web Worker oder Entwickler – klar auf der Hand. Typo3 ist, wie viele andere PHP CM Systeme auch, historisch und hysterisch gewachsen und ursprünglich von Leuten entwickelt, die mit Programmierung und sauberer Softwarearchitektur, vornehm ausgedrückt, nicht so viel zu tun hatten. Wie bei so vielen PHP basierten Redaktionssystemen hat eine naive Begeisterung für Gefrickel Typo3 zu dem gemacht, was es heute ist – im positiven wie im negativen.

Typo3 neu aufgezäumt, aber falschrum – Warum Neos eine schlechte Sache ist weiterlesen

Google DevFest Düsseldorf 2016 Recap

What a great event! Thanks to all that made this possible. Especially the GDG Düsseldorf and Sipgate.

Google Polymer Summit 2016

Once again the Google Polymer Summit was a blast. This time in London.

Quoted of the Web: “PHPs badness is its advantage”

I love Python, I think JavaScript is sort of OK and I did a lot of serious programming in ActionScript 2&3, both of which are quite simular to JS. I was basically forced into doing PHP by the market. I never really liked PHP but I really never hated it either. The thing about PHP is that it’s so specific in its domain and such a hack that no one doing PHP development for a living will go around boasting about the greatness of the language. There is a refreshing lack of arrogance in the PHP community which, in my observation, makes it very easy for n00bs to pick up. As a result we get countless people reinventing the wheel in PHP and discovering basic programming patters anew for them selves and starting yet another Framework/CMS/Whatnot and the results often are really bizar. But the community remains alive that way.

Working with Drupal with a current project because it’s the prime go-to CMS here is like a live alice in wonderland trip. A strange historically grown mess, barely tamed by sanitiy and a relentless chaotic community that all by accident seem to come up with hacks that somehow solve the problem in some way. And yet there’s a solid global corporation building its business all around Drupal [acquia.com]. The surreal hacks with which the Drupal people solve their problems are mindboggling, and yet everybody seems totally OK with it. And Drupals track record of deployments is impressive.

I guess with PHP it’s somehow like the C vs. Lisp argument: C is so shitty compared to Lisp that you have to get yourself together and work as a team, or you won’t get anything done. Hence Lisp has this loner exisitance on the side and all the real work gets done in this ancient C thing.

PHP is a simular thing. It is so bad that no respectable programmer would pick it up voluntarly nowadays, but yet it grew out of Perl (which is worse in some ways), was somewhat of an improvement and was at the right place at the right time. The badness of PHP accounts for its considerable lack of arrogance (compare the PHP community to the Ruby community for instance) and for no one feeling guilty when he does a quick bad hack.

As a programmer you don’t feel dirty when you do bad programming in PHP, you already felt that when you picked PHP as the solution. Hence quite a bit of work gets done in PHP. That’s why PHP has Drupal and Typo3 and Joomla and the Java Community has nothing of that proportions. The barrier of entry into PHP is *very* low which gives it its momentum.

WordPress Path to actual active theme / Pfad zum eigentlich aktiven Theme

preg_replace("/\/\w*?\.css/", "/", get_stylesheet_uri());

Gibt den Pfad des aktiven Themes zurück, auch wenn dies ein Child-Theme ist. Vorrausgesetzt, das Child Stylesheet ist mit WordPress Bordmitteln im Theme eingebunden und aktiviert.

Returns the path of the actual active theme, even if this is a child theme. This only works if the child themes stylesheet is included with WordPress methods.

Return value comes with trailing Slash!!

Show Active Web VHosts on Linux

List all active apache web vhosts on Ubuntu/Debian Linux / Liste alle aktiven Apache Web VHosts auf einem Ubuntu/Linux Server auf:

ls /etc/apache2/sites-enabled | sed 's,\s,\n,g' | sed 's,^,/etc/apache2/sites-enabled/,g' | xargs cat | grep -v "#" | grep ServerName | sed 's,ServerName,,g' | sed 's,\s,,g'