This is my first blog entry. I’d like focus here on software architecture in Delphi world. Why do Delphi developers need architectural patterns? Do they need it? In my opinion, they do not only need it, but they use it constantly. In my opinion, the question worth considering is: what patterns should we use and whether each pattern fits each project? I would like to start by looking at the patterns that today are used massively.
I also would like to explain to all C++ developers why I'm not writing about the C++Builder. Although architectural issues are the same for both groups of developers, however, specific solutions are completely different, so I will focus only on one part of cake.
Every day I work as a software consultant so I have the opportunity to look at many of our clients' projects. Most of them are very advanced and I'm surprised how complicated projects can lead such small teams. Have you ever wondered why? In my opinion, thanks to the patterns we have in our favorite tool.
Delphi history and architectural heritage
Delphi as a development tool has proven its effectiveness and has for over 20 years enabled developers to deliver incredible solutions. This performance owes itself to the design patterns and history. Product architects such as Danny Thorpe, Anders Hejlsberg, Philippe Kahn, and many others worth mentioning here, left their marks. We are constantly using their ideas. Heritage products and technologies such as Turbo Pascal, Turbo Vision, Object Vision have allowed to build what we can currently use in Delphi 10. Delphi contains inside the whole history of these architectural experiences.
Delphi projects today – balanced, but still imperfect
Today we use a tool that is very simple on the one hand and very advanced on the other. Sometimes this simplicity, also called obsolete, bothered many programmers, and sometimes complexity makes the first contact difficult. I think developers are getting an incredibly balanced tool that keeps programmers in a very rigid architectural framework. I do not want to say that the architecture of all projects is great. No, it is not. The majority of large projects are written just as one-forms simple apps created for fun. However, thanks to architectural rigors, it is possible to implement such large projects by such a small team written in such an imperfect way.
Delphi future – code better way
Thanks to the developer community, the last five years have dramatically changed the approach to architecture for medium and large projects. It's worth mentioning Nick Hodges, Primož Gabrijelčič, Stefan Glienke, David Heffernan, Daniele Teti and dozens of other Delphi developers. This knowledge is still very scattered today, but has changed many projects. I hope that these new experiences combined with the Delphi tradition will allow us to push new energy into our favorite tool – Delphi. I also would like to contribute here. That is the origin of this blog.