Triple D : Design, Develop, Deploy

Our approach

In order to achieve our ambitious goals we believe that there are certain prerequisites in order to make this possible.

  • Honest partnership
  • Direct communication
  • Ownership of the development process
  • Ownership of the deployment process

Honest partnership

We value open communication more than negotiated contracts. The end goal of a successful partnership is that both partners are pleased with the result. We want to build the software you need and enable you to continuously reap the benefits from a well-designed solution. Since software is a learning process, developing it iteratively is paramount in order to get the best result from our learnings. An open and honest communication, where there is trust in having a mutual goal is paramount for this.

Direct communication

We don’t believe in long communication chains and huge documents. We build software for the business, they should be the ones we are talking to. There is no need for a middle man, we don't want to be become code monkeys. We can bring so much more to the table.

Ownership of the development process

When you hire Triple D, you hire people who have spent a lot of their time in getting proficient in their job. A job that is so much more than writing code. So let us own the development process. That way we can really deliver. Waterfall is not the way.

Ownership of the deployment process

Continuous integration and continuous delivery enables the team to work at full speed. A good delivery pipeline also allows the customer to see and use the features within minutes after finishing a development iteration. This enables the team to quickly gather feedback on the delivered product, pivot if necessary and constantly go for maximum business value. We want to maximize learning and reduce the cost of wrong decisions. The faster we know, the faster we can switch gears.

Programs must be written for people to read, and only incidentally for machines to execute.

Abelson and Sussman

Architecture represents the significant decisions, where significance is measured by cost of change.

Grady Booch

How it is done is as important as getting it done

Sandro Mancuso

A document shouldn’t try to do what the code already does well.

Eric Evans

If you think good architecture is expensive, try bad architecture.

Brian Foote and Joseph Yoder in Big Ball of Mud

The quickest methods aren't always the fastest methods

Gordon Beeming

The quickest methods aren't always the fastest methods

Gordon Beeming

The only way to go fast, is to go well

Robert C. Martin

The only thing dumber than big design up front, is no design up front

Simon Brown

If you can't deploy services independently, you don't have micro-services. You have a distributed monolith.

Beth Skurrie

If you can't see and understand a solution. You can't evaluate it

Simon brown

A good architecture rarely happens through architecture-indifferent design

George Fairbanks

It is easy to say that a piece of code is bad. It is easy to complain or even laugh. But the question is: are you good enough to make it better?

Sandro Mancuso