When our work is done and we seem to have made people happy with it, it’s time to celebrate. We never forget to say thank
Read more
Slowness proofing
Performance is often on the top of the requirements list when we are asked to build a component. And we like to prove we are up to
Read more
API design and abstraction
Explaining an API key features (natural design for REST routes, extendability brought by high level of abstraction, …) by sharing them on a whiteboard says much
Read more
Daughter visits work
My 4 year-old daughter came at work with me today and let a nice drawing to say thanks to the team.
Read more
Outline and explain
Way before we get deep into the implementation details, we always make sure everyone adheres to the goals and how the system should work with
Read more
Streams of data
Good use cases helps capturing the streams of data and will guide to a properly designed solution. This is one out of the many we have
Read more
Define a strategy
We also stand by the side of our customers whenever a strategy has to be defined, expressed, presented and promoted. This above is only a
Read more
Sizing a platform
When designing a solution, we like to go through all the design aspects. Take some time and decide on the proper deployment plan and platform
Read more
Design for performance
Designing a solution without thinking about how it is actually going to be used now and then is rather risky. We treat future performance and system
Read more
Team work
Having stakeholders of all kinds to sit at the table and work together as a team is part of our work as well. And not one
Read more
Design a solution’s components
Designing the BOM’s abstraction model for multi providers support. Smart implementations often start with a chat around a whiteboard refining a model.
Read more
Capture requirements
Key points of a solution are always to be searched in the requirements. Gathering them all helps drawing the proper design, whatever their type.
Read more