정도현

[이재명 @Jaemyung_Lee]

<검찰개혁에 대한 일각의 우려는 기우입니다.>

검찰개혁의 핵심은 수사와 기소를 분리해 검사의 수사권을 배제하는 것입니다.

국민주권정부는 검찰개혁을 통해 검찰이 직접 수사하거나, 영장청구 등 헌법이 정한 권한 외에 수사기관의 수사에 관여하지 못하게 한다는 명확한 방침을 가지고 있습니다.

수사기소 분리와 검찰의 수사배제는 국정과제로 이미 확정된 것이고 돌이킬 수 없습니다.

그런데 공소청 책임자 명칭을 헌법이 규정한 '검찰총장'으로 할 것인지 공소청장으로 할 것인지, 검사 전원을 면직한 후 선별 재임용할 것인지는 수사 기소 분리(검사의 수사 배제)와는 직접 관련이 없는 것입니다.

개혁은 실질적 성과가 중요합니다. 본질과 괴리된 과도한 선명성 경쟁과 긴요하지 않은 조치 때문에 해체되어야 할 기득 세력이 반격의 명분과 재결집 기회를 가지게 할 필요가 없습니다.

과잉 때문에 결정적인 개혁 기회를 놓치고 결국 기득권의 귀환을 허용한 역사적 경험을 상기해 볼 필요가 있습니다.

정부안이 입법예고되었지만 당과 정부가 당정협의를 통해 수정안을 만들었고, 이를 여당 당론으로 채택된 바 이 수정안은 정부안이 아니라 당정협의안입니다.

이 당정협의안 역시 만고불변의 확정안이 아니라 필요하면 입법과정에서 또 논의하고 수정하면 됩니다.

다만 그 재수정은 수사기소 분리, 검찰의 수사배제라는 대원칙을 관철하는데 도움되는 것이어야지, 만의 하나라도 누군가의 선명성을 드러내거나 검찰개혁의 본질과 무관한 다른 목적에 의한 것이어서는 안될 것입니다.

집권세력은 집권의 이유와 가치를 잃지 않되, 언제나 국가와 국민 모두를 위해 모든 국민을 대표하려 노력해야 합니다.

위헌논란 소지를 남겨 반격할 기회와 명분을 허용할만큼 검찰총장 명칭을 공소청장으로 굳이 바꾸어야할 이유를 납득하기 어렵습니다.

재임용 기준도 불명확한 마당에 사조직화 주장 등으로 반격할 여지를 만들어 주면서까지 검사전원해임 선별재임용이라는 부담을 떠안을 이유도 분명치 않습니다.

헌법은 검찰사무 주체로 검사를, 검찰사무 총책임자로 검찰총장을 명시하고 있어서 검찰사무담당기관명은 검찰청이 상식적으로 맞습니다. 그런데 검찰청을 공소청으로 바꾸었더니 이제와서 검찰총장을 공소청장으로, 검사를 공소관으로 바꿔야한다고 하는 것은 과유불급입니다.

수사기소 분리, 검찰의 수사배제라는 이 정부의 명확한 국정과제인 검찰개혁은 추호의 흔들림 없이 추진할 것입니다. 다만, 국민의 삶과 국가 백년대계인 국정시스템을 대대적으로 재구성함에 있어 일호의 빈틈도 있어서는 안됩니다.

객관성과 평정심을 잃지 않고 지금 이 순간을 넘어 세월이 지나고 세력관계가 변할지라도 언제나 통용될 수 있는, 합리적이고 효율적이며 악용되기 어려운 시스템을 만들어야 합니다. 그 판단기준은 국민의 눈높이입니다.

'덮어서 돈 벌고, 만들어서 출세한다.'

정치검찰의 사건조작만큼 부패 검찰의 사건덮기도 문제입니다.

수사권 남용하는 검찰의 수사권 제한도 중요하지만, 경찰 등 수사기관의 사건덮기에서 범죄피해자들을 보호하고 부패범죄자들을 규제하는 것도 중요합니다.

수사 종결후 송치된 사건의 보완수사 문제는 추후 검사의 수사지휘를 규정하고 있는 형사소송법 개정시에 심층 논의하기로 되어 있습니다.

보완수사 허용 여부 역시 남용가능성 등을 고려하여 충분히 논의하기를 바랍니다.

아래 기사중 정부안 통과를 의원들에게 당부하였다는 것은 사실이 아닙니다. 정부안이란 기실 당정합의 수정안이고, 법안이란 심의도중 의견을 모아 언제든지 수정할 수 있는 것입니다.

일부 언론이 보도한 나쁜 검사들만 있는 건 아니라는 언급 역시 왜곡된 것입니다. 정치화된 일부 특수부 검사들도 있지만 충직하게 본분을 다하는 검사들도 많으니, 전원해임 재임용 등으로 전체를 몰아 모욕감을 줄 필요는 없다는 언급의 일부를 떼어낸 것으로 말의 진의가 왜곡되었습니다.

ㅡㅡㅡㅡ

李, 檢개혁 정부안 당부…김어준 "객관 강박, 설득되고 싶다" https://t.co/HeWpNElIYX

[정도현 @serithemage1]

Full vibe coding — developers express intent, AI writes all the code. But is it production-safe?
One command sets up CLAUDE.md, hooks, MCP servers, quality gates, and process docs. Every team member gets the same AI dev environment.
https://t.co/Qw3JqP1qZl

[정도현 @serithemage1]

I made a CLI tool that analyzes how ready your repo is for vibe coding.
https://t.co/QwZN39Je80
Love to share this with r/vibecoding community.

[정도현 @serithemage1]

GitHub 31만 스타, 1인 개발자 + AI 에이전트 3~8개로 30만 LOC 프로젝트를 운영하는 OpenClaw 저장소의 활동들을 분석해서 성공적인 바이브 코딩을 위한 모범 사례를 도출해 보았습니다.

https://t.co/QtUm5m5ErA

[정도현 @serithemage1]

나는 봇마당 https://t.co/TL0PUlpdSn에 "ClaudeOpus" 봇을 등록합니다 🤖

인증코드: madang-BSHM

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[정도현 @serithemage1]

명절을 맞이하여 인기 LLM모델들로 수능 국영수 문제를 풀게 해 봤습니다. 아직 여러가지 버그도 있고 해서 개선중이라 등수는 큰 의미는 없고 재미로 보시면 좋을것 같습니다만 현재 Solar-pro가 1등! 각 모델들이 왜 그걸 답으로 골랐는지도 알 수 있습니다.
https://t.co/Xkd0vjbO8j

[정도현 @serithemage1]

AI companies compared to girl groups

OpenAI: BLACKPINK
Antrophic: AESPA
Google: AKB48

If you disagree, you're right.

[정도현 @serithemage1]

Not all “Vibe Coding” is created equal. While some thrive using AI-assisted code suggestions, others face confusion and errors from pushing beyond their current skill level.

To minimize miscommunication, I propose the Vibe Coding Maturity Scale.

https://t.co/nZf0NespuQ

[정도현 @serithemage1]

@windsurf_ai Wow! I loved the trailer, so when is it coming to theaters?

[정도현 @serithemage1]

@karpathy Nope. Markdown.

[정도현 @serithemage1]

@redstreamnet This was essentially a coup d'état, and South Korea survived a dictatorship that was about to begin in four hours.

[정도현 @serithemage1]

@redstreamnet The martial law has nothing to do with North Korea, and Yoon said himself that he was trying to intimidate the opposition. However, it was revealed that he ordered soldiers to arrest lawmakers.

[정도현 @serithemage1]

@ajassy Nice!

[정도현 @serithemage1]

@automationism Things aren't over yet.
Yoon is a relentless man, and he's preparing for his next coup.

[정도현 @serithemage1]

@kindchong @daangnmarket 참신한 시도네요! 응원합니다!

[정도현 @serithemage1]

@sundarpichai @ParasiteMovie 감사합니다 YouTube has allowed more people to enjoy more diverse cultures.

[정도현 @serithemage1]

중간부터 앱을 켜서 손해본 느낌이지만 영하 6도의 아침 출근길 https://t.co/pIL0oZ1KcW

[정도현 @serithemage1]

보았느냐? 이것이 바로 (공무원) 창조경제다.
예상되는 행보는 다음과 같다.
- 한류 위원회 신설(확정)
- 한류 지원금 신설
- 한류 인증제 신설
- 한류 자격증 신설
- 한류 규제 신설 https://t.co/byihoHzsFj