The DIB philosophy and history

The DIB-system is a system that has slowly evoled through the idea that Subject Matter Experts shall able to write complex and business critical software to be available in the mobile space. This can be achieved if documentation are written according to a strict XML scheme, which is the case in e.g. the aviation industry, where the idea first came to mind. The first attempt was made in the early 00's.

Also it has been important from day one to be more agile than what was normally seen at that time, and even today the DIB team are considered very agile in the approach of developing software. Again not only want we the product to disruptive and also the way we bring the software alive must be disruptive.

However the 1 generation of the DIB software was developed in Microsofts VBA and .net with MSSQL database under the hood. We quickly realise that was not the right choice to move forward but it demonstrated the DIB paradigm well, so it was just a matter of moving to better software platforms. During that period JSON became more widely used plus JSON databases also became more used. At the same time Nodejs became very popular because of the V8 javascript engine developed by Google. It also means that client and server applications suddently are written in the same programming language, which is ideal for a small startup company.

Totally DIB has so far required 20000 develoment hours and it has been spread accross a number of people where the majority are external. Reasons for this are

  • It creates a more flexible and dynamic team that can scale up and down as needed
  • It keeps people more updated on new things because they are in touch with many environments
  • They also understand more about the best practices used in the open community
  • It becomes easier to find new people for the DIB development people, because often has people who is pulling out of the DIB-team already found new people to step in.

In the following there is a list of people who has played a signifant rule in the development of the DIB environment