Split View: 글로벌 개발자 커뮤니티 가이드: Recurse Center부터 KubeCon, IndieHackers, Discord까지 (2026)

A Guide to Global Developer Communities: Recurse Center, KubeCon, IndieHackers, Discord, and More (2026)

"A community isn't a place to share code. It's a place to share the loneliness of writing code."

The companion piece to this article — the Korean-developer-community guide — covered GDG, AWSKRUG, KOSSCON, and the Korean-language clusters on Discord and Slack. This is the global version. For non-native English speakers, global communities mean two things at once: a wider learning surface, and a higher entry barrier. So instead of a vague "you should join," this post walks through what each community actually is, who it fits, and what it costs in time and money.

The goal is simple. After reading, you should have a clear mental table for the question: "Which community should I invest in next quarter?"

Prologue — Why global communities, and what to stop expecting

Let's clear the fantasies first. Joining a global community will not magically improve your English, drop a Silicon Valley offer in your inbox, or explode your Twitter followers. Start with those expectations and you'll burn out in six months.

Realistic rewards

• Wider field of view: You're exposed to areas Korean communities often underweight — distributed systems operations, compilers, systems programming, indie hacker businesses, security research.
• Timezone asymmetry: When it's dawn in Seoul, it's mid-afternoon on the US East Coast. Used well, you can build a 24-hour learning cycle.
• Writing pressure: Writing issues and PRs in English improves your writing in your native language too. Every senior engineer agrees on this side effect.
• The value of weak ties: As Granovetter's classic argued, job opportunities flow through weak ties more than strong ones. Global communities are weak-tie power plants.

Common fantasies

One sentence to remember. The scarcest resource in a global community isn't English — it's your consistent time. Every recommendation in this post is a variation of that one sentence.

Chapter 1 · Retreats — Places that clear your calendar entirely

1.1 Recurse Center — The programmer's retreat in NYC

Recurse Center is "a retreat for programmers" based in Brooklyn, NYC. It is not a school and not a bootcamp. There are no teachers, no curriculum, and no diplomas. Instead, 50 to 80 programmers with similar motivation gather for 12 weeks (mini-batch: 6 weeks, micro-batch: 1 week) in one space to work on whatever they want. The tagline says it all — "a writers' retreat for programmers."

The core of the experience is four social rules. No feigning surprise (no "you don't know that?" reactions), No well-actually (no pedantic corrections), No back-seat driving (no unsolicited code advice), No subtle -isms. Those four rules manufacture the psychological safety that is RC's real asset.

• What it is: A non-profit-style self-directed learning retreat. Recursers build whatever they want — a compiler from scratch, a toy operating system that boots, a speech synthesizer.
• Who fits: People who can already code but feel stalled and want to "go deeper," who want time to build the thing they actually wanted to build.
• Cost/access: Tuition is free. RC monetizes by referring alumni to partner companies for a hiring fee. You still need to fund living in NYC for 12 weeks (roughly USD 6,000 to 12,000). Several fellowships exist (for women, people of color, trans and non-binary applicants).
• Time commitment: Full batch is 12 weeks, weekdays roughly 10:00 to 18:00. Counting visa and housing setup, plan for 6+ months of life logistics.
• What you walk away with: A lifelong peer network, a deep side project, and an answer to "what kind of building actually makes me happy?"

The admission is a two-step interview: a 30-minute "why RC?" conversation, then a pair-programming session. The acceptance rate is undisclosed, but RC evaluates learning attitude and value alignment over raw coding skill. Korean applicants get admitted every year.

1.2 Other comparable retreats and fellowships

• South Park Commons / Hacker Fellowship Zero: San Francisco-based, oriented toward seniors who are pre-startup. More business-leaning than RC.
• Square One (UK): A short coding retreat sometimes called "the British RC."
• One- to two-week micro-retreats: Pop up in the US, Portugal, Bali, etc. Check Lu.ma calendars and SNS.

The shared admission price of these retreats is clearing your calendar entirely. If that's hard right now, start with the conferences in the next chapter.

Chapter 2 · Conferences — A community experience compressed into a few days

2.1 KubeCon + CloudNativeCon (CNCF)

The headquarters of Kubernetes and the cloud-native world. Held every spring (Europe) and fall (North America). 2026 dates — KubeCon + CloudNativeCon Europe 2026 is April 7 to 10 in Amsterdam, Netherlands; KubeCon + CloudNativeCon North America 2026 is November 9 to 12 in Los Angeles, USA. KubeCon + CloudNativeCon + Open Source Summit Japan 2026 is June 16 to 17 in Tokyo — the most accessible Asia option.

• What it is: The cloud-native ecosystem's largest event with 10,000+ attendees. Beyond the main conference, 50+ co-located mini-events run the same week (Cilium Day, ArgoCon, Rust Day, and many more).
• Who fits: Infrastructure, platform, and SRE engineers; OSS project maintainers; decision-makers evaluating vendors.
• Cost/access: Main pass USD 1,200 to 1,800. Co-located events USD 75 to 150. Student discounts and diversity scholarships are real and award hundreds of seats yearly.
• Time commitment: 4 to 5 days plus jet lag. The real value is hallways and dinners, not main sessions.
• What you walk away with: Direct conversation with maintainers, a sense of the hiring market, and your next-quarter adoption priorities.

The consensus take: "If you go alone and only attend sessions, you wasted 80%." The pro pattern is to plan the schedule on Sched, prioritize co-located events and SIG meetings, and attend at least one vendor party or BOF (Birds of a Feather) every evening.

2.2 Strange Loop and its heirs

Strange Loop ran from 2009 through 2023 in St. Louis, Missouri. A legendary multi-paradigm conference loved for talks crossing functional programming, distributed systems, programming-language design, and digital humanities. The 2023 edition was officially announced as the last (organizer Alex Miller's decision). All videos remain free on the official YouTube channel.

Several adjacent or successor events have grown in to fill the gap.

• LambdaConf: Functional programming. The closest heir to Strange Loop's FP track. Annually in Colorado, USA.
• P99 CONF: A free online conference focused on low-latency systems and performance. Hosted by ScyllaDB. Carries Strange Loop's systems-talk spirit.
• Handmade Seattle / Onward!: Closer to academia and indie makers. Worth a look if you care about serious systems thinking.
• Papers We Love meetups: Local chapters worldwide read classic papers together. The closest grassroots heir to Strange Loop's academic flavor.

2.3 !!Con — "The best computer moment of your life"

!!Con (pronounced "bang bang con") has two rules: every talk is exactly 10 minutes, and every talk must be about something you're excited (!!) about in computers. Originally in NYC, with a West Coast edition called !!Con West (currently on hiatus). Example talks — "The saddest regex I ever wrote," "Looking for the soul of BeOS," "Sorting integers by flipping coins." Wonder and curiosity matter more than heavy technical content.

• Who fits: People tired of the heaviness of other conferences. People who want an explicitly diverse and inclusive environment.
• Cost/access: Low ticket price with generous scholarships (historically USD 0 to 150). CFP acceptance is roughly 10 to 15%.
• Time commitment: 2 days.
• What you walk away with: A renewed sense of wonder at computers.

2.4 Security conferences — DEF CON, Black Hat, BSides

• DEF CON: Every August in Las Vegas. The heart of hacker culture since 1993. Famously cash-only at the door (USD 460 in 2025). The villages (30+ — Lockpicking, Car Hacking, AI Village, and more) and CTFs matter as much as the main track. DEF CON 34 is scheduled for August 6 to 9, 2026.
• Black Hat USA: Right before DEF CON, in the same Las Vegas. More corporate, more expensive (USD 3,000 to 4,000). The training courses are the real product.
• BSides: Started as "a place for talks rejected by Black Hat." Today, BSides chapters run in 200+ cities worldwide (including Seoul). Tickets typically USD 0 to 50. The most accessible entry point to security communities.

2.5 Academic conferences — TheWebConf, ICML, NeurIPS

Where industry practice meets academia.

• The Web Conference (formerly WWW): The academic home of web technology. 2026 is April 13 to 17 in Sydney, Australia. Recommendation, search, social networks, and web security papers concentrate here.
• ICML (International Conference on Machine Learning): Scheduled for July 2026 in Toronto, Canada. One of the top-tier ML conferences.
• NeurIPS: Scheduled for December 2026 in San Diego, USA. The largest deep-learning and AI conference. Industry booths and workshops now matter as much as the main track.
• Note: For industry engineers, the workshops and industry tracks are usually more practical than the main track. Main-track talks target PhD students; workshops are full of applied work.

2.6 Language and ecosystem conferences

• PyCon US (May 2026 in Pittsburgh, USA): The Python ecosystem headquarters. Sprints and post-conference Slack are big bonuses. Regional siblings include EuroPython (July, Prague) and PyCon JP / KR.
• Rails World: The official Ruby on Rails conference. Toronto (2024), Amsterdam (2025) — and the live tradition continues. RailsConf's 2025 edition was announced as its last, and Rails World becomes the primary event going forward.
• GopherCon: The Go language conference. Scheduled for July 2026 in Las Vegas. GopherCon Europe (July, Berlin) is also popular.
• JSConf series: JSConf US, JSConf EU (Berlin), JSConf JP, etc. Among the most culturally rich JS events. NodeConf, React Conf, and Next.js Conf are cousins.

2.7 Open Source Summit (Linux Foundation)

A general OSS event hosted by the Linux Foundation. Often co-located with KubeCon during the same week. The core value is the OS / kernel track and the governance track. Maintainer workshops, licensing sessions, and policy discussions like the EU Cyber Resilience Act (CRA) are uniquely available here.

2.8 FOSDEM — A massive free OSS gathering

FOSDEM (Free and Open source Software Developers' European Meeting) is held in Brussels, Belgium on the first weekend of February every year, completely free of charge — no registration required. Over 8,000 attendees, more than 700 talks across 50+ devrooms running in parallel. The devrooms are the real value — they're run directly by each community (Rust, Go, Python, Postgres, Kernel, and more). FOSDEM 2026 is January 31 to February 1 at the ULB campus (Université libre de Bruxelles).

• Who fits: Anyone who wants to meet the widest variety of OSS people in one event, and anyone who wants the ticket cost to be zero.
• Time commitment: 2 days plus European travel (Brussels in late January can be cold).
• What you walk away with: An unawkward first meeting with OSS maintainers, and a glass of Belgian beer.

Chapter 3 · Online forums — Where 5 minutes a day accumulates over 5 years

3.1 Hacker News

Operated by Y Combinator. The front page is algorithmically ranked, and comments are widely praised for their quality. There's a persistent critique of consistent bias on politically-charged topics, which should be remembered.

• What it is: A link-and-comment aggregator covering tech, startups, and society.
• Who fits: Every developer who wants to scan trends quickly.
• Cost: Free. Readable without an account.
• Time commitment: 5 minutes a day (a morning scan of front-page headlines) is optimal. The comment rabbit hole is dangerous.
• What you walk away with: Short-term industry trends, and occasionally one really good comment.

3.2 Lobsters

A tech forum built as a response to Hacker News, invitation-only. No politics, no startup news — just pure tech, with strict tagging. New accounts require an invite from an existing member (often granted when you submit a short introduction and links to your activity).

• Who fits: Anyone tired of HN noise who wants serious threads on systems, programming languages, and security.
• Time commitment: 5 minutes a day.
• What you walk away with: Deep, short discussions; occasionally maintainers chiming in directly.

3.3 IndieHackers — A forum for indie founders

Founded by Courtland Allen, the home of solopreneurs and bootstrapped founders. Even after the Stripe acquisition, the community DNA remains. Every day, someone shares their MRR (Monthly Recurring Revenue) progress and others give feedback. That transparency is IndieHackers' charm.

• What it is: A forum, podcast, and meetup network for indie SaaS builders.
• Who fits: Any developer who wants their side project to generate revenue, and anyone seriously considering one-person founding.
• Cost/access: Free. Join groups after sign-up.
• Time commitment: 1 to 2 hours per week.
• What you walk away with: An honest cross-section of "how do people who made money solo actually live?"

Sister sites — MicroConf (indie SaaS conference), Starter Story (interview archive), Tiny Seed (bootstrap accelerator).

3.4 dev.to / Hashnode

Tech blogs plus community. dev.to has a famously kind comment culture; Hashnode offers domain mapping and a strong markdown workflow. These are the fastest ways to find a global beginner-friendly audience.

3.5 Reddit's tech subreddits

• r/programming, r/coding: General tech news.
• r/ExperiencedDevs: Serious discussion for 5+ year engineers. Heavy on career, leadership, and burnout. Beginners go to r/cscareerquestions.
• r/devops, r/sre, r/kubernetes: The reality of running infrastructure.
• r/rust, r/golang, r/python, r/learnprogramming: Languages and learning.

Subreddit moderation varies wildly. A writing tone that wins upvotes in one place gets downvoted in another. Read the sidebar rules first, always.

3.6 Stack Overflow and its relatives

The original Q-and-A site. The consensus is that the golden age has passed, in large part because GitHub Copilot and ChatGPT absorb first-pass questions. Still, for certain questions (especially 5+ year-old stable topics), Stack Overflow remains the most accurate answer. Within the Stack Exchange network, domain-specific sites like mathoverflow, crypto.stackexchange, and security.stackexchange remain very much alive.

Chapter 4 · Chat servers — The arenas of real-time learning

4.1 Discord-based communities

Discord started as a gaming-chat tool, but it's now the default platform for developer communities. The big servers, roughly.

• Reactiflux: The largest React Discord, 50,000+ members. The channels are well-separated between "help me" and "deeper discussion."
• The Rust Programming Language Discord: The official Rust community Discord. The rust-help channel is famous for the quality of answers.
• Python Discord: One of the largest Python communities, 1M+ members. Regular pair-programming and code-review events for beginners.
• ThePrimeagen's Discord: ThePrimeagen (former Netflix, currently a full-time content creator on Twitch / YouTube). His audience community — Vim, Rust, systems programming, with his signature high-tension humor.
• Theo (t3.gg) Community: Theo Browne (founder of Ping Labs and Uploadthing). Many T3 Stack (Next.js, tRPC, Tailwind, etc.) users.
• Latent Space Discord: The Discord for the Latent Space newsletter (swyx + Alessio). One of the highest-signal AI engineer communities.
• MLOps Community: Focused on ML operations and infrastructure. Runs both Slack and Discord.

The shared structure of every server: a handful of active channels and many dead ones. When you first join, watch only #introductions and two or three #help channels, and mute the rest.

4.2 Slack-based communities

• Kubernetes Slack: Every SIG and project has a channel. You can ask maintainers directly. kubernetes.slack.com.
• Gophers Slack: The Go community. invite.slack.golangbridge.org.
• CNCF Slack: A unified Slack across CNCF projects.
• Rust Slack / Rustacean Station: Less central than the Discord, more side-project flavored.
• Vendor-extended Slacks: HashiCorp User Group, Cloudflare Developers, Vercel Community, and the like.

Slack has message-retention limits (the free plan's 90-day window, for example), which makes it unsuitable as a long-term knowledge store. Serious discussions tend to migrate to GitHub Discussions or forums.

4.3 ML / AI Twitter (X) and Bluesky clusters

Traditionally, ML research trends circulate fastest on Twitter. When an author tweets an abstract line, dozens of fellow researchers comment within an hour. It's a first-source signal channel faster than conference proceedings. However, after the 2023 Musk acquisition and algorithm changes, some researchers migrated to Bluesky or Mastodon. As of 2026, the community is split between platforms.

• Useful ML clusters: Researchers at Anthropic, OpenAI, DeepMind, Meta FAIR, and newsletter operators like Latent Space and Last Week in AI.
• Bluesky tech cluster: An impression that systems, language design, and PL researchers migrated more heavily. Depending on your domain, monitoring both platforms is the safe move.

4.4 IRC and Matrix — The classic channels

• IRC (Libera.Chat and friends): Still alive. Long-running OSS projects like Debian, KDE, Gentoo, and NetBSD still call IRC home.
• Matrix: A federated messenger built on the Element client. Mozilla, KDE, and others migrated from IRC to Matrix. Try Matrix if you want a more modern UI.

Chapter 5 · Learning- and content-driven communities

5.1 YouTube-driven learning communities

• ThePrimeagen: Systems programming, Vim, algorithms, with a high-energy joke tone. The live-streaming format is half of the learning.
• Theo - t3.gg: Fullstack, Next.js, TypeScript. A style of turning Twitter debates into videos.
• Fireship: 100-second technology explainers. A great trend-scanning tool for beginners.
• The Coding Train (Daniel Shiffman): Creative coding and p5.js. A tone enjoyable for both children and seniors.
• Andrej Karpathy: ML / LLM lecture series. Minimal implementations like nanoGPT and micrograd are textbook-grade videos.
• Ben Awad, Web Dev Simplified, ByteByteGo: Fullstack, frontend fundamentals, system design.

For these channels, the viewer community (Discord, comments, X) often holds more value than the videos themselves.

5.2 Newsletters — Curated weekly tempo

Newsletters have the best signal-to-noise ratio. A recommended set.

• TLDR: Daily, 5 minutes. Trend-scanning use.
• Pragmatic Engineer (Gergely Orosz): Deep analysis for seniors and managers. The paid tier's reputation as "worth it" is consistent.
• Latent Space (swyx): For AI engineers. Comes with a Discord and a podcast.
• Last Week in AI: Academic news curation.
• Bytes (by ui.dev): Frontend-focused with a humorous tone.
• Console: Curation of new developer tools.

Each newsletter often runs a Discord or Slack. That chat server often has higher value than the newsletter itself.

5.3 Substack and the personal-blog network

The era of long writing is not over. If anything, seniors who find X's first-signal volume tiring write more seriously on Substack and their own domain blogs. Collect 30 favorite blogs in an RSS reader (Reeder, Inoreader, Feedbin), and scan during a 15-minute commute — one of the most consistent learning routines.

Chapter 6 · Summary matrix

One table to plan your next quarter.

Chapter 7 · How to join a global community from a non-English country

For non-native English speakers, every community above has one extra layer of friction. Acknowledge it honestly and plan accordingly.

7.1 The introduction template that works

Most Discord and Slack servers have a #introductions channel. This template performs best.

Hi! I'm [name], a [role] from [country/city].
I mostly work with [stack], and I'm here because I want to learn more about [specific topic].
Currently building [current side project or book].
Happy to help with [what you can offer].

The key is the final line — what you can give. Introductions that only take get forgotten quickly.

7.2 Attitude toward English mistakes

• The overwhelming majority of global communities are non-native speakers. They don't care about your grammar. Only you do.
• Polishing messages with an LLM (Claude, GPT) is an honest strategy. But — write the message in English yourself first, then ask the LLM to polish. Writing in your native language and translating flattens your voice.
• If you're anxious about pronunciation, spend your time in asynchronous text channels (GitHub Discussions, Issues) rather than voice channels.

7.3 Using timezone asymmetry

01:00 to 06:00 Korea time is mid-afternoon on the US East Coast. Real-time chat hits its highest response rate during that window. Daily is unsustainable, so set a weekly slot — "Wednesday 01:00 to 02:00 KST" — and stick to it.

Chapter 8 · Anti-patterns — Don'ts in global communities

• Joined 30 servers, active in none: Limit yourself to 3 or fewer in your first month.
• The HN / Lobsters rabbit hole: Comment-thread immersion eats your real work time. Cap comments at 1 or 2 a day.
• First message is "please help": Asking for help without any introduction. At minimum, a one-line intro first.
• Asking already-answered questions: Asking without searching docs or prior threads reads as time-wasting.
• AI-slop replies: Pasting LLM output without verification destroys credibility fast.
• Collecting business cards at a conference: A pile of cards without follow-up messaging is worth zero.
• Going to a conference only for sessions: Every session is recorded. On site, meet people.
• The chain of negative comments: One negative thread shapes your reputation faster than you think. Disagree once at length, and stop responding to replies-to-replies.
• Discord on 24/7: Notification fatigue is the most common burnout cause. Set per-channel notifications and night-mute.
• Self-promotion spam: Cross-posting your blog or product link to every channel will get you banned.

Chapter 9 · A one-year roadmap — A realistic, cumulative pattern

Closing with a one-year realistic roadmap.

Q1: Asynchronous habit base

• HN 5 minutes a day, Lobsters 3 times a week.
• Join 1 Discord for your main language or framework (Reactiflux or Rust Discord, etc.).
• Subscribe to 3 newsletters (TLDR, Pragmatic Engineer, plus 1 in your domain).

Q2: First conference

• Pick 1 conference with the lowest distance and cost. Recommendations — FOSDEM (free, but Europe) or KubeCon Japan (June, Tokyo).
• Join the attendee Slack or Discord in advance. Pick 3 people you want to meet and DM them ahead of time.

Q3: Start writing

• 3 English articles on dev.to or your own blog. Topics — problems you got stuck on at work and solved.
• Share articles in your Discord and on X.
• If possible, share on HN's Show HN or Lobsters too (sharing your own work is allowed by the rules).

Q4: Go deep in one community

• Pick 1 Discord or Slack you visited most often. Switch from reader to answerer.
• Answer in a channel where you can help, once a week.
• If possible, apply to speak at a side event of that community (BSides, a local meetup).

After one year — 1 conference, 3 English articles, and a reputation as an active answerer in one community. That's an asset no GitHub contribution graph can replicate.

Epilogue — A self-check checklist and a teaser for the next post

Per-quarter starting checklist

1. Did you cap new community sign-ups at 3 or fewer this quarter?
2. Did you commit to a 5-minute daily asynchronous habit (HN / newsletter)?
3. Did you book one conference within the year on your calendar?
4. Did you write your introduction template in English at least once?
5. Did you define your one-line "what I can offer" statement?
6. Did you minimize Discord notifications per channel?
7. Did you pick a writing platform (dev.to / your own blog)?
8. Did you set a weekly timezone-asymmetry slot (once a week is enough)?
9. Did you prepare an English-writing tool (Grammarly / LLM)?
10. Did you write in one line where you want your reputation to stand 6 months from now?

Next post teaser

The next post covers "Becoming a speaker inside a community — from your first CFP to a keynote stage." How to write a CFP that gets accepted, the structure of a first talk's slides, the traps of live demos, and how to handle the post-talk Twitter rabbit hole. Speaking is a different muscle from writing, and the global stage is yet another level of challenge.

A community isn't a place to share code. It's a place to share the loneliness of writing code. And the moment you share that loneliness, the code itself gets better. May you return to one place next quarter.

References

• Recurse Center: https://www.recurse.com/
• KubeCon + CloudNativeCon Europe 2026: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/
• KubeCon + CloudNativeCon North America 2026: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/
• KubeCon + CloudNativeCon + Open Source Summit Japan 2026: https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-japan/
• Strange Loop (archive and announcement): https://www.thestrangeloop.com/
• LambdaConf: https://www.lambdaconf.us/
• P99 CONF: https://www.p99conf.io/
• Papers We Love: https://paperswelove.org/
• !!Con: https://bangbangcon.com/
• DEF CON: https://defcon.org/
• Black Hat: https://www.blackhat.com/
• BSides (Security BSides): http://www.securitybsides.com/
• The Web Conference 2026: https://www.thewebconf.org/
• ICML: https://icml.cc/
• NeurIPS: https://neurips.cc/
• PyCon US: https://us.pycon.org/
• EuroPython: https://ep2026.europython.eu/
• Rails World: https://railsworld.com/
• GopherCon: https://www.gophercon.com/
• GopherCon Europe: https://gophercon.eu/
• JSConf: https://jsconf.com/
• Open Source Summit: https://events.linuxfoundation.org/open-source-summit-north-america/
• FOSDEM 2026: https://fosdem.org/2026/
• Hacker News: https://news.ycombinator.com/
• Lobsters: https://lobste.rs/
• IndieHackers: https://www.indiehackers.com/
• MicroConf: https://microconf.com/
• dev.to: https://dev.to/
• Hashnode: https://hashnode.com/
• Reactiflux Discord: https://www.reactiflux.com/
• The Rust Programming Language Discord: https://discord.gg/rust-lang
• Python Discord: https://www.pythondiscord.com/
• ThePrimeagen: https://www.youtube.com/@ThePrimeagen
• Theo - t3.gg: https://www.youtube.com/@t3dotgg
• Latent Space: https://www.latent.space/
• MLOps Community: https://mlops.community/
• Kubernetes Slack: https://slack.k8s.io/
• Gophers Slack: https://invite.slack.golangbridge.org/
• Bluesky: https://bsky.app/
• Mastodon: https://joinmastodon.org/
• TLDR Newsletter: https://tldr.tech/
• Pragmatic Engineer: https://newsletter.pragmaticengineer.com/
• Last Week in AI: https://lastweekin.ai/
• Fireship: https://www.youtube.com/@Fireship
• Andrej Karpathy: https://www.youtube.com/@AndrejKarpathy
• The Coding Train: https://thecodingtrain.com/

That's all. See you back in at least one of these places next quarter.