News for hackers. Stuff that matters.
Re:Apache NiFi by closeparen on Monday May 11, 2020 @03:32PM (#23146023)
I have not found that argument persuasive to the managers who believe that coding is inherently wasteful if what you’re trying to do is technically possible in a workflow builder GUI.
Re:Apache NiFi by marcinzm on Monday May 11, 2020 @03:39PM (#23146090)
That's true but, personally, I just avoid working for managers like that.
Re:Apache NiFi by closeparen on Monday May 11, 2020 @03:48PM (#23146186)
I can avoid this at the line manager level, but Directors love these things.
Re:Apache NiFi by tatersolid on Tuesday May 12, 2020 @05:49AM (#23152215)
No, we don’t.
Re:Apache NiFi by monstrado on Monday May 11, 2020 @05:31PM (#23147337)
NiFi is also very useful for visually chaining together scripts (e.g. foo | bar | baz). In NiFi you can use ExecuteProcess and ExecuteStreamCommand to basically do what pipes (|) does. Further, the intermediate data between each process is backed by a WAL. You can also mix and match your pipeline, for example you can mix-in some of your custom scripts, and periodically use built-in processors that are provided to do additional stuff (e.g. PutKafka).
Re:Apache NiFi by oneplane on Monday May 11, 2020 @04:40PM (#23146784)
Compare coding to managing and suddenly they're on board. In practical terms: a checklist for work can achieve the same thing as a manager verbalising and visualising that checklist. Every argument the manager has against that is the same as 'gui workflow' vs code.