181–190 of 230 posts
This is basically what I want, but with a UI that non-techie spouse wouldn’t mind using. Though that doesn't seem to be your intended direction, which is fair. We use Apple Reminders for grocery lists and Paprika for recipes, but something a little more organized than just a shared note for these sorts of things would be great. I will probably check it out for myself though.
If you can reliably extract line items, scope, and vendor info from those and link them to a project, that's where you'd actually save real time.
The TUI is nice but that pipeline is what I'd use this for.
I want MiBoat ;)
Earlier quoted context omitted.
I've been working on something like this the last few months specifically around service quote analysis (repairs, construction, hvac, auto, etc.) and it's really cool. I think LLM analysis is the way to go because the amount of complexity is absolutely staggering - just to start the difference in quality and information available on a quote is drastically different between vendors within the SAME vertical. Then to do…
This is in line with my thinking, can you say more about how intent changes how you would use a system like this? I had a really complex negotiation for car repairs (goodwill warranty, balancing a long list of repairs/recalls etc) which was pretty time sensitive. If I had already had my service record in a structured format along with the manufacturer's policies I feel like I could have responded with better preparat…
I do have the concept of an "asset" which could be a car, house, etc. and with enough basic info it's pretty easy for the LLM to cross reference common problems, or at least suggest questions that you should follow up on.
I'm leaving intent pretty free-form for now, the most friction I'm willing to add is 2 things:
- Basic enum preferences around budget and flexibility to help with prompting
- A claude code style "a few questions" follow up
Any additional form friction I think gets too complex.
It's funny, a lot of my research has been from subreddits for auto, homeownership, questions for people who work in trades, etc. Every time someone asks "is this quote fair", the response from the experts is almost always "But what do you want"
So in a time-sensitive repairs scenario, intent could "What get's my car safe to drive again for daily commute.... or for a long roadtrip". The output analysis could recommend which fixes are highest priority, where work could be split up, delayed etc.
Earlier quoted context omitted.
I wonder what the state of workflow engines is these days. Back in the (distant, distant) past, everything seemed to use Lotus Notes. Today, there are oodles of workflow engines of all shapes and sizes, but asides from domain-specific stuff like Salesforce, I hardly hear anyone mention them.
I helped a legacy Lotus Notes application reincarnate once, and it was impressive how reasonably solid it's ability was to be offline-first, and mobile first, and how fewer sychronization/replication errors there were than I expected.
One thing that would make this extra trustworthy for day-to-day use is a strict dry-run/preview mode: show exactly what fields/rows would change before writing state or triggering integrations.
Also +1 for stable entity IDs and an append-only history table (timestamp + source + diff summary). That makes rollback and auditing much easier when automations or scripts misbehave.
This is quite cool. Makes me philosophical: isn't it odd, that this is like an Excel template? Like a "domain model" template? In this case, presented nicely in a TUI that makes basic CRUD workflows work. Most SaaS companies are just that: 1) Curated domain model (stored in their cloud db) 2) Some way for users do to almost raw CRUD on the tables 3) Curated high-level domain specific workflows that do n CRUD calls un…
Web UI's for power tools are generally not a good idea. A browser will always have limitations and not quite reach the level of e.g. a TUI. On the other hand, TUI's as you point out has some serious limitations on its own. So the answer is native app - I think what the world need is a super fast native spreadsheet that is NOT Excel. Kinda like a combination of Excel, TUI, and MS Access in one. Fast like Numbers.app,…
I’m using Google Sheets for house and cars. Columns that should be easily grouped are using data validation and yes - few times deep into the experiment (because I’m sometimes lazy and miss some data - so experiment is good name) I’ve changed domain a little by adding columns. It meant empty values for existing rows - that I couldn’t fill in most cases, because a lot of time passed.
Reading many comments here I think we will create multiple frameworks/standards like always and some tools will be missing things others have :(
Funny thing is sheets works good and with scripts I can (still for free in terms of money) send notifications to selected channels or do some automated actions (like check disks status or order something automatically)
Edit: sheets have sync across devices too. Single SQLite for this specific case, having less nerdy people at home is an disadvantage.
I just use org-mode + lots of recurring tasks.
Like car.org has monthly tasks for check fluids, clean inside, clean outside. In April and October theres a task to remind me to change tires and as I'm German a task to remind me yearly to check the first aid kit (you get a fine if its expired and they spot it when they stop you).
So, almost every appliance has its org-file with routines. Same for me and my family, check vaccinations, see the dentist ...
So, if you are already using org, theres no need for an additional tool. Plus, its all text, just throw it in your git. Also, there's tools like beorg to have your org on your iPhone.
This is quite cool. Makes me philosophical: isn't it odd, that this is like an Excel template? Like a "domain model" template? In this case, presented nicely in a TUI that makes basic CRUD workflows work. Most SaaS companies are just that: 1) Curated domain model (stored in their cloud db) 2) Some way for users do to almost raw CRUD on the tables 3) Curated high-level domain specific workflows that do n CRUD calls un…
Web UI's for power tools are generally not a good idea. A browser will always have limitations and not quite reach the level of e.g. a TUI. On the other hand, TUI's as you point out has some serious limitations on its own. So the answer is native app - I think what the world need is a super fast native spreadsheet that is NOT Excel. Kinda like a combination of Excel, TUI, and MS Access in one. Fast like Numbers.app,…
There's no reason you can't jam a TUI into a browser. Perhaps to the surprise of both kinds of user, but it's possible.
> I think what the world need is a super fast native spreadsheet that is NOT Excel.
> I'd use that. But it needs to have a keyboard centric operation
You should boot up an emulator and check out the OG: Lotus 1-2-3. Keyboard driven, extremely fast, all written in 16-bit assembler for the original IBM PC running at, what, 4MHz?
It's because of Lotus 1-2-3's use of F2 for "edit cell" that F2 is still "edit" or "rename" in most applications.
(you can then continue the tour with WordPerfect and Borland Turbo Pascal, if you like light blue)