[bravura]

The text-based software that would eat work management is one that embraces the incumbents rather than avoid them.

I want a bidirectional SaaS <=> YAML/JSON adapter. So that I can push and pull our CRM (and other SaaS utilities like project management) into a common (schematized) YAML format.

The YAML then can be analyzed and modified using LLMs and/or stored in git.

And then use the bidirectional sync to reconcile conflicts and push.

So I can do work processes on the console, and still collaborate with people who want the native web UI.

[danielrothmann]

Agreed, this is on my mind as well.

Thinking of Terraform, you have data blocks that can grab data from an external source. Still trying to grok what would be a convenient way of doing something like this - whether that gets generated to DSL, or if data pulled in dynamically as you build the org graph...

Having your plain-text workspace as a unified structural source where you pull in data from external systems would be potentially powerful.

[rirze]

You'll unfortunately have to agree on some sort of state representation for each source and then delve into those APIs to extract that information

[montague27]

Hi there, I've made my own text-based todo list with compatible web view which is kind of similar to what you did. (though far from completion)

There's a sync engine behind it so the UX is extremely responsive.

Link: https://mglogi.com/portfolio

[everforward]

I’d be happy with SQL access, which I think gets to roughly the same place.

I’ve done something like what you’re talking about before for a CMDB, though it was one way YAML -> DB sync. Many to many relationships were a pain to view, there’s not a great way to put them in YAML that makes them easy to read. Can’t embed them because then you have multiple copies and which one is the real one. References suck because you can’t see the relationship and the related objects at once.

The real killer is permissions, though. Your sync tool basically has to have admin privileges, which means permissions have to be checked at merge time, and then you’re rebuilding the entire permissions flow as a git hook.

SQL with RLS is capable of implementing permissions in a way that works for both API access and direct SQL access. I get the feeling few companies do it, but they could.

[swoorup]

I would like the native web UI when I am being too lazy, and terminal when I am in the zone..

[kstrauser]

Huh. Could those be git submodules? Like you’d have all your personal state in foo/ and then clone the work state into foo/work/ .