About

One day in 2024, I was building a site with Next.js 14 when the middleware entered an infinite loop. I searched Google, checked GitHub issues, and found almost nothing. After three days of debugging, I finally found the root cause and wrote down the process. That post helped more people than I expected. Comments came in saying "I had the same issue and your post saved me." That's when I realized: the process of solving a problem I actually went through could be the fastest solution for someone else. This blog is an extension of that belief.

My name is Joel Park. I was born and raised in South Korea, and I currently live in Lisbon, Portugal. I got into coding in 2016, watching the match between Lee Sedol and AlphaGo. I read AlphaGo's architecture paper and realized "you can change the world by combining math and computers." That summer, I started learning Python. I began as a web developer at a small IT company, then went freelance. Now I focus on building trading systems and writing this blog. My dream is to build a quantitative trading company like Renaissance Technologies.

**No images.** All content is composed of code blocks and text only. **Tested in real environments.** Every code snippet and benchmark result has been verified in my actual development environment. **Sources are always cited.** Official documentation links, GitHub issue numbers, and release notes are always referenced.

- **Troubleshooting**: Records of how I solved real errors. - **Benchmarks**: Direct performance comparisons between frameworks, libraries, and tools. - **Deep dives**: Analysis of how specific technologies work internally. - **Migrations**: Problems encountered during version upgrades or technology switches. - **Architecture**: System design decision-making processes and their outcomes.