A Java Geek weekly 126

Broadcast devices' name on the local network. Password managers less secure than promised. Anthropic Study: AI Coding Assistance Reduces Developer Skill Mastery by 17%. Flickr’s URLs scheme. The Day a Google L7 Engineer Tore My System Design to Shreds. Your AI coding agent is drowning in noise. Moving beyond Strings in Spring Data. Code Mode: give agents an entire API in 1,000 tokens. After 24 years of building systems, here are the architecture mistakes I see startups repeat. Anthropic courses.

Broadcast devices' name on the local network

With years, I accumulated devices on my local network, which in general run on Linux. I meticulously added them to my /etc/hosts/ file, so as not to remember their IP. Something puzzled me, though: my Synology NAS was readily available as nas.local on the network, without doing anything. I have close to zero skills in system administration, so here are my findings.

Password managers less secure than promised

Another marketing promise that goes down the drain. I’d really would love the same study on the OpenSource ones as a comparison.

Anthropic Study: AI Coding Assistance Reduces Developer Skill Mastery by 17%

Clickbait title, but the content is interesting - and a bit more nuanced.

Low-scoring patterns, averaging below 40%, included complete AI delegation for code generation, progressive reliance where developers gradually handed all work to AI, and iterative AI debugging where developers relied on AI to solve rather than clarify problems.

High-scoring patterns, averaging 65% or higher, shared a common thread of cognitive engagement: asking follow-up questions after generating code, combining code generation with explanations, or using AI only for conceptual questions while coding independently.

AI can actually help depending how you use it. Delegate everything and you’ll get crappy results; wear it like an exoskeleton and you’ll enhance your skills.

Flickr’s URLs scheme

Any URL being easily editable required for it to be easily readable, too. Flickr’s were. The link names were so simple that seeing the menu told you exactly what the URLs for each item were.

The Day a Google L7 Engineer Tore My System Design to Shreds

I can’t say for sure the story is true, but the content is worth repeating.

Engineering is the Art of Trade-offs:

  • Consistency vs. Availability
  • Latency vs. Cost
  • Complexity vs. Maintainability
Your AI coding agent is drowning in noise

When working with Claude Code, having an eye on your context window is a must. Seeing those context windows fill up pretty quickly, you start to realize this needs to be optimized so you can have longer/better sessions (with less distractions a.k.a. context rot). Then a brick hits you in the face when it dawns on you that all of our tools are dumping crazy amounts of non-relevant context into stdout thereby polluting your context windows.

Moving beyond Strings in Spring Data

It was also a bit weird that Spring, which helps developers write better code, didn’t have a way to enforce correctness at compile-time on Spring Data.

Code Mode: give agents an entire API in 1,000 tokens

For a large API like the Cloudflare API, Code Mode reduces the number of input tokens used by 99.9%. An equivalent MCP server without Code Mode would consume 1.17 million tokens — more than the entire context window of the most advanced foundation models.

Pretty smart approach. I wonder how it fares "for real".

After 24 years of building systems, here are the architecture mistakes I see startups repeat
  • Premature microservices
  • No clear data ownership
  • Ignoring operational complexity
  • Over-engineering for hypothetical scale
Anthropic courses

In case you missed it. I followed some of them; they are quite good.

Besieged

This quote echoes my sentiment:

If you’ve been reading what I write, it’s not like I’ve been a believer the whole time. But I am today. Because I’m doing it. It’s amazing. We will never go back, as an industry. We will simply use this capability and catapult forward.