Every dev hates the word 'gluecode'. It feels dirty, if you like building everything from the ground up. There is another way.
This is a codex, there is no canon. This is just a collection of tools that, when hung in a row, with the right mindset, provide the option to build solutions faster, with less code, and less vendor lock in.
My first version of the low-code cookbooks (which is still up) was more of spreedsheet, with search options. Where it only has 15 options, it was fine. But it outgrew the format. So this approach, while manual, is designed to map to the thinking process I take when I start to map low-code and no-code options to a clients use case.
| Storage | Can I put stuff in it, and it remembers? | 12 options | |
| Hosting | Basically, options to get off of AWS S3. | 7 options | |
| Workflows | Tools to make information move. | 7 options | |
| Comms | Every stack needs a way to communicate. Customers like to get receipts when they give you money. | 3 options | |
| The "Big Boys" | Even the low-code solutions have vendors that offer it all, and provides an end to end enterprise pleasing options. | 3 options | |
| Who are you? | i.e. identity management. Identity can be stack buster. How do you know who your users are. | 3 options | |
| Strange Use Cases | This is at the wild card category. Very wild. These are low-code solutions that fall way outside their terms of use. | 3 options | |
| Ai Tools | This category is growing faster then expected. There are huge number of niche solutions that fit really well into a low-code stack, and can dramatically impact the costs, both in a good and a bad way. | 3 options | |
| The Firehose | Is there groupings are not what you need, you can always just drink from the firehost. Meaning query database directly. | 3 options | Cookbook |
Enough people know about my strange obsesion with not doing the think that I have spent my career learnign to to; coding. Every week I zoom with CTOs, lead devs, and every time they hand me a new low code solution.
First I will offer a simple disclaimer. This approach is my solution to breaking the curve of the tech curve. If you have a solution to submit, then the best way is to find me on LinkedIn, make a connection request and share. I do not really read email. (Voice mail is no-go)
Connect on LinkedIn