I heavily utilize ChatGPT to generate .ics files to populate my Apple Calendar with various events, but I have been wanting to upgrade my time management and also use the Reminders app.

I recently used ChatGPT to help me populate a Trello board with tasks associated with a project I am working on, but I was getting annoyed with having my workflow split across Apple Calendar and Trello. I exported my Trello board as a CSV and was trying to have ChatGPT turn it into a file I could import into Reminders, but as it turns out, this is not easy.

.ics files do contain syntax for reminders tasks with due dates that populate the Apple Calendar, but generating an .ics file with only reminders tasks and importing into Calendar doesn’t actually work. Calendar recognizes that the .ics contains Reminders tasks and opens Reminders to import the tasks, but Reminders returns an error because it doesn’t support import, it only supports export to Calendar.

I found that Reminders has a Reminders.scpt dictionary file within the .app package that details .applescript commands that can create new tasks, so I fell into the world of AppleScript. The issue with AppleScript is that it was created in the 80s and hasn’t been updated since 2013. It has no native CSV support and is pretty clunky.

AppleScript does have text file support, so I was able to have ChatGPT convert my CSV into a .txt that I could parse with AppleScript. This allowed me to automate the creation of tasks in the Reminders app from my Trello CSV, but it was annoying and I still feel like there must be a better way.

Does anyone here use AppleScript regularly and know its full capabilities?

Also, are there any good resources out there for learning more about AppleScript? The Apple documentation is very out of date and it seems like more of a legacy language than something Apple regularly maintains.

The year is 2025. The C programming language is something like 50 years old now - a dinosaur within the fast-moving environment of software development. Dozens of new languages have cropped up through the years, with languages like Rust and Go as prime contenders for systems-level programming. Bootstrapping a project in C these days will often raise eyebrows or encourage people to dismiss you out of hand. Personally, I've barely touched the language since I graduated.

Now, with all that said: I still consider learning and understanding C to be key for having an integrated, in-depth understanding of how computers and programming really works. When I am getting a project up and running, I frequently end up running commands like "sudo apt install libopenssl-dev" without really giving it much thought about what's going on there. I know that it pulls some libraries onto my computer so that another program can use them, but without the requisite experience of building and compiliing a library then it's kind of difficult to understand what it's all about. I know that other languages will introduce this concept, but realistically everything is built to bind to C libraries.

System libraries are only one instance of my argument though. To take a more general view, I would say that learning C helps you better understand computers and programming. It might be a pain to consider stuff like memory allocation and pointers on a regular basis, but I also think that not understanding these subjects can open up avenues for a poorly formed understanding about how computers work. Adding new layers of abstraction does not make the foundation less relevant, and I think that learning C is the best avenue toward an in-depth understanding of how computers actually work. This sort of baseline understanding, even if the language isn't used on a regular basis, goes a long way to improving one's skills as a developer. It also gives people the skills to apply their skills in a wide variety of contexts.

I'm no expert, though: most of the programming I do is very high-level and abstracted from the machine (Python, Haskell, BASH). I'm sure there are plenty of folks here who are better qualified to chime in, so what do you think?