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:
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 [Chess.com] 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:
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:
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:
How to find Yulia on the internet:
This week's picks:
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:
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:
This Week's Picks
Special Guest: Jacob Schatz.
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:
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:
This weeks picks:
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:
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:
Our Picks:
Alex
Ari
Tessa
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:
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:
Where to find Gift Egwuenu online:
This week's picks:
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:
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:
This Weeks Picks:
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:
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:
This week's Picks:
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:
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:
Proposals:
test262, TC39 (GitHub)
What is Rust's turbofish?, David Pedersen
SmooshGate FAQs, Mathias Bynens
Where to Find Mark Online:
This weeks picks:
Mark Cohen
Alex
Ari
Oscar
Tessa
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:
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:
Picks:
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:
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:
Find Ben Goddard online:
Picks:
Ben Goddard
Alex
Tessa
Special Guest: Ben Goddard.
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:
Links Mentioned in Today’s Episode:
Resources:
Jenny Lee:
David Ashe:
Special Guests: David Ashe and Jenny Lee.
Sponsored By:
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:
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:
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:
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:
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:
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:
Special Guest: Ash Ryan Arwine.
Sponsored By:
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!
“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]
Sponsored By:
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:
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:
Special Guest: Dave Rupert.
Sponsored By:
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:
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:
Special Guest: Laurie Barth.
Sponsored By:
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:
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:
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:
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:
Special Guest: Rahat Chowdhury.