My coworker Toby Crawley recently developed this Firefox plugin to randomize the order of files in GitHub PR reviews:

https://addons.mozilla.org/en-US/firefox/addon/github-pr-fil...

I help build Shortcut (https://www.shortcut.com/) and I think it fits the bill of light—but not spartan—on customization and day-to-day management.

To set up a new Shortcut workspace:

1. Sign up 2. Invite teammates, group them into teams if desired 3. Activate the GitHub/Gitlab/Bitbucket integration, so as engineers work via VCS their work in Shortcut progresses automatically 4. Set your workspace's timezone 5. Turn on/off Iterations (sprints) based on your process. Unfinished stories can be set to automatically roll from one iteration to the next. 6. Turn on/off point estimation based on your process

Then start writing Stories (tickets/issues) to track work.

Going further: Stories can be grouped into Epics. Epics can be grouped into Objectives (with associated Key Results if that's your thing). You can put Epics on a Roadmap to "share out" what your team is planning to work on. All optional, based on how you work and the size of your org.

Shortcut (https://www.shortcut.com/) is a solid alternative to Pivotal Tracker. I work as an Engineering Manager there and helped build an importer for Pivotal Tracker data into Shortcut (https://github.com/useshortcut/api-cookbook/tree/main/pivota...).

Shortcut as a product is team-oriented with solid GitHub/Gitlab/Bitbucket and Slack integrations.

Still feels like too many columns, too many states.

Pivotal Tracker - ice box, backlog, or current iteration.

I see companies in Trello Hell - well meaning, but often conflated, grey area states. There's like 10-15 columns on their boards.

It's a hot mess.

I worked on a tool more crowded than this and of late I’m coming around to the idea that these tools are all built for management which is why they get deployed. These drag and drop views aren’t that helpful for engineers. And they just make it easy for someone else to accidentally fuck up the status on your tasks.

The task list in Jira is good enough for finishing or marking one task as blocked and starting another. If anyone is using the interface like Tom Cruise in Minority Report, dragging things around at pace, it’s because people aren’t keeping their tasks updated and a tool can’t and probably shouldn’t try to fix that. You fix that by orienting the UI so devs benefit from using it, not by guilt tripping or lecturing.

I agree. People who like Pivotal Tracker (like me) for its focus and simplicity would not enjoy Clubhouse.

Woah wasn't this called Clubhouse at one point? I'm getting blast from the past! We used Clubhouse at Papa long time ago.

It was, and at that time it suddenly became much harder to do a web search on how to do anything in their UI! Turns out, Shortcut is not the most Google friendly name.

To better understand how different ClojureScript is from CoffeeScript, read the last paragraph on the ClojureScript wiki's Rationale page: https://github.com/clojure/clojurescript/wiki/Rationale

It's purpose is not to compile down to vanilla, readable JavaScript, but rather to make it easy to write production-ready JavaScript applications that can easily leverage the "advanced mode" of the Google Closure compiler.