---
title: "A Software Engineer's IRONMAN PENGHU 226 Journal - Part 2: Race Day"
description: "Race-day account of IRONMAN Penghu 226: dealing with foggy goggles in the open water swim, bike segment strategy, fighting through cramps on the run, and reflections at the finish line."
canonical_url: "https://blog.markkulab.net/en/post/ironman226-racing-day"
author: "Mark Ku"
author_url: "https://blog.markkulab.net/en/author/mark-ku"
site: "Mark Ku's Tech Notes"
date_published: "2022-04-12 01:01:01 +0800"
category: "Triathlon"
tags: ["ironman", "226", "triathlon", "鐵人三項", "澎湖", "比賽", "完賽"]
language: "en"
license: "CC BY 4.0"
license_url: "https://creativecommons.org/licenses/by/4.0/"
attribution: "when reusing or quoting, credit the author and link back to the original"
---
# A Software Engineer's IRONMAN PENGHU 226 Journal - Part 2: Race Day
#### Related Links
[A Software Engineer's IRONMAN PENGHU 226 Journal - Part 1: The Preparation](https://blog.markkulab.net/2022/03/14/ironman226/)
#### Two days before the race - Early morning, off to Penghu with my luggage
#### Once at the Penghu hotel, I quickly assembled my bike and went for a spin. About 200m in I got a flat, so I took it to the IRONMAN venue mechanics for inspection. Turned out I'd run over a very thin nail. Honestly, lucky! Glad it surfaced before the race. In the afternoon we did a 30km bike course familiarization ride.
#### A month before the race I'd noticed bruising on the inside of my right ankle and had been applying ointment. Walking and easy running were fine, but bending the foot at certain angles hurt — I was scared the old injury was flaring up. So in Penghu I hit several drugstores and finally found an L-size ankle brace.
#### One day before the race - To keep nerves from affecting performance, I went with Kevin to Shili Beach for a test swim. Facing a bottomless ocean, I wasn't fearless, but training had made me brave! That day the waves were small and easy to swim.
## Race Day - D-Day
The wait before getting in the water is always the hardest — I was beyond nervous, having never swum this long an open water distance in my life.
(Because I'd loaded up on dinner the night before and lots of bread for breakfast, I forgot to suck my stomach in for the photo — the puffy dolphins waiting to enter the water - The Puffy Dolfins)
## Swim 3.8 km
Just as dawn broke, the gun went off at 6:00 and athletes entered the water in waves. About 1000m in, my goggles fogged up — I could barely see anything. I flagged down a lifeguard for direction, and he told me to swim toward the sun. I felt increasingly off-course, then found another lifeguard who let me grab onto a SUP and tread water while I rinsed my goggles in the sea. Only then could I continue. With the tide rising, by the time I rounded the third buoy heading back to shore, I was hit by a strong counter-current — really tough swimming. Eventually I found a guy with a similar pace and drafted off him, finally exiting the water at 2:11.
## Bike 180 km (1200m elevation)
As the sun rose and around 11am, the Penghu course got blazing hot. I started pouring water over myself, holding wattage around 120W. The wind in Penghu was strong, with both tail and headwinds — I rested on the tailwinds and put down steady output on uphill headwinds, while taking in at least 80g of carbs per hour and topping up water. I finished the bike segment cleanly and entered the run.
## Run (42 km)
Surprisingly, after the bike, I didn't cramp up like in past triathlons. The sun was scorching, so I held an 8-9 min/km pace, jogging steadily until around 20km, when the outside of my right thigh started seizing. I couldn't keep running, so I walked nearly 10km, eating at aid stations to recover. Then the announcer called out that there was only 1 hour 20 minutes until the cutoff. I felt time was tight and didn't want to walk away with regret. With the last 10km loop ahead, my right outer thigh was still seizing, but I told my right leg, "We've trained for half a year — just hang on for one more hour and twenty minutes!" Strangely enough, it stopped hurting. I crossed the finish arch with arms raised, 13 minutes before the cutoff, and heard "You're an IRONMAN!" — yes, I'd taken on myself once again and won.
(The official race clock broke and stopped at 13:77:17)
## Final Thoughts
Triathlon has given me far more than I ever expected — and I couldn't have gotten here alone. Thanks to everyone who's helped me along the way.
Over the years I've been looked after by two bosses / triathlon partners. From Kevin Yeo I learned team management and grit; from Harry Chen, crisis handling and leadership.
Most of all, thanks to my girlfriend LALA, who flew over from Taiwan to be there for the race, document this important moment, and even prepared a special restaurant celebration.
Finally, thanks to my brother for training with me at the open water year after year. This time, when my goggles fogged up mid-swim and I could barely see anything, I stayed calm, found someone on a SUP, and treaded water to clean my goggles.
Going forward, on the racetrack of life, we all face our own challenges. Find your balance, keep moving forward steadily — go for it!
## Reflection
That night is etched into my memory.
I almost didn't make it back,
and it gave me a new understanding of what IRONMAN means.
"What is an IRONMAN? It's when you've been through everything,
your body is exhausted, your legs are trembling,
and you're still running toward your goal!"
[Run video](https://youtube.com/shorts/lu5XPx0K6Vo)
## Series Articles
* [A Software Engineer's IRONMAN PENGHU 226 Journal - Part 1: The Preparation](https://blog.markkulab.net/2022/03/14/ironman226/)
* [A Software Engineer's IRONMAN PENGHU 226 Journal - Part 2: The Preparation](https://blog.markkulab.net/2022/04/11/ironman226-racing-day/)
---
## About this article and its author
Originally published on [Mark Ku's Tech Notes](https://blog.markkulab.net/en/post/ironman226-racing-day)
License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) — when reusing or quoting, credit the author and link back to the original
### About the author
**[Mark Ku](https://blog.markkulab.net/en/author/mark-ku)** — Software Solution Provider
- 10+ years senior software engineer, now an AI Builder
- Focused on large-platform architecture — North-American e-commerce, AI SaaS subscription billing
- Combining AI Agents and automation to build evolvable product foundations
### Free tools built by the author
All of these are free to use:
- [Free PDF Sign Tool](https://blog.markkulab.net/en/tools/pdf-sign): Online PDF sign tool — draw, type, or upload a signature, then drag, resize, and download. Everything runs in your browser; nothing is uploaded.
- [VS Code Refactory](https://blog.markkulab.net/en/tools/refactory): Refactory is a VS Code refactoring extension: 34 actions plus a 37-rule code-smell inspection layer with a Code Health dashboard, across 18 languages, backed by 534 tests. It learns your repo's conventions: where interfaces live, where DI is registered, whether 'use client' belongs. It ranks files by git churn × complexity so you know what to fix first, and hands any smell to the Claude Code already on your machine. Free to use, and your source never leaves your computer.
- [DB-Kit Database Manager](https://blog.markkulab.net/en/tools/db-kit): DB-Kit is a lightweight, cross-platform database manager built with Tauri + Rust + React. Manage MySQL, MariaDB, PostgreSQL, SQL Server, Oracle, SQLite, MongoDB, Redis, Kafka, Elasticsearch and RabbitMQ from one consistent interface: passwords encrypted in the OS keychain, SSH tunnels, full CRUD, a visual query builder, stacked multi-statement result sets, cross-connection data transfer and compare/sync, Excel / CSV import & export, visualized execution plans, ER diagrams, scheduled backups, SQL stress testing with p50–p99 latency percentiles, a 15-rule SQL review engine, Kafka message browsing with monitoring & alerts, a bilingual UI (Traditional Chinese / English), a built-in AI assistant (natural-language SQL, AI review and tuning advice) and the dbk CLI. Free and open source (MIT), with installers for Windows, macOS and Linux.
- [VS Code Super Mermaid](https://blog.markkulab.net/en/tools/super-mermaid): Super Mermaid is a VS Code extension for beautiful Mermaid diagrams out of the box: auto-colored live preview, mouse pan & zoom, high-res PNG / SVG export, 21 templates and multiple themes. Free and open source (MIT).
- [React Super Mermaid](https://blog.markkulab.net/en/tools/react-super-mermaid): react-super-mermaid is an open-source React component library: render beautiful Mermaid diagrams with a single , with built-in colorful / sketch themes, pan & zoom, in-diagram search, and high-res SVG / PNG export. Lightweight, SSR-safe, fully typed. Free and open source (MIT).
- [Jira / Confluence Super Mermaid](https://blog.markkulab.net/en/tools/jira-super-mermaid): An Atlassian Forge app: write Mermaid syntax directly inside a Jira issue or a Confluence page and get flowcharts, sequence diagrams, state machines and Gantt charts. 11 diagram types, SVG / PNG export, light and dark themes, full CJK support. Runs on Atlassian: your diagrams live in your own site and the app calls no third-party service. Free, coming soon to the Atlassian Marketplace.
- [Mermaid Live Preview](https://blog.markkulab.net/en/tools/mermaid-preview): Write Mermaid in your browser, see it render instantly, and share the whole diagram as a single link. No sign-up, nothing uploaded to a server, and mermaid.live share links work as-is.
- [React Intl Phone Number](https://blog.markkulab.net/en/tools/react-intl-phone-number): react-intl-phone-number is an open-source React component: framework-agnostic and antd-free, with E.164 in/out, a searchable flag / country-code dropdown, configurable validation levels (strict / mobile-strict / loose), themeable CSS, and i18n — phone logic powered by google-libphonenumber. Lightweight and fully typed. Free and open source (MIT).
- [Uptime Kuma Cluster](https://blog.markkulab.net/en/tools/uptime-kuma-cluster): Turn single-node Uptime Kuma into a highly available cluster: OpenResty + Lua smart load balancing, shared MariaDB state, health checks and automatic failover, plus cluster-management REST APIs. One Docker Compose command to start. Free and open source (MIT).
- [Special Education](https://blog.markkulab.net/en/education): Learning materials crafted for special education students
### Daily podcasts
- [Mark's Tech Insights — Daily AI News](https://blog.markkulab.net/en/category/tech-news): Daily curated AI and tech trends. Catch the latest developments via audio summaries — covering AI applications, software architecture, DevOps, and engineering practice. — RSS: https://blog.markkulab.net/feed.xml
- [AI股市蝦聊](https://blog.markkulab.net/en/category/ai-stock-chat): Every trading day, an AI-analyzed take on the Taiwan stock market, delivered as a two-host conversation covering the session and the next-day outlook. — RSS: https://blog.markkulab.net/ai-stock-chat/feed.xml
- [開源好物週報](https://blog.markkulab.net/en/category/open-source-weekly): A weekly two-host pick of free open-source tools surfaced from real Hacker News, GitHub, and Reddit buzz — what pain they solve and the fastest way to get started. — RSS: https://blog.markkulab.net/open-source-weekly/feed.xml
### Newsletter
[Subscribe to the newsletter](https://blog.markkulab.net/en/subscribe) — Be the first to know about new posts. No spam, unsubscribe anytime.