logoalt Hacker News

stephbookyesterday at 9:57 PM1 replyview on HN

Take it to the logical conclusion. Track the intended behavior in a proper issue tracking software like Jira. Reference the ticket in your version control system.

Boring and reliable, I know.

If you need guides to the code base beyond what the programming language provides, just write a directory level readme.md where necessary.


Replies

andyferrisyesterday at 10:07 PM

I think the externality of issue tracking systems like Jira (or even GitHub) cause friction. Literate programming has everything in one place.

I’d like to have a good issue tracking system inside git. I think the SQLite version management system has this functionality but I never used it.

One thing to solve is that different kinds of users need to interact with it in different kinds of ways. Non-programmers can use Jira, for example. Issues are often treated as mutable text boxes rather than versioned specification (and git is designed for the latter). It’s tricky!