김정현 JH8459

I'm a software engineer who loves the Node.js ecosystem and TypeScript.
I mainly build RESTful APIs with NestJS, and frontend apps with Next.js.
I also enjoy writing and sharing practical insights.

💼 Career

스마일드래곤(주) / B.E Developer · Full-time [2025.07 – ]
코드잇 / Career Mentor · Freelance [2026.03 – ]
(주)에이시지알 / B.E Developer · Full-time [2022.04 – 2025.06]
코드스테이츠 / Career Mentor · Freelance [2023.03 – 2023.08]

🛠 Tech Stack

💻 Algorithm Solving

🌍 Open Source Contributions

Reporting regressions with minimal reproductions and sending fixes upstream in the Node.js backend ecosystem.

Repository	Contribution	Link & Status
forwardemail/supertest	🐛 Regression report + fix (7.3.0) On macOS, test requests could land on another local process: the ephemeral server binds the wildcard address while the client connects to `127.0.0.1`. Filed a plain-`http` reproduction and a PR that binds the server to the loopback address it connects to.	Issue #906 PR #907
mikro-orm/mikro-orm	🐛 v6 → v7 regression report Joined populate threw when a single-property embeddable shared its name with its column. Provided a minimal reproduction across v6.6.16, v7 and `next` on SQLite and MariaDB; fixed upstream within a day in #8293.	Issue #8292
ramiel/mikro-orm-cache-adapter-redis	♻️ `clear()` refactor Replaced mixed Promise and callback logic with a `for await...of` async iterator, keeping the batched `pipeline.del()` flow and the behavior unchanged.	PR #10

✍️ Writing

Contributing author at 요즘IT, writing about how backend teams build, review, and ship software in the AI era.

Date	Article
`2026.10.01`	하위 호환성은 언제까지 유지해야 할까? _{How long to keep backward compatibility across APIs, events, and DBs, via expand → migrate → contract.}
`2026.07.08`	이벤트 기반 MSA, AI 시대엔 더 비싸진다고요? _{Faster code changes don't make event-driven MSA cheaper; the cost shifts to tracing event flows and contracts.}
`2026.03.23`	cURL은 왜 버그 바운티를 끝냈을까? _{Why cURL ended its bug bounty: the bottleneck is no longer finding issues, but scarce human review capacity.}
`2026.02.25`	AI로 빨리 만드는 팀보다 '덜 흔들리는' 팀이 이기는 이유 _{In the vibe-coding era, teams win on decision quality, not coding speed: four questions that make AI output reviewable.}
`2026.02.10`	AI로 코드는 빨리 나오는데, 왜 출시는 그대로일까? _{AI speeds up implementation, so the bottleneck moves to validation, review, and approval before release.}

📚 Blog Posts

좋은 이슈 리포트는 어떻게 만들어지는가 - 2026.09.22
조용히 비어버린 값 하나에서 시작한 ORM 메이저 업그레이드 검증 전략 - 2026.09.18
53분짜리 크론 하나에서 시작한 배포 종료 설계 - 2026.09.08
복합 인덱스는 언제 필요할까? - 2026.08.09
Conductor에서 Supersets로 정착한 이유 - 2026.06.21

Navigation Menu

김정현 JH8459

Achievements

Achievements

Highlights

Block or report JH8459