Software Engineering is less about coding and more about communication, between stakeholders, team members and programs themselves. The true job of a Software Engineer is to establish a control- and message-flow mechanisms that are easily maintained, understood by other developers and can scale up well. This is especially true with Web Computing. However, with the rise in the number of readily available “frameworks” that claim to solve it in a way, the traditional values behind building software systems are gradually lost.

The author was very proud to study Computer Science at the University of Sussex, where he was taught the basics of web computing, with such concepts as XSLT, but he also saw that a lot of other people would prefer to learn a trendy framework instead. Having passed his exam with 97% and now founded a Software Engineering company, he can’t emphasise enough the importance of the computing tradition as well as culture, which must be preserved at all cost.

In trying optimise the internal development process, we have come up with a discovery called type.engineering, which by looking at the waterfall model, decides to take a step back and focus on the design of systems before implementation. The paper contributes a novel way to write programs in XML notation, which can then be converted into any language of choice via abstract classes and code generation. We explore the topic of developer satisfaction to understand the significance of auto-completion hints and demonstrate how multiple inheritance is arguably one of the best features of a programming language, which sadly is missing from most technology stacks.