Design – Geared Minds' activity roller

Promising new application

20/12/2016 Jerome

We are used to quickly start drawing a solution in-session. Our latest pre-sales appointment was no exception to this. With time, these early drawings have even become

ficus_dynamic_queries_explained_compressed

API design and abstraction

24/03/2016 Jerome

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

Outline and explain

14/12/2015 Jerome

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

Birth of a solution

11/12/2015 Jerome

A whiteboard and a crowd is generally pretty much what’s required to imagine a new solution altogether. This one is the very first drawing of a

Streams of data

10/11/2015 Jerome

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

Sizing a platform

18/05/2015 Jerome

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

Design for performance

26/03/2015 Jerome

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

Design a solution’s components

21/02/2015 Jerome

Designing the BOM’s abstraction model for multi providers support. Smart implementations often start with a chat around a whiteboard refining a model.

Capture requirements

26/01/2015 Jerome

Key points of a solution are always to be searched in the requirements. Gathering them all helps drawing the proper design, whatever their type.