Even Before Everything Else
In the very early days, our load taking system is highly scattered in scattered file system files It works well on Linux but doesn't work on Windows Later we used YNote, which had serious migration problems.
After that we had KMD.
Two modern variations are dated notes and also simple flat lists of to-do items (both of which are in Markdown) which we will not provide examples here.
The Old System
Based on previous experience at BBI, I devised a costume ticket-based task management system. It works very well but requires a bit more manual bookkeeping.
After using it for a while, I decided to merge everything into a single markdown file and eventually decided to try ADO for small scale personal projects, as long as other larger scale collaborative production projects, for easier and more contextual linking between tasks/tickets.
The New System (Now Depreciated)
Azure DevOp is a very useful sophisticated task management system suited for agile project management and for team work I honestly think there is no better alternative, despite poor integration with git (and I doubt many would use its own repo management system).
For personal projects, there are may serious issues:
- Complicated project setup, impossible to change project type after creation, unclear conventions (e.g. priority number), impossible to configure enums.
- The GUI is too complicated and even for production use, the search functionality is not very predictive. On the other hand, when it comes to have an overview of all the task items, it's not very clear what are the key information.
ADO supports sophisticated APIs, but it's not worth it for custom projects to develop for it.
Travelling Back
Now, we are trying to migrate back to the ticket based custom system for easier version control and oversight, and local file system searchability.
Top comments (0)