https://github.com/markdowntool/mdt
I use shared markdown files to collaborate with agents. Their biggest complaint was that, when content changed, they needed to either re-read the full file or write code to find the difference.So I made mdt. It's light - one binary, one sqlite file - and lets your agent track the changes to a shared file, so that it only reads the diff.Ping me if I can make it better.
It’s small (zip < 7MB) and fast (launches in 300 ms, opens Moby Dick in < 300 ms).
Ping me if you use and something is missing.
It’s my daily note-taking app.
What’s more interesting to me than time-to-first token or latency is the time it takes for the agent to execute, from starts to finish, excluding when it’s waiting on a human.
As a developer, I wager that any gains I get from Podman will be dwarfed by bugs that I’m encountering in the other software I use.
I’m not implying that Podman causes the bugs. I’m saying that I’ll be more likely to be the first person to encounter the bug.
It’s really cool, I’d love to see it smart.
Wow, Voxtral is amazing. It will be great when someone stitches this up so an LLM starts thinking, researching for you, before you actually finish talking.
Like, create a conversation partner with sub 0.5 second latency. For example, you ask it a multi part questions and, as soon as you finish talking, it gives you the answer to the first part while it looks up the rest of the answer, then stitches it together so that there's no break.
The 2-3 second latency of existing voice chatbots is a non-started for most humans.
Something that balanced empowering participants and protecting their privacy, while also protecting them from financial abuse.
I'd love feedback.
When I buy Apple, I pay a premium price for a premium product.
The ways ads work, is that the ad revenue shows up in the company’s quarterly earnings, and very quickly the company has to increase ad load across every surface to meet earnings expectations. The user experience deteriorates, getting worse each year.
When I buy Apple, it’s based on my expectation that Apple will remain a premium, mostly ad-free experience for the life of the device. When, after my purchase, they make the product worse, like with the recent iOS update that rolled back usability, it destroys a lot of trust.
I will leave the ecosystem.
This is not in Apple’s long term best interests.
When I buy Apple, I pay a premium price for a premium product.
I would rather you simple charge me more for my product.
The ways ads work, is that the ad revenue shows up in the company’s revenue, and very quickly the company has to increase ad load across every surface to meet earnings expectations. The user experience deteriorates, getting worse each year.
When I buy Apple, it’s based on my expectation that Apple will remain a premium, ad-free experience for the life of the device. When, after my purchase, Apple make the product worse, like with the recent iOS update that rolled back usability, it destroys a lot of trust.
I will leave the ecosystem.
This is not in Apple’s long term best interests.
The author’s math considers how mines would be distributed if mines were distributed to the empty squares after reaching that board state.
This is wrong.
This is classic Monty Hall Problem. The author is doing the equivalent of saying “there are two doors left, so the odds are 50 / 50 that the prize is behind either door.
It invalidates all of the numbers after this point.
You’re able to fit more code on a screen, and it’s less visual noise. It’s like Pareto better. I really don’t get why others don’t copy it.
I use Trax is my NLP class, so I hope it gets more adoption.
There's now at least one business bank the will purchase t-bills on a companies behalf with minimal transaction costs.
Python generally provides one and only one best way to do things. With one exception (single quotes vs. double quotes) I can’t think of any cases where my company didn’t espouse or require using regular, idiomatic Python.
My company consistently preferred using expressive features do the language. For example, using list comprehension instead of for-loops.
After learning Python, reading up on the frameworks used at my company (Django and Django Rest Framework) would be the next best use of a new dev’s time.
This advice might be specific to Django and Django Rest Framework. Both frameworks are old, popular, and opinionated; other people have thought through the best way to do things.
Understanding all the packages in the standard library is by no means a requirement, but knowing the language itself backward and forwards pays enormous dividends when debugging.