@XSGeek
I'm deconstructing the sequence of LLM prompts that will build an SOP for wildfire mitigation.
The really interesting process is designing the QA procedures to minimize the impact of LLM hallucinations.
@heatherdale @XSGeek
I'm also still on the non-technical side. It's my day-job. I write requirements, specs and design process flows for clients.
Then AI showed me that I could actually code. After a year coding with AI, I've been able to make a lot of progress building an MVP. I'd have needed 2-3 engineers to do what I've built by myself.
@heatherdale @XSGeek
I do not. But, I have found that structuring your requirements in a tabular format is adequate. So, a spreadsheet is how I start.
Flesh out the Design Principles first. They evolve as you progress.
I'm only now starting to understand how to systematically build UX requirements. So, I'm no expert.
Process design is ok to start with tabular format. But, flowcharts are still the best way to finish.
@heatherdale @XSGeek
(CoSo isn't pushing notifications, so I just saw this now)
I think flowcharting is an excellent way of getting your thoughts clear. Your process does sound complex. But, if you don't try to flowchart it, you may be allowing it to become more complex than it has to be.
I often iterate on the flowchart. Yes/No branching (Questions that can only be answered as Y/N) is a great exercise to determine what is most important at what time.
@jurban
Thank you so much for these details! I wish I could see it. It sounds fascinating and also helpful if I could implement something like that. I believe I put a lot of faith in the programmers I hired. Like if I just explain very thoroughly to the programmers what has to happen they will know how to make it happen. But you are saying there is nuance. Kind of makes me nervous that I can’t play around with it myself 😕
@heatherdale
This past week I've been documenting the process I thought I understood months ago. I thought I needed only about 3 modules.
I just counted 56 process steps this morning.
I look at documentation like playing a piano. If it doesn't sound right, play it differently.
I'm starting off using a tabular format to get the macro perspective. That's the 56 processes.
The flowchart should be more simple and will be informed by the tabular format.
Better than bad code!