Showing posts from 2018

Terraform from your messaging systems…

Above is a short demonstration of how you can interact with Terraform from any messaging systems like Slack. If you want to know more about this, have a look to: Terraform-Api which provides an API to terraform and git to apply and change itHubot-Terraform ; a set of scripts to interact with the terraform API from Hubot and any messaging providers it supports Have fun!

Trigger Terraform in the cloud with Terraform-deck

For a few weeks now, I've been working on Terraform-deck, an API to kick off Terraform workspaces remotely. I'm using it on a project a for some time and, if it is not easy, I've started to turn it into an open source. It has been a real opportunity. A lot of people I love are supportive and some have already contributed more than I had expected. I'm very grateful. It is a lot of talks, energy and passion!

This first article introduces the tool and shows how you can put an hand on it.
What is Terraform-deck? If you are using Terraform, I don't have to explain its principles... You can spawn or destroy hundreds of resources in a few minutes. If you need to scale and make them more robust, Terraform Enterprise is the way to go: it is serious; it integrates registries to share your code; it manages parameters; it helps enforce policies; it provides a nice and easy UI; it help you integrates your CI/CD pipelines. Plus, it is worth and fair to reward the fantastic peo…

Monolithic Repository and CI/CD

After working with dozen of independent projects and dealt with the difficulties of sharing components, fighting the technical debt, duplicating parameters from the projects to the infrastructure code or simply helping people to join our teams/projects, we've decided to move towards a monolithic repository... And by this mean, overcoming some of the challenges we had faced, as a start up, to develop and grow a micro-service architecture.

As you can guess, storing different services in a single repository does not come without any challenges either. You want to enforce good practices. You need to optimize your CI/CD pipeline. You need to accelerate and add new people; new teams.

A monolithic repository comes with its own set of questions:

Scrum Is Killing Me...

Software is eating the world and it is a lot of fun. A lot of fun to work on products that are shaping our future or, at least, to hope and fight for it. It is a lot of fun to work with smart people, enthusiastic people, committed people. It is a hard work too. We do not want to compromise. We fail a lot. We need to stay right-in-time: not early, not late either. We need skilled people, talented people. We need diversity. We need to be part of teams. We need to be involved with a team; remain positive, accept ideas from others, be passionate and tolerant. So it is fun and it is hard! Well, it is especially hard since Scrum is killing me... again!

Lets start with facts I sometimes wonder if people know:
Scrum has been defined and maintained by Ken Schwaber and Jeff Sutherland who are 2 distinguished gentlemen. Scrum is documented as a whole in "The Definitive Guide to Scrum: The Rules of the Game" that is available under CC BY-SA that is an OpenSource License. There is no …