"Day: Go. Night: Rust."
Personal blog and portfolio of daite — a developer based in Seoul, South Korea, writing about Go, Rust, and systems programming.
Live at daite.github.io.
I'm a developer who writes Go by day and Rust by night. This blog is where I document what I learn, share code walkthroughs, and think out loud about engineering problems — from concurrency patterns and CLI tools to memory safety and performance.
Topics covered:
- Go — web services, CLI tools, concurrency patterns
- Rust — systems programming, memory safety, performance
- Linux — shell scripting, tooling, server administration
- Jekyll — static site generator
- Chirpy theme — modern, text-focused, feature-rich
- GitHub Pages + GitHub Actions for CI/CD
- Full-text search
- Category and tag browsing
- Syntax-highlighted code blocks with line numbers
- Table of contents on every post
- Responsive, mobile-friendly design
- RSS feed and sitemap
- PWA support (installable, offline caching)
Prerequisites: Ruby 3.4+ and Bundler.
# install dependencies
bundle install
# serve locally at http://localhost:4000
bundle exec jekyll serve
# production build
JEKYLL_ENV=production bundle exec jekyll buildAdd a new Markdown file to _posts/ using the YYYY-MM-DD-title.md naming convention:
---
title: "Your Post Title"
date: 2026-04-18 09:00:00 +0900
categories: [Category]
tags: [tag1, tag2]
---
Your content here....
├── _config.yml # site configuration
├── _posts/ # blog posts
├── _tabs/ # sidebar pages (about, categories, tags, archives)
├── assets/
│ ├── css/
│ │ └── jekyll-theme-chirpy.scss # custom CSS overrides
│ └── img/ # images
├── .github/workflows/
│ └── pages-deploy.yml # CI/CD workflow
├── Gemfile # Ruby dependencies
└── index.html # home page entry
Pushes to main trigger the pages-deploy.yml workflow, which builds the site with Jekyll and deploys to GitHub Pages.
The site is wired for Google Analytics 4 (GA4) using Chirpy's built-in analytics support.
To enable tracking in production:
- Create a GA4 web data stream for
https://daite.github.io. - Copy the measurement ID, which looks like
G-XXXXXXXXXX. - In GitHub, open this repository's Settings > Secrets and variables > Actions.
- Add a repository secret named
GA_MEASUREMENT_IDwith that value.
The deploy workflow injects this secret at build time, so the tracking ID is not stored in the repo. Local development builds keep analytics disabled unless you intentionally provide your own override config.
- GitHub: github.com/daite
Content (blog posts) © daite. Theme © Cotes Chung, MIT-licensed.