Software engineer · .NET & Node.js · AWS
I build backends in .NET and Node.js and like the part of the job where code meets infrastructure: Terraform, CI pipelines, DNS, and the small tools that keep everything running.
Discord bot for a private server, running on deliberately overcomplicated infrastructure.
A bot for a friends-only Discord server. The features are small; the point is the playground around them: deployments, observability and cloud plumbing I wanted to try for real.
wiktorkowalski.pl and the blog. Astro, static, on Cloudflare, content in Markdown and YAML.
Two small Astro sites sharing one look. Every project here is a Markdown file, the CV and stack are YAML, and the posts on the NAS come from the blog’s JSON feed at build time.
My Cloudflare zones and DNS as code. PRs plan, merges apply, CI authenticates with OIDC.
Every DNS record I own lives in this repo. Pull requests show a terraform plan, merging to master applies it.
A Kubernetes cluster on AWS EKS built from scratch with Terraform.
Infrastructure for running my side projects on EKS: networking, the cluster and the Route53 plumbing around it.
A Minecraft server on AWS that starts when someone wants to play and shuts down when nobody does.
World data on EFS, the server on Fargate, and DNS that wakes the whole thing up. Costs close to nothing while nobody plays.
Example of hosting a static Astro site on S3 and CloudFront with Terraform.
The companion repo to the blog post about the same setup.