Potluck — Freelancing × Leveraging your experience × Component size × Dealing with mediocrity × How to spend “extra time” × Rust vs Node × Free hosting? × More!

Episode Summary

Executive Summary: In this potluck episode, Wes and Scott answer listener questions on freelancing rates, proving expertise, component sizing, throttle vs. debounce, career strategy, design systems, SOAP APIs, incremental React adoption, hosting personal projects, and the value of sharing work online. They emphasize practical experience, online visibility, and systematized workflows over rigid rules.

Main Topics: Freelancing and proving experience: They advise remote freelancers not to anchor rates to local markets unless serving local businesses, and to build credibility through public writing, posting, and professional visibility instead of relying on hidden past work. Component sizing in modern frameworks: The hosts reject hard size limits for components, arguing that encapsulation, reusability, state ownership, and readability should determine when to break something out into its own component. Throttle vs. debounce: They explain throttle as limiting execution to at most once per interval, while debounce waits until input activity stops for a period before firing, using UI and search examples. Career progression and first tech jobs: Boris’s question prompts advice that working in IT can help contextually, but direct effort toward portfolio building, projects, and interview readiness is a better path to a developer role than trying to transfer internally. Designing better with systems: For developers struggling with CSS/design, they recommend Figma, type scales, vertical rhythm, and design systems to reduce subjectivity and build consistent UI with reusable rules. Legacy integration: SOAP, React, and hosting: They discuss how to integrate React into existing apps incrementally, work with SOAP/XML when necessary, and host side projects cheaply using practical tools and lower-cost infrastructure. Monetizing learning and public content creation: For students or career switchers, they recommend blogging, YouTube, TikTok, or similar content creation to make money now while building a future job pipeline and public expertise.

Key Arguments: Remote freelance rates should be set by the market and your skills, not only by local rates, unless you are specifically serving local businesses. Public proof of expertise matters: blogs, Twitter/X, LinkedIn posts, videos, talks, and podcasts can help attract future clients or employers. Component boundaries should be based on state, reuse, encapsulation, and readability rather than arbitrary line counts. Throttle prevents repeated execution during a time window; debounce waits for silence before firing, which fits typing/search behaviors. A first non-dev job in IT may provide stability and time to code, but it is not a reliable shortcut into a software engineering role. Design systems reduce CSS frustration by replacing ad hoc styling decisions with consistent scales, typography, and spacing rules. SOAP is outdated but still used; if a company can provide REST instead, that is preferable, but libraries and DOM/XML tools can bridge the gap. React can be introduced incrementally into legacy sites by mounting into specific DOM nodes and reading initial data from the DOM or server-rendered payloads. Free hosting with unrestricted SSH/root access is unrealistic because providers must prevent abuse such as mining and spam; low-cost VPS or specialized free platforms are more realistic. Teaching what you are learning online is a strong way to create income, build a portfolio, and improve job prospects simultaneously.

Data Points: Suggested starting freelance rate: $60/hour - Wes suggests a remote freelancer can start here and raise rates over time. Premium freelancer rates: $100+/hour, sometimes 2x-3x that - Wes notes experienced freelancers can scale well above beginner rates. Throttle interval example: 10 seconds - Used to explain how throttle suppresses repeated clicks or triggers. Debounce delay example: 1 second or 10 seconds of silence - Used to explain waiting for the user to stop typing before firing a search. Frequency of LinkedIn checking: Once every 6 months / annual click - Scott jokes about how rarely he visits LinkedIn. SOAP API recency: Used once 6 months ago; previously 12 years ago - Wes describes modern rarity of SOAP in his own work history. NPM SOAP package usage: 200,000 people per week - Wes cites this to show SOAP tooling still exists and is actively used. Writer's first job duration: A couple of years - Scott says his first IT job did not directly help him get a web dev role. Youth listener age: 13 years old - Tijas mentions being 13 and starting web development at age 12. Walkie-talkie range: 1 kilometer claimed - Wes describes the Rativa RT45 walkie-talkies and says real-world range exceeded the claim. Smart sprinkler controller price: $57 - Wes’s Wise sprinkler controller cost and value assessment. Smart sprinkler controller alternative cost: $150 or more - Wes says he would not pay this much for a sprinkler controller. Site/hosting trial: 14 days free - LogRocket sponsor offer. Vonage promo credit: 10 euros - Offer tied to promo code syntax10. FreshBooks trial: 30-day unrestricted free trial - FreshBooks sponsor offer. Level Up discount: 25% off yearly signup - Promotion for Brian Douglas’s GitHub Actions course.

Pivotal Quotes: "Throttle only happens at most once every 10 seconds, and all the other ones are ignored. And debounce only happens after 10 seconds of silence." — Wes Boss: Explaining the difference between throttle and debounce with UI and search examples. "I don't think that you need to base your rates locally, unless you are specifically making websites for local businesses." — Scott Tolensky: Advice to a new remote freelancer asking whether local market rates matter. "The real world is that sometimes you don't have the APIs that you need, and sometimes the data that you do have is just dumped into the DOM via server rendering." — Wes Boss: Explaining how to integrate React into legacy sites without a perfect API-driven architecture.

Implications: Listeners are encouraged to focus on practical leverage: ship work, share knowledge publicly, use systems to reduce friction, and adopt tools incrementally. The episode reinforces that career momentum comes from visible expertise and iterative problem-solving, not rigid rules.