I've found almost every "low code" tool unintuitive as hell. SSIS is most certainly on that list. And because of that, it's never been my choice for any ETL or data tasks.

But I have come to appreciate it over the years. It's a robust product with excellent logging, a form of version control (if you use the SSIS catalog), and decent encryption to protect passwords. And though I may have never liked it, lots on non-developers seem to love it. If it gets the job done for them, so be it.

So what's an SSIS developer to do? For on-premises folks like me, I'd avoid another low code/no code solution. 20-ish years ago, I used VBScript (or even DOS batch files).

As the years went by, I moved more towards C# console apps or PowerShell scripts. Seeing all the code in front of me (and not having to find a needle in an unintuitive GUI hay stack) made me much more productive--both on the development side and the support side.