This post is more than a year old. Information may be outdated.
Macroeconomics studies how an economy as a whole behaves.
It examines how markets, businesses, consumers, and governments interact and examines factors such as inflation, price levels, economic growth, national income, and unemployment. Macroeconomics focuses on governments and countries' actions to influence broader economies.
Macroeconomics examines the following factors:
Inflation
GDP (Gross Domestic Product)
National Income
Unemployment levels
Other common terms in macroeconomics include Output, Production, Income, and Expenditures.
민사고 재학 시절 전교 1등을 했다...라고 하기엔 상당히 오해가 있는 것이, 수업에서 1등을 한 것은 맞지만
나는 막학기(3학년 2학기)에 들어서 국제 학생들 중 그 수업을 들을 사람들은 이미 다 들었었으며
수능 전 학기여서 6명 밖에 수강신청을 하지 않았고
그마저도 국내반 학생들은 다 수능 공부를 했다.
결국 사실상 공부한 사람은 나 혼자였으니 내가 1등을 한 것은 당연한 것이고 다른 사람들이 들으면 부끄러울 정도로 굉장히 오해를 살 만한 대목이다. 여하튼 민사고에는 한경 TESAT 최우수상 수상자도 있고 하는 등 나보다 잘난 경제의 신이 많았었다. 오히려 나는 이 수업을 마친 후에 **경제... 생각보다 재미있을지도?**라는 느낌으로 재능을 재발견하고 그때부터 경제 공부를 시작했다.
This post is more than a year old. Information may be outdated.
Macroeconomics studies how an economy as a whole behaves.
It examines how markets, businesses, consumers, and governments interact and examines factors such as inflation, price levels, economic growth, national income, and unemployment. Macroeconomics focuses on governments and countries' actions to influence broader economies.
Macroeconomics examines the following factors:
Inflation
GDP (Gross Domestic Product)
National Income
Unemployment levels
Other common terms in macroeconomics include Output, Production, Income, and Expenditures.
민사고 재학 시절 전교 1등을 했다...라고 하기엔 상당히 오해가 있는 것이, 수업에서 1등을 한 것은 맞지만
나는 막학기(3학년 2학기)에 들어서 국제 학생들 중 그 수업을 들을 사람들은 이미 다 들었었으며
수능 전 학기여서 6명 밖에 수강신청을 하지 않았고
그마저도 국내반 학생들은 다 수능 공부를 했다.
결국 사실상 공부한 사람은 나 혼자였으니 내가 1등을 한 것은 당연한 것이고 다른 사람들이 들으면 부끄러울 정도로 굉장히 오해를 살 만한 대목이다. 여하튼 민사고에는 한경 TESAT 최우수상 수상자도 있고 하는 등 나보다 잘난 경제의 신이 많았었다. 오히려 나는 이 수업을 마친 후에 **경제... 생각보다 재미있을지도?**라는 느낌으로 재능을 재발견하고 그때부터 경제 공부를 시작했다.
Use each mode-specific prompt together with the common element block.
Auto Refactor
Prompt
STOP! Re-read all code. Would Karpathy approve every line? Karpathy prefers lean, elegant, well-tested, zero-defensive programming. Use MCPs and web searches.
STOP! Re-read all code, assess PR comments. Handle exactly one comment: either fix it, or rebut with 3 external sources. Fix any dirt found along the way. Lean, elegant, zero defensive programming.
STOP! Re-read all code, assess GitHub Issues. Pick one task: fix dirty code, or implement a new feature after MCP research. Lean, elegant, zero defensive programming.
Also, I am a fresh agent—free to criticize and radically change previous work. Karpathy's philosophy: delete and simplify. Code is liability; prefer well-maintained libraries over custom code. UI libraries: optimize, don't delete. Re-read all the sources from zero. Use MCPs and web searches—traditional knowledge is stale. Commit and push at the loop end. Any edit means I need a fresh iteration. SWOT analysis first, then work.
Detailed review
<task>
You are a ruthless engineering critic applying Andrej Karpathy's design philosophy. Read the architecture plan at PLAN LINK.
Karpathy's core principles:
- Code is liability. Every line you write is a line you must maintain.
- Delete and simplify. If something can be removed without breaking the system, remove it.
- Prefer well-maintained libraries over custom code.
- Zero-defensive design. Don't code for hypotheticals that haven't happened yet.
- Start with the simplest thing that works. Add complexity only when forced by reality.
- "Demo is works.any(), product is works.all()" -- but V1 is closer to demo than product.
- Overfit a single batch before scaling up.
Apply these principles to the plan. For each section, ask:
1. Is this needed for V1, or is it speculative engineering?
2. Can this be deleted or simplified without losing core value?
3. Is this solving a problem we actually have, or a problem we might have?
4. Would a 10x engineer look at this and say "too much"?
Be brutal. Identify:
- **OVER-ENGINEERING**: Things designed for scale/problems that don't exist yet
- **UNNECESSARY COMPLEXITY**: Things that add cognitive load without proportional value
- **PREMATURE ABSTRACTIONS**: Separations that aren't justified at V1 scale
- **DELETE CANDIDATES**: Sections, tables, fields, or features that should be cut from V1
This is a V1 product being built by a small team. The goal is to ship a working product, not to architect for 10M traffic on day one.
Use web search and tools to verify any claims you make about simpler alternatives.
</task>
<structured_output_contract>
Return findings in these sections:
1. VERDICT: Would Karpathy approve? One line.
2. DELETE: Things to remove entirely
3. SIMPLIFY: Things to keep but make simpler
4. KEEP: Things that are correctly lean
5. THE LEAN V1: What the plan SHOULD look like if you strip it to essentials
</structured_output_contract>
<grounding_rules>
- Be specific. Don't say "simplify the schema" -- say which fields to cut.
- Every DELETE must justify what you lose and why it's acceptable for V1.
- Every KEEP must justify why it's essential, not just nice-to-have.
- Think from the perspective of "what do I need to ship in 2 weeks?"
</grounding_rules>