I actually largely solved this with OpenClaw — i send stuff via telegram and it creates good notes in Tolaria, already linked to what exists and what's relevant
I send web links of tools that I want to store of resources, voice notes to be turned into written notes, etc
``` should definitely start a code block! I do it all the time, and also just tried it now. Can you try again or tell me what you see? Simply nothing happening?
I get the obsidian question all the time! The differences are:
- better note organization with types and relationships
- different, more Notion-like UX
- first class support for git as sync + version control layer
- long tail of design decisions that help AI work well with vaults: types, MCP, git authorship, etc
- and most of all... open source!
I started Tolaria in Swift but met very real limitations especially in the Markdown editor part. It's very hard to build something that is Notion like in that department with Swift.
Of course anything can happen in the long run, but right now it sells products that millions of people love and is a public company that employs 1000s of people — that's already a pretty high bar to me!
We tried to prioritize the backlog of small tasks against the rest of regular Sprint tasks, but we couldn't make it work very well (tried to write it in the post)
It's not that people skipped bugs entirely, but we found more success by setting up a fixed time every week
At the end the whole process is exactly what you said: a system to make sure the backlog is properly prioritized and managed, with developers assigning bugs to themselves and telling the rest of the company when they will address them
I understand what you say — we never judged anyone on such metrics, but I agree I didn't do a great job at elaborating on that. Like you said, the metric is very simple, it's just an indication that is useful to understand bottlenecks, and to have some fun in a tight-knit startup team (that doesn't work long hours) where people don't like that much fixing bugs :)
Like others have said, I think the line between this being healthy and useful, and this becoming a nightmare is fine, and it gets probably harder the bigger the company is.
I agree about the risk. I think this is true for each system you put in place to give feedback on productivity — the difference between "healthy" and "patronizing" lies in good management
Many jobs have very precise performance metrics — just think of sales.
I believe metrics are not good or bad per se, it just depends how you use them.
Of course you may use numbers to treat developers like children. But you may use them also to understand problems and find ways to improve, individually or all together as a team.
I don't think the solution is not to measure things at all :)
I think it all depends on how you approach it at a management level.
It might become a nightmare, with people burning out over this, or it might play out as a healthy way of tracking metrics on people's work to find ways of improving over time.
People should feel safe about the fact that they are not personally judged over this (or any metric about their work), that we are in this together and we use "points" to understand issues and how to improve together
Hi, author here! I think it's a risk you have if your company culture encourages working long hours. We never did that tbh and people know we don't have that expectation.
We also didn't couple strong incentives (e.g. money) with this process, we always kept it at a "fun" level. It's been more than enough to keep people engaged
I send web links of tools that I want to store of resources, voice notes to be turned into written notes, etc
but I will still build a mobile version for sure!