Heh, turn excel into etl. Dump pure data in whatever format (a mini data lake). Project as tables/lists of data. Present in an excel style.

The problem with that pitch is that the venn diagram of people who could make an excel like thing and the people who are power excel users has a small intersection

like excel only works if you can do like... pivot tables and such

Perhaps. Excel is unintimidating because it's such a direct data grid. Complicating it could be too much. But then I think Access DBs demonstrated how many power users in businesses would get on and do things if they had to power. Echos of "low-code" in this.

You might be onto something 😉 https://techcommunity.microsoft.com/t5/excel-blog/announcing-lambda-turn-excel-formulas-into-custom-functions/ba-p/1925546

But the performance

wrong message correct message

a middle option is inlining the diff 😁

The Welcome message tells recruiters specifically to use the #jobs and #remote-jobs channels only -- but it seems recruiters don't bother to read that...

You could mash up these libraries depending on your use case: https://github.com/viesti/sql-to-spec https://github.com/Provisdom/spectomic https://github.com/stathissideris/spec-provider

Cons: you'd have to do it manually (time-consuming) Pros: you'd have to do it manually (being explicit about the modeling / conversion is probably worth it long term)