"Putting a cool front end on an old process and system spaghetti doesn’t help."
Common Lisp was not our first choice, but when we went with it it simply clicked. And for me, it's "philosophy" seeps through all the way to the user. One way or the other.
But not only there, more stuff seeps through:
The back-end, the database.
How you see the reality you're trying to model (that's what software is all about).
Then, the UI. But no UI can fully cover a messy base. I would say that a good UI is porous, simply enhancing a well concocted base.
So with thingamy we build from bottom using building blocks that hopefully fit and enhance each other, here's our stew-thinking:
- One big chunk reality model that differs from "how it's done today" (which is already another model created in the days of pen and paper). We started over again. Object oriented, object driven processes, no hierarchies.
- An object oriented database obviously.
- All held together with Common Lisp befitting and complementing the two first ingredients.
- With a nicely done and balanced stew we have to present the dish in a way that enhances it's underlying flavours. Ajaxy freshly cut herbs is popular these days and can be used, but one have to be careful not too take the focus away from the stew itself.
Still in the kitchen as we speak, tinkering with twists to the basics and cutting parsley with the other hand.
[Ajaxy herbs and tools]