Working through a Development Process

I have recently been writing and updating various bits of code recently. Through working on a Google Summer of Code project as a mentor, I have found that I am updating how I use repositories.

Like many developers, I use varying git repositories such as Gitlab and Github among others. My first year on the Google project was spent looking at and building the documentation locally. This year, I spent time on the Github workflows to build across architectures and the associated documentation and making sure that the code built on a Mac using Apple Silicon. I did some work on a manifest tool that still needs some work. A frustrating part is that there does not seem to be a standard for this.

While the documentation building and testing did drive me slightly mad, it did get me looking at the Python mkdocs package. As part of recent work where user facing documentation is useful, I began to implement mkdocs on an irregular basis. It has a particular way of being set up for Github that I found tricky if I missed a step. Since this is a regularish task, I wrote a short bash script to make my life a but easier for the basic local repository.

As a small project, I am finding it useful to develop my knowledge of bash, which sometimes feels like it is stagnating as I run through a small set of tasks. I also hope that it will continue with updating my repositories for varying processes and shaping them to help other colleagues and users.

As a side thing, I noticed that I end up having a template to set up automation within an automation tool, which places a reliance on making sure that the templates are correct.

No Comments

Leave a Reply

Your email is never shared.Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.