Skip to content
View thumbrise's full-sized avatar
👍
rising up
👍
rising up
17 followers · 14 following

Achievements

Achievement: QuickdrawAchievement: Pair ExtraordinaireAchievement: Pull Sharkx2

Achievements

Achievement: QuickdrawAchievement: Pair ExtraordinaireAchievement: Pull Sharkx2

Block or report thumbrise

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
thumbrise/README.md

Hi, I'm Ruslan

In production since 2019. Building open-source tools that close fundamental gaps in the Go ecosystem.

NIH & Gaps researcher. Open-source tooling author. Tech lead.

My work is an ecosystem of tools born from real production pain, documented through RFCs, devlogs, and adversarial architecture reviews.

The Ecosystem (My Public Portfolio)

Tool Problem Solved Artifacts
resilience Go lacked a composable, zero-dependency resilience toolkit with a Go-native DSL. Devlogs, Adversarial Review, RFC-002
multimod Go has no cargo-release. Multi-module monorepos require manual tagging, replace management, and release orchestration. Devlogs, RFC-001
autosolve GitHub issue triage is manual, repetitive, and context-heavy. No self-hosted AI solution existed. Devlogs, Do Primitive
ghset Setting up a new GitHub repo means clicking through 15 settings tabs. No declarative tool existed for Go. Devlog

The Deathbook

Tools emerge from tools. Every GAP gets an entry, every entry eventually gets crossed out.

# GAP Born inside Status
1 Resilience patterns in Go autosolve Extracted → resilience
2 Task runner lifecycle hooks resilience Documented, waiting
3 Multi-module release tooling resilience Extracted → multimod
4 Version bumping from commits multimod Planned → version-bumper
5 GitHub Release creation multimod Planned → ghreleaser
6 Declarative repo settings multimod Extracted → ghset
7 OTel extension reuse autosolve Extracted → otelext
8 Generic event system resilience RFC written → RFC-002
9 Fallback chain pattern resilience RFC written → RFC-002

Full Deathbook with dependency graph and artifact links →

Behind the Code

Since 2019, I've been architecting backend systems in Go (and previously PHP).

  • Leadership: Led a 6-person backend team, 2023–2025.
  • Systems: High-load marketplace, event-driven architecture, observability stack.
  • Culture: Introduced adversarial review, ADR processes, and semantic release workflows.

Stack: Go, PostgreSQL, Redis, Kafka, Docker.

Let's Talk

If you're facing ecosystem gaps, scaling engineering culture, or just want to discuss adversarial review over a virtual coffee.

Pinned Loading

  1. autosolve autosolve Public

    Lightweight daemon that polls GitHub for new issues and dispatches AI agents to solve them automatically

    Go 3

  2. resilience resilience Public

    Zero-dependency composable resilience toolkit for Go with optional fundamental extensions

    Go 3

  3. multimod multimod Public

    Unix-way CLI ecosystem for Go multi-module monorepos — zero-config workspace sync, replace management, detached-commit releases, sub-module tagging. The missing cargo-release for Go.

    Go 1

  4. ghset ghset Public

    Declarative GitHub repository settings. Describe existing repos into YAML, create new repos from that YAML.

    Go 1

  5. otelext otelext Public

    Extensions for OpenTelemetry Go SDK

    Go 1

  6. srtor srtor Public

    Translator of subtitles in srt format

    Go 2