41–50 of 69 posts
What is an “antigenic AI” or “antigenic workflow” in this context? It’s used so consistently that I’m not sure if it’s just careless editing or if it’s something new I don’t know about.
What is an “antigenic AI” or “antigenic workflow” in this context? It’s used so consistently that I’m not sure if it’s just careless editing or if it’s something new I don’t know about.
Seems the writer made a typo in the prompt.
Neither please god. We used Node-Red at a previous job for integrating some third party software, total disaster, from upgrading, using JSON for code reviews, to overall performance. Its a fun toy, leave it at that.
https://github.com/daniel-payne/functions-templates-manager
https://discourse.nodered.org/t/node-red-and-vs-code-integra...
Earlier quoted context omitted.
Seems the writer made a typo in the prompt.
Funny enough, I choose not to use AI to review my stories, as I find it results in an article that is not in my own voice. As i am Dyslexic, I will update this typo.
The article made me check node-red so it did provided something valuable.
Isn’t there something more native to the AI landscape? I know both make for excellent all purpose digital glue but would think that’s last resort
What is an “antigenic AI” or “antigenic workflow” in this context? It’s used so consistently that I’m not sure if it’s just careless editing or if it’s something new I don’t know about.
Earlier quoted context omitted.
I'd be happy to take your experience into account in case I'll need to vouch this in the future. But unfortunately it's not very clear what shortcomings of Node-Red were a problem for you. Could you rephrase your experience, focusing on what you believe Node-Red does wrong?
I'm also interested in this. My workplace is looking into this, and my intuition says no, but I'd really like to hear other people's experiences, both positive and negative ones.
Once you start to get big and complicated with node-red you will have this issue. But the rest of node-red is fantastic. It also covers a fix for git code reviews and integration with external testing frameworks.
--------------------------------------------------------
I hope this can help anybody having the same issues as I have when writing long functions in node-red editor.
Coding anything over 50 lines become difficult to work with, or trying to view multiple functions at the same time. The rest of node-red is fantastic!
----------------------------------------------------
I understand nothing of this article. What does it mean by "n8n" lacks a UI? All it has is a UI, what use cases does the UI not handle? The writing is very poor and does not make sense at all.
agreed, I'm running it on my localhost right now and it's got a full WYSIWYG interface. This article is slop
However I have updated the article so it is much clearer, the UI that is missing from n8n is not WISIWIG, but a management dashboard, to be viewed once the system is live. I have added the following:
"To be clear here, I did not mean the UI that you use to create flows with, both systems are drag and drop flow creators. The issues I come across is visualizing what is going on inside of a system once it is created and up and running."
Neither please god. We used Node-Red at a previous job for integrating some third party software, total disaster, from upgrading, using JSON for code reviews, to overall performance. Its a fun toy, leave it at that.
I'd be happy to take your experience into account in case I'll need to vouch this in the future. But unfortunately it's not very clear what shortcomings of Node-Red were a problem for you. Could you rephrase your experience, focusing on what you believe Node-Red does wrong?
2. Often times you end up writing code to help support node-red, you must avoid this at all costs because you end up shifting more and more into code bases, making node-red pointless.
2. Lots of sub menu "advanced" functions that you will need to use for any complex flow.
3. Observability is poor out of the box, especially if you use a service like datadog or NewRelic, we ended up using a catch all error handler that just shipped events to NewRelic.
4. Poor out of box defaults for security, mainly authentication
5. Conflict resolution sucks, you have to JSON stable stringify the changes to ensure you can deal with conflicts and conduct proper code reviews.