[WEEK08-2] 추슬기#39
Merged
Merged
Conversation
raejun92
previously approved these changes
Apr 3, 2026
Collaborator
There was a problem hiding this comment.
역시 배열로 푸셨군요!
투 포인터를 금방 떠올리기가 쉽지 않은 것 같아요ㅠ
Align README with the revised study rhythm: three Programmers problems due by Wednesday night, Thursday lunch review/replay, and occasional SQL add-ons. Keep PR title guidance compatible with the existing automation flow so the documented process does not drift from the current script behavior. Constraint: Scope limited to README documentation only Rejected: Rename PR title format now | would diverge from current automation script Confidence: high Scope-risk: narrow Reversibility: clean Directive: If the automation workflow changes away from [WEEKNN-1], update the README and tooling together Tested: README diff review; searched README for removed Tuesday/Friday/4-problem wording Not-tested: Automation script behavior
Remove the Codex automation CLI section that was accidentally included with the README schedule update. The document should stay centered on the study process itself without personal tool usage notes. Constraint: Preserve the new weekly study schedule wording Rejected: Leave the CLI section in place | user wants README limited to study guidance Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep personal automation notes out of the shared study README unless explicitly requested Tested: README grep for removed CLI/script wording Not-tested: Any automation tooling behavior
sik9252
approved these changes
Apr 4, 2026
Collaborator
There was a problem hiding this comment.
역시 배열! ㅋㅋㅋ 배열에 값을 저장한 뒤 뒤에서부터 꺼내 비교하는 방식이라 직관적으로 잘 구현하신 것 같습니다~!
raejun92
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
이렇게 풀었어요
1. Palindrome Linked List
1) 복잡도 계산
2) 접근 아이디어
false를 반환하고, 끝까지 같으면 회문이라고 판단했다.3) 회고
스택으로 푸는 방식은 비교적 직관적이라 바로 구현할 수 있었는데,
다른 사람 풀이를 보니 결국 투포인터 방식이 더 효율적인 풀이인 것 같았다.
다른 사람 풀이:
다른 사람 풀이 핵심: fast/slow 포인터로 중간을 찾고, 뒤 절반을 뒤집은 뒤 앞 절반과 비교해서 추가 배열 없이 확인하는 방식이었다.
내 생각: 투포인터 방식이 더 효율적일 것 같은데, 그 방식으로 계속 안 풀다 보니 어떻게 적용해야 할지가 아직 잘 안 잡힌다. 계속 노출시키면서 익숙해져야 할 것 같다.
2. Move Zeroes
1) 복잡도 계산
2) 접근 아이디어
index위치로 옮겼다.index를 증가시켰다.3) 회고
0이 아닌 숫자를 앞쪽에 순서대로 다시 배치하고, 남은 자리를 0으로 채우는 방식으로 풀 수 있었다.
이 방식은 swap보다 더 직관적이고, 구현 실수도 적은 편이라 지금 단계에서는 훨씬 안정적으로 느껴졌다.
문제를 풀면서도 결국 핵심은
이 두 줄로 정리되는 문제였던 것 같다.