thomas-vds

Hi folks, I built this over the week-end as a side-project to learn GraphQL. It focuses on giving you actionable SLAs on your issues. In particular it should give you interesting insights about how fast your team is solving bugs :) Note that if you have multiple Linear workspaces, the app will by default connect to the latest one you logged in to.

Hi folks, I built this site initially as a companion to workshops about Blockchain mechanics. Since it's a rather playful thingy, I thought it's worth sharing to a broader audience :) There's no actual blockchain connection involved as everything is done in the browser (except at the very end). Hope you enjoy!

Thanks so much for your feedback, indeed the project is still quite WIP but you know, shipping fast was the only alternative for me vs continuing to polish it forever ;)

Typically built for teams of less than 10 people, where everyone knows everyone and no one is hence ever reduced to their metrics :) The comparison with China's social score is a bit harsh IMO, as here there are no consequences for your "bad" behaviour, and on top the positive micro-interactions are fostered. When it comes to time it takes, goal is basically that it takes you less time than cheering via Slack (which you hopefully would do otherwise).

Thanks for your frank feedback - I do share you POV on the risk of metrics being used for the wrong intentions. Nevertheless I do think that introducing a bug in CI/CD tests on master (because e.g. you did push directly on master and not on a feature branch, where introducing bugs is fine) is the kind of behaviour that as a manager you want to see reduced. If such things happen, as a CTO I'll anyway ping the dev to let them know they should watch out next time. Delegating this to a simple rules-based engine with rules that everyone agrees on suddenly makes the whole discussion much more objective and avoids human friction. All the while with the more positive cheering which is purely about sharing good stuff. When it comes to actual monitoring of productivity, the current rules don't really allow that, because we all know how hard it is to measure dev productivity (e.g., a single commit of 1 line can add as much value as a big commit of 20 files).

The idea of rewarding devs from my team for following collaboration best practices first arose when I was managing a team of 6 junior developers, nearly all of them freshly graduated from coding bootcamps. I was losing a lot of energy to remind them about the need to quickly fix bugs, minimise WIP etc. And clearly, rewarding good behaviour with gamification works better than playing the blame game for suboptimal behavior.

As time went I got the chance to work with and manage more senior and incredibly talented devs - but still, some issues remained around sticking to our commonly agreed best practices.

Then came COVID and the full-remote setup and it also became increasingly important to keep regular interactions within the team, even micro-interactions when some folks don't get the opportunity to work together but still want to connect.

So I ended up building Karma initially as a side-project to learn Go during my paternity leave (oops). I've had a lot of fun building that little CLI with the Cobra framework (same one as the one that powers Github CLI). The front-end is built using Tailwind UI and Vue 2.

I hope you'll have good fun trying this out, and that like me you will also discover what a cool TUI looks like :) Go spread the good karma, looking forward to getting feedback.