About this blog

A tech blog that investigates problems actually hit while building software, and shares guides and ideas useful for development along the way. Problem-solving posts lead with the cause and the fix, then show the investigation afterward.

How this is written

• The source material is the author's real development history. Only the points where work actually got stuck, and the causes that were actually confirmed, are picked from sessions where the author worked alongside AI coding tools.
• AI writes the draft, a human reviews it. AI assists in reading the record and producing a draft. Every article is published only after the author has read and approved it. Unapproved drafts never appear on this site.
• Nothing gets written if it can't be verified. Every factual claim in a draft is checked against the matching point in the work record. The citation markers used for that cross-check are removed from the published text.

The character script

The investigation section at the end of each article is written as a conversation between four characters — Jung Haneul, Park Dohyun, Jung Bada, and Park Doeun. All four are fictional; the real hypotheses and confirmations from the actual process are simply split across these roles.

Ads, affiliates, and support

• Only tools actually used while writing are mentioned. Affiliate links are marked affiliate, and any fee or credit the author may receive is disclosed up front and in the tool list.
• Support is optional. Articles stay free either way.