3 ms·
We are providing similar services to several financial institutions using a first-party solution we have developed over the course of the last 5 years. Our appr
by bob1029 6y ago
We are providing similar services to several financial institutions using a first-party solution we have developed over the course of the last 5 years. Our approach for enabling non-technical people to impact the business is on a radically-different side of the spectrum though. Instead of "no/low" code with fancy UIs and modules, we went in the other direction. We asked the following question:
"Can we reorganize the codebase in order to expose common business concerns in such a way that non-technical people can reason with them simply by viewing the source code?"
The answer so far has been a resounding "Yes". We proved that there was extreme amounts of value in non-technical people being able to read the current state of the business implementation. Using functional business rules instead of imperative ones makes all the difference in the world. E.g. "if(CustomerIsAMinor) {...}" vs "if(customer.Age<MinorLimit && someothercondition) {...}". Using C#8 and having the ability to use functional paradigms as well as things like pattern matching also enable us to write highly expressive code that non-technical people enjoy reading. Also, really basic stuff like splitting important points of focus into class partials can make it 10x easier for non-developers to get into that 1 focused file and understand what is going on (e.g. MyBankWorkflow.CustomerValidations.cs).
But we didn't stop there. We then asked this question:
"Could non-developers make changes to certain areas of the codebase?"
We have done a few trials with our project managers and are finding that they are more than capable of: turning a new branch in GitHub, checking it out locally, opening Visual Studio, updating a parameter listing or resource file, making a commit, and then submitting a PR for review (typically by an actual developer). As confidence with this practice grows, we will further expand the "safe" areas of the codebase (i.e. what non-developers are allowed to edit).
Ultimately, we are trying to move into a direction where the development team is more of an internal consulting group rather than the means by which every line of code must be authored. The other view of this is that highly-intelligible source code is also useful for quickly ramping new employees and growing the team. We are beginning to view our codebase as not just a tool for the developers, but something that anyone in the organization should be able to work with in some useful way.
If you think more broadly about this cyberpunk reality we are sliding into, this is the only reasonable path. You have to enable everyone in your organization relative to the technology. You cant afford to slap a Fisher Price UI around every scary technical thing you run into. Tear down your silos and do not be afraid to show code to your project managers or even customers. Start writing your new business apps with these ideas in mind and you may reap some very unexpected benefits down the road.