Dev Log #3: Building the Website

Disclaimer: The coding-time tracker for this project is inaccurate by approximately 5–6 hours due to starting this project before stardance.

This week, I focused on building the main website for the AI calendar system. The website now includes a calendar interface where users can view and manage events, an AI chat section that allows users to create events through natural conversation, and a device pairing page for connecting an ESP32-C3 reminder device.

The biggest challenge I ran into was getting the AI to properly use tool calls. Sometimes the AI clearly understood what the user wanted, but instead of calling the event-creation function, it would simply respond with text describing what it would do. This led to a lot of testing and experimentation with prompts, tool definitions, and API settings until the AI consistently triggered the correct functions.

By the end of this development session, the website was functional, the AI could create events through tool calls, and the device pairing system was successfully integrated into the interface.

Dev Log #3: Building the Website

Disclaimer: The coding-time tracker for this project is inaccurate by approximately 5–6 hours due to starting this project before stardance.

This week, I focused on building the main website for the AI calendar system. The website now includes a calendar interface where users can view and manage events, an AI chat section that allows users to create events through natural conversation, and a device pairing page for connecting an ESP32-C3 reminder device.

The biggest challenge I ran into was getting the AI to properly use tool calls. Sometimes the AI clearly understood what the user wanted, but instead of calling the event-creation function, it would simply respond with text describing what it would do. This led to a lot of testing and experimentation with prompts, tool definitions, and API settings until the AI consistently triggered the correct functions.

By the end of this development session, the website was functional, the AI could create events through tool calls, and the device pairing system was successfully integrated into the interface.

Dev Log #2: Fighting the API

I thought adding the Grok API would be one of the easier parts of the project. It turns out I was wrong.

Since I had never worked with the API before, a lot of my time was spent tracking down small syntax mistakes. The API was very specific about how requests needed to be formatted, and even tiny errors could cause everything to fail. For example, at one point I wrote:

payload = {
    "model": GROQ_MODEL,
    "messages": [{"role": "user", "content": message}]
    "temperature": 2,
    "max_tokens": 500,
}

I forgot the comma after “message}]” which caused an error and took me longer than I’d like to admit to find.

The frustrating part was that the code usually looked correct at first glance. I would spend time checking API keys, debugging functions, and rereading documentation, only to discover that the issue was a single missing character. Now I know to read the documentation more and also if you like this project like and follow me.

Dev Log #2: Fighting the API

I thought adding the Grok API would be one of the easier parts of the project. It turns out I was wrong.

Since I had never worked with the API before, a lot of my time was spent tracking down small syntax mistakes. The API was very specific about how requests needed to be formatted, and even tiny errors could cause everything to fail. For example, at one point I wrote:

payload = {
    "model": GROQ_MODEL,
    "messages": [{"role": "user", "content": message}]
    "temperature": 2,
    "max_tokens": 500,
}

I forgot the comma after “message}]” which caused an error and took me longer than I’d like to admit to find.

The frustrating part was that the code usually looked correct at first glance. I would spend time checking API keys, debugging functions, and rereading documentation, only to discover that the issue was a single missing character. Now I know to read the documentation more and also if you like this project like and follow me.

Dev Log 1

Discamer time is off by about 5 hours- joined Stardance midway through development.
The project is an AI-powered calendar assistant that allows users to create and manage events through natural conversation.
Users can speak to the AI, and their speech is transcribed into text before being sent to an AI model such as Grok or Llama.
The AI analyzes the request and generates tool calls to create, edit, or manage calendar events automatically. After the tool call is executed, the calendar is updated and the user receives confirmation. I also worked on integrating a companion reminder device that provides physical notifications for upcoming events.
One of the most interesting parts of the project was building and understanding the AI pipeline that connects speech recognition, AI processing, tool calling, and calendar management into a seamless user experience.

Dev Log 1

Discamer time is off by about 5 hours- joined Stardance midway through development.
The project is an AI-powered calendar assistant that allows users to create and manage events through natural conversation.
Users can speak to the AI, and their speech is transcribed into text before being sent to an AI model such as Grok or Llama.
The AI analyzes the request and generates tool calls to create, edit, or manage calendar events automatically. After the tool call is executed, the calendar is updated and the user receives confirmation. I also worked on integrating a companion reminder device that provides physical notifications for upcoming events.
One of the most interesting parts of the project was building and understanding the AI pipeline that connects speech recognition, AI processing, tool calling, and calendar management into a seamless user experience.