Ben I'm a big fan of all you do but this is a bit binary and short-sighted. Many low-code tools also offer Git-control like Coalesce or Orchestra. So Broad-brushing all low-code tools as being without Governance is just ridiculous
Oh I am not trying to say that all low code tools lack governance but that they ways team implement the workflows themselves can. Git control alone is not governance, it’s a piece for sure!
Like I can still git control my projects and press the big red button and merge directly into main right, that's because of *me* not because of *tooling*
Yes, my point was that you can make things faster which isn’t bad but if you have those cultural issues and have the benefits of low code, you now make bad decisions faster because you never fixed the cultural issues
@hugo with those tools, when you create the pull request into main, are you able to automatically fire off CI checks and have a human-readable diff for the PR reviewer? Also, is it possible to run linters and formatters to make sure the work complies with team standards? (realize w/ low code / no code that’s a bigger lift)
Having worked on several teams that use them as a key part of the process, pull requests are an incredible QA tool, and not all tools allow for building in these practices
Faster often goes hand in hand with riskier. It's part of the game. As most of the things in business, low-code / no-code solutions shall be paired with good governance.
Great article! I have a hunch that there’s a lot of “don’t know what they don’t know” happening w/ population that shades towards low code / no code. Once you learn to do things “the engineering way” you realize just how much risk that process can mitigate and how much more stable and modular of a system it enables, with lower overall effort
Ben I'm a big fan of all you do but this is a bit binary and short-sighted. Many low-code tools also offer Git-control like Coalesce or Orchestra. So Broad-brushing all low-code tools as being without Governance is just ridiculous
Oh I am not trying to say that all low code tools lack governance but that they ways team implement the workflows themselves can. Git control alone is not governance, it’s a piece for sure!
Like I can still git control my projects and press the big red button and merge directly into main right, that's because of *me* not because of *tooling*
Also I believe this point only makes your reference to tools having git moot. But I also believe it likely means we are trying to say the same thing
Yes, my point was that you can make things faster which isn’t bad but if you have those cultural issues and have the benefits of low code, you now make bad decisions faster because you never fixed the cultural issues
User error
@hugo with those tools, when you create the pull request into main, are you able to automatically fire off CI checks and have a human-readable diff for the PR reviewer? Also, is it possible to run linters and formatters to make sure the work complies with team standards? (realize w/ low code / no code that’s a bigger lift)
Having worked on several teams that use them as a key part of the process, pull requests are an incredible QA tool, and not all tools allow for building in these practices
Well it depends on the tool doesn't it lol
For sure, but some tools claim to have “git integration” but they’re missing one of the key benefits
Which is a cultural point rather than due to the use of any particular tool
Faster often goes hand in hand with riskier. It's part of the game. As most of the things in business, low-code / no-code solutions shall be paired with good governance.
Hi Ben,
The day after your post, I received this email from Microsoft.
https://info.microsoft.com/US-AccLC-CNTNT-FY24-01Jan-12-Accelerate-Innovation-with-a-Low-Code-Application-Platform-SRGCM11559_LP01-Registration---Form-in-Body.html?wt.mc_id=AID3060137_QSG_EML_651661&ocid=eml_pg430915_gdc_comm_ba
Microsoft Fabric and Power BI have plenty of governance and work with Excel users as well.
Great article! I have a hunch that there’s a lot of “don’t know what they don’t know” happening w/ population that shades towards low code / no code. Once you learn to do things “the engineering way” you realize just how much risk that process can mitigate and how much more stable and modular of a system it enables, with lower overall effort