Yes and no. If your goal is to learn how to code manually, then you are “cheating” in that you may not learn as much.

If your goal is to learn how to utilize AI to assist you in daily tasks, I would say you’re not.

If your goal is to provide value for others through how much you can produce in a given amount of time, then you’re definitely not.

The only thing I can think of is when the user edits meetings en masse – say they’re rescheduling their whole day and are simultaneously creating and updating the timing of blocks. That probably will be functionality I’ll want to implement (allowing users to enter “edit mode” for their schedule).

That’s a good question though, other than that case it wouldn’t be relevant. Plus, I probably would implement a createOrUpdateMeetings() API rather than createOrUpdateMeeting should that occur. Since Create and Update are both relatively simple APIs to implement, I think I’ll stick with those for now and possibly shift over to createOrUpdate if the need comes up. Thanks for the insight!

Edit: After thinking about it and tinkering a bit more, I ended up going with the createOrUpdateMeetings() approach. At least on the surface, it seems simpler and cleaner for my use case – there will be times where my client will have a list of both existing and new meetings to send over. Still open to suggestions from everyone though, people have made good points.