2 ms·
This is a problem caused by the differing world outlooks of technical people and "business people". I have fallen down this rabbit hole plenty of times myself
by jiggy2011 15y ago
This is a problem caused by the differing world outlooks of technical people and "business people".
I have fallen down this rabbit hole plenty of times myself as well as seeing others do so.
Technical people have a desire for maintainable and fast code , coherent architectures , DRY principles and designing a robust , well tested system with the long term in mind.
Business people are interested in cashflow , agility and being able to get their ideas into production quickly. They are worried about waiting months for a requested change to make it into production and not having it be exactly what they wanted/needed.
Managers often have a belief that programming should be unnecessary and there should be some way to drag and drop functionality into their applications. For example anybody who implements simple email capabilities into their web app will soon have users demanding to know why it does not have a spellchecker , contacts database , spam filtering , mail merge , mail folders etc etc (basically everything that MS outlook has)
This conflict leads to problems where business will ask for what they feel should be a simple change and will want it working by the next business day. The technical team will take this change and promise to include it in the next large update. For example the small change may interface with parts of the system that are undergoing bigger changes upon the next release.
Developers do not want to mess up their code base doing these half assed changes without proper testing so they attempt to anticipate everything that might be required and simply add more and more options to their program making it increasingly complex.
When this becomes too much to manage they will eventually create a small DSL or a "rules engine" of some kind. This starts off simple enough that the secretary can use it and everyone is happy since the developers get their nice codebase as seperate from the messy code developed by the users.
Of course this rules system becomes more and more complicated in itself and it becomes a full time job to maintain this rules engine while more and more of actual live code is being written by people who have a baptism by fire introduction to programming as well as no testing facilities or version control.
Eventually the developers have to step in , view the programming atrocities that have been created in the higher level engine and somehow re-integrate it all back into the original codebase and start again.
Basically you are moving the mess out your area of responsibility and moving it to someone elses.
This isn't always a bad idea provided you limit the power of the rules system and make sure expectations are clear as to what it will be able to perform.