When you're creating a #SaaS you may receive weird testing messages and find bugs because it messed up the name π€£, it was a real incident from another site, so only thing to do was fix the messages of this integration @monitorito #buildinpublic#Automation
One of the best things (from the developer POV) of using nocode tools, is that you can make the change and be live in a matter of seconds, that is like video games immediate feedback loop. For non developers is a door for a new world.
I started to work on the notify workflow of my #SaaS, this @n8n_io workflow is called by another (in charge of ETL from different sources), maybe it's not the best design yet but you can see how easy it's to test values before sending a msg. #buildinpublic
I was thinking about setting lambda functions to execute every minute, now I think using my own @n8n_io instance would speed up the MVP development tremendously.
Would you start with the easiest or the hardest part when working on your side business, the low hanging fruit gives traction, but I don't want to leave an important part to the end.
So much to do over the holidays, a little roof, programming side project (come up with a name also), maybe #buildinpublic in YouTube?, want to record some videos for another channel, use my new pool, make some woodworking micro projects.... I just ran out of time. Haha
Can you explain me the #buildinpublic concept? I mean, what do you share just starting, the idea, the name, the progress, will someone steal the work/idea?