roulive.com
The R Blog | Le blog qu'il est bien pour le lire | Page 2
https://roulive.com/page/2
Aller au contenu principal. Le blog qu'il est bien pour le lire. A propos du R Blog. Les films attendus en 2015. Un peu brut de décoffrage, les films les plus attendus (par moi en tout cas) en 2015. Une belle année en perspective …. The Theory of Everything. Laquo; Difficile de passer outre la brillante interprétation d’Eddie Redmayne, déjà assez magnétique dans les Piliers de la terre. ». What we do in shadows. Bande-annonce, score 7/10. A Most violent year. Laquo; Première vraie claque de 2015. J&#...
blog.8thcolor.com
Blog
http://blog.8thcolor.com/page10
Automated Code Review for Ruby. The unexpected reality of deployment. The task Three months ago, another company interested in Sybil accepted to be a pilot. Very quickly, the question of installation came, and we had to plan it. First of all, we met with. more. Woodcutting in the morning. Developer, the modern architect and general contractor. The incredible learning machine. TL;DR; If learning new things is one of your priorities in your work as IT professional, you should quit your work and create a st...
blog.8thcolor.com
5 reasons you are not doing code reviews
http://blog.8thcolor.com/en/2014/04/5-reasons-you-are-not-doing-code-reviews
Automated Code Review for Ruby. Back to posts list. 5 reasons you are not doing code reviews. 18 Apr 2014 Martin. Whether your work in a startup like us at PullReview. Or in a multinational, getting your team to start doing code review probably got stuck with the typical answer. That’s a very good idea, but. Having been there several time, and being quite convinced on the added value of code review, I listed the most common pushbacks. I’ve encountered, and some ways to go past them. I don’t have time.
blog.8thcolor.com
When is your code DRY enough?
http://blog.8thcolor.com/en/2014/04/when-is-your-code-dry-enough
Automated Code Review for Ruby. Back to posts list. When is your code DRY enough? 25 Apr 2014 Christophe. You're aware that duplication is a rampant disease. More code, more fragile, less maintainable, less readable. You even use one. And make your code reviewed. To find most of them. When facing some duplicate code, you're not always feeling comfortable to dry it up. Should you avoid similar. Actions in different Rails controllers? Should you use metaprogramming and avoid long similar case expressions?
blog.8thcolor.com
7 slow and painful deaths by regexp
http://blog.8thcolor.com/en/2014/03/7-slow-and-painful-deaths-by-regexp
Automated Code Review for Ruby. Back to posts list. 7 slow and painful deaths by regexp. 28 Mar 2014 Stéphan. The road to hell is paved with regular expressions. Dot is a special char. Carriage return in content. Denial of Service by regexp. Non escaping of special chars. Validating an URI with a regexp. Write once debug everywhere DSL. 1 Dot is a special char. Simple elegant, you read it, you understand it. Process all ruby files process ruby file(file name) if file name.match(/.rb/) # and profit. You h...
blog.8thcolor.com
Blog
http://blog.8thcolor.com/page3
Automated Code Review for Ruby. A Journey in Payment world - Part 4: we have a Plan. A Journey in Payment World This is a series about integrating a payment system into your web application. While inspired by our own experience, and so Stripe and Ruby oriented, most of the problems and solutions are probably useful in other technical environments. Ebook review: Memoirs of a team leader. PullReview: GitHub Status and others. First of all, dear reader, I wish you Happy Holidays! The only part needed? Read ...
blog.8thcolor.com
From Wordpress to Jekyll
http://blog.8thcolor.com/en/2014/05/migrate-from-wordpress
Automated Code Review for Ruby. Back to posts list. From Wordpress to Jekyll. 28 May 2014 Martin. As you can see, we’ve moved to a brand new blog, powered by Jekyll. This is a good opportunity to shed some light on a process that, although not terrifying, is not totally without surprises. In software in particular, there are no. When we started 8th color. We set up this blog quickly as a way for us to write about our company and what we were doing. Since we started PullReview. The switch to Jekyll. At th...
2015.rubyday.it
Sponsors - RubyDay 2015 | RubyDay 2015 - Turin 13/11/2015
http://2015.rubyday.it/sponsors
November 13th, 2015.
blog.8thcolor.com
Blog
http://blog.8thcolor.com/page2
Automated Code Review for Ruby. 7 daily use cases of Ruby Hash. Everyday, you deal with Hashes. We use a lot of them everyday when coding PullReview, from Rails infamous 'params' to the various data we get from the GitHub JSON API. Creating a new Hash or retrieving an element by its key, are common and simple to do. more. Avoid spilling your Rails application secrets. Get notified of your Rails app exceptions with Errbit. Now, hopefully, users are coming to use your application, whether a. more. You've j...
SOCIAL ENGAGEMENT