Well, after many years of using what frequently turned out to be inappropriate technology to solve a range of software problems, and being faced with the consequences of those choices, it was time to concentrate on being able to just solve the problem.
To develop technology that truly supported the solutions required. Developed with a simple purpose...
...to Cut The Crap - and solve the problem!
The current technology is derived from over twenty years of experience and has been in fulltime development for over two years.
Let's sprinkle around a few keywords in rough chronological order when first encountered:
Systems programming - multi-user systems - transaction processing
- word processing systems - 5G research - object oriented langauges - functional languages - logic languages -
parallel processing - knowledge representation - medical diagnosis - distributed systems -
graphical models - asynchronous communication - messaging systems - actors - computer learning
- assembler - C - Lisp - Smalltalk - Prolog - Object Pascal - C++ - graphics - collaborative
research - network modelling - production control - client-server - alarm reporting
- relational databases - persistence mechanisms - messaging mechanisms - retail systems
- code generation - EFT architectures - device interactions - OPOS - COM -
large systems integration - heterogeneous architectures - java - topic maps - XML - applets -
Swing - servlets - RDF - peer 2 peer - JSP - struts - tiles - web applications
- model-driven applications
All this experience has contributed to where CTC Technology is today and provides a context to evaluate new technologies.
The current CTC Technology is very close to an aspiration first discussed in 1986 - to be able to informally describe and directly evaluate new systems in an incremental and evolutionary way.