Intro:
Low code platforms have become increasingly popular in recent years, offering the promise of faster and more efficient application development. However, while these platforms are designed to streamline the development process, they can also lead to operational issues if proper system design thinking is not integrated into the process. The lack of design considerations can result in applications that are difficult to maintain and manage, leading to problems with scaling, performance, and overall operational efficiency. It's important for organizations to approach low code platforms with a focus on both speed and quality to ensure that their applications are not only developed quickly, but also built to last.

This blog is parallels to the book "Thinking, Fast and Slow" written by Daniel Kahneman, a Nobel Prize laureate. In this book, Kahneman describes the ways in which we think or make decisions – and how those ways work against and with one another. I am leveraging the key construct to explain computer coding philosophy

System-1(Low Code):

Low-code is when you use special tools to make a program without writing a lot of code. Low-code, on the other hand, is a visual, drag-and-drop approach to software development that allows non-technical users to build applications without writing a lot of code. This approach is designed to be more accessible, faster, and easier to use than traditional coding, but it also comes with certain limitations in terms of customization and control. It's like using a cake mix instead of making the cake from scratch. You can still make a cake, but it's easier and quicker because you don't have to write out all the instructions yourself. With low-code, you can make simple programs without needing to know how to write code, but you don't have as much control over exactly what the computer will do.

• Generally encompasses Loss Aversion i.e, is often preoccupied with loss or fear or focused on avoiding risks and negative reactions.

• Is prone to Overconfidence and blindsides the non functional consideration

• Seeks a Coherent Story and is prone to jumping to conclusions and creating a faulty story even if the evidence doesn’t fully add up.

• Novelty is dangerous to the System 1

System-2 (Pro Code):

Pro-code is when a programmer writes a lot of lines of code, or special instructions, to tell the computer exactly what to do. This approach typically requires a high level of technical expertise and can be time-consuming and complex, but it offers complete control over the application's functionality and design. This is like writing a recipe to bake a cake. It gives the programmer complete control over what the computer will do, but it takes longer and can be more difficult to understand.

• System 2 thinking often requires you to seek out alternative opinions to counteract your own internal biases.

• It’s usually much easier for us to point out the harm or bad that others do rather than ruminate on our own shortcomings. But you can only engage in System 2 thinking and limit your own biases by actively becoming aware of your own blindness and working to improve your thinking.

• Only when new events or stimuli arise to grab your attention will you slow down your thinking and begin to approach a problem analytically. System 2 thinking will be when you encounter an unexpected situation.

General Direction:
In general, low-code is well-suited for rapid prototyping and small-scale projects, while pro-code is better for large, complex projects that require a high degree of customization and control.

Further Read:
1) Book "Thinking Fast and Slow" (https://www.amazon.co.uk/Thinking-Fast-and-Slow/dp/B006QXGLA8/ref=sr_1_1?keywords=thinking+fast+and+slow&qid=1675703244&sprefix=thinking+%2Caps%2C118&sr=8-1)

2) Unpacking the decision decision to use leverage Low code platform
https://www.linkedin.com/pulse/lowcode-rises-balagopal-madhusoodhanan/
3) https://www.linkedin.com/pulse/low-code-platform-darkside-balagopal-madhusoodhanan/