저는 이번에 Java hwplib을 .NET으로 포팅하면서 AI 코딩 어시스턴트를 활용했습니다. 단순 포크가 아닌, 원본과 지속 동기화되는 'Living Port' 방식입니다.
C# 파일에 원본 Java 파일 힌트를 남기고 AI가 upstream diff를 분석하게 했더니, 동기화 시간이 80% 이상 줄었습니다. AI는 경험을 대체하는 게 아니라 증폭시킵니다.
https://devwrite.ai/ko/posts/hwplibsharp-upstream-management/
#OpenSource #DotNet #CSharp #AI #HWP #LivingPort #MicrosoftMVP #AIAssistedDevelopment #GitHub
![Wait - I need the cancelled message to arrive BEFORE quitting. The message comes through the queue which Tea processes in its event loop. But once "q" is processed, the loop exits. Maybe I need more event loop iterations between "c" and "q".
Actually, looking at test
Not just the test. Shouldn't the _runtime_ forcibly stay open until all commands are finsihed?
Thought for 13s
You're right! When the runtime exits (Command.exit), it should wait for active commands to finish or cancel them. That's the shutdown behavior from the spec (Unit 4d).
Let me add it to make the test pass:
Analyzed @runtime.rb#L70-80
Or should you consider that to be a pre-requisite, stash your changes, implement just that with [@/tdd], then come back in and pop _just_ your test off the stash?
Thought for 3s
Yes, that's the proper TDD approach. My cancel test depends on shutdown behavior. I should:
1. Stash current changes
2. TDD shutdown (Unit 4d)
3. Pop just the cancel test back
~/…/ratatui_ruby-tea $ git stash push -m "WIP: cancel_command test + impl with debug" -- lib/ratatui_ruby/tea/runtime.rb test/test_runtime_custom_command.rb
Run command? [Reject] [Accept]](https://files.mastodon.social/cache/media_attachments/files/115/873/882/048/466/770/small/26c9c5432d9178f0.png)


