If this is useful, a ❤️ helps others find it. All tests run on an 8-year-old MacBook Air. HiyokoLogcat supports Japanese and English. The AI diagnosis needed to respond in whichever language the user chose. The simplest solution: write the system prompt in the target language. Gemini follows it reliably. // Don't do this let prompt = format!("Analyze this log: {}\nRespond in Japanese.", context);
When you bind Ctrl+S to "save" in a web app, do you check event.key === "s" or event.code === "KeyS"? The honest answer is "I don't remember, I copy-paste from Stack Overflow." Until a Dvorak user reports the shortcut is broken — or a Japanese IME user reports it fires mid-composition. This is a live inspector for KeyboardEvent: press any key (or combination), see every field — key, code, keyCode,
37 days. That's how long the main and submain branches diverged before the big merge today. It wasn't just about closing this gap; it was about making the biggest forward leap we've seen in weeks. The test matrix exploded from 78 to 117 tests, and we dropped an 11-commit sprint into IR lowering that hammered out essential struct and array support. That alone makes you want to take a closer look at
When building modern applications, one problem shows up everywhere: How do I uniquely identify data across systems? That’s where UUIDs (Universally Unique Identifiers) come in. A UUID is a 128-bit unique identifier used to identify information in distributed systems. Example: 550e8400-e29b-41d4-a716-446655440000 It looks random - and that’s the point. Traditional IDs (like auto-increment integers
If this is useful, a ❤️ helps others find it. All tests run on an 8-year-old MacBook Air. If a user closes the AI diagnosis overlay and reopens it, should you call Gemini again? No. Cache the result. Same input → same output. No reason to burn rate limit quota. Here's the caching layer I built into HiyokoLogcat. Without caching: User clicks diagnose on error line 847 Gemini responds in 3 seconds U
It happened to me. My site — bashsnippets.xyz — had been down for six hours before I knew That's the kind of thing that sits with you. The fix took 20 minutes to build. Here's exactly what I wrote and why The natural instinct is to just open a browser and load the page. You only check when you remember to You don't check at 2am when it actually goes down What you want is automated, logged, and
I got tired of not knowing why users were dropping off in my app. Heatmaps show you where people click. Analytics show you when they leave. But nothing tells you how they felt while using it. So I built SessionMood API — a REST API that scores user mood in real time based on behavioral events. You send behavioral events from your frontend: fetch("https://session-mood-api-production.up.railway.app/
Posted on vicspot.com — All tools run 100% in your browser. Zero data sent to any server. As developers, we constantly switch between 10+ different tabs just to do basic tasks — format some JSON here, generate a password there, convert a hex color somewhere else. It's frustrating and slow. I built Vicspot.com to fix this — a single page with 12 free browser-based utilities that run entirely client