Microsoft AI Tour for Partners に参加した際に、NVIDIA提供のハンズオンセッション「RAG Pipeline with Nemotron on AKS」を体験した。MicrosoftパートナーとしてAzureとNVIDIA双方の技術スタックが組み合わさるセッションで、実際にコマンドを叩いてシステムを動かせる内容だった。
Azure上でNVIDIAのRAG Blueprintを動かすハンズオンに参加した。Helmコマンドを数回叩くだけでLLM推論・ベクターDB・ドキュメント取り込みパイプラインが一括起動し、PDFに質問できるUIまで立ち上がる体験は、想像以上に示唆が多かった。
手順を追いながら気づいたことを記録しておく。
After reading eda-san's (@eda_sann) article "Turning Book Knowledge into Agent Skills — System Design Principles Edition," I was inspired to build the same thing myself — this time for GitHub Copilot.
While eda-san used Claude Code's Agent Teams, this article takes a different angle:
On March 31, 2026, two security incidents hit the npm ecosystem simultaneously.
The first: Anthropic forgot a single line of configuration and accidentally published the entire source code of Claude Code. The second: the npm account for axios — a package downloaded 100 million times a week — was hijacked and used to distribute malware. The two incidents are completely different in nature, but both shook trust in npm as infrastructure.
Following the SEO and performance improvements on the portfolio side (previous article), I turned my attention to the Docusaurus blog on the same day. The starting point was Mobile Performance 94 / Accessibility 94 — not bad, but with room to improve. Running PageSpeed Insights repeatedly kept surfacing new problems. Here's the full record.
A record of going from nearly zero SEO to PageSpeed Insights ALL 100.
Images converted to WebP for 95% reduction, 7.8 MB of fonts removed, JSON-LD/OGP implemented — everything the code could address, all done. Including some surprising traps along the way, like Cloudflare's email obfuscation.
I investigated whether a private MCP server can be registered with Azure Foundry Agent Service. The short answer: not currently. Having understood that constraint, I also laid out the security risks lurking in MCP-based architectures.
Today I debugged two separate things. One was a CSS stacking context issue. The other was around AWS authentication infrastructure. Both end with "oh, of course" once you know the cause — but getting there is draining.
Following the Azure Weekly Update last week, there were several updates I found personally interesting, so I decided to write them up. The Foundry Agent Service GA in particular is directly relevant to my work in agent development, so I read it carefully.
I implemented "likes" and "comments" on the blog — the kind of feature note.com has, where there's a heart button and a comment section under each article.
The implementation itself took a few hours. But the decision process of figuring out how to build it was interesting enough to write up.
From morning to night, I kept fixing small things across the blog. It wasn't about adding features — it was a day of hunting down every "something feels off." Unglamorous work, but it's days like this that make a site grow.