Part 13: A Second Opinion, Using One AI to Check Another

Digital Den has an Events section, but until we start hosting our own live builds and video sessions, it was empty. On October 5 I decided to turn it into an editorial calendar of outside tech events, like conferences and product launches, that would give readers something to watch for and give me ideas for articles.

Confirmed, expected or rumored

I asked Claude to act as a tech researcher and find upcoming events. It came back with a list split into confirmed events and rumored ones, because a rumored date that slips would look bad on a site that's supposed to help people sort fact from rumor. It also suggested that every event should carry a status and an end date, so events that are over drop off on their own.

A second opinion

I'd given ChatGPT the same task, and it wrote a detailed prompt for changing my Events setup in Sanity. I pasted that prompt to Claude with a clear instruction: don't do anything with this yet, just give me feedback. That instruction matters. Asking for a review rather than action keeps you in charge of what actually happens.

The review was useful. ChatGPT's list of event categories overlapped in places, so Claude suggested trimming it to categories that don't. It added fields for topics, an end date, an all-day flag, a status, private editorial notes and a show-on-site switch, all optional so nothing already in place would break. And it caught a subtle problem: if the site decides an event is "upcoming" by its start date alone, a four-day show like CES disappears from the list on day two. The fix is to compare against the end date when there is one.

I agreed with the analysis, and noted that the dates in ChatGPT's prompt had only been examples, not checked facts. Then I said to move forward. Before changing anything, Claude checked my live Sanity project first and found the Events section didn't have any records yet, which made the change safe to make.

Looking back

This is a good place to pause the series. In about three months, Digital Den went from two static mockups to a live site with member accounts, a community board, daily content drafts, real email and an editorial calendar. I didn't write most of the code. My job was the one I've done for thirty years: knowing what we're building and for whom, making the calls, and checking the work. The AI tools changed how fast things move, not who's responsible for them.

The lesson

Use AIs to check each other, and ask for feedback before you ask for action. A second opinion is cheap, and it catches the problems a single source misses.

Try it yourself

Next time one AI gives you a plan, paste it into another and say: "Don't do anything yet. What's wrong with this, and what's missing?" Then you decide which suggestions to keep.

The build continues, and so will this series. Follow the project to catch the next entry.