The first code of PullReview has been pushed in January 2013. We were 3, Martin, Stephan, and I. It was launched in October 2013. It slowly grew for about 2 years. Life being about choices and decisions, we split, Martin and Stephan taking different roads. I tried to actively run... more
Giving Back with 24 Pull Requests
What would we do without all those magnificent Gems and Rubies? Thanks to the many developers that make them and open their source, we can develop great apps. Now is the time to give back. It’s time to say thanks to their authors, to send them a pull request, to... more
PullReview: Shareable Private Review and Test Coverage Integration
It’s been a while since the last PullReview news, so it’s time to give you some updates. Over these past three months, we certainly haven’t been slacking and have brought in a bundle of features, for example: Share your reviews with your devmates Never miss... more
Blogging the developer's way
Our last post was about migrating from WordPress to Jekyll. Although the engine is pleasant and has a great design, the main benefit of the move is actually something else. Of course, we’ll need blog hosting services before we can start writing anything. Hosting One of the many... more
From Wordpress to Jekyll
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 happy surprises. Switching When we... more
When is your code DRY enough?
You're aware that duplication is a rampant disease: more code, more fragile, less maintainable, less readable. You even use one or another tool and make your code reviewed to find most of them. When facing some duplicate code, you're not always feeling comfortable to... more
5 reasons you are not doing code reviews
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,... more
PullReview: Badge and integration with BitBucket and GitLab
PullReview recently gets a few new features: Badge Public Review for Public Repo BitBucket and GitLab and lots more: HipChat notification Performance of the home page Profile Heartbleed Support Contact Badge Badges in README.md are a very common way... more
7 daily use cases of Ruby String
Strings are everywhere. You deal with String instances not only every day, but probably every minute. They came from files, databases, REST APIs, or you simply use them to print results. It's a pervasive representation, and Ruby provides plenty to ease its manipulation. But String comes with... more
When should I use a Set in Ruby?
You develop a small contact manager for a client. Contact = Struct.new(:name, :email) One important feature is the possibility to define a list of contacts. granny = Contact.
subscribe via RSS