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
I Built a VS Code Extension to Bring IntelliJ’s “Show History for Selection” Experience If you come from IntelliJ, you probably miss one super useful feature in VS Code: Show history for selected lines. I built a new extension to solve exactly that. Show History for Selected Code This extension helps you inspect Git history for a specific code selection, not just the whole file. Shows commit h
Microsoft's 'Co-Authored-by Copilot' Tag: Unpacking the Strategic Play for AI Dominance in VS Code The persistent insertion of 'Co-Authored-by: Copilot' into commit messages within VS Code—often irrespective of GitHub Copilot's active contribution to specific changes—is far from a benign engineering detail. It represents a calculated, multi-faceted strategic maneuver by Microsoft, signaling a pr
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
I have a bad habit of jumping between projects. It's not a big deal. But it happens every single day. So I built rewind. rewind That's it. No setup, no IDE, no agent loop burning through tokens. Just one binary, one command, one LLM call. cargo install git-rewind GitHub: https://github.com/Chronos778/git-rewind Would love feedback — on the idea, the UX, anything. Still early days.