It feels to me that the OP on the forum expects this to work: "read this existing function, then read my mind and do stuff" (probably followed by "do better").
It still takes a lot of practice to get good at prompting, though.
Kinda off-topic but I love the quality of images used in this article. Even memes are HD. Quite rare as people tend to use whatever meme creator provides - super-pixelated, low-quality source image with text slapped on top.
Sorry for going off-topic, but kudos for UI/UX on your blog!
To name a few: Nice style (colors, font, style), "footnotes" visible on the margin, always on table of contents, interactivity and link previews on hover.
I'm a heavy user of the llm tool, so as soon as I saw your post, I started tinkering with MCP.
I’ve just published an alpha version that works with stdio-based MCP servers (tested with @modelcontextprotocol/server-filesystem) - https://github.com/Virtuslab/llm-tools-mcp. Very early stage, so please make sure to use with --ta option (Manually approve every tool execution).
The code is still messy and there are a couple of TODOs in the README.md, but I plan to work on it full-time until the end of the week.
Some questions:
Where do you think mcp.json should be stored? Also, it might be a bit inconvenient to specify tools one by one with -T. Do you think adding a --all-tools flag or supporting glob patterns like -T name-prefix* in llm would be a good idea?
Be careful with iPhones/iOS too. Ignoring „not enough space” warnings will eventually put it into a boot loop.
There are threads on Reddit about this.
For me, flashing it through Finder with the official firmware was the only option. I lost some photos, the rest I was able to restore from iCloud backup.
If anyone is interested in Infrastructure as Software, I also recommend giving Pulumi a try. I've been using Terraform for a couple of years, Pulumi for about a year and I think that Pulumi is on a completely different level.
It also supports higher level abstractions (Component Resources). For example: check out AWS EKS provider.
Nice! Ability to quickly choose goggle would be nice, something similar to "site:" or !bangs in ddg. Example search: "integration tests best practices goggle:tech-blogs".
Some recommendations in this pdf are sooo vague and lack proper context. For example, what the hell does this mean: "Let the Code Make the Decisions: There is no need to spell everything out in minute detail".