I like building software from the ground up — libraries, tools, build systems, and the occasional questionable side project.

My main interests are C, C++, and Go, with a particular interest in low-level programming, developer tooling, clean APIs, and portable software.

C / C++       Low-level libraries, utilities, build systems
Go            Libraries, tooling, applications
Systems       Filesystems, processes, networking, portability
Tooling       Build systems, parsers, developer utilities, small libraries and reusable components

A collection of Go utilities.

Collections, asynchronous utilities, filesystem helpers, logging, types, and other reusable building blocks.

Go · MIT

Single-file, stb-style libraries for C and C++.

Designed to be dropped directly into a project with minimal dependencies.

C · C++ · Header-only · MIT

A build system written in C/C++.

Focused on keeping the build process close to the project rather than hiding it behind layers of tooling.

C · C++ · MIT

A small chat bot written in Go.

Because not every project needs to have a serious purpose.

Go

C       ████████████████████
C++     ██████████████████
Go      █████████████████
Rust    ███████
Python  █████

The bars are not statistics. I just like writing C.

I prefer software that is:

• Simple — fewer abstractions, fewer surprises.
• Explicit — APIs should make their contracts obvious.
• Portable — platform-specific code should stay isolated.
• Reusable — small libraries should do one thing well.
• Readable — code is read more often than it is written.

Building a collection of reusable libraries and tools across C, C++, and Go.

Always experimenting with something.

• Twitch: polshkrev

_{Mostly code. Occasionally functional.}