Summary of 1010: No one cares anymore?

Overview of Syntax 1010: No one cares anymore?

This potluck episode covers a mix of practical frontend career advice, browser curiosities, code quality culture, testing philosophy, refactoring animation libraries, web security awareness, learning strategies, update fatigue, and the emotional impact of AI on software development. Wes and Scott lean into a recurring theme: modern web development is changing fast, but the core skill is still solving problems well.

Key Questions and Answers

Why is it so hard to find good frontend developers?

• The hosts argue that frontend has become much broader and harder than many people assume.
• A lot of candidates may know “some React” but lack fundamentals like:
  • CSS/HTML
  • web performance
  • accessibility
  • bundlers
  • file formats and browser basics
• They blame part of the issue on the bootcamp boom and shallow “React-only” training.
• Advice: keep searching, and be realistic about compensation and sourcing.

What is document.designMode for?

• designMode turns the whole document into an editable surface, similar to applying contenteditable to the entire page.
• It was likely intended to support browser-based WYSIWYG/rich-text editing.
• In practice, robust rich-text editors are extremely hard to build, so most real products layer a lot of custom behavior on top.
• They note it can still be useful for:
  • quick page edits
  • debugging
  • simple invoice/receipt editing workflows
• It’s a “real” browser feature, not just a Chrome trick.

How do you work with teammates who don’t care about code quality?

• The hosts challenge the assumption that only one side is right, especially around testing strategy.
• They define the test types:
  • Unit tests: one small unit, like a function
  • Integration tests: how components/systems work together
  • End-to-end tests: simulate a real user in a browser
• Their advice:
  • Don’t lead with criticism or ego.
  • Work with management/engineering leadership to establish enforceable standards.
  • Use concrete examples of customer pain and business impact.
  • Bring a clear solution, not just complaints.
• They emphasize that culture and standards must be backed by leadership and automation, not just personal preference.

Should you keep both Motion and GSAP in the same codebase?

• They recommend consolidating to one library if possible.
• Motion is praised as currently being in a very strong place in terms of UX and defaults.
• GSAP is still powerful, but having both libraries can lead to inconsistency and unnecessary complexity.
• If the codebase is large, use AI-assisted refactoring to:
  • find every GSAP usage
  • map the migration path
  • simplify the animation stack
• They suggest 3D/Three.js work may be a separate concern.

Can you recreate CSS visually without running it?

• Yes — this is something they’ve already done in a video.
• They mention a challenge where they had to recreate a design from CSS using a visual editor without rendering the code.
• It was intentionally difficult because the drawing tool was bad, which made the challenge funnier and harder.
• They also filmed the reverse exercise: coding a design without seeing the rendered output.

How should you think about malicious interview code or suspicious coding challenges?

• They revisit a warning about interview tasks that include code you’re asked to run locally.
• Red flags mentioned:
  • strange API keys
  • ZIP/Google Drive delivery
  • odd formatting or spelling
  • suspicious install scripts
• Best practice: inspect before running anything, and use tools like Claude or similar to review it.
• They note that while obvious bad English used to be a giveaway, AI-generated phishing is becoming more polished.

How do you level up as a mid-level engineer?

• Learning should happen in two modes:
  • Surface-area learning: staying aware of the landscape through podcasts, blogs, social media, docs
  • Deep learning: building real things and pushing into edge cases
• Their advice:
  • Pick projects you’re genuinely excited about.
  • Use those projects to go deep.
  • Try to become the person at work who truly understands the latest AI tooling/workflows.
• They believe the most valuable people will be those who understand modern AI tooling deeply and can teach others.

Is it reasonable to avoid updates?

• They discuss the tension between stability and progress.
• Wes is strongly pro-update; Scott is more cautious but still sees the benefits.
• Reasons people avoid updates:
  • UI changes that degrade workflow
  • invasive new features
  • apps getting bloated and harder to use
• Their conclusion:
  • Avoiding updates entirely is often resistance to change, not a strategy.
  • Some updates are genuinely bad, but many fix bugs or add useful features.
  • It’s reasonable to be selective, but not to freeze everything forever.

How do you reconcile loving coding with AI changing the job?

• Patrick’s question is framed as a career/identity crisis: AI is making coding feel less craft-based and more uncertain.
• Wes and Scott acknowledge the emotional impact:
  • people who love the craft may feel their identity threatened
  • some of the “deep” parts of programming matter less in a world of AI assistance
• Their main point:
  • the job is still problem-solving
  • the problems are simply changing
  • there are new, interesting problems to solve in AI workflows, browser APIs, and tooling
• Scott compares it to other industries changing tools over time: the craft evolves, even if the old skills still have value.

Main Takeaways

• Frontend hiring is difficult because the field now requires broad fundamentals, not just framework familiarity.
• document.designMode is a real but niche browser capability for editable documents.
• Team quality problems are usually solved through leadership, standards, and automation — not argument.
• If two libraries solve the same problem, consolidating often reduces complexity.
• Security hygiene matters: never blindly run code from interviews or strangers.
• Staying relevant means learning both the new AI tooling and the deeper problem-solving skills behind it.
• Resisting all updates can be as limiting as updating too aggressively.
• AI is changing software work, but it is not eliminating the need for strong engineers.

Mentioned Resources and Events

• Syntax meetup in Amsterdam: June 10, opening party for JS Nation and React Summit
• JSNation / React Summit: June 11–12
• Syntax live streams on YouTube: weekly, covering recent web/dev news and projects
• Motion: motion.dev
• Referenced testing tools: Playwright, Cypress
• Security review tool mentioned: Claude
• Phases podcast: Scott’s wife’s parenting podcast, discussed as a shameless plug