César de la Cal - PHP Entwickler München

Skrill is certainly the lousiest payment provider I have ever had the bad luck of working with. They will advertise a free account and milk you for every penny you own.

Skrill charges for everything you do on their platform. They charge you for adding money from your bank account, they charge you for retrieving money to your bank account and they charge for sending money to other users.

I had Skrill as a backup, to send some payments to people who didn’t have Paypal available to them. But no more. Good riddance Skrill. You won’t be missed.

Immer wieder habe ich das Gespräch mit Kunden und die widerkehrende Frage: Wieso kann man mir ein bestimmtes Projekt Feature nicht zur Deadline X versprechen?

Das komplizierte bei Software ist das jedes Projekt ein komplett neues Projekt ist. Man muss das Projekt und seine komplikationen verstehen, analysieren und eine Software schreiben die diesen Problemen entgegen steuert.

Wenn man nicht “Wordpress + Theme + 3 Plugins“ versteht, dann muss man sich eingestehen das man dieses Projekt noch nie gemacht hat. Und das man deshalb niemals weiß wie das Projekt konkret aussehen wird, welche schwierigkeiten sich auf dem Weg auftuhen.

Oft ist es so, das die einzige realistische Lösung ist das Projekt in der Planungsphase zu beenden, denn es ist evtl garnicht mit den aktuellen Mitteln und Resourcen machbar.

Manchmal, wiederum, ist die Software die einzige realistische Lösung. Die Frage die man sich als Projektleiter dann stellen muss. Wäre diese Software in 20 Jahren erst verfügbar, würde man sie dennoch haben wollen?

Man vergisst oft wie viel Arbeit alte Domains machen. Habe heute wieder eine meiner Lust Käufe die ich letztes Jahr getätigt habe auf meinen Blog umgeleitet - damit ich zwar den coolen Domainnamen nutzen kann aber mir die Mühe eine Zweite Seite mit Content auszustatten nicht machen muss.

Ist auch super einfach, einfach bei der Domain die man nicht mehr brauch in die Apache config (oder NGinX config - je nach geschmack) folgendes Eintragen

RewriteEngine On RewriteRule ^(.*) http://neue-domain.com/$1 [R=301,L]

Habe letzt einen Artikel gelesen das Hamburg aus dem Microsoft Ökosystem aussteigen und auf Open-Source wechseln will.

Der Artikel erwähnt auch das München in der ganze Sache vorreiter ist, was leider nur zu hälfte stimmt. Denn wir in München haben es leider nicht geschafft dabei zu bleiben und das Limux Projekt ist wieder eingestellt worden.

I’m a freelancer, and a web developer, that means that I’ve always got stuff to do. Often I have more projects than I feel than I can tackle.

I feel like lately, work has become a series of tasks that I’d best describe as quick-sand tasks. I call them like this because they just feel like whenever you want to pick them up, you’re missing two things to do them - so you start with the things you’re missing, and you notice that these are each missing a thing or two, so you start with those...

In my experience, this usually goes several layers deep. And suddenly you’re in ticket hell. That’s where I’m getting the name from.

Quick-sand tasks are both exciting and terrifying. I personally have an amazing time figuring out all the things I want to do, and dreaming up the possibilities. But it also means that the project I’m currently working on has increased it’s scope massively and needs a lot more attention than I originally expected.

For me, the most comforting thing to do when I come across one of these tasks is to just sit back, relax, make a cup of coffee and block a few days for planning the scope of the application, break everything up into smaller tasks and re-negotiating the schedule with the client.

And then put the hours in to actually resolve the issue.

Personally, I find it frustrating to tell the client that there’s a delay, it makes me uncomfortable and makes me feel unprofessional. I hate telling the client that something that seemed stupid simple ended up costing a ton of time and hurting the schedule.

Went to the PHP User Group meetup in Munich the other day. Check has some really nice offices!

These last weeks, we have been hearing of Microsoft starting to get rid of old documentation and old projects that they no longer care about. It seems that right now, Internet explorer is their main victim.

I have heard a lot of push-back from people who wish to see documentation for the old software archived, and wish to preserve these things. On the other hand, there’s people who welcome Microsoft removing documentation for software that was often broken, is definitely legacy and finally, holding back the industry.

I totally understand the argument that the people wishing to preserve the documentation are making. It’s important to keep good historical records, it’s often really helpful to know what you’re dealing with when working with legacy software.

But I feel like I’m in the other camp. This information, legacy documentation, should be gated as ‘historical records’. It should not be polluting current and up-to-date information. It encourages people to continue holding onto broken and outdated tools that should be let go.

Nobody should be using Internet explorer outside of a museum right now. Nobody should be using any outdated Linux kernel, windows or macOS in production. And yet people do, because they feel like the support for their broken toolkit is still available.

This makes the industry stagnate, it keeps us from unleashing ourselves from the past. And while we should learn from the past, we should not hold onto it.

I think that old software should be archived and catalogued. But it should be done in a way that helps historians work with it, not people who don’t know any better.