One Year of PullReview
(Photo credit: Wikipedia) I don’t scale Two years ago, I was still employed as team leader of an architecture team in... more
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
Some weeks ago, we stumbled upon Lukasz self-published ebook “Memoirs of a Team Leader”. Lukasz picked my interest by professing: “This is the book I wanted to read after I had become a software team leader.“ Having been a team leader for a good part of the... more
PullReview: GitHub Status and others
First of all, dear reader, I wish you Happy Holidays! This blog post is about the last release of PullReview, that includes a few features before the end of the year: Same Actions are grouped for Code Smell, Complexity, Design, and Duplication Lower severity for... more
A Journey in Payment World - Part 3: what is happening here?
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. more
A Journey in Payment world - Part 2: the only part you need
The only part needed? (missed the part 1? Read it here) Making a serie with a part 2 titled “the only part you need” is probably a little misleading. Fact is, just after having picked up Stripe as our provider and... more
Rubies, Gems and Dollars - a journey in the payments world - Part 1: The backpack
Update: Part 2 available This is the first post of a short series about our experience of integrating payments into PullReview. My objective is to be as practical as possible. There will be code, but also some reflexion/question that are not strictly... more
Code Review - why the tooling matters
A tale of two teams Several months ago at 8th color, we did setup a rule of “no story should be closed without a code review”. This has worked well for us so far. Two weeks ago, I was at... more
Why you need a "Definition of Done"
OH Customer: Strange, I don’t see the new merged list feature we discussed about last month. Developer: No, it is not there yet. Customer: But it was marked “done” in our last... more
We don't have time for code reviews
OH If you’re a developer since some years, you probably have heard several or all of those explanations: “We would love to do code reviews, but we have a very tight schedule" “Quality matters to us,... more
subscribe via RSS