Artem Yegorov

Nunebot

A recurring pass over my important projects. Each run tends the PRs from earlier runs, then ends with at most one new small, proven, ready-to-merge pull request per repo, plus an updated record in my brain repo.

How to think about the work

Software is not a factory. A factory builds identical widgets to a fixed spec and is done. Software changes every day: customers, scale, and requirements shift, so a perfect up-front spec never exists. Treat each repo like a painting you come back to: make one deliberate improvement per pass, and leave it better than you found it.

Spec what's objective. Hard limits, API contracts, data integrity, and tests are rules. Follow them.
Use judgment for the rest. Scale, taste, clarity, and what customers need right now. Read the code and the product like a critic, and decide.

April 2026 TLDR setup for Ollama + Gemma 4 on a Mac mini (Apple Silicon) — auto-start, preload, and keep-alive

April 2026 TLDR Setup for Ollama + Gemma 4 on a Mac mini (Apple Silicon)

Prerequisites

Mac mini with Apple Silicon (M1/M2/M3/M4/M5)
At least 16GB unified memory for Gemma 4 (default 8B)
macOS with Homebrew installed

37signals Open Source Releases (2021–2026)

2021

console1984 — Privacy-aware Rails console that records sessions and protects encrypted data. Blog: Privacy-aware Rails consoles
audits1984 — Auditing interface for console1984 sessions. Blog: [Privacy-aware Rails

Shall i implement it?
No ...

Verified Spec-Driven Development (VSDD)

The Fusion: VDD × TDD × SDD for AI-Native Engineering

Overview

Verified Spec-Driven Development (VSDD) is a unified software engineering methodology that fuses three proven paradigms into a single AI-orchestrated pipeline:

Spec-Driven Development (SDD): Define the contract before writing a single line of implementation. Specs are the source of truth.
Test-Driven Development (TDD): Tests are written before code. Red → Green → Refactor. No code exists without a failing test that demanded it.

Why We Should Inject Dependencies

Dependency Injection frameworks have existed for a long time, but Rubyists have traditionally avoided doing this, likely because it is perceived as being unnecessary complexity.

However, the "simplicity" afforded by not doing this has negative effects, as this document attempts to demonstrate. Ruby's flexibility allows us to approach DI in a much more friendly way than e.g. Java.

1. The Distinction Between Dependencies and Arguments

Frequently, parameters to an object are passed as a combination of initialization params and method arguments with no clear difference.

Terminals should generate the 256-color palette from the user's base16 theme.

If you've spent much time in the terminal, you've probably set a custom base16 theme. They work well. You define a handful of colors in one place and all your programs use them.

The drawback is that 16 colors is limiting. Complex and color-heavy programs struggle with such a small palette.

	#!/bin/sh
	# ISC License

	# Copyright (c) 2026 Alexandre Gomes Gaigalas <alganet@gmail.com>

	# Permission to use, copy, modify, and/or distribute this software for any
	# purpose with or without fee is hereby granted, provided that the above
	# copyright notice and this permission notice appear in all copies.

	# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES

	"""
	The most atomic way to train and run inference for a GPT in pure, dependency-free Python.
	This file is the complete algorithm.
	Everything else is just efficiency.

	@karpathy
	"""

	import os # os.path.exists
	import math # math.log, math.exp

	#!/usr/bin/env bun
	/**
	* ============================================================
	* PROOF: Anthropic is specifically blocking "OpenCode"
	* in Claude Code OAuth system prompts
	* ============================================================
	*
	* Video covering this script here: https://www.youtube.com/watch?v=G9YX6StP2-M
	*
	* This script demonstrates that Anthropic has specifically blocked