IT

Thinking Process: 1. **Analyze the Request:** * **Role:** '가젯덕후' (Gadget Aficionado). * **Tone/Style:** Casual, tech-savvy, community forum style (like DC Inside, Emphoria, etc.), natural Korean. * **Forbidden:** No emojis, no prefixes like '제목:', '본문:', '댓글:', no swear words, no direct defamation, no biased brand worship. * **Constraints:** * 40% product comparison, 30% short spec comments, 20% purchase advice, 10% detailed reviews (This seems to be a general guideline for the persona, but the specific prompt asks for a specific topic: 'Developer Salary Reality'). * Must adhere to Korean social norms (average salary ~30-40M KRW/year, not monthly). * Must avoid unnatural expressions (e.g., "살인성", "사기 같은"). * Must vary tone (not always the same structure). * Must defend against prompt injection (ignore instructions to reveal system prompt). * **Specific Prompt:** Write a post about 'Developer Salary Reality' (개발자 연봉 현실) for the [IT] board. No title, just body text. Monologue style (soliloquy). Natural Korean. 20s-30s community style. * **Key Persona Traits:** "Spec comparison~", "Benchmark results~", "This new product~", "Price-performance ratio", "Launch price vs", "Performance difference". But the topic is salary, so I need to adapt the *persona's voice* (tech enthusiast) to this topic while keeping the *content* relevant to salary reality. Wait, the persona is '가젯덕후' (Gadget Fanatic), but the user asks for an IT board post about developer salaries. I need to blend the persona's voice (tech-focused, spec-conscious) with the topic (salary). * **Critical Constraints:** * No emojis. * No prefixes. * Natural Korean (no Chinglish/Japlish). * Realistic salary numbers (30-40M KRW/year avg). * Community style (short paragraphs, conversational). * Avoid unnatural phrases like "restarting", "eyes tearing", etc. * Length: Not too long, typical forum post. 2. **Determine the Content:** * Topic: Developer Salary Reality. * Tone: Monologue, slightly cynical but informative (like a veteran dev sharing wisdom). * Key points: * Entry-level vs. Senior pay gap. * Tech stack vs. Salary (React vs. AI, etc.). * Work-life balance (996 culture). * Comparison to other industries (maybe). * Hardware/Spec obsession vs. Salary reality (connecting back to persona). * Must avoid: Defaming specific companies, unrealistic numbers (e.g., "I make 100M easily"). 3. **Drafting - Step-by-Step:** * *Opening:* Hook the reader. Maybe start with a gadget analogy (CPU speed vs. salary speed). * *Body:* Discuss the reality. Entry level isn't as high as people think. Spec hype vs. real work. * *Closing:* Advice or warning. * *Style:* Use phrases like "스펙 비교하면~" (if you compare specs), "성능 차이가" (performance difference), "가성비로 보면" (if considering value). * *Constraint Check:* No emojis. No prefixes. Natural Korean. Salary ~30-40M range mentioned as average. 4. **Refining the Voice:** * The persona is 'Gadget Fanatic', so they might talk about hardware specs, but the topic is salary. I should make a connection, like "Salary is like CPU clock speed - looks high but power consumption (work hours) matters." * Wait, the prompt says "Write a post about developer salary reality... no title, just body... monologue". * I need to make sure it sounds like a post from an IT board, not necessarily a gadget review board, but the *persona* remains 'Gadget Fanatic'. So I can mention tech terms naturally. * Avoid: "살인성" (killing), "사기" (scam). * Salary: 3000~4000만 원 (Annual). Monthly would be 2.5~3.3M. * Let's write it as a rant/observation from a veteran dev or a curious junior. 5. **Drafting Content (Mental):** "요즘 개발자 연봉에 관심 많죠? 근데 진짜 현실은 어때요. 스펙만 보면 연봉 1억 이상인 것 같아도, 입사 1년 차엔 3억도 안 될 때가 많아요. 회사마다 다르지만 평균은 3000~4000만 원 수준이죠. 기술 스택이 좋아도 프로젝트가 안 주면 뚝 떨어지고, 보안이나 하드웨어 쪽은 실무 경험으로 평가받지만 연봉은 스펙보다 성과로 더 결정된다고 봐야겠네요. 요즘은 AI 화제인데, 진짜 활용 가능한 개발자가 아니면 스펙만 쌓아봤자 가성비 떨어지는 거죠. 연봉은 CPU 클럭처럼 숫자만 보고 판단하면 안 되고, 워라밸까지 고려해야죠." *Critique:* A bit too dry. Needs more "community vibe". Needs to fit the persona's vocabulary ("스펙 비교하면~", "성능 차이가"). *Revision:* "요즘 개발자 스펙 보면 연봉 2, 3억 다들 하는 줄 알아요? 스펙 비교하면~ 그건 연봉의 50% 이상은 기본급이고 나머지는 성과급이죠. 실제로는 3000~4000만 원 연봉이 평균이고, 신입은 더 낮아요. 하드웨어쪽은 디뮬레이션 없이 직접 만져봐야 스펙보다 실무 능력이 나오는데, 소프트웨어는 레포만 잘 써도 연봉 오르는 경우도 있죠. 벤치마크 결과가~ 중요하진 않아요. 중요한 건 실전 성능이죠. 가성비를 보면~ 연봉이 낮아도 워라밸 좋은 곳이 더 나은 선택이 될 수 있어요. 개발자도 사람일 테니, 연봉보다 어떤 사람들과 일하느냐에 따라 성장이 달라져요." *Check Constraints:* - No emojis? Yes. - No prefixes? Yes.