A Java Geek weekly 85

The OpenTelemetry Collector sits at the center of the OpenTelemetry architecture but is unrelated to the W3C Trace Context. In my tracing demo, I use Jaeger instead of the Collector. Yet, it’s ubiquitous, as in every OpenTelemetry-related post. I wanted to explore it further.

Badgetizr is a tool that will add badges to your pull requests to increase your team’s productivity. It is fully customizable and you can add (almost) as many badges as you want. With Badgtizr on your CI, you will be able to save time by:

• Stop adding a link to your ticket in the description of the PR if you add the id of it in the title of the PR.
• Reminding that some tasks are still missing to do in the PR.
• Stop adding a visual indicator if your PR is a WIP.
• Having a badge to know the status of the CI pipeline without having to click on it, scrolling down to the bottom of the page (coming soon).

[…​] I’m astonished by the apparent lack of mature engineering practices. All the major players spend billions of dollars on training and tuning their models, only to turn around and, from what I can tell, have an interns write the documentation, providing subpar SDKs and very little in terms of implementation guidance.

This trend seems to have continued with MCP, resulting in some very strange design decisions, poor documentation, and an even worse specification of the actual protocols.

My conclusion is that the whole suggested setup for HTTP transport (SSE+HTTP and Streamable HTTP) should be thrown out and replaced with something that mimics stdio…​ Websockets.

Disambiguation involves getting the system to respond with a clarifying question when faced with a question that is not clear enough (in the example above of "What is the best selling shoe?" should lead to a follow-up question like "Would you like to see the shoes ordered by order quantity or revenue?" from the text-to-SQL agent). Here we typically orchestrate LLM calls to first try to identify if a question can actually be answered given the available schema and data, and if not, to generate the necessary follow-up questions to clarify the user’s intent.

Copilot excels at low-to-medium complexity tasks in well-tested codebases, from adding features and fixing bugs to extending tests, refactoring, and improving documentation.

1. Open by default: Making Open Source the standard approach for projects.
2. Contribute back: Encouraging active participation in the Open Source ecosystem.
3. Secure by design: Making security a priority in all software projects.
4. Foster inclusive participation and community building: Enabling and facilitating diverse and inclusive contributions.
5. Design for reusability: Designing projects to be interoperable across various platforms and ecosystems.
6. Provide documentation: Providing thorough documentation for end-users, integrators and developers.
7. RISE (recognize, incentivize, support and empower): Empowering individuals and communities to actively participate.