About

About

Hello. Apple-IO is a personal blog run by a single developer.

Author

  • Handle: GOLDTAGWORKS
  • Working as a developer since 1998 (currently 28+ years in the industry)
  • 2011–2017: Developer at RealNetworks
  • 2018–2021: Developer at Kakao
  • 2022–present: Developer at Kakao Entertainment
  • Current focus: AI-assisted development (Claude, ChatGPT) and side projects
  • Side projects in progress:
  • A tarot card reading web app
  • A Saju (Korean astrology) analysis app
  • A visual novel game (built with Ren'Py)

The development logs of the projects above are currently being curated and will be published gradually on this blog.

External Links

What this blog is about

This blog is about how to actually, comfortably weave AI into everyday development work in this fast-changing environment. Rather than the grand theories you see from many influencers, I write about the concrete problems a working developer runs into every day at the keyboard — how I actually use Claude, ChatGPT, GitHub Copilot, where I get stuck, and how I get unstuck — and I share those experiences personally, as a working developer.

Topics covered include:

  • Coding, debugging, and architecture design with AI tools
  • The full process of building real side projects with AI — wins and missteps
  • Hands-on experience with prompt engineering, AI agents, and emerging tooling like MCP
  • How developer workflow and productivity are shifting in the AI era
  • The doubts and detours working developers are going through in this era

Why I write

Even before AI showed up, the code I wrote 20 years ago, 10 years ago, a month ago, and today were all different. Why did I build it like that 20 years ago? Why did I do it that way 10 years ago? What about a month ago? Sitting with those thoughts, when I watch AI-generated code lose its context at some point, it feels like a familiar pattern from the past being projected onto the present.

There's no shortage of takes on how AI is changing software development. What I found rare were posts that concretely tracked which lines of today's code came out differently because of AI. So I started writing them. If they help someone else, great. If not, they're at least a useful logbook for future-me.

Editorial principles

  • No hype — I write about what AI does well and what it doesn't
  • Concrete examples — Code samples and before/after comparisons whenever possible
  • Failures included — Wrong choices and unsolved problems get documented honestly

Blog info

  • Domain: apple-io.com
  • Author: GOLDTAGWORKS
  • Started: 2026
  • Languages: Korean (primary), English (translation)

댓글

댓글 쓰기

이 블로그의 인기 게시물

개발자는 코드를 쓰는 사람이 아니다 — AI 시대에 남는 자리는 '책임'에 있다

개발자는 코드를 쓰는 사람이 아니다 — AI 시대에 남는 자리는 '책임'에 있다 AI 때문에 개발자가 없어질 거라는 말, 요즘 진짜 많이 듣는다. 특히 AI를 매일 쓰는 개발자들이 더 불안해하는 것 같다. 매일 AI가 자기 대신 코드를 짜는 걸 보다 보면, 이 일이 얼마나 더 이어질까 싶은 거다. 예전엔 주니어만 대체된다는 이야기였는데, 이제는 시니어까지 같이 묶여서 이야기가 나온다. 얼마 전엔 지인 한 명이 커리어를 바꿀까 고민 중이라고 했다. 30년 넘게 코딩했는데, 요즘 자기가 일주일 걸릴 작업을 AI가 몇 시간 만에 해치우는 걸 보면서 "내가 지금 쌓고 있는 스킬이 3년 뒤에도 의미가 있을까"라는 생각이 든다고 했다. 다른 한 명은 반대로, AI를 거의 안 쓰는 동료들을 보면서 "저 사람들 지금 뭐하고 있는 건가" 싶다고 했다. 같은 시기에 완전히 다른 종류의 불안을 겪고 있는 거다. 둘 다 이해는 간다. 근데 이 불안의 전제 자체가 틀렸다고 본다. 정확히는 반은 맞고 반은 틀렸다. 개발자가 없어지는 게 아니라, "개발자"라는 단어가 가리키는 대상이 바뀌고 있을 뿐이다. 근데 그 변화가 혼란스러워 보이니까 "개발자가 사라진다"는 쉬운 말로 퍼지는 것 같다. 작년에 사내에서 한 발표를 준비하면서 이 주제를 나름대로 정리해본 적이 있다. 주제는 복잡한 크로스플랫폼 데스크톱 앱을 리팩토링하면서 겪은 경험이었는데, 진짜 하고 싶었던 이야기는 프로젝트 경험담이 아니라 한 발짝 더 떨어진 곳에 있었다. "AI를 잘 쓰는 법"이 아니라, AI를 쓰다 보니 내가 하는 일의 무게중심이 어디로 옮겨가고 있는가. 그 이야기를 하고 싶었다. 그리고 1년이 지난 지금, 그때 적었던 결론은 오히려 더 또렷해졌다. 구현자에서 "다시 설계자로" 발표에서 썼던 문장 하나가 지금 다시 봐도 정확한 것 같다. 개발자가 사라지는 흐름이라기보다는,...
자세한 내용 보기

What Is Harness Engineering — Designing the Reins for AI Agents

What Is Harness Engineering — Designing the Reins for AI Agents In Part 1 of this series, I talked about the decline of prompt engineering. With CLI-based tools on the scene, the value of manually crafting elaborate prompts was fading. But as 2026 unfolded, I realized that what replaced prompt engineering wasn't simply "better tools." Prompt engineering gave way to context engineering, and now context engineering is giving way to an entirely new paradigm: harness engineering . In this post, I'll break down what harness engineering is, why it matters right now, and what its key components look like. A Harness for a Horse, a Harness for an Agent A harness originally refers to the tack fitted onto a horse. Bridle, saddle, stirrups — equipment designed not to suppress the horse's power, but to channel it in the right direction. In AI, the term means exactly the same thing. A harness is the entire external system that controls and directs an AI agent's power...
자세한 내용 보기

Harness Engineering in Practice — How Anthropic Designs AI Agents

Harness Engineering in Practice — How Anthropic Designs AI Agents The previous post covered the concept and components of harness engineering. This time, it's the real thing. Drawing on the concrete architecture patterns Anthropic published in their official engineering blog — along with experimental results from the OpenAI Codex team — let's look at how harnesses are actually applied in practice. The Basic Structure of an Agent Loop: The Inner Loop At the heart of every AI agent sits an agent loop . In Claude Code, it's called queryLoop . At its core, it's a while(true) loop. while (true) { 1. Prepare context (plan-mode attachments, task reminders) 2. Call the model (streaming API call) 3. Execute tools (detect tool call → validate schema → check permissions → execute) 4. Decide whether to continue (does the model have more to do?) } Each iteration is one "think, act, observe" cycle. The model thinks, invokes a tool, observes the resul...
자세한 내용 보기