DiscoverBackend Banter
Backend Banter
Claim Ownership

Backend Banter


Subscribed: 102Played: 1,561


The only podcast dedicated to backend development, technologies, and careers. Lane Wagner, the founder of, interviews successful backend engineers to get their takes on various trends, technologies, and career tips for new backend developers. Golang, Python, JavaScript, and Rust are the programming languages most commonly discussed, but speakers dabble in all sorts.
63 Episodes
In today’s episode, we go to war with Sam Selikoff, co-host of the Frontend First podcast, and specialist on everything Frontend related. We have an amazing conversation where we discuss Sam’s journey, as he also did some backend work in the past, we talk about abstractions, what JavaScript is doing differently from other languages and frameworks, why the frontend should be driving the backend and not the other way around, and finish it off with a discussion about RSCs (React Server Components). Learn back-end development - Listen on your favorite podcast player: Frontend First: Sam's X/Twitter: Sam's Youtube: Timestamps: 00:00 Intro 00:51 Who is Sam Selikoff 02:12 Abstractions - Should you go a level deeper? 06:37 What was Sam's talk about 10:51 What is JavaScript doing differently? 19:10 Do you want the frameworks to push more features out of the box for backend work? 24:04 Strong opinions on a library level 30:29 Shipping more standardized interfaces 37:06 The frontend should be driving everything in the backend 39:12 Your types should flow from the database to the frontend, but not the product decisions 46:53 React Server Components 58:49 Where to find Sam
Today we bring Thomas Ballinger, a developer at Convex, an open-source backend for application builders. We will be discussing mainly databases, and why at Convex they use Rust and Typescript. We'll also talk about systems scalability, infrastructure and go over different practices regarding abstractions Learn back-end development - Listen on your favorite podcast player: Convex: Thomas' X/Twitter: Thomas' Website: Timestamps: 00:00 Intro 00:33 Thomas' background 02:29 Convex - what it is and why should you use it? 03:16 What are query planners? 06:32 SQL is a very high level language 07:43 The primary differentiator of Convex 10:49 Who are Convex's biggest competitors? 14:20 How do you build the infrastructure 17:11 What type of database is Convex? 19:18 Why is Convex written in Rust? 23:35 Cheap abstractions 25:47 Productivity suffering from compile times 29:47 The different approaches for a backend developer to build scalable systems 32:28 Backend for Frontend 37:21 You want to be close to your data 42:13 Are there plans to support other languages at Convex? 47:06 Does the schema update the autocompletion in the editor 48:31 Naming and behavior of the queries with Convex 51:06 Why sqlc is great 52:28 Why TypeScript is a great "shortcut" for Convex 59:34 Where to find Thomas
Today we bring anothe returning guest, Adam Elmore! An AWS Hero, Teacher and fellow content creator! You might notice today's talk is a bit different, as we don't cover too much technical details but we do cover a lot of other interesting topics that permeate our everyday lives, such as kids and family time, religion and purpose in life... But don't worry, we also share some hot takes on indie hackers, business models of education platforms and finally content creation and how it can help you propel your career! Learn back-end development - Listen on your favorite podcast player: Adam's Twitter: Adam's Youtube: ProAWS: Timestamps: 00:00 Intro 01:42 Terminal Coffee 06:42 Kids' books 09:00 How serious is the Terminal Coffee business 12:51 Indie Hackers 19:11 Books 23:42 The March of Time 25:56 Commitment to the lessons 27:21 The problem with course platforms 28:31 ProAWS 35:45 The education industry isn't as cutthroat as it seems 39:13 What's Adams plan of attack with the courses? 40:00 How does streaming affect Adam? 44:05 Who is Adam's audience? 44:44 Podcasting 47:34 Who is TomorrowFM targeted at? 49:14 Burnout in podcasts 52:01 Growing up religious 57:34 Would you say that you've distanced yourself from religion for epistemological or cultural reasons? 01:03:00 Throwing the religious labels out 01:13:03 Where to find Adam
In today's episode, we bring back James Q Quick. Last time we talked about his best tips to land your first ever job as a developer. Today we talk about James' new startup and how he manages all his new tech adventures with being a parent and also provides some helpful insight as to why having an audience and personal connections in the industry is beneficial - but not strictly necessary to succeed. We also talk about AWS, abstraction and the current (healing) state of layoffs, so don't lose hope if you're demotivated in your job search. Learn back-end development - Listen on your favorite podcast player: Deals for Devs: James' Website: James' Twitter: James' Youtube: Timestamps: 00:00 Intro 00:55 On being a parent 04:28 Idiocracy 05:47 Deals for Devs 10:09 Comparison with Dixie Direct 12:22 How do you quantify the really high quality deals 15:57 The challenge with a two-sided marketplace 22:28 Doing stuff manually is actually pretty good 25:38 Having a personal connection helps A LOT 29:12 Zeta 34:05 The Web is being modeled on AWS 36:38 You shouldn't be learning one JavaScript framework 38:30 Know how to answer a question if you don't know the technology 41:43 When you learn to code, how much layers of abstraction you should go? 43:45 Should passion be required for a job in tech? 49:02 The state of layoffs 52:29 The ease of finding a job after a layoff when you're highly talented 55:58 Do you need an audience to find a job easily? 58:40 Developers of the world - Interviews in person 01:02:12 Where to find James
In today's episode, we bring back BadCop! Since last episode, she joined's team and is now writing courses with us! Today we will be discussing the approaches to writing good educational material, Bash (of course, duh), working outside cloud solutions, SSH, NAS systems, workflows with different editors and cultural shifts in different areas of programming. Enjoy! Learn back-end development - Listen on your favorite podcast player: BadCop's Twitter: BadCop's Twitch: Timestamps: 00:00 Intro 00:58 BadCop Joined the Team! 01:15 Writing courses is harder than it looks 03:45 Lane's approach to writing courses 05:21 What's the hardest part of writing a course for BadCop? 09:01 On writing Bash 13:19 How useful is it to know how to work outside the cloud solutions? 17:28 SSHing into the home network 20:49 What is a NAS? 23:26 Using VTuber Software off the shelf 25:55 When did BadCop start using NeoVim? 29:41 IRC talk 33:20 Cultural shift in the programming space 38:05 Getter and Setter functions 42:35 People are overusing the idea of encapsulation 48:41 Dependency Inversion Principle 51:11 The VTuber Project 52:58 Where to find BadCop
In today's episode, we welcome Ken Wheeler, a dope programmer, who creates cool projects and just gives them away for free, helping thousands of developers worldwide, a based beatmaker and just in general a cool person. In this episode, we talk about AI, React, OCaml, why stressing over specific frameworks is not worth it, advice for new developers, HTMX, SPA's and a LOT of other stuff, so stay tuned! Ken's X/Twitter: Timestamps: 00:00 Introduction 00:25 Do you hate AI? 02:10 How diffusion works 17:47 First impressions with writing Go 18:29 Where's the line between Backend Development and DevOps 24:11 Does anyone version their REST? 24:57 urql 25:38 Offloading the data work to the other side 29:55 Wordpress is 80% of the websites 31:15 HTMX 33:12 Single Page Apps 34:02 Is React still your go-to 36:38 Is it hard to switch from React to Vue? 39:37 Picking a first language to learn 40:43 OCaml 43:12 HEX and raw Binary Data 44:42 Bluetooth powered crossbow 52:20 What got Ken into doing talks 58:45 Where to find Ken
In today's episode, we welcome Casey Muratori, a seasoned programmer who specializes in game engine research and development who is currently working on a narrative game about organized crime in the 1930s in New York. And oh boy, is this episode packed with valuable knowledge! In this talk, we go over the differences between different job positions in the Game Development Industry and how it compares to the Web Development arena, as well as dive deep on the notions of technical knowledge, is it all useful or is some of it just a waste of time? We talk about bloated systems, how we already surpassed the tipping point of code written, so that new exploits will be appearing indefinitely. Casey gives us his opinions on what a programmer should ABSOLUTELY know to be the best at what they do, and a lot of other exciting and interesting topics. Learn back-end development - Listen on your favorite podcast player: Computer, Enhance!: Casey's Twitter/X: Timestamps: 00:28 Casey's Background 02:43 Game Developer vs Game Designer 09:08 What are the different ways people should think about careers that exist for game developers 14:33 Is all knowledge useful or is some of it a waste of time? 16:16 Computer, Enhance! and Casey's teaching methodologies 24:00 Devil's advocate about understanding at the hardware level 29:48 Software is getting slower, bloatier and less performant 35:42 What is the primary reason behind the rise of slow software 38:20 Top 3 concepts that people SHOULD know 43:43 Do you need to know both ARM and x86? 57:03 30 million line problem 01:08:29 Is there any way to mitigate these types of problems? 01:13:39 Where to find Casey 01:14:50 Which was the best part of Twin Peaks
In today’s episode, we bring AnthonyGG, a highly requested guest, a Go developer with over a decade of experience with Golang and a fellow content creator. This episode will be all around Web Development with Go - from how Anthony started writing code with Go and why he chose this language, to tooling, migrations, integrations with databases, generics, Go job interviews and much, much more! Learn back-end development - Listen on your favorite podcast player: Anthony's Youtube: Anthony's Twitch: Anthony's Twitter/X: Timestamps: 00:00 Introduction 00:29 Anthony's backstory, how he learned to code and started writing code professionally 08:55 Going from go migrate to goose 13:20 What does Anthony use in tandem with goose/go migrate to interact with databases 14:46 Bun vs gorm vs sqlc 18:26 The way is running goose at the moment 20:14 Problems with migration tools 23:47 Should HTTP handlers explicitly return an error? 29:05 Building your own middleware and helper functions 36:00 Generics 38:09 How often does AnthonyGG use a context package and for what purposes 44:57 Golang job interviews 46:12 Developer experience with working with Go on Web Applications 54:51 You still need community-built tools 57:08 Where to find Anthony
Today, we bring back a dear guest and friend of the podcast, ThePrimeagen! Now Ex-Netflix engineer who turned his full focus to content creation surrounding software engineering and tech. In today's episode, we talk about his new Git course on, where he shares motivations on why he decided to write a course on Git, how he incorporates it into his workflow and shares some hot takes regarding today's tech education landscape, his opinion on bootcamps, colleges, and what his ideal way of teaching computer science is. To finish off, he shares some of his exciting new ventures, namely a coffee shop and a Doom game which you can play through twitch chat! Learn back-end development - Listen on your favorite podcast player: ThePrimeagen's Youtube: ThePrimeagen's other Youtube: ThePrimeagen's Twitter: Terminal Coffee Shop: Timestamps: 00:00 Introduction 00:27 Why teach about Git? 02:55 Was Prime taught Git? 04:50 add files individually or git add . 07:22 Hot take about git in school 10:27 What should you learn in school in the first place? 11:34 Where did school come from? 16:42 You can't become a software engineer in 3 months 19:45 Contents of Part 1 and what will Part 2 of the Git course be about 22:58 Rebase vs Merge and Prime's current workflow 24:22 Why you shouldn't merge 29:10 A lot of the times, people just don't know the tools 32:29 The advantage of rebase 34:03 Rewriting history criticism 36:30 Prime's terminal coffee shop 44:22 Doom in the terminal? 54:08 Is the bandwidth the problem with the Doom game? 55:27 Ideas for the controls for Doom 58:57 Where to find Prime
In today's episode, we welcome Low Level Learning, a fellow programmer and content creator. With over 500k subscribers and his own course where he teaches low level programming topics, he came on the podcast to talk about what he knows most: C, low level concepts, AI, as well as share some of his own developer experiences and preferences that he garnered over the years. Learn back-end development - Listen on your favorite podcast player: Low Level Learning’s Twitter/X: Low Level Learning's Youtube: Low Level Learning's Twitch: Low Level Academy: Timestmaps: 00:47 Who is Low Level Learning? 01:34 C is a High Level Language 02:47 Is C lower level than Rust or Zig? 04:33 Front-end vs Back-end, which is harder? 06:34 The stack 07:11 The Low Level Academy stack 07:59 Low Level Academy 09:56 Project-based learning 12:18 sqlc 14:44 How do you debug C? 17:26 Fuzzing Harness vs Unit Testing 22:28 Favorite Feature of C 23:45 If you could change one thing in C, what would it be? 26:53 Where do C programmers work? 29:16 The White House and Garbage Collectors 31:19 What is a side-channel attack? 33:56 Power side-channel attack 35:41 Side-channel attack on 37:08 What tooling does Low Level Learning use to write C? 43:59 How do you deal with the lack of a package manager? 48:12 Opinion on statically compiled and dynamic libraries 50:36 Where to find Low Level Learning
In today’s episode, we welcome Natalie Pistunovich, host of the Go Time podcast, OpenAI Ambassador and Google Developer Expert for Go. She advises companies on how to make the most of AI and adopt it properly and also teaches the Cloud and Infrastructure course for B.Sc. students at the HTW Berlin. In this episode, we talk all about AI driven development and how is Go one of the best languages suited for code generation, the future of LLM’s and how can we boost the average developer’s job with AI, creating custom GPT’s, changes in the area of AI Chips, and a lot of other fascinating topics. Learn back-end development - Listen on your favorite podcast player: Natalie's Twitter/X: Timestamps: 00:47 Who is Low Level Learning? 01:34 C is a High Level Language 02:47 Is C lower level than Rust or Zig? 04:33 Front-end vs Back-end, which is harder? 06:34 The stack 07:11 The Low Level Academy stack 07:59 Low Level Academy 09:56 Project-based learning 12:18 sqlc 14:44 How do you debug C? 17:26 Fuzzing Harness vs Unit Testing 22:28 Favorite Feature of C 23:45 If you could change one thing in C, what would it be? 26:53 Where do C programmers work? 29:16 The White House and Garbage Collectors 31:19 What is a side-channel attack? 33:56 Power side-channel attack 35:41 Side-channel attack on 37:08 What tooling does Low Level Learning use to write C? 43:59 How do you deal with the lack of a package manager? 48:12 Opinion on statically compiled and dynamic libraries 50:36 Where to find Low Level Learning
In today’s episode, we bring fellow developer and tech content creator NeetCode, to talk about his obstacles and observations on his path in becoming a FAANG engineer, where he shares his struggles and how he started both his tech career and content creation journeys. Among a variety of other topics, NeetCode shares his advice for anyone that’s open to receiving it, and explains the pros and cons of grinding LeetCode, if it is even worth doing it or not, while also dabbling into why networking is somewhat important and highlights the importance of standing out in today’s job market environment. Learn back-end development - Listen on your favorite podcast player: Neetcode's Website: Neetcode's Youtube: Neetcode's Twitter: Neetcode's LinkedIn: Timestamps: 00:46 Who is NeetCode and a bit of his background02:24 Why did NeetCode start a YouTube Channel?03:40 People don't talk about where they mess up at these big companies04:47 Portray yourself in the best possible light at interviews07:37 Why LeetCode?08:44 Why Grinding LeetCode is not the smartest choice11:31 Why LeetCode is still important if your goal is a FAANG-level company14:47 What would be the approach for someone with CS-degree knowledge that wants to get into Google in 2024/202517:26 How to know if you're having trouble getting or passing interviews?19:01 You can put projects on a resume, not LeetCode solutions21:47 Tutorial Hell24:47 You have to be able to prove your knowledge, just putting it on the resume isn't enough29:20 You don't have to do content creation to get a developer job30:29 Social Media works well for networking33:03 NeetCode philosophy37:57 Monetizing education content42:17 How to level up the product experience44:04 Amazon vs Google's culture46:24 As usual, managers don't know what they're doing a lot of the time49:30 Managers at these companies should be technical51:17 Difference between Engineers and other Tech Roles55:40 Where to find NeetCode
In today’s episode, we welcome John Crickett, veteran software engineer, having worked at Staff, VP, and C-Suite positions over the years, and now focusing on helping thousands of engineers worldwide, through his coding challenges that have you building real applications, as well as helping with the soft skills through his articles and posts about software development. Today we cover a LOT of ground where we explain exactly what a Software Architect is, discuss different leadership types, advice to get a software job, remote work, unpopular opinions on programming languages, performance and scale, and a couple other things, so stay tuned because this episode is a true fountain of knowledge. Learn back-end development - Listen on your favorite podcast player: John Crickett's Twitter/X: John Crickett's Linkedin: Coding Challenges: Coding Challenges on Substack: Research mentioned at 27:33 : More on the topic of Deindividuation: Timestamps: 00:12 Who is John Crickett01:13 What is a Software Architect03:04 People vs Technical Leadership03:53 What kind of decisions does a software architect make?04:43 Is there a lot of "Thought Leadership" involved?05:23 Do you prefer Technical or People leadership?07:47 How did John start his coding career?11:39 Most people don't start working at "sexy" companies13:58 Juggling off-topic14:32 What are the Coding Challenges?19:03 Remote work and downtime22:56 The wrong culture might spoil the remote environment and people care less about the work27:05 Anonymity turns people into assholes29:58 Why did we have a phone call when this could've been an e-mail?33:42 Doing LeetCode vs Building Projects36:54 Most of the time you'll be using already existing solutions40:05 Is there too much abstraction nowadays?41:56 Using the Command Line is cool again!43:44 When talking about scale, what matters most is the architecture, not the language or framework51:30 Why just switching to a "faster" language isn't enough53:48 Go vs Rust performance comparison54:44 Learning how to write performant code is more important than the programming language itself55:25 The importance of benchmarking58:33 Where to find John
In today’s episode, we bring Leandro Ostera, a seasoned software engineer, who’s currently leading the OCaml build system team, with the mission of making OCaml SaaS ready! Join us as this episode is packed with a variety of topics, where we mainly focus on the OCaml ecosystem, compare it to other languages and frameworks, but also dabble into very obscure topics such as Idris (hint: it’s a programming language), and explore concepts such as routine blocking, scheduling, types, and other issues. Learn back-end development - Listen on your favorite podcast player: Check out Riot: Leandro's Twitch: Leandro's Twitter/X: Timestamps: 00:28 Leandro's Background01:37 How Leandro got involved with OCaml02:50 What the heck is Idris???07:03 When Leandro started working with OCaml11:34 ReasonML15:48 The Riot Library and OCaml issues18:00 Type Inference in OCaml23:10 What allowed Riot to move so fast24:17 The ecosystem of a language28:14 Is Riot a Concurrency Library or a Web Framework?31:01 Goroutines refresher33:02 How Riot implements the actor-model38:34 Cooperative Scheduling vs Preemptive Scheduling41:30 How to fix routine blocking43:14 What has Leandro and other contributers shipped?46:25 How does Leandro manage his time to work on all of these projects?49:45 Where to find Leandro
Today, we're excited to have Bashbunni join us, a software developer and fellow tech content creator currently rocking it as a DevRel at Charm, whose purpose is all about glamming up the CLI experience. In this episode, we cover a lot of ground, from diving into Charm's cool libraries and their real-world applications to chatting about the self-taught programming journey. We also touch on TikTok and addictive social media use, content creation and its intricacies, and share some insights into the world of Golang. Learn back-end development - Listen on your favorite podcast player: Bashbunni's Twitter: Bashbunni's Twitch: Bashbunni's Youtube: Charm: Charm's video that Bashbunni mentioned: Timestamps: 00:36 When did Bashbunni start working with Go? 02:10 School during COVID and education nowadays 04:23 Is self-taught still a viable way to learn programming? 08:50 Discipline can be learned 10:04 Why it is much harder to focus nowadays? 11:08 TikTok and Addictive Social Media Use 14:31 What kind of media does BashBunni consume, if not short-form content 18:14 Is creating content for Charm a bit part of the job? 21:05 On Tech content creators being technical 24:41 Quality vs Quantity 25:31 What is Charm? 29:09 Why Golang is the best language for CLI Applications 32:52 US vs Canadian Accents 34:05 Melt - One of Charm's Libraries 36:24 Soft serve - Self hostable git server 37:39 VHS - Terminal GIFs as code 39:10 How many people are behind Charm? 39:17 How does Charm make money? 42:40 GUI's are bloated, Terminal is the GOAT 45:56 Bashbunni's beef with JavaScript 48:47 Where to find Bashbunni
In this episode, we host Trash Puppy, with her amazing story of how she went from Nursing to becoming a Software Engineer. Today, we talk about her story, why she chose Golang, her exciting personal projects and her experiences and advice as a self-taught developer. As Trash Puppy is accepting job offers at the moment, we also dove into the current job market and job hunting process, as it definitely isn't an easy one to navigate these days, while also touching up on her thoughts of the threats of AI. Learn back-end development - Listen on your favorite podcast player: Trash Puppy's Twitter: Trash Puppy's Youtube: Trash Puppy's Twitch: Trash Puppy's Github: Trash Puppy's LinkedIn: Timestamps: 00:31 How Trash Puppy went from a Nurse to a Software Engineer 05:06 Lane shares how his wife went from an X-Ray technician to Software Dev 07:00 When did Trash Puppy start learning to code? 08:24 Trash Puppy pivoted to Golang? 09:29 Was there anything else about the industry that motivated Trash Puppy to switch to WebDev? 10:38 NetPuppy 13:12 Coding in Cyber Security 18:10 Do you want to hire Trash Puppy? 18:27 Current Job Market and Job Hunting 22:51 You have a better chance applying to local jobs 25:25 Lack of experience in the field when searching for a job 29:26 Outlook on AI 30:15 Impact of not having a CS Degree 33:11 Building projects or studying up on foundations? 37:19 The learning happens during the struggle 41:47 What has been the hardest thing about learning Go so far? 45:27 What do you like the most about Go? 47:03 What's your least favorite part about Go? 48:20 Installing Go modules vs GOPATH 50:31 Where to find Trash Puppy
Today, we're thrilled to have Tommy Graves, co-founder of RWX, a company focusing on building tools that optimize build and test performance, reliability, and developer experience. In this episode, we're delving deep into the realm of CI/CD (Continuous Integration and Continuous Deployment), with a special focus on Mint - their latest CI platform. We'll be exploring its unique features, how it differs from its competitors, caching, security, cost-efficiency in production pipelines. Apart from that, we'll also discuss GitHub Actions along with it's biggest flaws and finally demystifying CI/CD, as it is not the big monster a lot of developers perceive it to be. Learn back-end development - Listen on your favorite podcast player: Mint: Timestamps: 00:54 Who is Tommy Graves 05:14 What is Continuous Integration? 06:57 What is Mint trying to solve, that isn't solved by other CI/CD platforms 09:57 Better Semantic Output on a CI/CD platform 14:20 What's the benefit to the structure of semantic logging, apart from visualization 15:23 CI/CD course on 17:59 Does Mint make it cheaper for companies that have high CI/CD expenses? 19:12 Why don't other companies do caching the way Mint does? 25:49 There are security implications of using the same platform for both CI and CD 30:42 How smaller teams could benefit from Mint 33:15 Verifying changes to the deployment workflow with GitHub Actions and Mint 36:49 Is GitHub Actions dominating the space or is there still competition? 39:04 One of the biggest frustrations with GitHub Actions 42:03 Does Mint relate to the Unix philosophy? 48:07 How does configuring the CI/CD tools drive the philosophy of Mint 50:36 Just understand CI/CD, you won't need those courses dedicated to CI/CD platforms 53:45 CI/CD is not as esoteric as it sounds 58:48 Where to find Mint
Today, we bring a special "Whiskey, Web and Whatnot" edition to our podcast, where we welcome Travis Wagner and Robbie The Wagner, to talk about controversial takes regarding tech CEOs, their experiences in the field, the impact of AI and other personal preferences towards technologies Learn back-end development - Listen on your favorite podcast player: Whiskey, Web and Whatnot podcast:'s Twitter:'s Twitch: Travis's Twitter: Timestamps: 01:22 Whiskey, Web and Whatnot 01:52 Elon Musk or Mark Zuckerberg, which Tech CEO of 2024 is your favorite? 03:28 Robbie's Background 04:42 Travis's background 06:23 Big company or small company? 10:07 Tenures, incentives and current market 12:33 Who would you pick for your team, Steve Ballmer or Sundar Pichai 13:41 AWS or GCP? 16:25 DevOps is not a real job 20:16 Be a DevRel or a Scrum Master? 23:38 What's the difference between DevRel and Dev Advocate? 24:56 AI or VR, which is more impactful on a developer's day-to-day? 31:53 Which Big Tech Company sucks the least? 36:21 Bigger Salary but Less Equity or Less Salary but More Equity? 41:19 Is Blockchain Gone Yet? 50:52 CS Degree or Being an Open Source Maintainer on a successful project? 55:10 Remote or On-site? 01:03:19 Where to find Robbie 01:03:43 Where to find Travis
In today's episode, we bring Thorsten Ball, author of "Writing An Interpreter In Go" and "Writing A Compiler In Go". In this talk, we discuss the different clashes and responsibilities between Product and Engineering teams, reignite the topic of working with technical managers, explain why cookie banners are dumb, and on a more interpersonal note, discuss how important coolness is in education, explain why a lot of the times, highly talented people just don't know how to work and also dabble into the ideas of fulfillment, responsibility and reliability.Thorsten's Twitter: Spill:'s Books: - The idea behind Register Spill (02:20) - It's a Negotiation: When Product and Engineering meet (05:58) - Engineering vs Product (07:31) - Thorsten's view of the Product team (09:36) - Thorsten's view of the Engineering team (11:06) - Engineers should inform product before building something (14:57) - Real-life example from Thorsten (18:04) - Measuring completixy in T-Shirt sizes and Time Estimates (22:46) - Set a cap on time dedicated to a task (23:50) - Do we need more technical leadership? (27:58) - Working with Engineering Managers that are technical is a bliss (35:19) - Not Every Company Is For Everybody (41:14) - Cookie Banners are Dumb (50:13) - Educators underestimate how important coolness is (56:19) - There are a lot of highly capable people that just don't know how to work (01:02:20) - Getting fulfillment just from the effort (01:04:23) - Be reliable (01:06:34) - Where to find Thorsten
In this episode, we bring Daniel Roe, the Lead Maintainer of Nuxt.js, an open source framework that makes web development intuitive and powerful. Today, he shares his journey into the framework and sheds some light on intriguing questions surrounding its development and usage. Today's talk ranges from the origins of Nuxt to its unique features and practical tips for developers, deliberate naming, comparison with Next.js and technical and detailed discussion regarding performance optimization and project structuring.Learn back-end development - https://boot.devListen on your favorite podcast player: https://www.backendbanter.fmDaniel's Twitter:'s Website: Framework: - How did Daniel Roe join Nuxt? (02:53) - Elk, Moose and Wilderness (06:07) - Was it named Nuxt intentionally to confuse people? (08:32) - Next.js vendor lock-in criticism and does Nuxt have any similar issues (11:31) - moved from a Vue 3 SPA to Nuxt (14:19) - Auto-importing by default? (20:01) - Using longer variable names because of global namespace (21:58) - Explaining the default Nuxt payload behavior (26:59) - Default prefetching (30:17) - What are the most common use cases for Nuxt apps (32:32) - Who has control in your project? (33:45) - Enabling JavaScript or not? (37:25) - Updating head tags in Nuxt (39:09) - New feature that improves script handling in Nuxt (41:01) - What do you prioritize? Interactivity or Scripts? (42:06) - Google Tag Manager (46:07) - What's Daniel's favorite Nuxt feature? (47:11) - Types are amazing! (49:37) - How did the Idea of came to be? (51:24) - Gamification of coding (53:46) - Theory is picked up from practice (56:05) - What's one thing you'd instantly change about Nuxt if you could (59:04) - Separation of what goes on in the client vs the server in the same file (01:04:44) - Where to find Daniel
Comments (2)

amir salmani


May 23rd

Paja Storec


Jan 16th