Explore >> Select a destination
|
You are here 
|
pliutau.com | ||
| | | | |
www.screamingatmyscreen.com
|
|
| | | | | Timo Zimmermann talking about software engineering, leading teams, consulting and start ups. | |
| | | | |
infinitedigits.co
|
|
| | | | | A lightweight Dockerfile for Golang apps. | |
| | | | |
philiplaine.com
|
|
| | | | | It has been an issue for a long time to run Docker images on multiple architectures. I remember the first time I got the idea to install Docker on my Raspberry Pi and I realized quickly that what I was trying to do would not work. The issue of course was that I was trying to use an AMD64 compiled Docker image on a ARM 32 bit CPU. Anyone who works with any lower level languages would call me an idiot for realizing this sooner than later. I would agree with them. Docker just seems to work like magic, running on most machines without any issue, like running Linux containers on Windows. One thing that has not been easy though is building Docker images on one type of CPU and running them on another. | |
| | | | |
ezyang.github.io
|
|
| | | Model Context Protocol servers provide a standard interface for LLMs to interact with their environment. Cursor Agent mode and Claude Code use agents extensively. For example, instead of needing a separate RAG system (e.g., as previously provided by Cursor) to find and feed the model relevant context files, the LLM can instead call an MCP which will let it lookup what files it wants to look at before deciding what to do. Similarly, a model can run tests or build and then immediately work on fixing problems when this occurs. It is clear that Anthropic's built-in MCP servers are useful, and you should use agent mode when you can. | ||
