I don't have much text here, just a link dump for today:
The art of command line:
https://github.com/jlevy/the-art-of-command-line/blob/master/README.md
Bash strict:
http://redsymbol.net/articles/unofficial-bash-strict-mode/
Friday, 10 July 2015
Monday, 4 May 2015
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
Friday, 17 April 2015
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
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
Thursday, 9 April 2015
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
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
Tuesday, 20 May 2014
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!
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!
Thursday, 8 May 2014
Postmortem
What should we do when something goes terribly wrong?
how-to-run-a-postmortem-with-humans-not-robots-velocity
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
See: http://stilldrinking.org/programming-sucks
Subscribe to:
Posts (Atom)