Elon's philosophy is great - how about using it for our daily job's management checklist?

Core Worldview & Purpose

• Elon Musk believes life should meaningfully improve the future, not just generate profit.

• Maximizing the probability that humanity survives long-term is a core motivation (multi-planetary life, AI safety).

• Civilizational progress is fragile and can stagnate or regress without active effort.

• Technology is the primary lever for accelerating human progress.

• Optimism must be engineered, not assumed.

First Principles Thinking

• Break problems down to fundamental physics or economics, not analogy.

• Analogy-based thinking is dangerous because it preserves outdated assumptions.

• Question every requirement: “Why does this exist?”

• Delete parts or processes before optimizing them.

• If you’re not adding things back later, you didn’t delete enough.

• Reason from what must be true, not what is common practice.

• Constraints are often imaginary, especially in engineering and regulation.

Engineering & Design Philosophy

• The best part is no part (reducing complexity improves reliability).

• Systems fail because of interfaces, not components.

• Design for manufacturability from day one, not as an afterthought.

• Overengineering is usually worse than underengineering.

• Prototypes should be ugly and fast, not polished.

• If a design isn’t failing, it’s not being pushed hard enough.

• Iterative improvement beats perfect upfront design.

• Vertical integration increases learning speed.

Work Ethic & Personal Discipline

• Extreme work hours are sometimes necessary to achieve extreme outcomes.

• Leaders should suffer more than their teams, not less.

• Being tired is acceptable; being complacent is not.

• Urgency is a moral obligation when working on existential problems.

• Comfort is the enemy of progress.

• High tolerance for pain is required to do important things.

• Sacrifice is justified if the mission matters enough.

Risk, Failure & Resilience

• Failure is information, not embarrassment.

• If you’re not failing, you’re not innovating fast enough.

• Taking no risk is the biggest risk.

• Public failure is acceptable if learning is extracted.

• Betting the company can be rational if the alternative is slow death.

• Survivability matters more than elegance.

Leadership & Management

• Titles are meaningless; contribution is everything.

• The best leaders are deeply technical.

• Managers should know more than their subordinates in at least one key domain.

• Chain of command should never block communication.

• Anyone should talk to anyone if it improves the product.

• Micromanagement is acceptable during crisis or innovation.

• Bad news should travel faster than good news.

• Meetings are a tax on productivity and should be minimized.

Hiring & Talent Philosophy

• Exceptional people are orders of magnitude more valuable than average ones.

• Skill matters more than credentials or degrees.

• Demonstrated ability > resume prestige.

• Smart people with low energy are less useful than driven people with slightly less intelligence.

• Small, elite teams outperform large bureaucracies.

• Cultural fit means commitment to truth and mission, not comfort.

Economics, Business & Capital

• Profit is a means, not the goal.

• Margins follow product excellence, not the reverse.

• Lowering cost expands demand and accelerates adoption.

• Scale is a moral force when it spreads beneficial technology.

• Short-term financial optics should not dominate long-term value.

• Subsidies are acceptable if they accelerate critical transitions (e.g., clean energy).

• Capital should be spent aggressively when opportunity is asymmetric.

Time, Speed & Execution

• Speed is the ultimate competitive advantage.

• Delays compound invisibly but catastrophically.

• Most timelines are wrong because people assume linear progress.

• If something takes long, question the assumptions, not just the effort.

• Decision velocity matters more than decision perfection.

• Bureaucracy exists to slow things down—fight it actively.

Truth, Reality & Communication

• Reality is the ultimate arbiter, not opinion or authority.

• You cannot negotiate with physics.

• Being wrong is acceptable; staying wrong is not.

• Candor is more respectful than politeness.

• Hard truths should be stated plainly.

• Narratives that feel good but are false are dangerous.

• Free speech is essential for error correction.

Society, Culture & Humanity

• Civilizations die from complacency, not catastrophe alone.

• Birth rate decline is a major civilizational risk.

• Energy abundance correlates with human flourishing.

• Technology should expand individual agency, not reduce it.

• Centralized control tends toward stagnation.

• Censorship is often justified emotionally but harmful structurally.

• Human curiosity is sacred and must be protected.

Space & Long-Term Civilization

• Earth is humanity’s cradle, not its permanent home.

• Single-planet species face inevitable extinction.

• Mars is the best near-term backup for civilization.

• Reusability is the key to space becoming affordable.

• Making life multi-planetary is a moral imperative, not a luxury.

• We must act before catastrophe, not after.

Artificial Intelligence & Existential Risk

• AI is potentially more dangerous than nuclear weapons.

• Unchecked AI development risks loss of human control.

• Regulation should precede catastrophe, not follow it.

• Alignment matters more than raw capability.

• Human-AI symbiosis may be necessary.

• We should be afraid—but productively so.

Personal Philosophy & Identity

• He does not seek happiness as a primary goal, but usefulness.

• Legacy matters more than reputation.

• Approval is irrelevant compared to impact.

• Loneliness is an acceptable cost of responsibility.

• Doing what is necessary often feels unpleasant.

• You should attempt what seems unlikely to succeed.

イーロン・マスクの哲学（事実・インタビューに基づく和訳・長文）

1. 世界観・人生の目的

• 人生は未来を実質的に良くするものであるべきだと考えている

• 人類が長期的に生き残る確率を最大化することが最大の目的

• 文明の進歩は自然に続くものではなく、放置すれば停滞・崩壊する

• 技術は人類進歩の最も強力な手段

• 楽観主義は「信じるもの」ではなく設計・構築するもの

---

2. 第一原理思考（ファースト・プリンシプル）

• 問題を物理法則や基礎的事実まで分解して考える

• 過去の慣例や「他社もそうしている」は危険

• すべての要件に対して「なぜそれが必要か？」と問う

• 最適化の前に削除せよ

• 後で元に戻さない削除は、削除が足りない証拠

• 「常識」ではなく「必ず真であること」から考える

• 制約の多くは思い込みである

---

3. エンジニアリング思想

• 最高の部品は、存在しない部品

• システム障害の多くは部品ではなく接続部分で起きる

• 製造を前提に設計しなければ意味がない

• 過剰設計はたいてい失敗を招く

• 初期プロトタイプは醜くて速い方がよい

• 失敗しない設計は、挑戦が足りない

• 完璧より反復改善

• 垂直統合は学習速度を高める

---

4. 労働観・自己規律

• 極端な目標には極端な努力が必要

• リーダーは部下より多く苦しむべき

• 疲労は許されるが、怠慢は許されない

• 人類存続に関わる課題では緊急性は道徳的義務

• 快適さは進歩の敵

• 大きな成果には痛みへの耐性が必要

• ミッションが重要なら犠牲は正当化される

---

5. リスク・失敗・回復力

• 失敗は恥ではなく情報

• 失敗していないなら、革新が遅い

• 最大のリスクはリスクを取らないこと

• 公の失敗も学びがあれば問題ない

• 会社を賭ける決断も合理的な場合がある

• 美しさより生存

---

6. リーダーシップ・経営

• 肩書きに意味はなく、貢献だけが価値

• 優れたリーダーは技術を理解している

• 上司は少なくとも一分野では部下より詳しくあるべき

• 指揮系統は情報伝達の妨げになってはならない

• 良い製品のためなら誰でも誰にでも話せるべき

• 危機や革新期にはマイクロマネジメントも正当

• 悪いニュースは良いニュースより早く伝える

• 会議は生産性への税金

---

7. 採用・人材観

• 卓越した人材は平均的な人材の何十倍もの価値

• 学位より能力

• 実績は学歴より重要

• 知能よりエネルギーと執念

• 小さく精鋭なチームが官僚的組織に勝つ

• カルチャーフィット＝快適さではなく真実と使命への忠誠

---

8. 経済・ビジネス観

• 利益は目的ではなく手段

• 利益率は製品の卓越性の結果

• コスト削減は需要拡大を生む

• 良い技術が広まるなら規模は善

• 短期的評価より長期的価値

• 補助金は移行加速のためなら容認

• 非対称な好機では資本を大胆に投下すべき

---

9. 時間・スピード

• スピードは最大の競争優位

• 遅延は見えない形で致命的に積み重なる

• 多くの計画は進歩を直線で想定するから失敗する

• 努力ではなく前提を疑え

• 完璧な判断より速い判断

• 官僚主義は意図せず減速を生む

---

10. 真実・現実認識

• 現実が最終審判者

• 物理法則とは交渉できない

• 間違えることより、間違い続けることが問題

• 遠慮より率直さ

• 気持ちよい嘘は危険

• 言論の自由は誤り訂正のために不可欠

---

11. 社会・文明観

• 文明は災害より慢心で滅びる

• 少子化は深刻な文明リスク

• エネルギーの豊かさは人類繁栄と相関

• 技術は個人の自由を拡張すべき

• 中央集権は停滞を招く

• 好奇心は守るべき価値

---

12. 宇宙・人類の未来

• 地球は揺りかごであり、終着点ではない

• 単一惑星文明は必ず滅ぶ

• 火星は最良のバックアップ

• 再利用が宇宙を安価にする鍵

• 多惑星化は贅沢ではなく道徳的義務

---

13. AI・実存的リスク

• AIは核兵器以上の危険性を持つ可能性

• 制御不能なAIは人類を脅かす

• 規制は事故の前に必要

• 能力より整合性（アラインメント）

• 人間とAIの共生が必要になる可能性

• 恐れるべきだが、建設的に恐れるべき

---

14. 個人的価値観

• 幸福より有用性

• 評判より遺産（レガシー）

• 承認より影響

• 責任には孤独が伴う

• 必要なことは大抵不快

• 成功確率が低く見えても挑戦すべき

---

Kiara Inc. Web Design Checklist (Vibe Coding Ready)

Color Tokens

• [ ] White: #FFFFFF — primary background
• [ ] Gray-100: #F5F5F5 — subtle backgrounds
• [ ] Gray-300: #D1D5DB — borders, dividers
• [ ] Gray-500: #6B7280 — placeholder text
• [ ] Gray-700: #374151 — secondary text
• [ ] Gray-900: #111827 — primary text
• [ ] Red: #DC2626 — primary CTA, errors, destructive
• [ ] Orange: #F97316 — secondary CTA, highlights, badges
• [ ] Green: #16A34A — success states
• [ ] Blue: #2563EB — links, info states

Color Hierarchy

• [ ] White/Gray → structure (80–90%)
• [ ] Red → action/danger (sparingly)
• [ ] Orange → support/promotion
• [ ] Green → success/confirmation
• [ ] Blue → links/info

Component States

• [ ] Default → base color
• [ ] Hover → 10% darker or opacity shift
• [ ] Active/Pressed → 20% darker
• [ ] Disabled → Gray-300 bg, Gray-500 text, no pointer
• [ ] Focus → 2px ring, Blue or current color offset

Button Rules

• [ ] Primary CTA → Red bg, white text
• [ ] Secondary CTA → Orange bg, white text
• [ ] Tertiary → Gray border, transparent bg
• [ ] Destructive → Red outline or red bg (context-dependent)
• [ ] No red + orange buttons in same group

Typography

• [ ] Font family: system or specify (e.g., Inter, Noto Sans)
• [ ] H1: 2rem / bold
• [ ] H2: 1.5rem / semibold
• [ ] H3: 1.25rem / medium
• [ ] Body: 1rem / regular / Gray-900
• [ ] Secondary text: 0.875rem / Gray-700
• [ ] Caption: 0.75rem / Gray-500

Spacing Scale

• [ ] 4px base unit
• [ ] xs: 4px | sm: 8px | md: 16px | lg: 24px | xl: 32px | 2xl: 48px

Borders & Radius

• [ ] Border color: Gray-300
• [ ] Border width: 1px default
• [ ] Radius: sm: 4px | md: 8px | lg: 12px | full: 9999px

Shadows/Elevation

• [ ] sm: 0 1px 2px rgba(0,0,0,0.05)
• [ ] md: 0 4px 6px rgba(0,0,0,0.1)
• [ ] lg: 0 10px 15px rgba(0,0,0,0.1)

Form Inputs

• [ ] Default → Gray-300 border, white bg
• [ ] Focus → Blue ring, Gray-900 text
• [ ] Error → Red border, Red text below
• [ ] Success → Green border (optional)
• [ ] Placeholder → Gray-500

Links

• [ ] Default → Blue, underline optional
• [ ] Hover → Blue darker, underline
• [ ] Visited → optional Purple or same

Icons

• [ ] Default → Gray-700
• [ ] Interactive → inherit button/link color
• [ ] Decorative → Gray-500

Accessibility

• [ ] Contrast: 4.5:1 (normal text), 3:1 (large text/UI)
• [ ] Never color alone for meaning — add text/icon
• [ ] Focus visible on all interactive elements
• [ ] Test colorblind modes (protanopia, deuteranopia)
• [ ] Touch targets: min 44×44px

Dark Mode (if applicable)

• [ ] Swap White ↔ Gray-900
• [ ] Reduce Red/Orange intensity (use lighter variants)
• [ ] Shadows → subtle or remove
• [ ] Test contrast again

Hard Rules

• [ ] No colored large backgrounds
• [ ] No red + orange in same action group
• [ ] If everything pops, nothing matters

(to make it accessible)

Here’s a practical, standards-aligned accessibility checklist you can use for websites and mobile apps. It’s organized by category so it works both as a design review tool and a handoff checklist for developers and QA.

1. Foundations (Standards & Planning)

• ☐ Follow Web Content Accessibility Guidelines (WCAG) 2.1 or 2.2, target Level AA

• ☐ Consider accessibility from the start of design, not as a fix later

• ☐ Design for permanent, temporary, and situational disabilities

• ☐ Include accessibility acceptance criteria in user stories

• ☐ Test with real users and assistive technologies

2. Visual Design & Layout

• ☐ Color contrast:

  • Text contrast ≥ 4.5:1 (normal text)

  • Large text ≥ 3:1

• ☐ Do not rely on color alone to convey meaning

• ☐ Text is resizable up to 200% without loss of content or function

• ☐ Clear visual hierarchy (headings, spacing, alignment)

• ☐ Avoid flashing content (>3 flashes/second)

• ☐ Support dark mode with sufficient contrast

3. Typography & Readability

• ☐ Minimum body text size ~ 16px (or platform equivalent)

• ☐ Use readable fonts (avoid overly decorative styles)

• ☐ Line height ≥ 1.5× font size

• ☐ Adequate letter and word spacing

• ☐ Text is not embedded in images unless essential

4. Navigation & Structure

• ☐ Logical heading order (H1 → H2 → H3)

• ☐ Consistent navigation across screens

• ☐ Skip navigation links (web)

• ☐ Clear, descriptive page and screen titles

• ☐ Breadcrumbs or clear location indicators (when applicable)

5. Keyboard & Input Accessibility

• ☐ All functionality usable with keyboard only

• ☐ Visible focus indicators at all times

• ☐ Logical tab order

• ☐ No keyboard traps

• ☐ Touch targets ≥ 44×44 px (mobile)

6. Forms & Data Entry

• ☐ Every input has an associated label

• ☐ Clear instructions and examples

• ☐ Error messages are:

  • Descriptive

  • Easy to find

  • Programmatically associated with inputs

• ☐ Required fields are clearly identified (not by color alone)

• ☐ Success and error states are announced to screen readers

7. Buttons, Links & Controls

• ☐ Buttons and links have descriptive text

• ☐ No “click here” or ambiguous labels

• ☐ Controls have clear states (hover, focus, active, disabled)

• ☐ Icons have accessible names or labels

• ☐ Links are visually distinguishable from text

8. Images, Media & Icons

• ☐ Informative images have meaningful alt text

• ☐ Decorative images are ignored by assistive tech

• ☐ Icons have text alternatives

• ☐ Video includes:

  • Captions

  • Audio descriptions (if needed)

• ☐ Animations can be paused or disabled

9. Screen Reader & Assistive Tech Support

• ☐ Content is announced in a logical order

• ☐ Dynamic updates are announced (ARIA/live regions)

• ☐ Role, state, and value are conveyed for custom components

• ☐ No redundant or repetitive announcements

• ☐ Landmarks are used appropriately (web)

10. Mobile-Specific Accessibility

• ☐ Supports screen rotation

• ☐ Respects system font size and contrast settings

• ☐ Gestures have alternatives (no gesture-only actions)

• ☐ VoiceOver / TalkBack tested

• ☐ Haptic feedback is not the only signal

11. Testing & Validation

• ☐ Automated checks (Lighthouse, axe, etc.)

• ☐ Manual keyboard testing

• ☐ Screen reader testing (NVDA, VoiceOver, TalkBack)

• ☐ Color-blindness simulation

• ☐ Accessibility issues documented and tracked

12. Legal & Compliance Awareness

• ☐ Meets regional requirements (e.g. Americans with Disabilities Act, European Accessibility Act)

• ☐ Accessibility statement provided (web)

• ☐ Ongoing monitoring and audits planned

Here’s a long, fact-based list of Jeff Bezos’s management philosophy and leadership principles drawn from Amazon’s official practices, his public statements, and third-party analysis of how he built and led Amazon. These are grounded in verifiable descriptions of Amazon’s culture and Bezos’s approach — not just inspirational wording. (Amazon.jobs)

✅ Core Management Philosophy Themes from Jeff Bezos

🟡 1. Customer Obsession

• Leaders start with the customer and work backwards. Obsess over customers rather than competitors. (Amazon.jobs)

🟡 2. Long-Term Thinking

• Bezos consistently emphasizes planning for the long term rather than short-term results — especially in strategic decisions like pricing and technology investment. (Business Insider Japan)

🟡 3. Visionary Leadership (“Day 1” Mentality)

• “Day 1 culture”: never lose the startup mindset of urgency and customer focus no matter how big Amazon becomes. (note（ノート）)

🟡 4. Invent and Simplify

• Leaders at Amazon are expected to innovate and simplify processes, products, and services. (Wharton Magazine)

🟡 5. Ownership

• Leaders act like owners, thinking beyond their teams and not sacrificing long-term value for short-term success. (Wharton Magazine)

🟡 6. High Hiring & Performance Standards

• Bezos insisted on hiring and developing the best employees and raising recruitment standards over time. (CliffsNotes)

🟡 7. Are Right, A Lot

• Leaders make sound judgments based on experience and data, even if it’s challenging or unconventional. (Wharton Magazine)

🟡 8. Bias for Action

• Bezos encouraged fast decision-making — even with imperfect information — because speed matters in business. (agile-academy.com)

🟡 9. Frugality

• Doing more with less; resource efficiency fosters innovation rather than hindering it. (agile-academy.com)

🟡 10. Dive Deep

• Leaders operate at all levels, stay connected to the details, and audit frequently. (agile-academy.com)

🟡 11. Earn Trust

• Leaders build trust through integrity and empathetic leadership. (Amazon.jobs)

🟡 12. Disagree and Commit

• Team members can respectfully voice disagreement — but once a decision is made, they commit fully to its success. (Business Insider)

🟡 13. Deliver Results

• Bezos’s philosophy stresses accountability and delivering high-quality results on time. (Louis Carter)

🟡 14. Learn and Be Curious

• Continual learning and exploration are core to Bezos’s management approach — improving individuals and teams. (agile-academy.com)

🟡 15. Think Big

• Bezos encouraged setting bold goals that push boundaries rather than settling for incremental improvements. (agile-academy.com)

🟡 16. Combined Risk-Taking & Operational Excellence

• Bezos is known for pioneering new ideas (e.g., AWS, Prime) while building systems to scale and control operational quality. (LinkedIn)

✅ Additional Philosophical Elements Frequently Cited

📌 Customer Focus Over Competition

• Bezos repeatedly said leaders shouldn’t just watch rivals — obsess over what maximizes customer value. (株式会社エモーションテック ｜ 感情データの解析技術で最適な意思決定を。)

📌 Minimal Regret Decision-Making (“Regret Minimization Framework”)

• When launching Amazon, Bezos used a mental model of minimizing future regrets to take big entrepreneurial risks (from early interviews). (ライフハッカー・ジャパン)

📌 Transformational & Visionary Style

• His leadership blends visionary goals with a willingness to transform industries and embrace change. (steeringpoint.ie)

✅ How These Are Practically Applied at Amazon

Many of the principles above are formalized into Amazon’s Leadership Principles (initially 14, now often described as 16) — concrete behavioral expectations integrated into hiring, performance evaluations, and decision processes. (Amazon.jobs)

🔎 Summary Table (Management Focus vs. Operational Style)

I’ll frame each as ❌ What Bezos pushed against → ✅ What he preferred instead.

❌ 1. Customer Apathy

Taboo: Making decisions based on internal convenience, org politics, or competitors
Instead: Customer obsession

• Bezos repeatedly warned that companies die when they become inward-focused.

• Famous line: “Customers are always beautifully, wonderfully dissatisfied.”

❌ 2. Short-Term Profit Maximization

Taboo: Optimizing for quarterly earnings or Wall Street applause
Instead: Long-term free cash flow and durability

• Amazon openly sacrificed profits for years.

• Bezos said public companies often fail because they “manage earnings instead of building value.”

❌ 3. Bureaucracy & Process for Its Own Sake

Taboo: Rules, approvals, and committees that slow decisions
Instead: Small teams, ownership, speed

• Two-pizza teams exist explicitly to fight bureaucracy.

• Process is only justified if it improves customer outcomes.

❌ 4. “Professional Politeness” That Hides Truth

Taboo: Fake harmony, sugar-coating, consensus theater
Instead: Rigorous debate + “disagree and commit”

• Bezos encouraged constructive confrontation.

• Silence or passive agreement was considered dangerous.

❌ 5. PowerPoint-Driven Thinking

Taboo: Slide decks replacing clear thinking
Instead: Narrative memos

• Bezos banned PowerPoint in senior meetings.

• Leaders had to write 6-page narrative memos, read silently before discussion.

❌ 6. Risk Avoidance

Taboo: Playing it safe to avoid failure or embarrassment
Instead: High-velocity experimentation

• Bezos distinguished between:

  • Type 1 decisions (irreversible, slow)

  • Type 2 decisions (reversible, fast — most decisions)

• Fear of failure was considered a bigger risk than failure itself.

❌ 7. “That’s Not My Job” Thinking

Taboo: Narrow role boundaries
Instead: Ownership mentality

• Leaders were expected to act like owners, not managers.

• Problems were everyone’s responsibility if they affected customers.

❌ 8. Comfortable High Performers Who Stop Growing

Taboo: Static talent, even if previously successful
Instead: Continually raised performance bar

• Bezos insisted hiring standards should rise every year.

• Past success never guaranteed future safety.

❌ 9. Prestige, Status, and Executive Perks

Taboo: Corporate luxury and visible hierarchy
Instead: Frugality as a cultural weapon

• Bezos used a cheap door desk as a symbol.

• Execs flew economy for years.

• Frugality was not about saving money — it was about resourcefulness.

❌ 10. Metrics Without Meaning

Taboo: Vanity metrics and dashboard theater
Instead: Input metrics tied to customer experience

• Bezos emphasized leading indicators (inputs) over lagging indicators (outputs).

• Example: shipping speed drivers vs. revenue numbers.

❌ 11. Slow Decision-Making Masquerading as “Being Careful”

Taboo: Over-analysis, endless reviews
Instead: Bias for action

• Bezos said many decisions should be made with ~70% of the information.

• Waiting for 90% certainty was often a mistake.

❌ 12. Copying Competitors

Taboo: Benchmark obsession
Instead: Inventing on behalf of customers

• Bezos explicitly said competitors never define Amazon’s roadmap.

• Copying was seen as reactive, not innovative.

❌ 13. “Day 2” Thinking

Taboo: Complacency, stasis, institutional decay
Instead: Day 1 mentality

Bezos defined Day 2 as:

• Stasis

• Irrelevance

• Slow decline

• Death

Avoiding Day 2 was a core cultural obsession.

❌ 14. Leaders Who Don’t Dive Deep

Taboo: High-level managers detached from details
Instead: Leaders who audit, question, and verify

• Bezos was known to ask granular questions deep into operations.

• “Trust but verify” was implicit.

❌ 15. Talent Preservation Over Customer Outcomes

Taboo: Keeping people because they’re likable or politically protected
Instead: Relentless focus on standards

• Bezos believed culture is defined by who gets promoted, rewarded, or tolerated.

❌ 16. Fear of Being Misunderstood

Taboo: Avoiding bold moves because they look strange
Instead: Willingness to be misunderstood for long periods

• One of Bezos’s most quoted principles.

• AWS, Prime, and marketplace expansion all looked irrational at launch.

🧠 Meta-Taboo (The Most Important One)

❌ Comfort

Bezos treated comfort as the enemy of invention.

“If you’re not willing to be misunderstood, you can’t invent.”

Below are the TOP 3 philosophies (phil) and TOP 3 anti-philosophies (anti-phil) of Jeff Bezos, selected strictly based on what he personally emphasized most often and most explicitly in:

• Amazon 1997–2020 Shareholder Letters

• Long-form interviews (Charlie Rose, 60 Minutes, Economic Club of Washington)

• Management mechanisms he personally enforced at Amazon

Then I explain the logical reason each matters most.

TOP 3 PHILOSOPHIES (What Bezos Built Amazon Around)

1️⃣ Customer Obsession (MOST IMPORTANT)

Bezos evidence

• Appears in every shareholder letter

• “Start with the customer and work backwards”

• Repeatedly says competitors should not define strategy

Logical reason

Customers are the only external constraint that cannot be negotiated.

• Employees can be replaced

• Investors can exit

• Strategies can change

• Customers leave

By anchoring decisions to customers, Amazon:

• Automatically thinks long term

• Avoids internal politics

• Scales decision quality without central control

➡️ Logic: Customer obsession is a self-correcting system.

2️⃣ Long-Term Thinking

Bezos evidence

• 1997 letter explicitly warns investors Amazon will sacrifice short-term profit

• Bezos said public companies fail by “managing earnings instead of building value”

Logical reason

Long-term thinking enables actions others structurally cannot take:

• Sustained losses (Prime, AWS)

• Heavy infrastructure investment

• Patience before monetization

➡️ Logic: It creates strategic asymmetry — competitors literally cannot copy you without dying.

3️⃣ High-Velocity Decision-Making (Bias for Action)

Bezos evidence

• Type 1 vs Type 2 decisions framework

• Most decisions should be made with ~70% information

Logical reason

Speed increases learning rate.

• More decisions → more experiments

• More experiments → more data

• More data → better judgment

➡️ Logic: Decision velocity compounds like interest.

TOP 3 ANTI-PHILOSOPHIES (What Bezos Actively Fought)

1️⃣ Short-Termism (MOST IMPORTANT ANTI-PHIL)

Bezos evidence

• Open criticism of “quarterly capitalism”

• Amazon tolerated minimal profit for ~20 years

Logical reason

Short-termism corrupts every other decision:

• Kills experimentation

• Discourages risk

• Pushes optics over reality

➡️ Logic: Once quarterly results dominate, innovation becomes irrational.

2️⃣ Bureaucracy as a Substitute for Thinking

Bezos evidence

• Two-pizza teams

• PowerPoint banned in senior meetings

• Bezos called bureaucracy the enemy of invention

Logical reason

Bureaucracy slows feedback loops.

• Slow feedback = slow learning

• Slow learning = loss of innovation

➡️ Logic: Scale creates bureaucracy automatically; innovation does not.

3️⃣ Risk Avoidance / Fear of Failure

Bezos evidence

• “Failure and invention are inseparable twins”

• Public acknowledgment of large Amazon failures

Logical reason

Avoiding failure guarantees mediocre outcomes.

• Big wins require many attempts

• Many attempts guarantee some failures

➡️ Logic: Punishing failure mathematically eliminates breakthroughs.

FINAL LOGICAL SYNTHESIS

Bezos’s system is not inspirational — it is mechanical.

Core logic:

Maximize long-term learning speed while minimizing comfort, ego, and short-term approval.

That’s why these 6 matter more than all others.

GitHub Events

Open Source Friday / Community Office Hours

• GitHub (issues / notes):
  https://github.com/github/opensourcefriday

• Non-GitHub (info):
  https://opensourcefriday.com/

Docs & Developer Experience Community

• GitHub:
  https://github.com/github/docs

• Non-GitHub:
  https://docs.github.com/en/community

Kubernetes SIG & WG Meetings

• GitHub (all SIGs & WGs):
  https://github.com/kubernetes/community

• Meeting notes repo:
  https://github.com/kubernetes/community/tree/master/sig-*

• Non-GitHub (calendar):
  https://www.kubernetes.dev/resources/calendar/

Node.js Working Groups

• GitHub (WG index):
  https://github.com/nodejs/node/blob/main/doc/contributing/working-groups.md

• GitHub (meeting notes):
  https://github.com/nodejs/meeting-notes

• Non-GitHub:
  https://nodejs.org/en/get-involved

Python Software Foundation Working Groups

• GitHub (PEPs & governance):
  https://github.com/python/peps

• GitHub (Packaging WG):
  https://github.com/pypa

• Non-GitHub:
  https://www.python.org/psf/working-groups/

W3C Working Groups

• GitHub (specs & issues):
  https://github.com/w3c

• GitHub (WG dashboards):
  https://github.com/w3c/w3c.github.io

• Non-GitHub:
  https://www.w3.org/groups/wg/

OpenSSF Working Groups

• GitHub (main org):
  https://github.com/ossf

• GitHub (WG index):
  https://github.com/ossf/wg-working-groups

• Non-GitHub:
  https://openssf.org/get-involved/

OpenJS Foundation Working Groups

• GitHub (cross-project work):
  https://github.com/openjs-foundation

• GitHub (WG repos):
  https://github.com/openjs-foundation/cross-project-council

• Non-GitHub:
  https://openjsf.org/community/

✅ Summary (Quick Copy List)

GitHub URLs

• https://github.com/github/opensourcefriday

• https://github.com/github/docs

• https://github.com/kubernetes/community

• https://github.com/nodejs/meeting-notes

• https://github.com/python/peps

• https://github.com/w3c

• https://github.com/ossf

• https://github.com/openjs-foundation

Non-GitHub URLs

• https://opensourcefriday.com/

• https://docs.github.com/en/community

• https://www.kubernetes.dev/resources/calendar/

• https://nodejs.org/en/get-involved

• https://www.python.org/psf/working-groups/

• https://www.w3.org/groups/wg/

• https://openssf.org/get-involved/

• https://openjsf.org/community/

Universal PPT Design Rules

1. Contrast & Readability First

• Background: White, off-white, or dark charcoal only
• Text: Black/dark gray on light, or white on dark—no exceptions
• Minimum contrast ratio: 4.5:1

2. Typography System

• One sans-serif font family (Inter, Helvetica, Arial, Calibri)
• Title: 36-44pt, bold
• Body: 28-32pt, regular
• Labels/captions: 20-24pt
• Never go below 18pt for anything

3. Color Palette

• 3 colors total: 1 neutral (text) + 1 primary accent + 1 secondary accent
• Use accent color only for: key data, CTAs, critical emphasis
• Avoid red/green combinations

4. Content Density

• One idea per slide
• Max 6 lines, max 6 words per line
• If you need more text, you need more slides

5. Visual Hierarchy

• Left-align body text
• Top-left to bottom-right flow (natural reading pattern)
• 30-40% white space minimum—if slide feels "empty," it's probably right

6. Imagery & Data

• Photos: High-res only, no watermarks, no clip art
• Charts: One chart per slide, clear labels, minimal gridlines
• Animation: None, unless movement explains a concept

7. The 50% Test

View slide at 50% zoom. If anything is hard to read or unclear, fix it.

The single rule behind all rules: If it doesn't help the audience understand faster, remove it.

Here's a straightforward breakdown:

DO

DON'T

The core principle: every element should either clarify or be cut.

Color

Font

Size

Quick test: View your slide at 50% zoom. If you can't read it easily, neither can your audience.

Below is a long, structured list of ways a company can collaborate with GitHub, ranging from technical partnerships to community, education, and go-to-market efforts. I’ve grouped them so it’s easier to scan or reuse in strategy docs.

1. Product & Technology Partnerships

1. Official GitHub App integration (build and publish an app in GitHub Marketplace)

2. GitHub Actions integrations (CI/CD, security scans, deployment, automation)

3. GitHub Copilot ecosystem integrations (developer tools that enhance AI-assisted coding)

4. Native API integrations (repos, issues, pull requests, webhooks)

5. Security tooling integrations (SAST, DAST, dependency scanning via GitHub Advanced Security)

6. DevOps platform integrations (cloud, observability, infra-as-code tools)

7. Code review and collaboration enhancements

8. Repository analytics and insights tools

9. Compliance and governance tooling (SOC2, ISO, enterprise controls)

10. Secrets management integrations

11. Package registry integrations (npm, Maven, PyPI, GitHub Packages)

12. Container & Docker integrations

13. Infrastructure deployment integrations (Kubernetes, serverless, IaC)

14. Developer experience (DX) tooling integrations

15. Testing frameworks and QA automation plugins

16. Monitoring and alerting integrations

17. ChatOps and workflow automation tools

18. Low-code / no-code platform integrations

19. Data & ML workflow integrations

20. Internal developer portal integrations

2. Marketplace & Distribution Partnerships

1. Listing products on GitHub Marketplace

2. Paid Marketplace offerings (revenue sharing)

3. Freemium tools for OSS and paid for enterprises

4. Bundled offerings with GitHub Enterprise customers

5. Co-selling with GitHub sales teams (select partners)

6. Promotional placement in Marketplace collections

7. Joint onboarding flows for enterprise users

8. Usage-based billing integrations

9. Trial-to-paid conversion programs

10. Partner badges and verification programs

3. Open Source Collaboration

1. Maintaining open-source projects on GitHub

2. Sponsoring open-source maintainers via GitHub Sponsors

3. Corporate GitHub Sponsors matching programs

4. Contributing engineering time to major OSS projects

5. Open-sourcing internal tools or SDKs

6. Running company-backed OSS foundations

7. Participating in GitHub OSS initiatives

8. Hosting public roadmaps and RFCs on GitHub

9. Providing long-term maintenance guarantees for OSS

10. Funding security audits for OSS dependencies

4. Developer Community & Advocacy

1. Sponsoring GitHub-hosted developer events

2. Running GitHub Discussions–based communities

3. Supporting hackathons hosted on GitHub

4. Community challenges and coding contests

5. Open innovation programs via GitHub repos

6. Developer ambassador or advocate programs

7. Maintaining example repos and templates

8. Publishing reference architectures

9. Hosting office hours via GitHub Discussions

10. Collaborative roadmap feedback via Issues

5. Education & Talent Development

1. Partnering with GitHub Education

2. Offering student developer packs integrations

3. Providing learning content via GitHub repos

4. Certifications or training aligned with GitHub workflows

5. Bootcamp partnerships using GitHub Classroom

6. University curriculum collaborations

7. Open courseware hosted on GitHub

8. Internship programs using GitHub as assessment platform

9. Hiring challenges based on GitHub projects

10. Mentorship programs using GitHub Issues/PRs

6. Enterprise & B2B Collaboration

1. Enterprise integrations with GitHub Enterprise Cloud

2. Enterprise Server ecosystem partnerships

3. Custom enterprise onboarding solutions

4. Security & compliance partnerships for regulated industries

5. Government & public sector collaboration

6. Industry-specific developer tooling partnerships

7. Joint customer case studies

8. Reference customers for GitHub features

9. Feedback partner programs (early access features)

10. Large-scale migration tooling partnerships

7. Go-to-Market & Marketing Collaboration

1. Joint webinars and workshops

2. Co-branded blog posts and whitepapers

3. Joint conference sponsorships

4. Speaking slots at GitHub Universe / GitHub events

5. Customer success stories with GitHub tooling

6. Joint solution briefs

7. Developer tool comparisons and benchmarks

8. Launch partnerships for new GitHub features

9. Community spotlights

10. Thought leadership collaboration

8. Data, Insights & Research

1. Developer productivity research partnerships

2. Open source ecosystem research collaborations

3. Anonymized usage insights studies

4. AI & developer tooling research partnerships

5. Software supply chain research

6. Security vulnerability trend research

7. Academic–industry research programs

8. Developer survey collaborations

9. Benchmarking initiatives

10. Open datasets published on GitHub

9. AI & Automation Focused Collaboration

1. AI coding assistant extensions

2. Prompt engineering tools for Copilot workflows

3. Code quality AI integrations

4. Automated refactoring tools

5. AI-powered code review tools

6. Natural language to code tools

7. Policy-as-code automation

8. AI-based security analysis

9. ML model versioning tools

10. Responsible AI governance tooling

10. Strategic & Long-Term Partnerships

1. Strategic alliance agreements

2. Preferred technology partner status

3. Joint product roadmapping

4. M&A or investment relationships (indirect)

5. Standards body collaborations

6. Cross-platform developer ecosystem alliances

7. Cloud provider + GitHub joint solutions

8. Startup accelerator partnerships

9. Regional developer ecosystem initiatives

10. Long-term platform dependency partnerships

11. Internal Company Use as Collaboration Signal

1. Publicly dogfooding GitHub tools

2. Publishing engineering handbooks on GitHub

3. Open engineering blogs linked to repos

4. Transparent issue tracking for products

5. Community-driven feature voting

6. Public changelogs and release notes

7. Open hiring repositories

8. Security disclosure programs on GitHub

9. Bug bounty coordination

10. Open governance models

Key Platform

All of these collaborations revolve around GitHub as a platform for code, developers, and ecosystems.

If you want, I can:

• Narrow this to realistic options for startups vs enterprises

• Map these to business goals (growth, hiring, security, revenue)

• Turn this into a partner strategy slide or checklist

• Highlight which ones GitHub actively encourages today

Just tell me the angle.

----

Here’s a highlighted subset of ways a company can collaborate with GitHub that GitHub actively encourages today — based on official GitHub partner programs, developer initiatives, and ecosystem integrations they publicly promote: (GitHub)

✅ Active GitHub-Encouraged Collaboration Paths

🧩 1. Official Partner Programs

GitHub explicitly promotes partnership tracks for companies to extend its ecosystem and engage in co-innovation: (GitHub)

Technology Partners

• Build deep technical integrations that embed your solution within GitHub workflows (e.g., GitHub Apps, GitHub Actions).

• Get technical enablement, early product access, testing support, and partner events.
  This is a core way GitHub encourages companies to participate in the ecosystem. (GitHub)

Services & Channel Partners

• Position your consulting, services, or solution delivery around GitHub Enterprise customers.

• Eligible for co-selling and wider customer reach. (GitHub)

Startup Partners

• GitHub encourages startups to grow with the platform (especially those building on GitHub APIs/Dev tools). (GitHub)

Education Partners

• GitHub actively supports companies involved in developer education and training. (GitHub)

🔌 2. GitHub Developer Program (API & Integrations)

GitHub encourages companies (and developer teams) to build integrations using its APIs and join its Developer Program: (GitHub Docs)

• Use GitHub’s REST/GraphQL APIs to build tools that extend GitHub functionality.

• Integrations can automate tasks, notify systems, and embed workflows with GitHub. (GitHub Docs)

• Once built, companies can publicize compatibility (use GitHub branding for integrations). (GitHub Docs)

This is a widely active route and is the foundational encouraged method for extensions.

📦 3. GitHub Marketplace

GitHub Marketplace is a core distribution channel GitHub promotes for third-party tools: (GitHub Docs)

• Publish GitHub Apps and GitHub Actions to the Marketplace for developers to install.

• Marketplace lets developers discover integrations and supports free and paid listings.

• Verified creators get badges and visibility in the platform. (GitHub Docs)

GitHub actively encourages Marketplace participation to grow its ecosystem of developer tooling.

🤝 4. AI & Developer Ecosystem

Although not a formal “program,” GitHub clearly signals a push toward AI-powered tooling collaboration (e.g., GitHub Copilot and AI agent extensibility), where third-party tooling and workflows integrate with GitHub’s AI ecosystem. (Business Insider)

• GitHub is positioning its platform as a hub for AI coding workflows and partner integrations.

• Third parties (e.g., analytics or insights tools) build deeper AI + GitHub workflows. (ファインディ株式会社(Findy Inc))

This aligns with GitHub’s current strategic direction.

🛠 5. Open Source & Community Enabling

GitHub natively supports companies that build or host open-source projects on the platform (open repos, CI workflows, contributor tooling, etc.) — though not always formalized as a program, this is foundational to GitHub’s business model. (GitHub Docs)

🧑‍🏫 6. Education & Developer Training

GitHub encourages participation in community training and education through:

• GitHub Classroom

• Publishing educational materials and templates

• Collaborating with academic partners (via their Education Partner track) (GitHub)

🧭 Summary: What GitHub Encourages Most

If you want, I can take this further and map these encouraged paths to specific business goals (e.g., revenue, developer adoption, enterprise sales) with examples of companies succeeding in each. Just let me know!

🎹 Core Jazz Piano Style Keywords

Use 2–4 of these together:

• jazz piano

• solo piano jazz

• acoustic piano

• instrumental jazz

• piano-led

• piano trio (even if solo, it influences phrasing)

🎶 Harmony & Language (VERY important)

These strongly affect musical quality:

• rich jazz harmony

• extended chords

• complex chord voicings

• lush voicings

• quartal harmony

• altered dominants

• modal harmony

• reharmonization

• chromatic passing chords

🕰 Jazz Substyle Keywords

Pick one main substyle:

• bebop

• cool jazz

• modal jazz

• hard bop

• swing jazz

• post-bop

• contemporary jazz

• neo-jazz

• impressionistic jazz

🎼 Piano Technique & Articulation

These help Suno generate more authentic piano playing:

• walking left hand

• stride piano

• shell voicings

• rootless voicings

• block chords

• comping

• melodic right-hand improvisation

• call and response

🥁 Groove & Feel

Use exactly one for clarity:

• swing feel

• laid-back swing

• medium swing

• slow swing

• straight-ahead jazz

• rubato intro

• relaxed tempo

• late-night jazz

🎭 Mood & Atmosphere

Pick 1–2:

• introspective

• smoky club

• intimate

• moody

• warm

• elegant

• melancholic

• reflective

• nocturnal

🏛 Influences (very effective in Suno)

Use 1–2 names max:

• Bill Evans style

• Thelonious Monk style

• Oscar Peterson style

• Herbie Hancock style

• McCoy Tyner style

• Keith Jarrett style

🎚 Production / Audio Feel

These subtly guide tone:

• natural room reverb

• close-miked piano

• live performance feel

• analog warmth

• dynamic touch

• expressive dynamics

✅ Example High-Quality Suno Prompt

Solo jazz piano, Bill Evans style, rich extended chords, lush voicings,
medium swing feel, introspective and warm, melodic right-hand improvisation,
natural room reverb, live performance feel

🚫 Keywords to Avoid (for jazz piano)

These often degrade results:

• EDM

• cinematic score

• epic

• lo-fi (unless intentional)

• trap

• synth piano

• orchestral

Absolutely — numeric / parameter-style prompt components are very effective in Suno when used sparingly. Below is a curated, jazz-piano-specific list of number-driven prompt components, grouped by function, with usage tips.

🕰 Tempo & Time Feel (most reliable)

Use one tempo value.

• 40 BPM (very slow ballad, rubato)

• 55 BPM (late-night jazz ballad)

• 70 BPM (slow swing)

• 85 BPM (medium-slow swing)

• 100 BPM (medium swing)

• 120 BPM (up-tempo swing)

• 140 BPM (bebop)

• 160 BPM (fast bebop)

Extras

• half-time feel

• double-time feel

• rubato intro → time enters at 70 BPM

⏱ Duration & Structure

Suno responds well to rough time framing.

• 2 minutes

• 3 minutes

• 4 minutes

• short form (AABA)

• 32-bar form

• through-composed

• intro (20s)

• head in → solo → head out

🎼 Harmony Density & Complexity (numeric phrasing)

These are subtle but powerful.

• dense voicings (7–9 notes)

• sparse voicings (3–4 notes)

• extended chords (9ths, 11ths, 13ths)

• frequent chord substitutions (every 2 bars)

• reharmonization every chorus

• modal vamp (8 bars)

• harmonic rhythm: 1 chord per bar

• harmonic rhythm: 2 chords per bar

🎹 Performance Dynamics & Touch

Numbers help shape realism.

• wide dynamic range

• velocity-sensitive playing

• soft touch (pp–mp)

• medium dynamics (mp–mf)

• strong accents (f)

• dynamic swells every 8 bars

• gradual crescendo over 16 bars

🎶 Improvisation Detail

Use one or two max.

• improvised solos (2 choruses)

• motivic development every 4 bars

• space between phrases (1–2 beats)

• phrase length: 2 bars

• phrase length: 4 bars

• call and response (4-bar exchanges)

🧠 Swing Ratio & Feel (advanced but useful)

These can improve groove clarity.

• heavy swing (triplet feel)

• light swing

• relaxed swing (behind the beat)

• straight eighths

• swing ratio ~2:1

• swing ratio ~3:1

🎚 Recording & Room Parameters

Numeric descriptors improve tone realism.

• close-miked (30 cm)

• medium room (20–30 m²)

• small jazz club ambience

• subtle reverb (10–15%)

• moderate sustain pedal

• pedal release noise

🎭 Emotional Arc (time-based)

These help shape the story.

• introspective first 60 seconds

• tension builds at 1:30

• peak intensity at 2:30

• gentle resolution in final 30 seconds

✅ Example: Fully Parameterized Jazz Piano Prompt

Solo jazz piano, 55 BPM, slow swing, Bill Evans style,
dense voicings (7–9 notes), extended chords,
32-bar AABA form, improvised solo (2 choruses),
soft touch (pp–mp), relaxed swing (behind the beat),
medium room (25 m²), subtle reverb (12%),
introspective first 60 seconds, gentle resolution in final 30 seconds

⚠️ Best Practices

• Use 1 tempo, 1 swing feel, 1 form

• Avoid stacking too many numbers (>8 total)

• Combine numeric + descriptive (not numeric alone)

info for solo founders - in the age of vibe coding 

Key Insights

Funding Trends

• Median 2024 Round: $1.5-2M at $15M post-money valuation
• Median 2025 Round: $3.1M (up 50%+ from 2024)
• Healthcare Average: $4.6M (highest sector premium)
• AI Companies: Dominate 67% of S24 batch, 46% of S25 batch

Sector Breakdown

• AI/ML: 40% of top fundings
• Developer Tools: 25%
• Fintech: 15%
• Healthcare: 10%
• Other: 10%

Lead Investors Most Active in YC 2024-2025

1. Initialized Capital
2. Khosla Ventures
3. Benchmark
4. General Catalyst
5. Bessemer Venture Partners
6. Sequoia Capital
7. Salesforce Ventures
8. Andreessen Horowitz

Notable Patterns

• Top-tier YC companies (5-10% of batch): $2M at $20-25M post-money
• Mid-tier companies (60% of batch): $2M at $20M post-money
• AI agent companies: Over 70 in Spring 2025 batch alone
• Second-time founders: 48% of S24 batch
• San Francisco dominance: 67% of companies headquartered in SF

Business Models

• B2B SaaS: 60%
• AI Infrastructure: 20%
• B2B2C/Marketplace: 10%
• Consumer: 10%

Data Sources

• Crunchbase
• TechCrunch
• Company announcements & press releases
• Y Combinator public data
• Venture capital firm announcements
• PitchBook

Note: Not all YC companies publicly disclose funding. This represents announced rounds as of January 2026. URLs verified as of compilation date.

For modern and handy, here are the best options:

Supabase (most popular choice)

• PostgreSQL under the hood, but with a clean dashboard
• Built-in auth, real-time subscriptions, storage
• Free tier is generous
• Works seamlessly with Next.js
• Easy to set up environment variables in Vercel

Neon

• Managed PostgreSQL, very lightweight
• Excellent free tier with good limits
• Serverless-friendly (scales to zero)
• Minimal setup needed

MongoDB Atlas

• If you prefer NoSQL/document-based
• Free tier available
• Good for rapid prototyping
• Simpler schema flexibility

Firebase (if you want the most "hands-off")

• Real-time database, auth, hosting all included
• Quickest to get running
• Less control over database structure
• Can get expensive at scale

My recommendation: Supabase is the sweet spot—it's PostgreSQL (reliable, powerful), but wrapped in a modern, developer-friendly interface. The free tier is practical, it integrates well with Vercel, and you get extras like auth and real-time out of the box.

In Codespace, you'd connect via connection string; in Vercel, you paste that same string as an environment variable. Both handle it transparently.

---

PlanetScale is a Y Combinator startup (S19) that fits this use case perfectly.

PlanetScale details:

• MySQL-compatible database (serverless)
• Built for scale from the start
• Free tier is solid
• Vercel integration is seamless (they work well together)
• Branch-based development (like git for databases)
• Great for modern web apps

Why it's good for your setup:

• Serverless architecture matches Vercel's model
• Easy environment variable setup in Vercel
• MySQL is widely supported; any Node/Next.js library works
• The branching feature is handy for development

Other YC databases worth noting:

• Neon (not YC, but backed by top VCs) - PostgreSQL serverless
• Clerk (YC S21) - focuses on auth, pairs well with any database

Reality check: PlanetScale was solid, but Supabase (not YC) has become the de facto standard in the Next.js/Vercel ecosystem because PostgreSQL is more feature-rich and the free tier is more generous. PlanetScale's free tier got more limited over time.

If you specifically want a YC startup, PlanetScale is your answer—it's production-ready and works great with Codespace + Vercel. Just check their current pricing since they've made changes.