MyCmd and MyProject Weekly Progress Report: 2025 Week 04

MyProject Demo

My demoable goal for the week was to be able to execute mycmd myproject run for tasks with 0 arguments.

The above screenshots show executing various tasks defined in this myproject/main.

MyProject Updates

I pushed five commits this week, including the following changes:

• Documenting concepts and conventions in the Concepts and Conventions Document and clean-ups related to those documented conventions.
• Moving all user-facing functions (those users call in their own task definition files) into a support library that is loaded from the main library.
• Implemented project:task.execute and project.execute_task as well as the minimal run command.

Next Week

My next area of focus will be supporting multiple task definition files in a project, other than just myproject/main. Next week will be basically working on the project internals and then allowing mycmd myproject list-tasks and mycmd myproject run work with multiple task definition files.

I have been thinking a little bit more about project organization and trying to be more explicit about the differing layers of my systems, between internal implementation, the API surface that is exposed to task definition file writers, and the user interface exposed to those that execute tasks using mycmd myproject run. There are many challenges that come from working in an implementation language like Bash and I have some things to think about to make sure my code is the most robust and user friendly.

All of my MyCmd and MyProject Weekly Progress reports will be linked from here.