← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 159
  1. Every piece of the protocol has been on the table on its own.

  2. The first two parts of this series ran entirely on a laptop.

  3. The last primitive is the newest, and the only one the spec still marks experimental.

  4. The authorization post controlled who may reach a server.

  5. Over stdio the connection is trusted: the server is a local subprocess the client launched.

  6. A server has two ways to tell a client something happened without being asked.

  7. The primitives are done, the four the client calls and the three the server calls back.

  8. Elicitation is the server asking a person for input in the middle of a task. elicitation/create runs server to client to user, the third and last of the inverted requests after sampling and roots.

  9. Roots are the smallest of the server-to-client requests.

  10. Generating an embedding is slow.

  11. Every method so far has run one direction: the client asks, the server answers.

  12. The series has deferred this method three times.

  13. Prompts are the third thing a server can offer, after tools and resources.

  14. Tools are actions the model takes.

  15. The last post covered discovery: what the model reads to decide how to call a tool.

  16. Discovery in MCP is one method, tools/list, and its response is the exact JSON the model reads to decide whether to call a tool and how to fill in its arguments.

  17. Streamable HTTP is the MCP transport for servers reached over a network, behind auth, serving many clients at once.

  18. The stdio transport is the simplest one MCP defines.

  19. Wrap a real API in an MCP server and you hit a wall almost immediately.

  20. Under 2025-11-25, a session opens with initialize, the server answers with what it can do, the client sends initialized, and only then do other methods become legal.

  21. MCP is JSON-RPC 2.0 over a transport.

  22. The common objection to MCP is that a REST API would do the same job.

  23. You write a Go function, tag its arguments, and hand it to mcp.AddTool.

  24. A pull request shouldn’t need four review rounds.

  25. Building an MCP-powered data platform taught me that LLMs will ignore the instructions I spent months writing.

  26. Moving analytics data from a Zalando-managed PostgreSQL cluster into OpenSearch for full-text search and dashboarding looks simple on paper.

  27. GoReleaser automates building, packaging, and publishing Go binaries.

  28. The principles article covered why verification matters.

  29. Ralph's Uncle

    My daughter called me an “unk” the other day.

  30. Andrej Karpathy coined “vibe coding” in early 2025: “forget that the code even exists… I ‘Accept All’ always, I don’t read the diffs anymore.”

  31. §Privacy Policy Effective Date: February 1, 2026 Industrial Media Technology, Inc.

  32. §End User License Agreement Effective Date: February 1, 2026 This End User License Agreement (“Agreement”) governs your use of applications and services provided by Industrial Media Technology, Inc.

  33. I’ve been experimenting with MCP for about six months now, building custom servers for data platform clients.

  34. Data warehouses handle structured queries.

  35. Data lives in PostgreSQL for transactions, MySQL for legacy systems, S3 for analytics, Kafka for streams.

  36. kubectl port-forward works fine for one service.

  37. kubefwd has been a stable and useful tool for my team and me for almost eight years.

  38. kubefwd is a tool that bulk-forwards Kubernetes services to your local machine, making them accessible by their real hostnames.

  39. I wrote portpxy to solve an annoying problem: NiFi lets you spin up HTTP listeners at runtime, but Kubernetes makes you update manifests every time you want to expose a new port.

  40. This article covers advanced JOLT transformations including cardinality, modify operations, wildcards, and chained specifications for complex JSON restructuring.

  41. This article introduces JOLT (JSON to JSON transformation Language) in Apache NiFi, covering the fundamental operations: shift, default, and remove.

  42. This article covers securing Apache NiFi deployments with TLS encryption, authentication providers, and role-based access control, including LDAP, OIDC, and certificate-based authentication.

  43. This article covers deploying Apache NiFi on Kubernetes for production workloads: a clustered deployment with ZooKeeper, persistent storage, and proper ingress handling.

  44. This final article in the series covers high-performance computing techniques for linear algebra in Go: BLAS/LAPACK integration, parallel operations, memory optimization, and benchmarking.

  45. This article implements neural network foundations in Go using gonum: a perceptron, forward propagation, and backpropagation from scratch.

  46. This article implements Principal Component Analysis (PCA) from scratch in Go using gonum, covering both the covariance matrix and SVD approaches.

  47. This article demonstrates building a regression library in Go from scratch using gonum: ordinary least squares, ridge regression, and cross-validation.

  48. This article covers statistics and data analysis in Go using gonum/stat and gonum/mat: descriptive statistics, covariance matrices, and correlation analysis.

  49. This article covers Singular Value Decomposition (SVD) and related matrix decompositions in Go.

  50. This article covers eigenvalue problems in Go using the gonum library.