RESTful essay

I never lost my interested in REST, I even more love how easy people can do it wrong. I'm dumping the link to this essay while reading it. 

In my definition, a real-world RESTful API is an API that provides answers to questions that you won’t find in introductory texts, but that inevitably surface in the real world, such as whether or not resources should be described formally, how to create useful and automatic command-line interfaces, how to do polling, asynchronous and other non-standard types of requests, and how to deal with operations that have no good RESTful mapping.

 https://restful-api-design.readthedocs.org/en/latest/intro.html

Microservice Architecture

Great article by Martin Fowler about the microservices architecture model.


Most application development efforts that we see use a project model: where the aim is to deliver some piece of software which is then considered to be completed. On completion the software is handed over to a maintenance organization and the project team that built it is disbanded.
Microservice proponents tend to avoid this model, preferring instead the notion that a team should own a product over its full lifetime. A common inspiration for this is Amazon's notion of "you build, you run it" where a development team takes full responsibility for the software in production. This brings developers into day-to-day contact with how their software behaves in production and increases contact with their users, as they have to take on at least some of the support burden.



Source: http://martinfowler.com/articles/microservices.html

Warning: No support for locale: en_US.utf8

Fix the locale warning in Linux Mint:
http://forums.linuxmint.com/viewtopic.php?f=42&t=111527

Update Linux Mint: http://www.tecmint.com/upgrade-linux-mint-16-to-linux-mint-17/

After update fix samba: sudo apt-get install gvfs-backends

More on CD with Jenkins, Vagrant and Docker

More on CD with Jenkins, Vagrant and Docker:

1. http://technologyconversations.com/2014/04/29/continuous-delivery-introduction-to-concepts-and-tools/
2. http://technologyconversations.com/2014/05/06/continuous-delivery-ci-tools-setup/
3. http://technologyconversations.com/2014/05/20/continuous-delivery-static-analysis/

And more to come...

Tnx Dennis!

Postmortem

What should we do when something goes terribly wrong?

how-to-run-a-postmortem-with-humans-not-robots-velocity

Programming Sucks

This is a world where people eschew sex to write a programming language for orangutans. All programmers are forcing their brains to do things brains were never meant to do in a situation they can never make better, ten to fifteen hours a day, five to seven days a week, and every one of them is slowly going mad.

See: http://stilldrinking.org/programming-sucks

Ansible for CD

I'm working on putting down a DTAP environment, but i want to skip the classic DTAP where there is a lot of manual work and time gained in a scrum process is wasted in the waterfall way of working.

So i need some automation there. Automating means that i want users to be able to go to a website, select (or create) an environment and install the software that should be tested.

I had a look at Puppet and set up a test between two VBox instances. Is working with not too much work, but i don't like it. Seems a bit of a steep learning curve.
Then someone pointed out Ansible and i started to watch the video from last PyConn: http://www.ansible.com/resources. I'm already convinced this is the tool i need. And i'm happy to set up a prototype implementation!