Hacker News Reader

Comment by apercu | Hacker News Reader

The thing about consulting is that someone needs to verify the output, know what questions to ask in the first place, and provide a throat for the client to choke in the event of an issue. Also, professional insurance. I could be wrong but in the worlds I live in professionally, accountability is still a thing.

View on HN

Yup. There's some places that we'll need that accountability. I suspect that this may be filled by folks that act as "LLM brokers," using AI in the background, while dealing with the legalities, in the foreground.

But in my case, it wasn't nearly so exotic. The LLM helped me to do a much better job, preparing the App Store presentation, Web support, privacy policies, budget prognostication, and app glossary.

I have just had an extremely complex app, pass App Review, in record time (from going into review, to approval). No niggles or bounces at all.

I'm thrilled.

I'd be curious to pick your brain about the process you went through for this. My mental gap here is not even knowing what to ask for a process like this.

Happy to do so. Probably not something a lot of folks here would find interesting, but I'm easy to contact, from my Web sites. People here, often do that.

Basically, my needs are different from others. I'm not working on the next NORAD upgrade, much of my work is open, and the more ChatGPT knows about me, and the app I'm designing, the better. One reason I chose it, was because of this "memory."

TL;DR: I feed it just about every scrap of information about my project as I can. Source files, documentation, screenshots, videos, information about the organization, information about the target demographic, etc.

With all that information, it gives me very useful advice.

It created a great tutorial. I usually write way too complicated ones. It did much better.

In the case of the App Store stuff, it helped me to choose the right privacy report, generated the privacy manifest, and helped me to compose all the copy on the storefront.

I'll probably be releasing the new app, soon. It's already passed review, but I want to make sure that everything is kosher, before releasing. It came together so quickly, that I have the luxury of time. I just need to release before (or as) iOS27 comes out.

When using LLM's to help write things like tutorials, how do you reduce the verbosity firehose?

Even though I use MD/skills and other methods, I have remind models that they are not paid by the word multiple times a day.

Oh, I don't really do much more than have feedback loops, where I review the output, then ask for things like less verbosity, or a lower-level vocabulary, etc. I like to apply this at each application, rather than make a blanket rule, as each page may have a different audience.

For example, I have made a tutorial, which is meant to be a "quick reference," from within the app (Use Safari to view the page), but I am also developing a "walkthrough," to show possible funders (we're an NPO). The walkthrough is a higher-level vocabulary than the tutorial. The LLM deals with stuff like making sure to keep the glossary consistent, etc., but I like to have the final say on the output.

I'm pretty sure that I can force the LLM to use certain levels of vocabulary, through the .md file that describes the default setup, but choose not to do it.

I am still in that "trust, but verify" stage of my relationship with LLMs.

Reply on news.ycombinator.com