Building an end-to-end testing strategy on top of Kubernetes
A Makefile based CI/CD chain for Go
Whatever the project you are working on, whatever the programming language, using a Makefile to handle common tasks is a great idea.
Makefiles are great at :
- Mask the complexity of a task;
- Handle multiple tasks;
- Help contributors to start with your project;
- Manage configuration using env var;
- Define a common interface / standard between projects;
- Abstract the underlying technology.
For all those reasons,
make is a perfect fit with any CI/CD chain. Using a Makefile helps you define a simple and common interface usable whatever the CI/CD chain you plan to use. The only thing you will have to worry about is that your CI/CD chain tool will call the right target.
And the job is done. It could be done with Travis. It could be done with Jenkins. The only thing that matters is the interface defined by your targets.
Handling validation errors from API-Gateway with AWS Amplify using ReactJs
Recently, I’ve been working with AWS in order to experience how it is to build a MVP really quickly. The goal I’ve been trying to achieve is to use as much AWS tools as possible to get a working product in production the fastest.
To do that, I choose to rely on :
- Lambda for back-end code
- API-Gateway for REST API
- DynamoDB as a database
- Cognito to manage Singnin / Singup and authenticated calls to the API.
Building a really smart Jabber chatbot with Dialogflow
Have you heard of Dialogflow?
Dialogflow (previously known as api.ai) is a conversational agent manager. Basically, you can see Dialogflow as a back-office were to manage an NLP engine.
As an admin, you can create intents that represent a suite of similar “user says”. Under the hood, Dialogflow provide an AI (Natural Language Processing) that learns to match user inputs (called “user says”) with intents depending on the context, in order to provide the more logical/appropriate response. It could be an actual answer, called a “speech”, as it can be an action. For example : starting a job, running a command, etc.[Read More]
Form validation with React using Formik and Redux
Parsing code snippets from markdown with Go
Talk : 19 millions searches per day @ Meetic
Bellow is the talk I made during the french PHP forum. That talk was a return on experience of integrating a search engine base on Elastic Search inside an microservice event-driven architecture.
As a developer in 2016, you need to learn Emacs (or Vi)
How to improve your productivity writing code and force yourself to think twice.
This post is not another Emacs vs Vi troll. My point is to explain why (deeply) learning to use a low level text editor is one of the first things any software engineer should do. I have personally chose Emacs because I found common shortcuts easier to memorize. As you will see later, it doesn’t matter which one of those editors you like to use, as long as you have learned to use it.
Editors like Emacs may seems old but they have been thought to be productive tools. Shortcuts are optimized with your hands place on the keyboard and the most used key. They let you do your work as quickly as you can think about it but still, they force you to think about what you’re doing. Not only they let you learn how to be more productive, they make you understand what you do instead of writing code with crappy CRLF.
Master your working environment.
I often meet developers working on a software or a web application development trying to master the programming language and the framework they use. This is a good idea, for sure. It let you being more productive with time. But, at some point, programming a new feature in your development environment is not enough to get things done. More effective and more comfortable you become with the software code, more features you should be able to design, code, and make run into production. And yet, most of the time, this doesn’t go as well as you expected. There could be thousands of management and technical reasons which explain why you don’t succeed at getting things done. Obviously, if your company culture is that only one of the lead developers is in charge of pushing new features into production, your possible improvement is limited (And you probably should think about quitting you job). However, most of the time, this is not the reason why you can’t push the feature you just get reviewed and validated into production. Most of the time, you just don’t want to work (or people don’t want you to work..) on the production environment because you don’t master it.
So, as (not) expected, mastering your working environment doesn’t mean mastering MS Windows. It means, however, mastering your VCS, mastering the deployment tools you use, mastering the server configuration (such as Apache or Nginx), mastering the programming language configuration, mastering Linux configuration and the Linux logging system.
As you probably know, all those tools configuration is made trough text files you need to edit directly on the server. At this point, no chance to open any of the graphical text editors you use everyday. Here is where comes Emacs (or Vi).