Hear from the developers

Hear from kinodb developers about why they value this revolutionary way of delivering enterprise systems.

Neil - Senior Developer, datb

"Having all of the detailed technical grunt work done behind the scenes as you build the application is fantastic - it means that I'm able to focus on what the users want the system to do.  Being able to deliver the working bones of a complex application in a couple of days means that we can work through detailed functionality using real data within the actual system - not hypothetically or on paper.

The speed of implementation, and particularly the ability to assess the impact of a change before making it, means that the design of the system can be tweaked - or radically altered - quickly and easily if a problem or new opportunity arises at any point in the development.

End users can contribute to the design process and developers can get immediate feedback on the way that the system works."
 

Neil - Senior Analyst / Developer
Simon - Product manager, datb

"I lead the development, support and maintenance of an industry-leading off-the-shelf package.  It's a large and complex application that is critical to its users - it manages billions of pounds of investments.  Managing client variants and implementing bespoke modules just wouldn't be feasible using a conventional development approach.  

Most importantly, the development of a large application over a period of years becomes very difficult if you need to change technologies every five years or so - we don't need to worry about technological currency at all, as the underlying framework gets updated in line with database & browser changes, and all of our clients receive those updates automatically."
 

Simon - Product Manager
Martin Rodell - Consultancy Director, datb

"It's just not reasonable for IT teams to expect users to be able to articulate a really complex set of requirements from some picture in their heads.

The speed of iteration that kinodb gives us - being able to implement a whole load of functionality between workshops on successive days - means we can drive out requirements with the users and then show them how it will look, and how it will work.  Users get immediate 'buy-in' into the process, as they're able to form the system almost in real time.

The overall productivity means that I can use a small team to deliver a large project - that reduces cost, but more importantly it increases the quality of what we deliver, and makes us far more responsive to user requirements, whether during initial development or as requirements change years after initial implementation.  This - and the technology independence that the framework gives us - means that systems that we implemented over ten years ago aren't just 'still going': they're actually among the most technically up-to-date systems in use by our clients."
 

Martin Rodell - Director, datb limited