lucaronin

7 ms·

1.
by lucaronin 5mo ago
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 t
2.
by lucaronin 5mo ago
big fan of Bear! It was a big influence for Tolaria — that's why you like it! thank you for the great feedback mate
3.
by lucaronin 5mo ago
``` 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?
4.
by lucaronin 5mo ago
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 dec
5.
by lucaronin 5mo ago
you bet it!
6.
by lucaronin 5mo ago
thank you so much!
7.
by lucaronin 5mo ago
the idea of being git-first it's exactly for that! so you can setup AI as a git contributor and see its changes clearly
8.
by lucaronin 5mo ago
releasing it over the next couple of days
9.
by lucaronin 5mo ago
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. But give it a try because Tauri is very fast
10.
by lucaronin 5mo ago
that's weird will look into it! thanks for reporting
11.
Show HN: Tolaria – Open-source macOS app to manage Markdown knowledge bases(github.com)
318 points by lucaronin 5mo ago|142 comments
12.
My AI Coding Workflow(refactoring.fm)
1 points by lucaronin 7mo ago|0 comments
13.
by lucaronin 4y ago
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!
14.
by lucaronin 4y ago
Thank you for sharing this! I am the author, happy to get feedback and hang in the comments (at my own risk)
15.
Have Few Meetings(refactoring.fm)
2 points by lucaronin 5y ago|0 comments
16.
The Cost of Developing New Features(refactoring.fm)
1 points by lucaronin 5y ago|0 comments
17.
Choosing Between Boring and Technology(refactoring.fm)
1 points by lucaronin 5y ago|0 comments
18.
The Operating Cost of New Features(refactoring.fm)
3 points by lucaronin 5y ago|0 comments
19.
About Tech Leads vs. Engineering Managers(refactoring.fm)
1 points by lucaronin 5y ago|0 comments
20.
The Worst Possible Solution(refactoring.fm)
2 points by lucaronin 6y ago|0 comments
21.
On Tools, Processes and Guitar Pedals(refactoring.substack.com)
4 points by lucaronin 6y ago|0 comments
22.
by lucaronin 6y ago
I would love to have feedback on this! I will hang in the comments hoping for a good conversation
23.
How to vastly improve your team's Pull Requests, by measuring them(refactoring.substack.com)
4 points by lucaronin 6y ago|1 comments
24.
by lucaronin 6y ago
That's good feedback thank you! 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 b
25.
by lucaronin 6y ago
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 bottlen
26.
by lucaronin 6y ago
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
27.
by lucaronin 6y ago
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 als
28.
by lucaronin 6y ago
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 o
29.
by lucaronin 6y ago
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) w
30.
How we use tennis rankings for fixing bugs(refactoring.substack.com)
31 points by lucaronin 6y ago|44 comments

More ›