DiscoverEnjoy the Vue
Enjoy the Vue
Claim Ownership

Enjoy the Vue

Author: The Enjoy the Vue Team

Subscribed: 78Played: 2,739


Enjoy the Vue is a Vue.js podcast bringing you panel discussions, guest interviews, and much more to keep you up to date on what's happening in the Vue and tech communities.
93 Episodes
Episode 93: Hiatus

Episode 93: Hiatus


Support us on Kofi! ( Everybody needs a break sometimes. That’s why we’re going on a brief hiatus! We know you will miss us while we’re gone so, to keep you entertained until our return, we are sharing some extra special picks in today’s episode. From the Steam Deck to the wonderful game of chess, from Inventing Anna to a new season of Taskmaster, we have an exciting list of games and bingeable TV shows for you, plus one or two movies, a horror novella, and some flashy moves too! Don’t miss this special edition of Enjoy the Vue, especially since it will be our last for a while. Thanks for joining us! Key Points From This Episode: Diving right into our special edition picks, starting with the Steam Deck. Why Ari says half the fun of watching Inventing Anna is imitating the accent. Oscar’s movie pick: Everything Everywhere All at Once and why you should watch it. Tessa’s experience of playing Fire Emblem: Three Houses on Nintendo Switch. Ghosts on BBC One (not the American version!) and Severance on Apple TV+. Oscar shares a pick he may or may not have mentioned previously: Slay the Spire. Why Tessa recommends Better Call Saul, even if you haven’t seen Breaking Bad. Ari on why Horizon: Forbidden West is everything she “hoped and dreamed of and more.” Play a game of chess between meetings with Oscar on! The diversity and inclusivity of the cast on The Good Doctor on ABC. A game show and a dramatization; Game Changer and The Girl from Plainville. Why Oscar suggests practicing flashy moves for when you play tabletop games. Tessa offers up an animated film, a book, a YouTube show, and a ginger seltzer. Oscar shares his professional opinion on whether seltzer is better out of a bottle or a can. We leave you with some classic Enjoy the Vue ‘goofing’ to close the show! Tweetables: “Severance, which is on Apple TV+, [is] honestly one of the best shows I have ever watched. Every moment is so intentional, even if it doesn't seem like it in the moment.” — @EnjoyTheVueCast ( [0:11:44] “If you want to just play a game [of chess] in the background with some folks between meetings, you just pop over to the [] tab, make a move, smile at how smart you are, and continue on.” — @EnjoyTheVueCast ( [0:26:07] “It's less about your ability to play [a game] and more about how high your intimidation skill is.” — @EnjoyTheVueCast ( [0:37:53] “People will disagree with me on this point, but I think your first chug of seltzer should be approximately half the can. You may take sips after that, but the initial chug should be about half the can to be enjoyed immediately.” — @EnjoyTheVueCast ( [0:45:18] Links Mentioned in Today’s Episode: Alex Steam Deck ( Ghosts (British version) (, BBC (HBO Max) Taskmaster series 13 (, Channel4 Chess: The Musical ( Game Changer (, Star Realms ( Seedlip Drinks ( Ari Inventing Anna (, Netflix Severance (, Apple TV+  Horizon Forbidden West ( (Playstation 4, Playstation 5) The Girl from Plainville (, Hulu Oscar Everything Everywhere All At Once ( Baba is You (, Hempuli Slay the Spire (, Mega Crit Chess ( Flashpoint ( Practicing meaningless flashy ways of placing pieces in games Tessa Fire Emblem: Three Houses (, Intelligent Systems, Koei Tecmo (Nintendo Switch) Better Call Saul (, AMC The Good Doctor (, ABC Helpmeet (, Naben Ruthnum ねこぢる草 (Cat Soup) (, J.C. Staff Stolen Focus: Why You Can't Pay Attention--And How to Think Deeply Again (, Johann Hari なつめさんち (, YouTube Ginger seltzer NuMuv Multi Use Grip Aid (
Support us on Kofi! ( Have you ever wondered if it's worth breaking the internet? No? Well, today's guest has! Tune in as we chat with Yulia Startsev, a software engineer for Mozilla, and a compiler for JavaScript. We dive into the conversation with who uses semi-colons (and when and why), followed by an anecdote from Yulia about Smoosh and the potential to break the internet. Yulia talks us through the considerations when naming a new JavaScript function, and the promising changes around immutability. We also learn how to remember the difference between the splice and slice functions, and why pattern matching is such an exciting prospect. We hear about the four stages of deciding to change JavaScript, why most programming languages are written in English, and why certain popular functions like caller and colleague were deprecated. We wrap up the episode with a summary of what the array by group function does, who funds the updates to JavaScript, and what Yulia’s fantasy changes to the web would be! So, for all this and so much more, tune in today. Key Points From This Episode: Welcome to today’s guest, Yulia Startsev, an engineer at Mozilla and compiler for JavaScript.  A discussion around semicolons and who’s pro and who’s against (and who’s neither!). Why it’s important not to break the internet: a funny anecdote about SmooshGate.  The considerations to take into account when naming a function.  What’s coming to JavaScript: Immutability.  Why Tuples are such an exciting prospect and their role in wrap-around vs incomplete infinite grids.  How the team understands the difference between splicing and slicing.  How Yulia and the JavaScript team come up with new names.  The idea behind pattern matching, and how it will reduce the cognitive load on developers.  The four stages of deciding to accept a change to JavaScript.  Why most programming languages are written in English.  Why the caller and colleague functions were deprecated.  Array by group: what it is, why it’s interesting, and the readability issues it is facing.  Things the team would love to add to or change in JavaScript.  When Yulia is willing to break the web.  Who funds the updates and changes to JavaScript.  Yulia’s fantasy changes to JavaScript, and why these are far in the future.  Where you can find out more about Yulia! Today's picks: from board games to body pillows to YouTube essayists.  Tweetables: “Pattern matching is a proposal I am quite excited about, switch in case statements are very interesting in JavaScript. By interesting, I mean, broken.” — @codehag ( [0:27:23] “[Pattern matching is] very exciting. It's very, very powerful, which makes it a little scary because using an overpowered tool for something that doesn't need that level of power can lead you to making mistakes that you wouldn't make with a less powerful tool.” — @codehag ( [0:33:19] “It’s significantly more difficult to remove something than it is to add something.” — @codehag ( [0:52:10] Links Mentioned in Today’s Episode: tc39: How We Work ( (GitHub) SmooshGate: The ongoing struggle between progress and stability in JavaScript (, Jacob Friedmann SmooshMonkey ( Reduce/Reduce Conflict (,zero%20or%20more%20word%20groupings.), JavaScript Records & Tuples Proposal (, tc39 (GitHub)  Record & Tuple Tutorial (,a%20deeply%20immutable%20primitive%20value.), tc39 Kolates? (non-English programming language conference) Function.caller ( (deprecated), MDN Why was arguments.callee removed from ES5 strict mode? (, MDN Temporal Proposal (, tc39 Symbol.species ( (please don’t use), MDN Companies scramble to defend against newly discovered 'Log4j' digital flaw (, Jenna McLaughlin (NPR) CommonJS (,outside%20of%20the%20web%20browser.&text=programming%20with%20Node.-,js.,browsers%20don't%20support%20CommonJS.), Wikipedia Run to completion scheduling (, Wikipedia English Linguistic Imperialism in Programming (, Hannah Chung (PagerDuty) Coding Is for Everyone—as Long as You Speak English (, Gretchen McCullough (WIRED) How to find Yulia on the internet: Twitter: @codehag ( Github: codehag ( codehag ( Compiler Compiler (, Yulia Startsev (YouTube) Mozilla Hacks: Yulia Startsev ( This week's picks: Yulia Startsev Sophie from Mars (, YouTube The Ballad of Himbo Geralt: A look at Netflix' The Witcher | Witchermania (, Sophie from Mars Lang Jam (, JT (GitHub) Advent of Code 2021 in APL #1! (, code_report (YouTube) Functional vs Array Programming (, code_report (YouTube) Alex Santa Monica (, Board Game Ari Golden Girls (, ABC (on Hulu) Tessa Body pillow Teacup (, Smarto Club (Xbox Series X and Series S, PlayStation 4, Microsoft Windows, Nintendo Switch, Xbox One, PlayStation 5) Hellbound (, Netflix Jorts ( Jorts update (
Support us on Kofi! ( Today we welcome our friend Jacob Schatz to the show to have an informative and hilarious conversation about his work and how Vue fits into the different projects he is busy with. Jacob is currently the Head of Automation at Remote and has a lot of experience working with JavaScript and Vue. In our conversation, we get to hear from Jacob about the lessons he has learned in these, and other, languages, and how he approaches making decisions about which language to use for a specific task. We also speak about his conference appearances, his home, color representation in games, and the most recent game that Jacob has been developing. Our guest admits that he has an urge to learn and try out all coding languages and keep broadening his horizons; he also touches on his recent efforts to learn Chinese. Stay tuned for this week's extended picks section, where we talk about our favorite TV shows, cleaning products, and interior decorating hacks! Key Points From This Episode: An introduction to Jacob, his current position, and his goal of learning Chinese!  A couple of self-help book recommendations from Jacob.  Jacob unpacks his perspective on side projects and why he likes to use Vue.  Some thoughts on humor at conferences and some of the longest jokes we know. A walk-through of Jacob's house and some of the remodeling he has been busy with.  The game that Jacob was working on recently as a means to explore the possibilities of Vue.js.   Color representation in games and exploring the importance of true and accurate colors.   Jacob's interest in learning and trying out all languages!   Thoughts on breaking up projects into separate components and using different languages for each part.   Examples of some popular devices and the languages that they use.   Jacob shares how he approaches his current work at Remote and the languages he uses.   Thoughts on when Vue is the right or wrong option to get something up and running. Where to find Jacob online and his funny story about his email address! This week's picks; Marvel TV shows, earplugs, comic series, drain cleaner, and more. Jacob shares the inside scoop on his headphone choices. Tweetables: “I've been writing Vue forever. I think the reason I chose it is just because at this point, it's boring and it's easy and I have all the problems solved already.” — @jakecodes ( [0:05:47] “If you had a choice between a lawnmower, React, Vue, Svelt, and an electric skateboard, choose Vue.js.” — @jakecodes ( [0:36:03] “I want to learn all the programming languages, even if it's like, nobody uses them. It's like talking to a bunch of different people.” — @jakecodes ( [0:47:24] “If you're going to build a game from scratch and you can always do whatever the hell you want, you can just technically put something in C++ and then have something in Vue.” — @jakecodes ( [0:54:44] Links Mentioned in Today’s Episode: ( Wireless bluetooth ear protection headphones ( Home Depot Videos ( Leightning L0F Folding Ultra-slim Passive Earmuff ( Allegro ( Wasm ( Internet Explorer 3, an adventure in cross-browser compatibility (, Chen Hui Jing Internet Explorer 3, Wikipedia ( RemNote ( Anki ( Mermaid ( Bang Bang! (!), Fox Star Studios Bang & Olafsen ANC headphones with long battery life ( Enjoy the Vue Cats (, Twitter This Week's Picks Jacob Schatz Learn Chinese with Rocket Languages ( HSK, Jonathan Stewart Taylor Swift ( in concert Alex What If…?, Marvel Studios (Disney+ ( Ari Manifest (, NBC (television show) Tessa Takefumi Ashi Tsubo Massage Board ( Loop Experience Ear Plugs ( Nodame Cantabile (, Ninomiya Tomoko Invade Bio Drain ( Special Guest: Jacob Schatz.
Support us on Kofi! ( Our focus in today's episode is more on the technical side of things and we get right into the weeds on the subject of how to continue your development work when you do not have all the API information you need. We speak about a bunch of options at your disposal, some of which we have tried and some that we have merely heard of, but whichever route you choose, this is definitely something you need to be able to do! Tuning in, you will hear about some recommended resources and tools for the processes of creating mock data and fake responses, and how to approach the data structure and model for the best results. We also get into some thoughts on the responsibilities related to APIs and why considering the different kinds of brains and machines that might be interpreting the data can help us format it most effectively. To finish off, we list a few of our wins and losses in the domain, before getting into this week's fun picks, including a novel, a TV show, a Japanese word game and more! Key Points From This Episode: Our past strategies to deal with an endpoint that is not yet ready to integrate with.  The packages, across different languages that can help in the process.   More online resources for finding necessary responses and elusive information.    The value of creating fake responses for a working API.  Approaches to data and making it readable for different types of people and machines. Data structure, sources of truth, and defining the data model.  Whose responsibility is it to maintain APIs?  Jumping off points for learning more about mocking data and playing with APIs. Mistakes and successes working with mock data and APIs!  This week's picks: books, Japanese crosswords, cookies, and Superstore! Tweetables: “Today, we're talking about what to do when the API endpoint that you need to integrate with isn't ready yet, but you need to still continue development.” — Ari ( [0:00:21] “Sometimes you need to actually be able to figure out the integration part of the API before the API is ready.” — Ari [0:06:16] “If you're wanting to be able to run tests quickly, having to run your tests against an actual API, that can take a while.” — Alex ( [0:10:07] “I do you feel like data transformation is one of the most painful parts of dealing with APIs, especially when the API is not in place.” — Tessa ( [0:12:40] Links Mentioned in Today’s Episode: Hypothesis ( Mockoon ( Httpbin ( Mock service worker ( RedwoodJS ( OpenAPI spec ( Swagger ( Cypress Intercept ( ​​Mock API Server Online Testing & API Mocking Guide, ( Stoplight ​​Setting up mock servers (, Postman ​​Mocking by API (, Postman API Mocking: Best Practices & Tips for Getting Started (, SoapUI Amina’s episode ( This weeks picks: Alex The Gilded Ones (, Namina Forna Ari Superstore (, NBC (television show) Tessa J-crosswords, renshuu (Android (, iOS ( Trader Joe’s Chocolate Chip Cookies Review: Sweet on Trader Joe’s: Chocolate Chip Cookies (, Bake at 350
Support us on Kofi! ( Today we turn our attention to our very own Ari! Join us as we get to know her journey before and after getting into programming. We hear from Ari about the time she spent working in her family's fabric business, some cutting and measuring techniques that she learned, her forays into studying engineering, and how she found programming around the age of 30. This leads to some discussion on conferences, boot camps, and how a brief experience can lead to a whole new direction! We then talk about getting into Vue and our regrets about the first code we wrote in the framework before we finish off the chat with some lighter thoughts on playing games and learning new skills. Stay tuned until the end of the episode to catch our latest picks, featuring a bunch of TV shows we are currently watching. Key Points From This Episode: Ari's professional history, working in the family fabric business, and her path into programming.   Studies in engineering and why this route did not pan out for Ari.  The important conversation that redirected Ari's life and career.    How conferences have influenced each of our lives and standout experiences we have had.   What Ari learned at her first boot camp and the languages it covered. Ari's first introduction to Vue and the first pieces of code we each wrote in the framework.  Thoughts on starting new games; aversion to learning, enjoyment, and new abilities. A reminder of where to find and connect with Ari online.   This week's picks: Netflix shows, game shows, and Ari's headphones! Tweetables: “Another great way to go to a conference for free is to be a speaker.” — @GloomyLumi ( [0:19:12] "There was not a lot of documentation around deploying with a full-stack application. I had to figure that out on my own, which I did.” — @GloomyLumi ( [0:27:08] “It’s pretty much never actually about the end product, at least not from a growth perspective as a developer.” — @GloomyLumi ( [0:28:20] Links Mentioned in Today’s Episode: Minky ( World of Warcraft ( Our Picks: Alex Kongen Befaler ( (IMDB) (Taskmaster Norway) Ari Love on the Spectrum (, Netflix  Tessa Squid Game (, Siren Pictures, Inc., Netflix
Support us on Kofi! ( There are very few barriers keeping you from creating the career you want. For many developers, formal education no longer matters. What matters is demonstrating your skill and your dedication to the craft you’ve chosen to pursue. When you learn in public, you do just that; you share your skill development and your work in progress online. Originally from Lagos, Nigeria, today’s guest is a frontend developer, content creator, speaker, and conference contributor who advocates for the benefits of learning in public. Gift Egwuenu relocated to the Netherlands in 2020 to begin her journey as a Frontend Engineer at Passionate People, a Javascript-focused consultancy based in Amsterdam. Since then, Gift has gained experience working in various environments, with various people, and in a multitude of frameworks and, in today’s episode, she shares some of the pros and cons of learning in public and what it means, from sharing what you’re learning on Twitter to creating video tutorials and live streams. We touch on the concept of conference-driven development, self-motivated learning versus audience-driven content, and work-life balance, and we share some of our favorite resources and suggestions for getting started on your learning in public journey! For all this and so much more, including our weekly picks (of course!), make sure not to miss this insightful conversation with Gift Egwuenu! Key Points From This Episode: Introducing Gift Egwuenu and today’s topic: learning in public. The concept of conference-driven development and #100DaysOfCode as public learning. Why Gift believes that Twitter isn’t necessarily the best forum for public learning. Alternative methods for learning in public, including YouTube videos or Twitch streams. Alex and Tessa share their opposing views on the benefits of seeing learners struggle. How having knowledgeable guests on your stream can be beneficial. Why you get more flexibility from having a specific framing context for public learning. Gift highlights the value of using her edited video content as practice for live streams. Creating audience-driven content versus self-motivated learning in public. How learning in public can engender accountability, according to Tessa. Gift shares the benefits of learning in public, from gaining visibility to community support. The panel reflects on the challenges of maintaining a healthy work-life balance while also learning in public and creating content consistently. Setting boundaries around learning in public without creating extra work for yourself. Some of Gift’s favorite resources, including Shawn Wang and Kent C. Dodds. Tips for getting started, from setting yourself up for success to embracing failure. Gift’s advice for those who want to try public learning: don’t take it too seriously! This week’s picks: United Parcel Service, live-action Sweet Home, Sally Rooney, and more! What headphones Gift is currently using and whether or not she likes them. Tweetables: “A lot of people [think], ‘Why would I come out and publicly humiliate myself? Because this is not something that I'm an expert in.’ They shy away from doing it, but I like to advocate for [public learning], because of the benefits that it comes with.” — @lauragift_ ( [0:09:54] “One of the reasons that learning in public is popular is because it can engender accountability.” — @EnjoyTheVueCast ( [0:22:39] “Job opportunities, getting access to mentors, or just people helping you out is another benefit you get out of [public learning].” — @lauragift_ ( [0:25:51] “The most important thing is to have fun with it. No one’s sponsoring you. No one’s paying you to do it. If you're just doing it for the heck of it, have fun with it. Learn however you want to learn. Don't let anybody get you down.” — @EnjoyTheVueCast ( [0:41:35] “Feel free to ask questions. Feel free to make mistakes. That's definitely the idea of [public learning] in the first place. You're not perfect, so you learn stuff, break stuff, and then you get better at it.” — @lauragift_ ( [0:43:30] Links Mentioned in Today’s Episode: #100DaysOfCode ( Sketchnoting 101 (, Nitya Narasimhan Learn With Jason ( “I hate writing, but loved having written.” —Dorothy Parker Simone Giertz (, YouTube Conversations with ( Friends, Sally Rooney JBL Live 460NC ( Where to find Gift Egwuenu online: Twitter: Instagram: Github: Blog/website: Other: This week's picks: Gift Egwuenu Beautiful World, Where are you, Sally Rooney ( (audiobook) You 3, (Netflix show) ( (, Learn Web3 Alex Atlanta Braves! Oscar New MacBook Pros again (mostly UPS) Tessa Play It as It Lays (, Joan Didion Sweet Home, Studio Dragon, Netflix ( I Tried Every Nespresso Pod (, James Hoffman
Support us on Kofi! ( The focus of today's episode is the tricky role of a solo front-end developer, and we kick things off by sharing some of the experiences we have had working in this configuration. This is a plain and simple show today, without any guests, and our panel gets into some thoughts on the links between front-end dev work and specialization, learning through negative feedback, and the many different levels of accessibility. The conversation also covers how to go about solving problems that reach beyond your scope, and why this can be so hard without a team focusing on the front-end. The consensus seems to be that there is a definite trade-off when working alone versus joining forces and that both scenarios have their advantages. To end things off for today's chat we share a few picks, from TV shows and DIY decor to a new YouTube personality who Tessa thinks is worth checking out! Join us to hear all. Key Points From This Episode: The panel's experiences of working as a lone front-end developer on a team. Front-end development and specialization; we explore how the two are linked.  Bad programming habits and learning what not to do on the job.  The importance of accessibility and the time that goes into the different levels.  Thoughts on solving new, unknown problems with no one else on your team. Finding answers to problems in the treacherous waters of Twitter!  Issues with trackpads, mice, scrollbars, and different browsers. Difficulties with asking the right questions; fear of embarrassment and a lack of vocabulary.   The kind of learning and knowledge accumulation that suits a solo front-end developer.  Final thoughts on the challenges and requirements for working alone on front-end dev.  This week's picks! Peet Montzingo, googly eyes, and Maid. Tweetables: “Even if you know CSS, I think it's not really something that you can show or that people are necessarily looking for.” — Tessa [0:08:11] “You can learn a lot about how to do things by learning how not to do things.” — Alex [0:13:56] “It has been tremendously helpful to have all of the resources I've gained through the people that I've interacted with on the show.” — @GloomyLumi ( [0:28:18] Links Mentioned in Today’s Episode: Grid Critters (, Dave Geddes Flexbox Zombies (, Dave Geddes CSS Grid (, Wes Bos Vue roving tab index ( The Manager’s Path (, Camille Fournier The Backstage Handbook ( Be Here Now (, Ram Dass This Weeks Picks: Alex Googly eyes ( Ari Maid (, Netflix (Limited Series) Tessa Peet Montzingo (, YouTube
Support us on Kofi! ( Today we have a special introduction to the newest member of our team! That means that we will be freewheeling through all things Oscar, taking in his history, current work, love of games, cocktails, music, and a whole lot more that you are not going to want to miss. To kick things off we hear from Oscar about his early interest in computers and tech, and how he began messing around with coding in high school. We also talk about the first time he used JavaScript, his initial thoughts on Vue and the community, and what keeps him excited about working with computers. From there, the conversation takes a decidedly casual turn to the other things that Oscar is passionate about, namely his piano, playing mobile games, going to restaurants, and making cocktails! We even get to hear about Oscar's dream to open a cocktail bar one day before we do a round of this week's picks. So to get it all, listen in and listen up, as we bring you the Oscarsode! Key Points From This Episode: Oscar's background, different jobs, and the paid open-source project he is currently managing.  First experiences of coding during high school, and Oscar's entry into college. Oscar's first job and early experiences of starting to work with Vue and the community.  Tracing Oscar's passion for games and game design.  Oscar's keen musical interests and a little about the piano that he owns!  Thoughts on an important battle: Slack versus Discord! The restaurant scene in Boston, and Oscar's passion for food and cocktails.  Oscar admits his life goal of opening a cocktail bar one day.  This week's picks; the new Beatles documentary, Alba, cleaning vlogs, and more! How to find Grain and connect with Oscar on Twitter and GitHub. Tweetables: “I got into technology, sort of the way I feel a lot of people do. Just playing around with computers, and just having a good time.” — @oscar_spen ( [0:05:58] “When I do get a chance, I love just relaxing and playing simple video games, stuff like that.” — @oscar_spen ( [0:21:52] “Find the things that you think you're awesome at. Also, find the things that you think that you can learn and keep growing.” — @oscar_spen ( [0:31:05] Links Mentioned in Today’s Episode: Enjoy the Vue on Ko-fi ( Tetris Blitz ( MetalStorm: Online ( Hot Dog Bush ( Overcooked ( Cooking Fever ( Clash of Clans ( Top War: Battle Game ( Magic the Gathering ( I am a genius! Oh no! ( Fullmetal Alchemist: Brotherhood ( Spirited Away ( Joe Hisaishi ( Barbara Lynch ( This week's Picks: Alex The Beatles: Get Back (, Disney+ Oscar Having a nice meal at a nice restaurant Tessa Alba (, ustwo games (PC, Apple Arcade, PlayStation 4, PlayStation 5, Nintendo Switch, XBox) 꿀주부 Honeyjubu (, YouTube Lost in Space (, Netflix
Support us on Kofi! ( Design by committee usually has a bad connotation but when it comes to specifying JavaScript, making sure a new feature doesn’t break the internet is just too big a task for one person. Today on the show we invite Mark Cohen to talk about what it is like being on the board of TC39, the institution which standardizes the JavaScript language under the ECMAScript specification. We kick things off with some history behind TC39 before diving right into some of the debates around how to implement new features within the committee and the larger JavaScript community. From there, Mark weighs in on the main goal of TC39, that of ensuring cross-browser functionality, talking about why it is such a challenging but necessary project. We also speak to Mark about their current focus of championing the move toward pattern matching in JavaScript, getting into some of the ideas being bounced around as far as syntax and all the possibilities this feature will enable. Our discussion doesn’t end there though, as we pick Mark’s brain about the processes the TC39 follows for seeing a proposal through from idea to implementation, and also hear about how they adhere to the ‘don’t break the web’ principle. So for all this and more on Enjoy the Vue, tune in today! Key Points From This Episode: Introducing Mark, their affinity for programming languages, and how they got involved with specifying JavaScript. The origins of JavaScript in the TC39 group created under Ecma International. The role of plenaries at TC39 and how the group comes to decisions via consensus. What the pipe operator is and the different sides in the debate for its syntax. Examples where big contributors to languages felt insulted by communities or decisions. Cool assignment operators like Python’s walrus and Rust’s turbofish. Whether ‘design by committee’ is a bad thing in the case of JavaScript. Mark’s perspective that the main goal of the committee is to ensure cross-browser functionality. How TC39 is preventing browser wars using the test 262 suite. The desire for pattern matching in JS and why Mark is championing this. How similar implementing pattern matching in JS would be to reusing switch statements. The intricacies of the syntax and keywords of JS pattern matching and what will be possible. Four phases of TC39 proposals and how they apply the ‘don’t break the web’ principle. The failed array.prototype.flatten project and what led to the ‘smooshed gate controversy’. Where to find Mark online. This week’s picks! Tweetables: “The primary charter of the committee is to make sure that things work across browsers.” — @mpcsh_ ( [0:22:12] “Companies still want control of the web and control of the users of the web, right? But there's a lot more protection now. One of the big invisible ways that this happens is a tool that the committee maintains called test 262.” — @mpcsh_ ( [0:25:30] “I'm championing the pattern matching proposal.” — @mpcsh_ ( [0:27:29] “So that phrase, 'don't break the web’ is a common refrain among the committee. It basically reflects our infinite backwards compatibility mandate.” — @mpcsh_ ( [0:46:33] Links Mentioned in Today’s Episode: TC39 resources: TC39 Homepage/Spec ( TC39 GitHub ( TC39 Discourse ( TC39 Matrix ( Proposals: Pattern matching ( Temporal ( Record & tuple ( Pipeline operator ( Ecma International ( test262 (, TC39 (GitHub) Walrus Operator ( What is Rust's turbofish? (, David Pedersen State of JS ( SmooshGate FAQs (, Mathias Bynens Where to Find Mark Online: Twitter: @mpcsh_ ( Github: @mpcsh ( Blog/website: ( This weeks picks: Mark Cohen Headphones: ÆON 2 Noire (, Dan Clark Audio Crafting Interpreters (, Bob Nystrom Baba Is You (, Hempuli Oy, Arvi Teikari (PC, Switch, iPad, Android) The Fifty: Mt Stimson (, Cody Townsend (YouTube) Alex My Awesome Jamstack Conf talk (, Alex Riviere (Jamstack Conf 2021) Ari Moosewood Restaurant Cooks at Home (, Moosewood Collective Oscar Slay the Spire (, MegaCrit (Microsoft Windows, macOS, Linux, Nintendo Switch, PlayStation 4, Xbox One, iOS, Android) Tessa Dumpster Fire - This is Fine Vinyl Figure (, 100% Soft x KC Green What's new in WSL 2 (, Microsoft On Your Side, Nathan Fielder (This Hour Has 22 Minutes (, CBC)
Support us on Kofi! ( Communities come in an enormous variety of shapes and sizes, each with its own set of values and way of operating. In general, a community should be an inclusive space where everyone involved feels a sense of belonging and is working together towards common goals. However, building a thriving community is no easy task, and in today's episode, we discuss some of the main challenges that can arise when a group of people joins forces, as well as some of the ways by which these challenges can be overcome. We also throw in some good Netflix recommendations! Shoutout to the Vue community which, of course, is near and dear to all our hearts!   Key Points From This Episode: Everyone shares the qualities that they believe make up a thriving community. Communities that we have been a part of, and the roles that we have played in building them. The challenges that come with forming a community.  The benefits of having a very clear code of conduct.  Code of conduct styles that we think will contribute to the creation of unhealthy communities. Advice for people who are in a position where they need to enforce a code of conduct. Ari shares her experience of misconduct and the aftermath within the Vue community. The importance of openly communicating the values that your community stands for. How communities should handle issues that arise. An unsettling trend that we’ve noticed taking place recently in the virtual world.  Appreciation for the Vue community.  Picks for the week, including K-dramas and weighted eye pillows.   Tweetables: “What I want to feel out of a community is that everyone here belongs, we’re all in this together.” — Oscar [0:02:05] “Not everyone has the same values and not everyone has the same experiences to understand how their actions will impact somebody else.” — Ari [0:07:52] “I believe in second chances for people, but people have to want to try.” — Oscar [0:09:13] “As a community, for sure, you need to be able to very quickly publicly acknowledge if something is going wrong, and decrease whatever issue is happening.” — Alex [0:39:51] Links Mentioned in Today’s Episode: Ruby Mailing List incident recap thread (, Brandon Weaver Recurse Center Social Rules ( After Years of Abusive E-mails, the Creator of Linux Steps Aside, ( Noam Cohen (The New Yorker) The Sneetches, supposedly by Dr. Seuss ( Picks: Alex Pixel 5a (, Google Ari Sex Education (, Netflix (television show) Oscar Squid Game, Netflix ( Tessa [청춘시대 (Hello, My Twenties!), JTBC (,MyTwenties!(KoreanDrama)) (Netflix) ( Rêve Pillow (
Support us on Ko-Fi! ( Writing elegant code is one thing, but communicating how it works to the wider world is another. This is where technical writers come into the mix and today on the show, we have one in the hot seat! Ben is a technical writer for a company that specializes in remote team collaboration software and he joins us to talk about how he got into the profession, what his workflow looks like, and the kind of value that people like him bring to teams. We hear about Ben’s technical background and how he decided to switch from a troubleshooting role into something more creative and fulfilling. He talks about his favorite tools for note-taking, image editing, writing, and refining his work. We also hear about how he relates with tech teams to learn about a particular product, and what his iterative process of research and writing involves. And if that was not enough, Ben dishes out some great tips for how programmers and technical writers can collaborate more effectively. Today’s conversation also meanders into many other subjects aside from technical writing, so expect to hear the panel’s thoughts on image processing gadgets, Apple versus Staedtler styluses, game programming using Bash, and a whole lot more! Key Points From This Episode: Ben introduces himself with the standard greeting in the artificial language Esperanto. The value of technical writers and Alex and Tessa’s experience working with them. Ben’s background as a technical troubleshooter and how he got into technical writing. The procedure followed at Ben’s company to release articles explaining how new products work. Tools Ben and his company use for note-taking, templating, storing, and publishing. The favorite tools of Alex, Ben, and Tessa’s for writing, presentations, and more. How to get the best deal on a Photoshop subscription and which apps are a good alternative. Different cameras and image processing technology the panel has encountered. Building things in the most complicated way: CodePen meme templates and Ben’s shell scripts. Ben’s love of interactive fiction and how he learned if-then logic building MUD games. How bad the design of the Apple Pencil 1 is and why other styluses are better. The panel’s knowledge of sentence structure and gendered words in different languages. Tips from Ben for how programmers can communicate more effectively with technical writers. More tips from Ben for how programmers without technical writers can create good documentation. How dev teams without technical writers can advocate for hiring one. Where to find Ben online.  Tweetables: “I decided I would maybe not like to troubleshoot things and that it might be fun to teach about technical things, translate technical speak into something that was more digestible.” — @blipsandbleeps ( [0:04:49] “I do a lot of writing on gut, at least for first drafts. You know, what sounds correct to say, and then I’ll use a tool to help me make sure that it’s the right sentence structure.” — @blipsandbleeps ( [0:34:55] “It’s a fun part of the job to learn about how a thing works. We very much enjoy working with developers and learning about products from their point of view.” — @blipsandbleeps ( [0:41:42] “Not everybody needs a technical writer but if you are trying to convey information to as wide an audience as possible it is good to hire somebody who is good with words.” — @blipsandbleeps ( [0:49:20] Links Mentioned in Today’s Episode: Resources: Bear App ( Docs to Markdown ( Google Docs extension StackEdit ( ReadMe ( Snagit ( Pixelmator ( Photopea ( GIMP ( Adobe Photography Plan ( Polaroid Now Plus Camera ( Game Boy Camera ( CodePen ( Bash ( MUD ( Ellen Korbes’ photography project ( Plus Ergo Grip for Apple Pencil ( STAEDTLER’s Noris digital ( stylus Josh Darnit (, YouTube (dad who follows instructions) Glass Reflection (, YouTube Blender ( Find Ben Goddard online: Twitter ( Picks: Ben Goddard TV: What We Do in the Shadows, Season 3 (Hulu ( Movie: Old (TheMovieDb ( Comics: Murder Falcon (Image comics ( Anime: YuruCamp (MyAnimeList ( Book: Wildwood (Goodreads ( Alex Razer Kishi ( game controller Tessa The Book You Wish Your Parents Had Read: (And Your Children Will Be Glad That You Did) (, Philippa Perry Jet 90 Complete Cordless Stick Vacuum (, Samsung Special Guest: Ben Goddard.
Sponsor us on Ko-Fi! ( The ongoing professional journey that many of us in the world of tech and developing find ourselves on can be exciting and daunting. Here to talk us through her experience on the hunt for a new job at a company that is more suited to her particular needs, is Jenny Lee. Jenny is currently employed as a Senior Software Engineer at Google and is also looking to improve her situation by finding a workplace in which she can engage with a more connected team, and utilize opportunities for monitorship. In our chat with Jenny, we get to hear all about the lessons she has learned along the way, why relationships and mentorship are such priorities for her, and how her approach to and ideas about her dream job have changed over time. We also discuss gauging company culture, different conceptions of management, and how to develop your strategy for job interviews. Jenny has some insightful reflections on the process, and as someone who is highly intentional about where she will next work. We think she is a great touchpoint for anyone with similar aspirations! Tune in to hear it all! Key Points From This Episode: Jenny's current position at Google and the job hunt she is embarking on.  How Jenny's ideal job has evolved since entering the professional world.  Thoughts on friends in the workplace and finding a team that you can relate to.  The questions that can be asked to gauge the culture of a team when applying.   Jenny's thoughts on the importance of mentorship and her personal experience with it.   Identifying red flags for company culture and things our panel finds worrying in interviews.   The best ways to get an idea about a company's approach to diversity and inclusion.   How managerial roles differ from company to company; variance in expectations and approach.  The narrative around switching jobs and how much to share with a recruiter.    Debate and disagreement; weighing the usefulness of these strategies for problem-solving.  Making space for worthwhile input and aiming for more useful meetings.   Reflections from Jenny about the important lessons and changes in her application philosophy.  Tips for negotiating around responsibilities, benefits, and salary.  This week's picks! Tools, films, and job hunt and mentorship sites. Links Mentioned in Today’s Episode: Resources: Soft Skills Engineering Podcast ( Radical Candor, Kim Scott ( Jenny Lee: Website ( LinkedIn ( Pramp ( David Ashe: Key Values ( My Octopus Teacher (, Netflix Special Guests: David Ashe and Jenny Lee.
The focus of today's show is the divisive topic of CSS. There are many different opinions on the strengths, weaknesses, and value of CSS, and to explore this in some detail, we are lucky enough to have Josh Comeau join us on our extended panel! One of the strongest messages that comes through from our discussion is the amount of time and effort that CSS requires you to invest, to reap its benefits. And while not every developer will agree to this exchange, it is hard to argue that certain parts of CSS can make this a worthwhile endeavor. We talk about the ever-increasing complexity of CSS and how this has occurred over time as the language has been added to. We also get into our favorite parts and features, looking at variables, current color, and a whole lot more. So, to hear it all from our team and our great guest, Josh Comeau, be sure to listen in with us today, on Enjoy the Vue! Key Points From This Episode: Opening remarks about CSS and thoughts on overcoming its challenges. How continually adding to the CSS language has increased its complexity over time.  Weighing the best and worst additions to CSS: exciting features and things that have not worked so well.  The original intentions for CSS and its place among other tools for web development.  The difficulties with improving your CSS skills and the issue of the lack of error messages.  Favorite CSS properties: current color, variables, tricks, and more!  The infinite possibilities of tooltips. Tackling the issues of absolute positioning through spending time with them.  Comparing the different web browsers and the most frustrating bugs. Questions of specificity and the hidden mechanisms around sufficient information.   Top recommendations for getting better at CSS and Josh's helpful course!  The availability of great tools and finding the ones that work for you.   This week's pics: the new MacBook Pro, Remarkable Tablet, Sweet Home, and more! Tweetables: “I started trying to really understand CSS. I really, really enjoy the language now. It's become probably my favorite part of doing web development.” — @JoshWComeau ( [0:05:55] “I do think that right now is an incredibly exciting time to be a CSS person because so many amazing things are right on the horizon." — @JoshWComeau ( [0:11:30] “That's what leads to that feeling that CSS is unpredictable and inconsistent. It's not. It's just that if you only have one of the puzzle pieces, of course, it's not going to seem consistent.” — @JoshWComeau ( [0:40:29] Links Mentioned in Today’s Episode: Table Caption ( Rachel Andrew ( Firefox Developer Tools ( Improve SMIL "Parsing timing specifiers" instructions #722 (, Oscar Spencer (W3) CSS SpeciFISHity (, Estelle Weyl Stacking Contexts (, Josh Comeau CSS Stacking Context inspector (, Andrea Dragotta (Chrome Extension) Debug your website in 3D (, Edge Dev Team Learn CSS (, Google Glamorous (, Kent C. Dodds G733 Lightspeed Wireless RGB Gaming Headset (, Logitech Astrolokeys (, Amy Wibowo and Cassidy Williams 3.5mm EarPods (, Apple Twitter: joshwcomeau ( Blog: ( The Long Way to a Small, Angry Planet (, Becky Chambers Champion Sports Lacrosse Balls ( Golden Girls Quotes API (  ReMarkable Tablet ( CSS for JavaScript Developers (, Josh Comeau Comic Parchment (, Ben Harman Buy font ( (referral link) Play It as It Lays (, Joan Didion Sweet Home (, Netflix Special Guests: Jenell Pizarro and Josh Comeau.
With the release of Vue 3, developers now have access to the Composition API, a new way to write Vue components. This API allows features to be grouped together logically, rather than having to organize single-file components by function. Using the Composition API can lead to more readable code, and gives developers more flexibility and scalability when developing their applications, which signals a bright future for Vue. At least, this is what today’s guest believes! Today, we speak with Oscar Spencer, developer at Tidelift and co-author of the Grain programming language, about Vue’s Composition API and why he believes it represents great things for Vue. We touch on Options API, our opinions of a template-first approach, and why Composition API is infinitely better than Mixins, as well as how JavaScript can prepare developers for Options API and what to watch out for when you first start working with Composition API in Vue. All this plus this week’s picks and so much more when you tune in today! Key Points From This Episode: An introduction to today’s guest, Oscar Spencer. The panel shares what sound their Slack makes when they receive a new message. Oscar shares his personal passion for the Vue Composition API. Why he believes that Vue’s bright future includes the options API too. Why Composition API represents great things for the future of Vue. The panel discusses commit messages, interactive rebasing, and squashing. What Oscar means when he says that the Composition API makes Vue more scalable. Oscar and the panel weigh in on taking a template-first approach  Discover Oscar’s situational approach to composables when reusing business logic. Composition API versus Mixins and why Oscar believes Composition API is superior. Whether Options API or Composition API is easier to teach to a beginner developer. How JavaScript prepares developers for Options API, which Oscar describes as ‘cozy’. Oscar on how to know when to use Composition API versus Options API. Why you would choose Composition API over simply using JavaScript: reactivity. The panel shares some of the longest Vue components they have worked on. Render functions in Vue and Oscar’s perspective on React versus Vue. What to look out for if you’re new to Composition API; not understanding Vue’s reactivity. Why the coolest thing Oscar has done in Vue is write a backend using the reactivity API. This week’s picks: Only Murders in the Building, The Artful Escape, Dyson Sphere Program, The Great Ace Attorney Chronicles, and more! Tweetables: “When I look at the Composition API, I see a very bright future for Vue.” — @oscar_spen ( [0:02:22] “The Composition API just gets rid of a whole host of issues that you have with Mixins. In fact, Mixins were my only complaint in Vue 2.” — @oscar_spen ( [0:24:05] “Don’t be too scared of the [Composition API]. It was definitely designed with composition in mind. It was designed for you to have your composables consuming composables and not blowing up the world – [while] being fairly easy to follow as well.” — @oscar_spen ( [0:27:34] “Regular JavaScript modules only get you so far because, fundamentally, what these regular JavaScript modules are missing is the reactivity. What the Composition API is letting us do is compose things that are reactive.” — @oscar_spen ( [0:41:44] “By far the biggest gotcha with the Composition API is not understanding Vue's reactivity. That’s going to be the biggest gotcha that you can possibly run into. I highly recommend, instead of trying to wing it, just go look at a tutorial.” — @oscar_spen ( [0:57:02] Links Mentioned in Today’s Episode: Vue-oxford ( Unconventional Vue - Vue as a Backend Framework (, Oscar Spencer (VueConf US 2020) AITA for being mad at my parents for decorating my first house without my consent? (, iamcag07 @oscar_spen ( (Twitter) ospencer ( (Github) Grain ( Dyson Sphere Program (  The Artful Escape ( Only Murders in the Building (, Hulu (Television Show) The Great Ace Attorney Chronicles (, Capcom (Nintendo Switch, PlayStation 4, Steam) TERRO® Fly Magnet® Super Fly Roll ( Tiny Beautiful Things: Advice on Love and Life from Dear Sugar (, Cheryl Strayed Special Guest: Oscar Spencer.
This Episode is sponsored by Cloudflare Workers ( Join us today as we talk to Ash Ryan Arnwine (developer experience leader for DataStax) about Getting Started Guides. Ash takes us through his experience with Vue, and how the guides in Vue 1 were the North Star for him when he was working with Adobe Creative Cloud. We discuss the challenges in migrating from different versions, and the downsides to Getting Started videos in place of text. Find out how keeping Ash's four-year-old daughter from sleeping is the highest praise the Vue team has received, and what each of the team feels is better: prescriptive or flexible guides. From picking the correct level to pitch your instructions at, to the different types of people defined as “developers”, you don’t want to miss out on this information-packed episode! Key Points From This Episode: Welcome to Ash Ryan Arnwine, developer experience leader for DataStax and previously, Adobe Creative Cloud. Ash’s introduction to Vue and why it became the North Star for thinking about writing documentation.  What makes the path from getting started to building an app clear.  Finding the balance between prescriptive and “sprinkling in some HTML” in Vue.  How Vue has a background framework beyond the beginner’s instructions. The importance of being able to access the full app code on GitHub. Picking the level of developer that your Getting Started Guide caters to (sometimes the middle-ground is the worst place to be). Why you need to maintain your Getting Started Guide. How to highlight important information that people might skip when reading the Getting Started Guide.  The challenges of migrating from Vue 2 to Vue 3, and communicating it to users. Why it’s crucial to make a roadmap of where the app is going. How Vue’s completely honest self-appraisal won Ash over.  Why videos are less appealing than documents about Getting Started.  The naming conventions for Vue. Creating a community to talk about “software things” in different places.  How to contact Ash. Discover this week’s picks from each of the team! Tweetables: “For a long time, I think Vue sort of became, in some ways, a North star for me personally, when thinking about documentation, and how do you orient somebody into a completely new technology.” — @ashryan_io ( [0:02:12] “One thing that I've learned over time with just in leading developer relations and developer experience is that oftentimes, it's the sample code that turns into the most popular resource.” — @ashryan_io ( [0:25:41] “Oftentimes, I think that the imperative is just like help people get started, help people get started, and we don't get a chance to step back and think, 'Okay, who are the people? What are they getting started doing?” — @ashryan_io ( [0:29:59] “Developers are not a monolith.” — @ashryan_io ( [0:33:44] "I think that when pondering developer experience, broadly, one of the things that is important to get to and be able to offer, but often isn't there at the very beginning is some sort of insight into the future, in terms of where things are going.” — @ashryan_io ( [0:46:19] “Today, there's like so many awesome resources to learn. It's almost too much, right?” — @ashryan_io ( [0:55:34] Links Mentioned in Today’s Episode: Adobe Creative Cloud ( DataStax ( Ash’s video with daughter ( The Breath of the Wild (, Nintendo Switch Saturn Devouring His Son (, Goya Twitter: ashryan_io ( Github: ashryanbeats ( Instagram: ( Website: ( Obsidian ( What You Do Matters: Boxed Set: What Do You Do with an Idea?, What Do You Do with a Problem?, What Do You Do with a Chance? (, Kobi Yamada Shang-Chi and the Legend of the Ten Rings ( Neutrogena® Hydro Boost Body Gel Cream ( The Great Ace Attorney Chronicles (, Capcom (Nintendo Switch, PlayStation 4, Steam) Humans of Flat Goya Rendition Print (, mimi-claire (RedBubble) Special Guest: Ash Ryan Arwine.
This episode is sponsored by Clouflare Pages! ( This week, The Enjoy the Vue panel digs into the topic of asynchronous event loops: how it can save you time, but also how it can trip you up. Asynchronous update queues are an efficient way for platforms like Vue to save time and energy by recognizing a group of similar commands and doing a batch run at the same point in time. We get into event loops, how the term ‘next tick’ came about, and how synchronous stacking can cause a Stack Overflow Error. You’ll also hear some of our favorite terminal commands, including a special tidbit on how to say ‘please’ to your computer! Lastly, we share our picks of the week that will add joy, intrigue, and deliciousness to your life, so make sure you tune in to hear it all! Key Points From This Episode: Introducing today’s topic: asynchronous event loop in JavaScript. An asynchronous update queue and why Vue uses one. Why an asynchronous update queue is so efficient. How an asynchronous update queue can also sometimes cause problems. Where the term ‘next tick’ originated and how it is applied today. A breakdown of event loops and stack heaps. Tessa shares her understanding of blocking. Why a blocking operation is synchronous. Alex explains what the heap is and how items transition to the stack. Recursive functions and the stack overflow error message. The team shares their favorite terminal commands. Hear our picks for the week, which include gourmet sour gummies, intriguing portraits, and a fascinating new board game!  Tweetables: “When you make a change to your data in Vue, it doesn't happen right away because that would potentially be inefficient. What it does is it groups all the changes together and then batch runs through them at a set point in time. That's the queue that they all get added to.” — @EnjoyTheVueCast ( [0:02:04] “Basically, it's like doing your math without showing the work. That's what Vue does. Teachers love it.” — @EnjoytheVueCast ( [0:03:20?] “My understanding is that blocking doesn't mean it never happens. It's just like I'm going to save all of these user interactions until the next time that the queue is free. Then, I'm going to jam all of them in there. You're going to get all 500 clicks in one second.” — @EnjoytheVueCast ( [0:18:25] “There is this nebulous event that may or may not happen. When it happens, that click, that event doesn't necessarily fire immediately. It gets put on the end of the event queue, the event loop queue.” — @EnjoytheVueCast ( [0:19:16] Links Mentioned in Today’s Episode: ( Back to the Vueture: Stuck in the Event Loop (, tessa (VueConf US 2019) * What the heck is the event loop anyway? (, Philip Roberts (JSConf EU) Olivia Beaumont ( Obscurio ( (Boardgame) The Legend of Zelda™: Skyward Sword HD (, Nintendo Switch Candy Kittens ( Web Exclusive Gourmies Bundle (, Candy Kittens
This week's episode is sponsored by Cloudflare Workers (! Have you ever wished that Vue was smaller? We know we have. Petite-Vue is an astonishing 5.5KB, which is so small, it’s almost invisible. Dave Rupert, a developer at Paravel, joins us today to discuss all things Petite-Vue. We hear how this smaller version was released, and Dave shares what his experience of using it has been like. Often, when a framework is more compact, there are tradeoffs or sacrifices users have to make, but this does not seem to be the case with Petite-Vue. We talk about Alpine, how Petite-Vue is different, and we also get stuck into the use cases for Petite-Vue. Dave shares one of his totally wild ideas, which, naturally, Alex is all over. Our wide-ranging conversation also touches on interviews and what needs to change with them, templates and styles, and as usual, we wrap up with everyone’s picks for the week. Tune in to hear it all! Key Points From This Episode: Get to know today’s guest, Dave Rupert. Everyone's take on how they would feel if Vue was five kilobytes. The story of how Petite-Vue came to be released. Dave’s experience of using Alpine and some of the challenges he had with this. What the jump from Vue to Petite-Vue is like. Hear about the idea that Dave runs past Alex. Some other great use cases for Petite-Vue. Unpacking the broken coding interview system; things need to change. Questioning some obscure hiring requirements. The framework Dave uses given that he works in an agency. In business, frameworks can become politicized and sites for contention. Things other people do that make everyone believe they are monsters. Diving into the world of template style and script. Where you can find Dave online to tell him how wrong he is about all his choices. Everyone’s picks for this week; there are some great ones! Tweetables: “I think five kilobytes is the perfect stealth technology, like Alex is talking about that you can kind of sneak it into a project and no one’s going to go, ‘Hey, hey, hey, what’s going on now? I didn’t approve this.’” — @davatron5000 ( [0:02:54] “I was kind of a late bloomer I guess for Vue but I just was like, you know, I think the more I’ve used Vue, the more it has all the features I like.” — @davatron5000 ( [0:37:36] “I’m just saying if you drop the opening curly brace on a four loop, you’re a monster.” — @davatron5000 ( [0:47:58] Links Mentioned in Today’s Episode: My petite-vue Review (, Dave Rupert Evan You’s petite-vue preview (, Twitter Angie Jones (, Twitter Twitter: davatron5000 ( Website: ( Mini Motorways (, Dinosaur Polo Club (Apple Arcade, Steam) Bubble (, Morris, Morgan, Cliff, Riess  Chester's Cheddar Flavored Paws Cheese Flavored Snacks ( Bat,bat Black Coffee Soda ( Special (, Netflix The Great Ace Attorney Chronicles (, Capcom (Nintendo Switch, PlayStation 4, Steam) Special Guest: Dave Rupert.
This week's episode is sponsored by Cloudflare Pages (! Laurie Barth, or Laurie on Tech as she is well-known in the dev industry, is a software engineer who started as a mathematician, currently working as a Senior Software Engineer at Netflix. Additionally, Laurie is a content creator and technical educator across various mediums. She is also a frequent conference speaker, speaking at events across the globe, and a technical blogger contributing to publications such as CSS Tricks, Smashing Magazine, and A List Apart, as well as an active member of the TC39 Educator's committee and a Google Developer Expert. In today’s episode, we share some of our more memorable job interview experiences, both good and bad, but mostly terrible, and we dive into how those experiences could be improved upon, starting with the company setting realistic expectations for potential candidates from the beginning. We also touch on unnecessary and unfair technical demonstrations, the value of affording candidates the option to show themselves in their best light, and the inherent biases that exist when interview panels aren’t diverse, and Laurie highlights the power that candidates actually have given the shortage of engineers making this appeal to listeners: take some of that power back! Tune in today for all this and so much more, including, of course, our weekly picks. Key Points From This Episode: Laurie shares a terrible technical interview that stands out from her experience. Why a generic interview format very rarely makes sense for any company. Why companies need to set their expectations at the beginning of the interview. The importance of recognizing how much time it takes to develop a technical interview. Why you can’t steal an interview from elsewhere rather than writing one yourself. The value of judging what is important based on the signal a company is looking for. Alex talks about one of the more memorable (read: terrible) interviews he has been through. Ari reflects on a pair programming interview that she describes as ‘interesting’. The pressure that is put onto incoming developers to demonstrate their technical skills when it isn’t necessary for the role they will fill. Laurie emphasizes why companies should be looking for someone to augment their team. Why it’s not about working with people ‘smarter’ than you, but people you can learn from. Laurie’s frustration with the use of trivia questions and the benefits of offering candidates options to present themselves in their best light. Tessa’s turn to share her experience with a terrible interview that featured live UI coding. The disconnect that exists between hiring managers, recruiters, and candidates. Laurie highlights the power that candidates hold given the shortage of engineers and urges listeners to take that power back. What Ari calls ‘douchebag alert’ questions, how people answer, and what it says about them. The gender bias that typically exists when interview panels aren’t gender diverse. Why it’s important for team members to meet potential candidates and vice versa. Tessa shares the acronym, REACTO: repeat, example, approach, code, test, optimize. How interviews tend to cater towards those who are extroverted, outgoing, and talkative. Laurie highlights some positive interview experiences and what companies can do better. Alex shares a tip about asking the same question of everybody, such as “what is the focus of your company?” Tweetables: “People can't read your mind. You need to preface, you need to set your expectations at the beginning [of the interview].” — @laurieontech ( [0:07:45] “I want to work with people who are smarter than I am, but here's the trip: everyone is smarter than I am. It depends what the measuring stick is and what category we're talking about.” — @laurieontech ( [0:26:51] “The goal of an interview, in my mind, should be for people to show you what they know instead of what they don't know. If you're giving people options, you are giving them the opportunity to present themselves in their absolute [best light].” — @laurieontech ( [0:29:59] “Right now, in this moment in time, unless you are an entry level candidate, the candidates have all the power. There's such a shortage of engineers. I would like to see people taking that power back a little bit.” — @laurieontech ( [0:38:41] “Interviews, pretty much no matter what you do, will always somewhat cater to people who are extroverted and outgoing and talkative. The only way I challenge that is I think people who can't communicate about their code at all are probably not great engineers.” — @laurieontech ( [0:48:47] Links Mentioned in Today’s Episode: ( @laurieontech on Twitter ( Fortnite (Windows, macOS, Nintendo Switch, PlayStation 4, PlayStation 5, Xbox One, Xbox Series X/S, iOS, Android) ( LEGO ( Wingspan ( (Boardgame) Heal & Glow Facial Serum ( How Not to Be Wrong (, Jordan Ellenberg Special Guest: Laurie Barth.
Imagine working on projects that last for two weeks or less. This is what today’s guest, Jason Etcovich, gets to do all the time! Jason is a Senior Software Engineer at GitHub, where he is part of the Special Projects team. He is also involved in the Paper Cuts project, which works directly with the community to fix small to medium workflow problems. In this episode, Jason sheds light on how he became a software engineer having come from a design background. While this may sound like a drastic shift, it was gradual, which made the transition smoother. We talk about some of the exciting happenings at GitHub, like GitHub Pilot, Paper Cut, and Codespaces, and what these projects will offer the community. Our conversation also touches on automation and where it goes right and wrong, how to use software to make our lives better, and as usual, we get into some classic developer debates. Tune in to hear it all. Key Points From This Episode: Get to know today’s guest, Jason Etcovitch, and want he does.  How Jason went from graphic design to working at GitHub.  Hear more about the work that Jason does through Paper Cuts.  Insights into Paper Cuts’ research and how they decide which projects to take on.  The importance of having a design thinking mindset when you problem solve.  A high-level view of GitHub Pilot, GitHub’s new machine learning feature.  What it is like working on projects that do not last longer than two weeks.  The open graph image generator project Jason is excited about.  How to justify projects without necessarily having the data to back up projects.  Some of the ways we can make our lives better with software, according to Jason.  Common pitfalls Jason sees when trying to set up automations.  Everyone’s take on Prettier and Standard JS.  Getting into the semicolon debate: everyone weighs in.  What everyone thinks about the age-old tabs versus spaces fight.  A look at one of GitHub’s latest releases, Codespaces.  Hear what the picks for the week are. Tweetables: “Part of learning that design mindset is understanding like, how does a person approach this thing? What are the various touch points that they have to consider?” — @JasonEtco ( [0:10:03] “How do you say like, ‘Oh, yes. This is important,” If you don't have the data to back it up.” How do you get the data to back it up, if you don't prioritize that project? Where in that loop does it fit to get all of that data?” — @JasonEtco ( [0:19:57] “If you build your automation tool in an inflexible way, you'll really regret it later.” — @JasonEtco ( [0:27:13] Links Mentioned in Today’s Episode: * ProBot ( * Github Feedback ( * Alex Tweets at Nat ( * StandardJS ( * Jason on Twitter ( * Jason's Website ( * Wyze Camera ( * She-Ra and the Princesses of Power (Netflix ( * Marple (puzzle game) ( * VSCode in the browser (, Joel Califa * The Matrix ( * @EnjoyTheVueCats ( Special Guest: Jason Etcovitch.
The increasing volume of the societal discussion on mental health is blooming into a variety of results. One of the interesting aspects of these developments are apps aimed at helping users with their self-care and mental health management and, today, we have a conversation about a new mobile app called Whimser, which is doing exactly that! We are joined by their founder and CTO, Rahat Chowdhury, who speaks to us about the startup, its roots in CBT or cognitive behavioral therapy, and how they approach using journaling to combat negative thought patterns and cognitive distortions. Rahat explains how the application is not designed as a replacement for therapy but rather as a tool to enhance practices that users already have in place, offering continuity and opportunities for further reflection. Rahat also explains a little bit about how the company is currently being run and the leadership philosophies that ground what they do. He strongly believes in bringing a human element into the work, and shares the interesting decision to bring in junior developers from the get-go and the motivations behind this. For this fascinating conversation with an inspiring young founder and developer doing important and conscientious work, make sure to tune in! Key Points From This Episode: A little bit about Rahat and the two companies he is involved with. Understanding cognitive behavioral therapy and cognitive distortions. Experiences of imposter syndrome and the ubiquity of these feelings across the industry.   Rahat's inspiration for creating Whimser and adding to the mental health conversation.   Considerations around broadening the scope of Whimser beyond therapy.  How Rahat approached things at the outset and how he chose his co-founders.   The importance of taking action and balancing this with patience and delegation. Rahat's approach to code reviews and the consideration that goes into better communication practices.   The impetus behind the decision to bring in early-stage developers at the beginning.    Lessons that Rahat has learned from working with different team leads during his career.  Decisions around salaries at Whimser; how Rahat and his co-founders are funding the company at this point. Translating skills as a web developer into the world of mobile applications. The funding component of running a startup; Rahat's thoughts on effective pitching.  Data collection considerations and the idea of user-owned and licensed data.    The inspiration for the name of the company: combining whimsy and whisper! This week's picks: Litter robots, Focusmate, headphones, new songs, and more. Tweetables: “We do stuff like having some natural language processing in the background that helps you categorize your thoughts into what could be potential cognitive distortions to help you set yourself up to figure out how to combat those thoughts.” — @Rahatcodes ( [0:02:14] “Trying to create a better atmosphere or a better community around tech will definitely help out in fighting imposter syndrome.” — @Rahatcodes ( [0:06:37] “Whimser started from when I started taking better care of my own mental health. I started going to therapy and treating my depression, and a few other things.” — @Rahatcodes ( [0:09:46] Links Mentioned in Today’s Episode: Rahat on Twitter ( Rahat on Github ( Rahat on Polywork ( Rahat's Blog/website ( Whimser ( VirtualCoffee ( meetup Focusmate ( Litter Robot ( Night owl t-shirt ( A-O-K (, Tai Verdes Deja Vu (, Olivia Rodrigo Special Guest: Rahat Chowdhury.
Download from Google Play
Download from App Store