2-6. In-class (1)

Google Technical Writing Course - 2

Course1과 마찬가지로 특별히 답안이 있는게 아니라, 라이브 세션으로 진행하면서 서로 의견을 나누는 실습활동.

다만 Course1보다 난이도가 조금 높아서 첨삭이라도 받고 싶은데, 당장은 수가 없으니...

이번에도 챗GPT의 도움을 받기로 했다. 우선 먼저 시도해보고, 챗GPT한테 모범답안을 달라고 하기.

Exercise 1: Writing is Rewriting

아래 'An Introduction to Hard Links in Linux' 문서의 초안 편집하기.

Part 1/2로 나누어 진행된다.

You need to know about Linux commands prior to reading this document. This document explains a lot of introductory material about hard links, not soft (symbolic) links. Suppose you run a Linux command that creates a file. When you create this file, Linux creates the contents of that file and a filename. A filename is a hard link to the contents. A hard link is a pointer from the filename to the contents. Now, here's the interesting part: you can create multiple hard links to the same existing content. For example, the command echo "Hello There." > foo creates a file named foo containing the textual contents "Hello There." The command ln foo bar is a way of creating a hard link named bar that points to the contents of foo. Changing foo and bar are now synonymous. You can create lots and lots of hard links to the same content. Any change made to foo will also appear in bar.

Part 1

위 문단을 4개 파트로 나누고, 적절한 소제목을 붙일 것.

그런데 이 문단의 내용 자체가 이해가 잘 되지 않아서, 먼저 챗GPT의 해석+설명 도움을 받았다.

영어 번역 자체가 되지 않은 것은 아니지만, 직역해도 이해가 되지 않았다. 예를 들어 "The command ln foo bar is a way of creating a hard link named bar that points to the contents of foo." 라는 문장에서 "In foo bar" 자체가 명령어(command)라는 걸 바로 파악하지 못했기에, 어떻게 나누어야 할지도 감이 잡히지 않았던 셈.

어쨌든 그렇게 도움을 받고 나서 시도한 결과는 아래와 같다.

1. Prerequisites

You need to know about Linux commands prior to reading this document.

2. What this document explains & not.

This document explains a lot of introductory material about hard links, not soft (symbolic) links.

3. Concepts of hard links

Suppose you run a Linux command that creates a file. When you create this file, Linux creates the contents of that file and a filename. For example, the command echo "Hello There." > foo creates a file named foo containing the textual contents "Hello There." A filename is a hard link to the contents. A hard link is a pointer from the filename to the contents.

4. Advanced topics (Learn more)

Now, here's the interesting part: you can create multiple hard links to the same existing content. The command ln foo bar is a way of creating a hard link named bar that points to the contents of foo. Changing foo and bar are now synonymous. You can create lots and lots of hard links to the same content. Any change made to foo will also appear in bar.

나누고 재배열하면서 문장이나 어휘를 고치고, 연결어를 추가하고 싶은 욕구가 엄청나게 차올랐지만, 잠시 눌러두고 챗GPT의 답을 먼저 참고해보았다.

1. Prerequisites

You need to know about Linux commands prior to reading this document.

2. Introduction to Hard Links

This document explains a lot of introductory material about hard links, not soft (symbolic) links.

A hard link is a pointer from the filename to the contents.

A filename is a hard link to the contents.

3. How Hard Links Work

Suppose you run a Linux command that creates a file.

When you create this file, Linux creates the contents of that file and a filename.

Now, here's the interesting part: you can create multiple hard links to the same existing content.

4. Example Commands and Behavior

For example, the command echo "Hello There." > foo creates a file named foo containing the textual contents "Hello There."

The command ln foo bar is a way of creating a hard link named bar that points to the contents of foo.

Changing foo and bar are now synonymous.

You can create lots and lots of hard links to the same content.

Any change made to foo will also appear in bar.

챗GPT의 답변과 내 답변이 좀 많이 다른데, 우선 크게 2가지.

1) 나는 'Hard link에 대한 소개'를 빠뜨리고 바로 "Suppose~"로 넘어갔다.

2) 내가 Flow 위주로 문장을 배열하려 했다면, 챗GPT의 답은 항목별 분류에 가깝다. 가령 예시는 예시로 싹 다 몰았다.

아직은 두 답변 모두 어색하니, Part2로 바로 넘어가보기.

Part2

Part2는 말 그대로 최대한 잘 고치기.

먼저 초안을 작성한 후, 챗GPT한테 점검을 요청했다.

챗GPT가 피드백 준 부분을 빨간색으로 표시하고, 챗GPT 수정 버전은 파란색으로 표시했다.

1. Prerequisites

You need to know about Linux commands prior to (→ before) reading this document.

→ "prior to"라는 표현은 다소 어색한 형식적 표현

챗GPT) Before reading this document, you should be familiar with basic Linux commands.

2. About this document

This document explains a lot of introductory material about hard links, / not soft (symbolic) links.

→ "a lot of introductory material"은 너무 포괄적이고 모호함.

→ "not ~~" : 부차적인 부분은 분리

챗GPT) This document introduces the concept of hard links in Linux. Soft (symbolic) links are not discussed in this guide.

3. What is(→ are) hard links?

A hard link is a pointer from the filename to the contents. Suppose you run a Linux command that creates a file. Linux creates the contents of that file and a filename. The filename is a hard link to the contents. Below is the example:

· The command echo "Hello There." > foo creates a file named foo containing the textual contents(→ text) "Hello There."

· The filename 'foo' is a hard link to the contents "Hello There."

→ "filename is a hard link to the contents"가 반복됨.

→ 문장 간 연결이 부자연스러움. 예시로 넘어가기 전 짧은 전환 문장 필요.

챗GPT)

In Linux, a hard link is a filename that points directly to the file’s content on disk. When you create a file, Linux stores two parts: the content itself and the filename that references it. This filename is considered a hard link.

Example

- The command `echo "Hello There." > foo` creates a file named `foo` containing the text "Hello There."

- The filename `foo` is a hard link to that content.

**설명 부분에 대한 챗GPT 답변이 너무 달라서, 내 수준에서는 어떻게 더 낫게 고칠 수 있었을지 생각하며 내 초안 기준으로 수정해봤다.

A hard link is a pointer from the filename to the contents. When you create a file, Linux makes contents and a filename. This filename is considered a hard link.

4. Creating Multiple hard links

You can create multiple hard links to the same content.

· The command `ln foo bar` creates a hard link named bar that points to the contents of foo.

· Changing foo and bar are now synonymous. Any change made to foo will also appear in bar.

→ "Changing foo and bar are now synonymous"라는 표현은 문법적으로도 어색하고 의미도 모호함. 특히 "synonymous"는 보통 '단어나 개념이 비슷하다'는 뜻으로 쓰이기 때문에 여기서는 부자연스러움.

→ "둘 다 같은 파일을 가리키므로 어느 쪽을 수정해도 동일한 결과를 나타난다"는 점을 직접적으로 설명하는 것이 나음.

** Header의 경우 "실제 작업하는 내용이 담기는 것"이 좋음.

⇒ 링크의 "Prefer task-based headings" 참고: https://brunch.co.kr/@eebbc6d856334ef/42

챗GPT)

You can create additional hard links to the same file content.

- The command `ln foo bar` creates a new filename `bar` that points to the same data as `foo`.

- Since both `foo` and `bar` refer to the same content, modifying one affects the other. Any changes made to `foo` will appear in `bar`, and vice versa.

챗GPT의 답변을 보면 중복되는 표현은 최소화하는 것을 알 수 있다.

그리고 따옴표는 코드에서 쓰이니, ``를 쓰는 것을 기억하자.

두 번째 예시는 modifying~ 구문과 뒷 문장이 동일한 내용인 것 같은데, 아래처럼 합쳐버리면 어떨까?

- Since both `foo` and `bar` refer to the same content, any changes made to `foo` will appear in `bar`, and vice versa.

뭐가 더 나은지는 잘 모르겠다.

취향의 차이일까?

*출처 : https://developers.google.com/tech-writing/twol/rewriting