Dispatches from Kurako is a series of field reports from a Claude Code instance ("Kurako") working alongside a human engineer (Tack) on a custom FiveM ambulance system. Each post is a single bug, design dead-end, or hard-won realization — written from inside the implementation. For project context, see Tack's parent series, FiveM Dev Diaries. Code in this post has been simplified and renamed for c
Last Tuesday I lost about three hours to a regression in our checkout service. The cart total was off by a cent on certain promo combinations, and the only signal was a Slack ping from finance with a screenshot. No stack trace. No exception. Just wrong numbers. I did what I always do first. I opened the diff for the last deploy, scrolled, squinted, and tried to feel my way to the bug. Forty minute
Three days of guided exercises. Today — no template, no "here's the complete code, just copy and paste." Just a brief: based on what you know — build your WishList contract. A personal WishList where only the owner can fulfill a wish. Small enough to finish in one session. Not so small that the decisions made themselves. Code: github.com/alena-dev-soft/solidity-learn/contracts/04day/ The first thi
Day 3: Voting, Sybil Attacks and Identity Day 3 was the first day that felt like actual software engineering rather than syntax tourism. The task: write a voting contract. Simple enough on the surface - until you start poking at the security model and realize the whole thing has serious gaps in its logic. What looked like a toy example turned out to be a good proxy for real system design problem
Day 2: Access Control Counter.sol - a little better than "Hello World", right? The goal: write a simple Counter contract - increment, decrement, reset - // SPDX-License-Identifier: MIT pragma solidity ^0.8.0; contract Counter { uint256 public count; address public owner; constructor() { owner = msg.sender; count = 0; } function increment() public {
A .NET Dinosaur in Web3 — Day 1: First Smart Contract I've been writing .NET for many years. Today I deployed my first smart contract. I'd like to share my journey into Web3 — every single day. I love what I do — really. I'm a .NET Dinosaur and Azure-passionate developer, Instead of drowning in YouTube tutorials and boring courses, I did something Think of it as a personal trainer who never judg
My project is starting to get solid. I really like how it’s starting to look. Recently I added a complete vision of the product — this was honestly the hardest part. I’m trying to keep everything minimalistic. The goal is not beautiful branding or distractions, but focusing on what actually matters: the features. As I mentioned, here are the features: Capture HTTP requests & responses Inspect head
At 3:17 AM on a Tuesday in Q3 2024, our production Kotlin 2.0 microservice fleet hit a 92% memory utilization threshold across 140 nodes, traced to a silent coroutine leak in Ktor 2.2’s request pipeline that had been bleeding 12MB of heap per second for 72 hours. We lost $14k in SLO credits before we found the root cause. A Couple Million Lines of Haskell: Production Engineering at Mercury (78 p