IT/Software career thread: Invert binary trees for dollars.

  • Guest, it's time once again for the massively important and exciting FoH Asshat Tournament!



    Go here and give us your nominations!
    Who's been the biggest Asshat in the last year? Give us your worst ones!

Palum

what Suineg set it to
27,399
43,507
I'm not sure what you mean. Azure Workflows all do the same thing and specifically things like Logic Apps have tons of pre-built functionality. "Development" in azure is done via a web browser with drag and drop shapes. Well, you can get plugins for VS and would want to for git/repository support but the point is these "low code" products aren't doing anything special at all. Unless its some super niche, industry specific thing.
OK. You're the expert. There's no need to integrate front end, back end, integrations and workflow management in a single pane of glass.
 

ToeMissile

Pronouns: zie/zhem/zer
<Gold Donor>
3,302
2,165
Yes we're deploying a lot of no-code for back office processes (accounting, purchasing, payroll, HR, recruiting, etc.)

No code and low code are somewhat marketing lies. It's true that you can create certain solutions without any custom "code" (at least in some platforms), but even then you have to understand program control flow, logic, integrations, data structures, etc. in order to create anything substantial.

To give an example, we have a no code workflow for purchase requests, and in order to make meaningful human readable and informative instance IDs for process tracking, we had to use regex to replace GUIDs. There's no earthly way random accountant person is going to figure that out on their own.

What this means for us is that some management, some devs and some BAs work on developing solutions as DT projects come up. Most business users are completely incapable, but a few may be able to manage some admin and updates.

Feedback from my devs is that it's really effective and time saving IF your solutions fit the box the platform offers. For us we went with Nintex over Outsystems (and others) because we had a high focus on paperwork reduction. Nintex has much more robust form building/controls, whereas Outsystems has more "app focus" (like MS PowerApps). It reduces a lot of technical debt from random one off web apps to handle one piece of paper some guy made 15 years ago.
Power Apps/Automate can be pretty convenient for places where O365/Sharepoint/etc is in heavy use, and there isn't 'proper' dev support/teams to create tools. That said, they're both kind of like Access; enough rope to do some cool stuff, or hang yourself.
 

Palum

what Suineg set it to
27,399
43,507
Power Apps/Automate can be pretty convenient for places where O365/Sharepoint/etc is in heavy use, and there isn't 'proper' dev support/teams to create tools. That said, they're both kind of like Access; enough rope to do some cool stuff, or hang yourself.
We reviewed those. They are very bloated for our purposes. Automate ends up a nightmare of distributed workflows because it didn't have a high level way to track and manage parent/child/component relationships. Power Apps is just visual basic.

The killer though is the fact that these mofos wanted $$$$ to integrate into SQL Server because it's a premium connector. Fuck that noise we already pay them millions for enterprise.
 

ToeMissile

Pronouns: zie/zhem/zer
<Gold Donor>
3,302
2,165
We reviewed those. They are very bloated for our purposes. Automate ends up a nightmare of distributed workflows because it didn't have a high level way to track and manage parent/child/component relationships. Power Apps is just visual basic.

The killer though is the fact that these mofos wanted $$$$ to integrate into SQL Server because it's a premium connector. Fuck that noise we already pay them millions for enterprise.
Yeah, the premium connector stuff is shitty. You can kinda get around it for smaller use cases but it’s a pain.