---
title: "Comment by Nikhil Nandagopal on \"The Case for Lower Code\" | Hashnode"
description: "Great article! One of the philosophies we live by at appsmith is that visual elements and configs should be configured visually while logic and workflows should"
url: "https://hashnode.com/posts/the-case-for-lower-code/603682710c99f77f2f8a5ee9/comment/6037766a15c9f056ec69c083"
---

[Discussion](https://hashnode.com/posts/the-case-for-lower-code/603682710c99f77f2f8a5ee9)

Comment [The Case for Lower Code](https://hashnode.com/posts/the-case-for-lower-code/603682710c99f77f2f8a5ee9)

[Nikhil Nandagopal](https://hashnode.com/@Nikhil-N)

[Feb 25, 2021](https://hashnode.com/posts/the-case-for-lower-code/603682710c99f77f2f8a5ee9/comment/6037766a15c9f056ec69c083)

Great article! One of the philosophies we live by at [appsmith](https://github.com/appsmithorg/appsmith) is that visual elements and configs should be configured visually while logic and workflows should be expressed via code. Anything that cannot be a simple config should just never be forced into a complicated visual interface! This has always been one of my peeves with workflow builders. They're great to connect to the data sources but the minute you have to write logic on the data in between, it becomes a nightmare!
