Added a read counter to posts on my blog. Can now see exactly how many real people vs bots read my stuff. #ai #bots
| Personal site | https://nmm.ee |
| Open Source Work | https://git.nmm.ee |
Asko Nõmm
@iamnmm
- 7 Followers
- 11 Following
- 34 Posts
Senior Software Engineer at https://codescene.com. I work on a whole bunch of AI tooling to, hopefully, make your life easier.
@glyph Yeah, it’s quite unsettling. In the end I couldn’t stomach the idea of my code being on GitHub at all, so I moved it to my own self-hosted place where nobody can contribute, but I understand for bigger projects it’s not realistic to do that.
@weavejester I don’t trust either, that’s why all these guardrails need to be added, and most of us no longer have the ability to avoid AI either due to pressure from above.
@weavejester It can make a whole lot of errors. That’s why the complicated part when it comes to working with AI is figuring out what guardrails to add, and how to add them. At
At work we incorporate MCP servers for deterministic code health insurance, so it can self-correct itself, but we also put focus on e2e tests now more than ever before so that if something does slip through we can be sure it doesn’t affect our end-users in any way.
@fribbledom I just ask AI to write code. I don’t know what editor it uses.
TL;DR of it is that for input tokens, they seem to have no difference, but then the main difference comes when using manually created CLI integrations with SKILL’s, where it differs behaviourly, both with their own pros and cons.
A lot of people seem convinced that MCP’s are bad when it comes to token spend, or that MCP’s are dead, and that manually created CLI integrations are the only true way. I set out to find out the truth, and so I ran a little experiment and did a bunch of digging on how things really work under the hood.
Spoiler: MCP’s are not dead.
Do MCP’s use more tokens than CLI’s?
There’s a long-held belief out there that MCP’s are bad, and that you should actually use CLI’s instead, if you want to save on token spend when it comes to LLM tool use. To me that argument never really made any sense, because you still have to provide the LLM context so it knows what CLI to run, how to run it and how to interpret the result of it. Things that the MCP does for you. How come the CLI takes fewer tokens?
@m3tti for me it’s definitely the relatively small standard library and the consistency of it. It makes me feel like I have actual mastery of the language, and can thus be confident in my creations.
KDEOn #IloveFS day, "This week in Plasma" brings the news that...
Plasma 6.6 is nearly ready for shipping! Look out for it next Tuesday.
... And videos in Plasma 6.7's SDDM login screens can be previewed in System Settings, KWin dialogs have been overhauled and polished, and much more.
https://blogs.kde.org/2026/02/14/this-week-in-plasma-finalizing-6.6/
@krishnadraws Oh wow, you're right! I also went down a bit of a rabbit hole and found some hidden ways to improve other things.
Via terminal I set:
Dock autohide time to 0s
Mission control animation to 0s
Launchpad show/hide to 0s
Window minimize effect to scale, which is faster than genie
Disabled Window animations
Changed Window resize time to 0.001s
Now the UX actually matches the hardware.