People have a bias to want to believe something works in all cases, when it seemingly offers benefits to them. Especially when there’s a sunk investment involved.
This was always kind of a problem with the “this will make icky programmers obsolete” techs. Like, so did MS Access and a couple generations of click-and-drag ‘no-code’ stuff. Not to mention Rails; remember when everyone thought that would radically increase productivity? I’m pretty sure that was entirely because it was well-suited to “make a todo list/fake twitter/whatever in half an hour” demos.
Don’t bother with this if you want to get promoted. Others have discussed this in thread and are right. If you build beautiful, simplified abstractions, your skill will be taken for granted as these interfaces appear obvious once discovered (by virtue of their proximity to truth, incredibly difficult to create, easy to verify). If you are in even a reasonably large org, go the other way. Be an Architecture astronaut. Build complex, clever stuff that is deliberately high cognitive load. Get your bus-factor as close to one as possible. Go the other way only if your comp is directly tied to company performance.
I used to consult on this type of thing. I’m not entirely convinced this is what’s happening here but it’s close enough, and is a well trod playbook - dress up the mundane in theatre and performance, create a taxonomy that’s specific to you, then sell access to the thing.
Next step is to try flood the SEO zone with your thing. It’s great if you can piggyback other key terms (deep *, agents) and.. I’m already bored writing this up it’s so [what’s the word for sheer resigned exhaustion at the capitalist corporate soul kill that is this type of work]
Reminds me of high write speed on SSD (1.5 GB/s continuously to TLC) means 1 TB SSD warranty expires instead of 5 years just in less than 5 days (600 TB written).
