![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/916c1d50-e579-4163-a4d2-ebec5dbaee5b.png)
Well you know if only they were wealthy enough to become a vegan in the first place they could buy the good looking carcasses the mean Vegans are making them eat! /s
Well you know if only they were wealthy enough to become a vegan in the first place they could buy the good looking carcasses the mean Vegans are making them eat! /s
I am a fan of structurizer and the C4 model in general.
I would use a single .dsl file and add the relationships and entities as you discover them. You can apply tags , and then write filtered views to only show specific tags for sub systems or workflows that a user will follow.
you can pair this with markdown/text notes that reference the png files of the views that structurizer will output.
For keeping track of tasks on my projects i use todo txt. For each of my projects will drop a file named todo.txt in the root. each line is a task, and i order them based on priority. I can walk away from it and when i start working on the project again, i have an simple way to see the list of tasks i have laid out for this project.
I personally find it less useful to see the “big picture” of all tasks, and this lets me focus on the details of my projects without forcing a bunch of structure.
VS Code’s extension system makes it pretty easy to build your own code snippet extension. I use my own private extension to easily “generate” different types of markdown files (ie readme vs a troubleshooting guide) from my personalized snippets.
While not a solution right now, I just want to add that the general transit feed spec aims to solve the data interoperability of different transit systems. The transit system keeps a publicly accessible zip file up to date, and then anyone can pull/parse the schedule/prediction data in a consistent way across transit systems. I know in the us adoption is slow, with vendors prefering to build their own walled gardens and transit agencies lacking the vocabulary or skills to advocate for more open data/tools
It looks like there is one here:
https://kevroletin.github.io/feed.xml