Programming

23936 readers

233 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

The Most Minimal Kanban (fd93.me)

submitted 3 months ago by fd93@programming.dev to c/programming@programming.dev

3 comments fedilink hide all child comments

Software design is weird. I wrote this article about implementing a minimal kanban board and the trade-offs I needed to make.

you are viewing a single comment's thread
view the rest of the comments

[–] nathanjent@programming.dev 5 points 3 months ago (2 children)

I've often wondered if it would be possible to track work in a git repository like this. Cloning code is so easy with git because it's an industry standard but every git front end wants to reinvent task management. Some of them allow you to manage a project wiki in git. It would be convenient to be able to clone the task management repository alongside the code repository, too.

[–] fd93@programming.dev 2 points 3 months ago

Yep - I do it in the scripted version.

The main challenge is dealing with dynamic data in a way that won't mess up merge conflicts. Sort order is the main one and it's pretty bad because a merge conflict will result in multiple tickets with the same sort order. The best way I could think of in the slightly less strict paradigm of the plainban project was to keep a data.yml file for each column which records the sort order of tickets by storing them as a list of uuids and making their name a comment. That way it's very easy to keep track of the order of tickets on merge conflict in a way that's not possible in a central data source like a csv file.

sort_order:
    - abcd # my cool ticket
    - 1234 # another cool ticket
    - ab12 # final ticket

Will change current, less merge-friendly implementation to this when I get to it.

load more comments (1 replies)