Potluck - Bootcamps × Career Change × Figma × Gatsby × AMP × Mongoose × More!

Episode Summary

Executive Summary: This Syntax potluck episode covers practical web-dev advice across design workflows, monitor preferences, React/Gatsby learning, AMP, a new full-stack framework (Blitz.js), databases, boot camps, securing serverless endpoints, HTML/CSS learning, utility-folder organization, docs vs tutorials, imposter syndrome, and GitHub repo renames. The hosts blend opinionated guidance with personal workflow examples, sponsor reads, and tool recommendations.

Main Topics: Design and implementation workflow in Figma and VS Code: Scott explains starting from a blank slate, building component groups first (buttons, forms, type systems, etc.), and thinking of design like assembling React components with reusable Lego-like pieces. Hardware choices: flat vs curved monitors: The hosts debate monitor shape and size, favoring large curved ultrawides for visibility, video editing, and code layout, while noting 4K vertical resolution tradeoffs. React before Gatsby and learning foundations: They advise learning React fundamentals before Gatsby for meaningful understanding, while also noting Gatsby can be used productively with limited React knowledge for static sites and templating. AMP and platform-provided publishing constraints: They discuss AMP as a Google-owned speed-focused format that can improve load times but introduces proprietary constraints, possible ranking incentives, and reduced control over the user experience. New full-stack framework Blitz.js: They react to Blitz.js as a fresh full-stack monolith/serverless framework with server-side data access and minimal client-side state, comparing it conceptually to Rails/Meteor-style approaches and noting uncertainty due to sparse docs/examples. Choosing databases and not over-optimizing: They argue that for their own apps MongoDB remains sufficient, but new projects should be evaluated case by case; they also note emerging patterns like GraphQL layers over databases (Hasura, Prisma). Boot camps, career changes, and vetting programs: Advice is given to a career-switching electrician on evaluating boot camps via Reddit, first-hand experiences, instructor quality, curriculum maturity, and caution around income-share agreements.

Key Arguments: Start design systems with reusable components rather than ad hoc mockups; this maps well to React thinking and makes implementation easier. Curved ultrawide monitors are preferred for many development workflows, especially when screen width matters for timelines, editing, and side-by-side work. You do not need deep React mastery to start with Gatsby, but you should learn enough fundamentals to avoid building on shaky abstractions. AMP can improve speed and user experience in some contexts, but it is proprietary and can create ecosystem lock-in and reduced editorial control. Blitz.js appears to push a server-first model where reads/writes happen server-side, which could simplify auth and state concerns if the framework matures. For personal and most moderate-scale applications, MongoDB is still adequate; changing databases should be driven by project needs, not novelty. Boot camp quality varies widely, so prospective students should research real student experiences and be wary of unproven programs. Securing serverless functions is fundamentally similar to securing any endpoint: authenticate with cookies/JWTs, check authorization, and optionally add DDoS protection layers like Cloudflare. Most docs are insufficient for beginners because they assume missing context; tutorials, examples, and experimentation often teach better than docs alone. Imposter syndrome and code shyness are normal and can be productive if they motivate improvement without becoming self-destructive.

Data Points: Gatsby course/react guidance: Learn React first, but not necessarily at expert level - Advice for a learner planning to take a Gatsby e-commerce course Monitor size: 38 inches - Scott’s preferred curved monitor size Monitors owned: Two 4K monitors: 32-inch and 28-inch - Wes explains his current setup and why he avoids curved due to vertical resolution concerns Podcast episode references: Episode 58 and episode 15 - They mention prior episodes covering imposter syndrome Free trial length: 14 days - LogRocket sponsor offer .tech promo discount: 90% off - Sponsor offer for .tech domains Domain promo duration: 10 years - Coupon applies to domain registration for long-term savings Boot camp financing model: Income share agreement (ISA/ICA) - Discussed as a common boot camp pricing structure LogRocket session replay: 14 days for free - Repeated sponsor offer in the ad read Stronger by Science episode length: 1.5 to 3 hours - Describing the long-form fitness podcast they recommend Course discount: $10 off - Wes’s course promo code syntax

Pivotal Quotes: "Our show, we do what we want here." — Wes Boss: Used while joking about the show’s casual format and tone "I would recommend grabbing a starter kit." — Scott Tolinski: Advice on beginning a Figma/design workflow, especially if not starting from scratch "If you are starting a new project, you're going to want to evaluate your database, and you're also going to want to host it on a.tech domain." — Wes Boss: Humorous transition into the .tech sponsor read

Implications: Listeners get pragmatic guidance: learn fundamentals before frameworks, use real-world feedback when evaluating boot camps and tools, and optimize for workflow fit rather than hype. The episode reinforces that good engineering is often about practical systems, not trends.