Podcasts about staff engineer

Grad za okiem, turniej piłkarski FIFA i prześcieradła maskujące logotypy na żądanie  – idealne tło na 68. odcinek Brew. Bez owijania w bawełnę i zdejmując marketingowe maski, rozliczamy najważniejsze wydarzenia tygodnia.Oto pigułka tego, co naprawdę myślimy o tematach odcinka:

Od ucieczki miliarderów i kosmicznych eksplozji, przez radykalne czystki w Dolinie Krzemowej, aż po... historyczne oświadczenia z Watykanu. W najnowszym, 67. odcinku Morning Coffee Brew nie ma miejsca na nudę! ☕Wojtek, Tomek i Sebastian wracają do Was z solidną dawką mocnych tematów. Rozkładamy na czynniki pierwsze szalony tydzień, który idealnie pokazuje, jak technologia bezpowrotnie zmienia biznes, społeczeństwo i geopolitykę.Oto szybki skrót tego, co tym razem bierzemy na warsztat:

Hoje o papo é sobre adoção de IA dentro de casa! Neste episódio, conversamos sobre como a Alura vem incorporando agentes de código, ferramentas como Codex e workflows agênticos no dia a dia da engenharia, e os impactos disso em produtividade, na revisão de código, na cultura de desenvolvimento e até na criação de produtos. Vem ver quem participou desse papo: Paulo Silveira, o host que quer saber se é top-down, ou bottom-up Vinny Neves, cohost, dev e professor na Alura Mauricio Aniche, CTO da Alura Crisley Marques, Engenheira de Software IA/LLM na Alura Carlos Müller, Staff Engineer na Alura Caio Burgorin, Engineering Manager na Alura Links: Alura: Luri OpenAI Codex Claude Code GitHub Copilot Datadog MCP Discourse Oracle Cloud Infrastructure (OCI) Stack Overflow IntelliJ IDEA No dia 26 de maio de 2026, a Alura vai te mostrar o que esperar do futuro e anunciar um novo movimento. Inscreva-se para uma live imperdível, com a presença de grandes especialistas do mercado. Confirme a sua presença. Vá para o Vale do Silício com Paulo Silveira, Marcell Almeida, Fabrício Carraro e Marcus Mendes na “Imersão IA Sob Controle e Alura no Vale do Silício“! Vagas limitadas, corra para reservar a sua. TechGuide.sh, um mapeamento das principais tecnologias demandadas pelo mercado para diferentes carreiras, com nossas sugestões e opiniões. #7DaysOfCode: Coloque em prática os seus conhecimentos de programação em desafios diários e gratuitos. Acesse https://7daysofcode.io/ Produção e conteúdo: Alura Cursos de Tecnologia – https://www.alura.com.br Edição e sonorização: Rede Gigahertz de Podcasts

If you're a software engineer right now, you likely feel like your world is changing overnight. We are writing half or less the amount of code that we wrote even a year ago, which represents a seismic, groundbreaking shift in our industry. For many of us, this career has always been engaging for deeply creative and intellectual reasons—and that excitement is still here. But our mental models of what it means to be a good engineer, and what it means to keep improving, have gone a little stale. In today's episode, I want to talk about a distinction that I believe will become the cornerstone mistake for seasoned engineers: confusing _practice_ with _adaptation_, and leaning on the wrong one at the worst possible moment. Two Surfaces Coming Into Contact: Picture your knowledge, skills, and toolset as one surface, and the actual state of the art as another. We've always known the surface area we could learn far exceeds what we can learn, which forces us to place bets on a learning strategy. What's changing is how fast that second surface is moving underneath us. Improvement by Practice vs. Improvement by Change: Practice is wielding what you've already adopted—smoothing out errors, building muscle memory, refining what you already know. Adaptation is fundamentally folding something new into your repertoire. Both are real forms of improvement, but they are not interchangeable. The Cornerstone Mistake for Senior Engineers: Later in your career, the time you spend adapting naturally goes down as you settle into practice. The biggest error I'm already watching engineers make is moving too quickly toward practice when the industry is loudly calling for adaptation instead. Inspect and Adapt—at the Right Altitude: Sprint retros were never really about getting marginally better at the thing you already do. The intent of "inspect and adapt" is to step up one level and examine the system. The trap is treating adaptation like a minor refinement—getting a little better at prompting—when it should mean asking whether you're thinking about prompting in the wrong way entirely. Question the Ratio, Not Just the Output: Real adaptation looks like asking whether you have the right mix of human and agent on a problem. Are you leaning on the agent for things you shouldn't, or failing to lean on it for the things you should? Have you genuinely thought about how sub-agents or an agent team are working the problem you're producing? A Spectrum, Not a Binary: On one end, you make micro-adjustments to your refinement process. On the other end of experimentation, you ask whether refinement—or even having engineers plan the work—is the right thing at all. The point isn't that practice is dead; it's that the industry is changing fast enough that the adaptive end of that spectrum deserves far more of your attention than it used to. Episode Homework: Take something you currently treat as a practice problem—"how do I refine tickets faster?"—and step up a level. Ask the adaptive version of the question instead: "Is refinement even the right thing anymore?"

Czy zautomatyzowane agenty AI są gotowe na zarządzanie krytyczną infrastrukturą? W dzisiejszym odcinku Tomek, Wojtek i Sebastian omawiają głośną katastrofę w PocketOS, bezwzględne kulisy procesu Elon Musk vs OpenAI, wielki powrót opłaty reprograficznej w Polsce oraz tajną operację Google, które wgrało model AI na dyski milionów użytkowników.W tym odcinku Brew™️ między innymi:

Czy era „miękkiej siły” i neutralnych technologii dobiegła końca? W dzisiejszym odcinku Tomek, Wojtek i Sebastian analizują brutalny manifest Palantira, kosmiczne deale Elona Muska oraz chińską ofensywę modelami DeepSeek, która ignoruje zachodnie restrykcje.W tym odcinku:

Czy nadeszła era, w której inteligencję można po prostu kupić na godziny? W dzisiejszym odcinku Tomek, Wojtek i Sebastian analizują, dlaczego największe firmy świata przestały walczyć o benchmarki, a zaczęły o realną przewagę w cyberbezpieczeństwie i adopcji wewnętrznej.W tym odcinku, między innymi:

Czy prywatność w sieci to już całkowita iluzja, a Twój mózg stał się kolejnym celem algorytmów reklamowych? W dzisiejszym odcinku Tomek, Wojtek i Sebastian analizują między innymi dane o polskim X (Twitterze), kontrowersyjne technologie Mety oraz radykalne zmiany w strukturach firm technologicznych.W tym odcinku:

Git nutzen wir jeden Tag. Aber Hand aufs Herz: Wie viel davon verstehen wir wirklich?Hinter commit, push und pull steckt kein bisschen Magie, sondern ein erstaunlich komplexes System aus Objekten, Referenzen, Protokollen und Designentscheidungen, die bis heute die Softwareentwicklung prägen. Und genau da wird es spannend. Denn Git ist 20 Jahre alt, aber alles andere als fertig entwickelt.In dieser Episode sprechen wir mit Patrick Steinhardt, Git Maintainer, Contributor zu libgit2 und Staff Engineer im Git Team bei GitLab. Gemeinsam tauchen wir tief in die Git Internals ein und klären, warum Git sich gegen Subversion durchgesetzt hat, was ein bare Repository auf der Server-Seite eigentlich macht, wie Clone, Fetch und Push wirklich funktionieren und warum große Repositories, Millionen Referenzen, Binärdateien und Git LFS bis heute echte Herausforderungen sind. Außerdem geht es um Reftables, Partial Clones, Large Object Promises, pluggable object databases, Git History, Interactive Rebase und die Frage, was Git 3.0 mit SHA-256, besserer Usability und moderner Architektur verändern könnte.Wenn du Git bisher vor allem als Werkzeug für deinen täglichen Workflow gesehen hast, bekommst du hier einen Blick unter die Haube, der vieles neu sortiert. Vielleicht hörst du diese Folge als Developer:in mit einem leichten Ich benutze Git seit Jahren Gefühl. Vielleicht gehst du raus mit dem Gedanken: Ich kenne bisher gerade mal die Oberfläche. So oder so, diese Episode ist Pflichtprogramm für alle, die Versionskontrolle, Entwickler-Workflows, Open Source und die Zukunft von Git besser verstehen wollen. Bonus: Danach wirkt selbst git rebase plötzlich fast freundlich.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Wiosna za oknem, ale w świecie technologii i finansów atmosfera gęstnieje. W dzisiejszym odcinku Tomek, Wojtek i Sebastian biorą na warsztat rewolucję w raportowaniu krypto, nowe rozdanie sprzętowe Apple oraz brutalną wizję Sama Altmana, według której za inteligencję będziemy płacić jak za prąd z gniazdka.W tym odcinku:

This was an incredible podcast with Hadla Bergman who spoke at the very first Node:Holm event back in September! Was great to catch up with Hadla as she maybe making an appearance as a DJ at the next event so keep an on the next announcements!We discussed the fundamental changes in software engineering entering the AI era.  What parts of the role are becoming more important as AI takes over more of the code generation itself? How do you stay relevant as developer?With Hadla's amazing rise with Einride it was insighful to hear her opinion on the next generation of AI-assisted development tools. Also how effective collaboration looks like between humans and AI in the development landscape.Community QuestionsDen Odell, Staff Engineer at CanvaDoes Hadla see a future where engineers spend all their time reviewing, testing, and measuring AI-generated code rather than writing any of it themselves? And if so, what skills become most valuable: deep systems knowledge, performance intuition, or something else entirely?Steve Sutherland, Senior Product Marketing Manager at Brite PaymentsWhat are the top 3 traits and/or habits you'd recommend aspiring or early-stage software engineers to develop?Hanyue Zhou, Senior Engineer at Ubiquiti“Will open-source ecosystems thrive or weaken when much code is created by proprietary AI models?”

Czy "wyczucie smaku" to nowa najważniejsza kompetencja techniczna? W dzisiejszym odcinku Tomek, Wojtek i Sebastian analizują przełomowe publikacje naukowe, kontrowersyjne tezy liderów branży oraz dane ze Spotify, które sugerują, że inżynieria oprogramowania właśnie przeszła punkt bez powrotu.W tym odcinku:

Narty się skończyły, pora wrócić do rzeczywistości, która w świecie technologii pędzi szybciej niż kiedykolwiek. W dzisiejszym odcinku Tomek, Wojtek i Sebastian analizują miesiąc pełen "wow momentów", kontrowersji wokół autonomicznych agentów i fundamentalnych zmian w procesie tworzenia oprogramowania.W tym odcinku:

Rahul Raja is a Staff Software Engineer at LinkedIn, working on large-scale search infrastructure, information retrieval systems, and integrating AI/ML to improve ranking and semantic search experiences.The Future of Information Retrieval: From Dense Vectors to Cognitive Search // MLOps Podcast #362 with Rahul Raja, Staff Software Engineer at LinkedInJoin the Community: https://go.mlops.community/YTJoinInGet the newsletter: https://go.mlops.community/YTNewsletterMLOps GPU Guide: https://go.mlops.community/gpuguide// AbstractInformation Retrieval is evolving from keyword matching to intelligent, vector-based understanding. In this talk, Rahul Raja explores how dense retrieval, vector databases, and hybrid search systems are redefining how modern AI retrieves, ranks, and reasons over information. He discusses how retrieval now powers large language models through Retrieval-Augmented Generation (RAG) and the new MLOps challenges that arise, embedding drift, continuous evaluation, and large-scale vector maintenance.Looking ahead, the session envisions a future of Cognitive Search, where retrieval systems move beyond recall to genuine reasoning, contextual understanding, and multimodal awareness. Listeners will gain insight into how the next generation of retrieval will bridge semantics, scalability, and intelligence, powering everything from search and recommendations to generative AI.// BioRahul is a Staff Engineer at LinkedIn, where he focuses on search and deployment systems at scale. Rahul is a graduate from Carnegie Mellon University and has a strong background in building reliable, high-performance infrastructure. He has led many initiatives to improve search relevance and streamline ML deployment workflows.// Related LinksWebsite: https://www.linkedin.com/Coding Agents Conference: https://luma.com/codingagents~~~~~~~~ ✌️Connect With Us ✌️ ~~~~~~~Catch all episodes, blogs, newsletters, and more: https://go.mlops.community/TYExploreJoin our Slack community [https://go.mlops.community/slack]Follow us on X/Twitter [@mlopscommunity](https://x.com/mlopscommunity) or [LinkedIn](https://go.mlops.community/linkedin)] Sign up for the next meetup: [https://go.mlops.community/register]MLOps Swag/Merch: [https://shop.mlops.community/]Connect with Demetrios on LinkedIn: /dpbrinkmConnect with Rahul on LinkedIn: /rahulraja963/Timestamps:[00:00] Vector Search for Media[00:33] RAG and Search Evolution[04:45] Cognitive vs Semantic Search[08:26] High Value Search Signals[16:43] Scaling with Embeddings[22:37] BM25 Benchmark Bias[29:00] Video Search Use Cases[31:21] Context and Search Tradeoff[35:04] Personal Memory Augmentation[39:03] Future of Cognitive Search[44:51] Access Control in Vectors[49:14] Search Ranking Challenge[54:43] Hard Search Problems Solved[58:29] Freshness vs Cost[1:02:12] Wrap up

Tomek wciąż na nartach ⛷️, ale Wojtek i Sebastian nie zwalniają tempa! Styczeń 2026 dowozi newsy z taką prędkością, że można poczuć zmęczenie samym ich śledzeniem

The software engineering landscape is shifting rapidly. Coding is becoming "cheap" because of tools like Claude Code, Codex, Gemini, Cursor etc. Interviews are evolving to focus on system design over syntax. In this Q&A, I break down exactly which skills matter now, how to negotiate the salary you deserve, and how to deal with difficult personalities on your team.In this episode:How juniors can leverage AI tools to reach senior-level outputReal-world salary negotiation tactics from my experienceWhy coding skills matter less in modern interviews (and what matters more)Handling "brilliant jerks" and toxic team cultureWhether you are looking for your first job with no experience or you are a mid-level dev trying to break into a Staff Engineer role, this session is packed with actionable career advice.Timestamps: 00:00:00 - Intro 00:01:06 - Handling Brilliant Jerks: Toxic Culture vs. High Performance 00:04:13 - How Juniors Can Use AI to Outperform Seniors 00:07:10 - The Future of Coding Interviews: System Design and AI 00:11:20 - The Real Difference Between Good and Great Developers 00:13:00 - One Mistake Mid-Level Developers Make That Stalls Growth 00:15:58 - Salary Negotiation Tactics: How I Got Two Raises in One Year 00:23:44 - Questions You Should Ask to Crush Your Tech Interview 00:27:42 - What Actually Moves the Needle: Side Projects vs. Experience 00:31:05 - Don't Wait for a Perfect Portfolio to Start Applying 00:32:25 - Finding Jobs: Why LinkedIn and Meetups Beat Job Boards 00:35:16 - Should Frontend Developers Worry About Learning Backend Skills? 00:37:39 - Do Tech Certifications Actually Help You Get Hired? 00:39:07 - Mastering Soft Skills: Training Budgets vs. Real Experience#softwareengineering #careeradvice #techinterviews

Nowy Rok 2026 zaczynamy od mocnych uderzeń!

Tomek wrócił z nart, a w świecie tech... lawina newsów! ⛷️ Wojtek, Tomek i Sebastian biorą na warsztat tydzień pełen miliardowych transakcji, nowych unicornów i agentów, którzy sami naprawiają kod.O czym rozmawiamy?

Are you just executing tickets, or are you driving business impact?In this episode, Praveen Murugesan (VP of Engineering at Samsara) breaks down why the best engineers don't just write code and why "coding skills" alone won't get you there.He explains the critical shift from "software engineer" to "product engineer," why you shouldn't wait for permission to solve problems, and how to de-risk high-stakes projects like a true owner.In this episode, we cover:The difference between a "Ticket Taker" and a Product Engineer Why Product Managers should NOT be doing project management How to grow to Staff Engineer without managing a large team The exact interview questions to ask to test a company's culture A real story of an engineer telling a VP: "That's not an important problem"Connect with Praveen Murugesan:https://www.linkedin.com/in/praveenmurugesanTimestamps: 00:00:00 - Intro 00:01:55 - Product Engineer vs. Software Engineer: What's the Difference? 00:06:20 - Why Product Managers Should Not Do Project Management 00:11:06 - The Danger of "Flying Blind" Without Business Context 00:15:24 - Why Curiosity Is the Ultimate Leverage in the AI Era 00:25:06 - Why the Best Ideas Must Win Regardless of Hierarchy 00:27:43 - The #1 Interview Question to Test for Engineering Ownership 00:32:12 - How to Test a Company's Culture Before You Join 00:36:04 - Why You Don't Need to Be Senior to Be a Product Engineer 00:40:46 - Managing High-Stakes Projects and De-risking Failure 00:43:56 - What I Learned From Breaking Production at Salesforce 00:48:29 - The Myth About Staff Engineering and Managing Teams 00:51:59 - The Engineer Who Told the VP: "That's Not an Important Problem"#SoftwareEngineering #StaffEngineer #CareerGrowth

What if your data platform could serve AI-native workloads while scaling reliably across your entire organization? In this episode, Benjamin sits down with Ritesh, Staff Engineer at Lyft, to explore how to build a unified data stack with Spark, Trino, and ClickHouse, why AI is reshaping infrastructure decisions, and the strategies powering one of the industry's most sophisticated data platforms. Whether you're architecting data systems at scale or integrating AI into your analytics workflow, this conversation delivers actionable insights into reliability, modernization, and the future of data engineering. Tune in to discover how Lyft is balancing open-source investments with cutting-edge AI capabilities to unlock better insights from data.

Od politycznych starć na linii Musk-UE, przez twarde lekcje biznesu z polskiego podwórka, aż po miliardowe przejęcia. Wojtek, Tomek i Sebastian biorą na warsztat okres pełen skrajnych emocji w świecie tech!

In this special episode of Book Overflow, Carter and Nathan are joined by Will Larson, author of Staff Engineer!The first ten listeners to tag Book Overflow on LinkedIn and share a link to this interview will receive a free copy of Will's new book, Crafting Engineering Strategy!-- Want to talk with Carter or Nathan? Book a coaching session! ------------------------------------------------------------Carterhttps://www.joinleland.com/coach/carter-m-1Nathanhttps://www.joinleland.com/coach/nathan-t-2or work with Nathan through his consulting practice, rojoroboto. Book Overflow Listeners get 10% off their first engagement https://rojoroboto.com/bookoverflow-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Staff Engineer by Will Larsonhttps://amzn.to/4p67dOUn (Paid Link)----------------00:00 Intro01:44 Interview with Will Larson05:00 Anti-patterns - Snacking, Pining, and Chasing Ghosts18:42 Navigating Senior Roles and Finding Sponsors36:26 Developing Intuition and Running Migrations48:47 Writing Staff Engineer - Stories and Archetypes58:45 Book Recommendations and Closing----------------Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Weekly Reflections Newsletter: https://rojoroboto.com/newsletter----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

Miał być krótki odcinek, a wyszło... jak zwykle!

Nowy odcinek CTO Morning Brew właśnie wylądował! Wojtek, Tomek i Sebastian  zapraszają na gorący przegląd najciekawszych tematów z pogranicza technologii, biznesu i... geopolityki. Tym razem dyskusja sięga od chińskiej cenzury po polski rynek VC i najnowsze narzędzia AI.Oto, co między innymi czeka na Was w tym odcinku:

Mówią, że presja i stres to standard w naszej branży, ale czy tak jest naprawdę? Czy i jaki poziom presji jest pożądany, z czego to wynika, a kiedy już jest za dużo? Porozmawiajmy o presji, jej roli i zarządzaniu w branży:

In this episode of De Nederlandse Kubernetes Podcast, we talk with Jim Bugwadia, founder and CEO of Nirmata, and Shuting Zhao, Staff Engineer and one of the maintainers of Kyverno — the CNCF project for Kubernetes policy management.Jim and Shuting share how Kyverno was born from Nirmata's commercial work and has since become one of the most widely adopted open source projects in Kubernetes governance, with over 3.4 billion image pulls.We explore the real question: Why does Kubernetes need policies if it's already declarative? Jim explains how policy as code helps developers, operators, and security teams collaborate on cluster configuration at scale — from pod security to resource quotas, network policies, and automation.Shuting dives deeper into how Kyverno enables granular control, policy exceptions, and flexible enforcement modes — from audit to enforce. They discuss how large organizations use policy automation to improve compliance, security, and even cost efficiency, citing use cases like Adidas saving 50% in dev/test environments using policy-driven resource management.We also touch on:

Zastanawialiście się kiedyś, skąd się biorą "seniorzy"? Czy każdy "wymiatacz" był kiedyś "żółtodziobem"?  A co jeżeli tych zabraknie, znaczy tych "juniorów"? Kto będzie wtedy robił kawę ☕ tym na panteonie?  To trochę żarty, ale porozmawiajmy poważnie. AI i oczekiwania dookoła niego, zmieniły oczekiwania co do "juniorów" ...⏫ czy i kto zatrudnia dziś junior developerów?⏫ główne czynniki, które doprowadziły do bieżącej sytuacji i ich "trwałość"⏫ czy Gen AI jest sprzymierzeńcem juniora?⏫ czy ta branża to ciągle perspektywiczny kierunek dla młodych ludzi?⏫ nie dajmy się zwariować - jaką, jako STL odpowiedzialny za budowę zespołu, przyjąć strategię w tej sytuacji?⏫ jakie widzicie DŁUGOFALOWE skutki zaistniałej sytuacji (w skali mikro- i makro-)?Zatrudniasz, szkolisz, opiekujesz się juniorami? Wpadnij, posłuchaj jak widzimy to my i nasi słuchacze. Jesteś juniorem? Aspirujesz? Uczysz się? Zajrzyj i zderz z nami swój punkt widzenia na to co się dzieje dookoła. Sesja obyła się Live i jest dostępna w formie video na YT:  Coffee #75 - Luka pokoleniowa ========================================================"Coffee" jest częścią projekty "CTO Morning Coffee". Najlepsze miejsce w polskim Internecie dla liderów w technologii

From pinpointing greenhouse gas (GHG) hot spots to modeling decarbonization scenarios, life cycle assessments (LCAs) can be a powerful tool for sustainability. However, a lack of standardized methodologies across the automotive industry makes progress difficult.   That's where the SAE J3341 Task Force comes in. It's a cross-industry initiative uniting automakers, government, and academia to establish a more flexible yet transparent framework on carbon footprint reporting methodologies for passenger vehicles through smarter LCAs.   To learn more, we sat down with Laurel Nelson, Chair of the SAE J3341 Task Force and Staff Engineer of Sustainability Science at Rivian Automotive. She discusses how the task force is implementing a “disclosure addendum” approach that encourages OEMs to clearly communicate their assumptions and data for more accurate and meaningful carbon reporting.   If you are interested in taking part in the SAE J3341 Task Force, please reach out to Laurel directly at laurelnelson@rivian.com  or Dante Rahdar at dante.rahdar@sae.org.   We'd love to hear from you. Share your comments, questions and ideas for future topics and guests to podcast@sae.org. Don't forget to take a moment to follow SAE Tomorrow Today — a podcast where we discuss emerging technology and trends in mobility with the leaders, innovators and strategists making it all happen—and give us a review on your preferred podcasting platform.  

Hoje o papo é sobre tradição e tecnologia! Neste episódio, mergulhamos em como o Banco do Brasil vem utilizando sua experiência de 200 anos para manter-se à frente na adoção das novas tecnologias que realmente contribuem para a vida dos seus clientes. Vem ver quem participou desse papo: André David, o host que dá bandeira para os hackers Paulo Silveira, CVO do grupo Alun e co-fundador da Alura Paula Moura, Principal Developer no Banco do Brasil Caio Soares, Staff Engineer no Banco do Brasil Igor Régis, Distinguished Engineer no Banco do Brasil

Thomas Dullien, (a.k.a. Halvar Flake) is a mathematician-turned-cybersecurity luminary and engineer. He co-founded zynamics, the reverse‑engineering tools company behind BinDiff, BinNavi, and VxClass, all of which had major impact on binary analysis and were later integrated into Google following its acquisition of zynamics in 2011. He subsequently served as a Staff Engineer at Google Project Zero, contributing to foundational research in software security and exploitability modeling. In recent years, he shifted focus to computational efficiency and cloud economics. Which brought Thomas to co‑founding optimyze.cloud, a company dedicated to reducing compute waste and improving cloud cost‑efficiency, driven by the end of Moore's Law and the economics of SaaS infrastructure. The company was acquired by Elastic in 2021.

In this episode of Book Overflow, Carter and Nathan discuss Staff Engineer by Will Larson! Join them as they discuss what it means to have staff-level impact, how being a staff engineer differs from being a senior engineer, and more!-- Want to talk with Carter or Nathan? Book a coaching session! ------------------------------------------------------------Carterhttps://www.joinleland.com/coach/carter-m-1Nathanhttps://www.joinleland.com/coach/nathan-t-2-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Staff Engineer by Will Larsonhttps://amzn.to/4p67dOU (Paid Link)---------- 00:00 Intro 01:08 About the Book and Author 03:34 Thoughts on Staff Engineer 09:29 Staff Engineer Archetypes and Organizational Dynamics 23:17 What Staff Engineers Actually Do 38:57 Soft Power and Cross-Team Impact 52:42 The Reality of Staff Engineering Work 1:03:16 Hot Takes - Silicon Valley and Career Paths 1:12:50 Final Thoughts----------------Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Functionally Imperative: www.functionallyimperative.com----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

In this episode of The Data Engineering Show, the bros speak with Paarth, a Staff Engineer at Uber, about his work on Genie - an innovative AI assistant that revolutionizes on-call support by combining RAG (Retrieval Augmented Generation) with agent-based automation to help engineers find solutions faster.

### 関連書籍等- 「Staff Engineer: Leadership beyond the management track」 - [https://amzn.to/3CGI7hd](https://t.co/2wTT0FyOgb) - 邦題「Staff Engineer - 管理職にならずに活躍しつづける最強のソフトウェアエンジニアへ!」- An Elegant Puzzle: Systems of Engineering Management https://amzn.to/4ly22Fv - **エレガントパズル　エンジニアのマネジメントという難問にあなたはどう立ち向かうのか** https://amzn.to/3YFcn8N - See also: The Staff Engineer's Path by [Tanya Reilly](https://www.linkedin.com/in/tanyareilly/)- Ryoichiの2021 読了メモ: https://x.com/ryo1kato/status/1425629458929643523### 関連エピソード- ep3. Thriving on the Technical Leadership Path- ep10. What distinguishes a great software engineer from a good one?- ep64. 技術チームのリーダーが優れた技術者であるべき理由感想をぜひハッシュタグ #todayILearnedFM #tilfm でつぶやいてください!Your co-hosts:- Tomoaki Imai, Noxx CTO https://twitter.com/tomoaki_imai- Ryoichi Kato, Software Engineer https://twitter.com/ryo1kato

In this special episode of Liquid Weekly, Karl and Taylor sit down with Brett, Staff Engineer at Shopify, to unveil an exciting new project: Storefront Web Components.This groundbreaking initiative aims to make Shopify integration accessible to anyone with basic HTML knowledge, allowing merchants to embed commerce functionality anywhere on the web.Episode Highlights:Introduction to Storefront Components and their visionDeep dive into component architecture and implementationHow to handle variants, cart functionality, and market-specific featuresDiscussion of development process at ShopifyComparison with existing solutions like Buy Button SDKFuture roadmap and potential use casesFind Brett OnlineTwitter(X): https://x.com/little_bretLinkedIn: https://www.linkedin.com/in/bretlittle/ Website: https://www.bretlittle.com/ Github: https://github.com/blittle Bluesky: https://bsky.app/profile/bretlittle.comInstagram: https://www.instagram.com/bret.little/ Timestamps:00:00 - Introduction05:30 - What are Storefront Components?15:45 - Technical Implementation Details30:20 - Component Demo45:10 - Development Process at Shopify52:30 - Future Plans57:00 - Picks of the WeekResources:Storefront Web Components: https://webcomponents.shopify.devPlayground: https://webcomponents.shopify.dev/playgroundShopify Editions Summer ‘25: https://www.shopify.com/editions/summer2025Blog post: https://www.shopify.com/news/summer-25-edition-devShopify Headless Documentation: https://shopify.dev/docs/storefronts/headless Web Components Documentation: https://developer.mozilla.org/en-US/docs/Web/API/Web_components Picks of the Week:Brett: Microsoft TypeScript Go Announcement & AI Assistant ArticleKarl: Ben McIntyre's SAS History BooksTaylor: Naked Nutrition Protein PowderSign Up for Liquid Weekly:Don't miss out on expert insights and tips—subscribe to Liquid Weekly for more content like this: https://liquidweekly.com/

As a leader that wants to optimize an organization you are bound to fail if you isolate social (culture and people) and technical (tools and process) changes. When we ask Lesley Cordero, Staff Engineer at The New York Times how to solve this dilemma she answers: "Platform Engineering, it can drive organizational sustainability by practicing sociotechnical principles that provide a community driven support system for application developers using our standardized shared platform architecture"Tune in to our latest episode and learn more about the importance of leadership to continuously keep up and balance the tension between "Developers" and "Operations", between "End User Experience" and "Developer Experience" and ultimately between "Culture and People and "Tools and Processes"Links we discussedLesley's LinkedIn: https://www.linkedin.com/in/lesleycordero/GOTO Conference Talk => https://www.youtube.com/watch?v=Jx-XrUONJ-o QCon 2025 Talk Details: https://qconlondon.com/presentation/apr2025/platform-engineering-practice-sociotechnical-excellence DevOpsCon 2024 Talk Details: https://devopscon.io/business-company-culture/platform-engineering-devops/

In this episode of Change Leader Insights, Jessica Crow speaks with Abhijit Patharkar, an entrepreneur and academic, about how artificial intelligence (AI)—a transformational change impacting businesses worldwide—impacts organizational culture and data governance. A serial entrepreneur and Columbia University alum, Abhijit grew up immersed in his family's retail business, giving him an intimate understanding of the industry's challenges. With an engineering background and a Staff Engineer role at VMware's Office of the CTO, he developed a deep love for solving complex problems using technology. Abhijit has set out to bridge the gap between traditional retail and cutting-edge AI-powered solutions. During the conversation, Jessica and Abhijit discussed data governance and AI to understand whether an organization is prepared to undergo the business transformation and changes associated with implementing AI. Abhijit explained that data governance is a critical factor for AI-readiness. In describing how to prepare from a governance perspective, ”Governance is based on three pillars. One is data quality, one is security, and the third is availability.” Highlights from the conversation include: ☑️ Understanding the importance of a unified data approach when leveraging AI for tools to be most useful for employees ☑️ The gap in data governance across organizations and how to address it to better prepare an organization for technological transformation ☑️ Practical steps for change management in AI adoption If you want to learn more about AI and organizational culture change, be sure to tune in and hear what Abhijit has to say!

Today's guest is AJ Stuyvenberg, a Staff Engineer at Datadog working on their Serverless observability project. He had a great article recently about how they rewrote their AWS Lambda extension in Rust. It's a really interesting look at a big, hard project, from thinking about when it's a good idea to do a rewrite to talking about their focus on performance and reliability above all else and what he thinks about the Rust ecosystem. Beyond that, AJ is just a learning machine, so I got his thoughts on all kinds of software development topics, from underrated AWS services and our favorite databases to the AWS Free Tier and the annoyances of a new AWS account. Finally, AJ dishes out some career advice for curious, ambitious developers.

Career progression in IT can feel a bit unclear at times. Start as a Helpdesk, get to be a CPE, what happens next? How does development actually work? What do most organizations do to tier their people? How do you move up as an individual contributor? We're talking with Graham Gilbert of Airbnb about what it's like to move up toward the rarified air of staff engineer and beyond. Hosts: Tom Bridge - @tbridge@theinternet.social Marcus Ransom - @marcusransom Guests: Graham Gilbert - LinkedIn Links: Eisenhower Matrix: https://asana.com/resources/eisenhower-matrix Sponsors: Kandji 1Password iMazing Smallstep Watchman Monitoring If you're interested in sponsoring the Mac Admins Podcast, please email podcast@macadmins.org for more information. Get the latest about the Mac Admins Podcast, follow us on Twitter! We're @MacAdmPodcast! The Mac Admins Podcast has launched a Patreon Campaign! Our named patrons this month include Weldon Dodd, Damien Barrett, Justin Holt, Chad Swarthout, William Smith, Stephen Weinstein, Seb Nash, Dan McLaughlin, Joe Sfarra, Nate Cinal, Jon Brown, Dan Barker, Tim Perfitt, Ashley MacKinlay, Tobias Linder Philippe Daoust, AJ Potrebka, Adam Burg, & Hamlin Krewson  

In this episode, Dave and Jamison answer these questions: A listener named Steven says, Long-time listener of the podcast here—it always brings me so much joy! Should I prioritize title over salary? I'm currently based in Europe, working as a Senior Engineer at a big company that pays really well. The problem is, there's almost no chance for promotion due to the economy and budget constraints. Plus, because of the organizational structure, I'm stuck solving small problems that don't have a big impact. It's frustrating—but again, the pay is great. Recently, I got an offer for a Staff Engineer position at another company. The catch is, the pay isn't as good (30%+ cut), and I'm not sure about their culture or structure yet. However, the title could potentially open more doors for me in the future. Should I take the offer, accept the pay cut, and hope it's a step forward for my career? Hello! Long time listener, first-time caller :-) I'm on the final stretch of classes to finish my BS in computer science at WGU, most of which I've done while working. I'm now 40, and I have had 3 previous occupations and employers: aircraft mechanic for 5 years at a small shop, figure skater with Disney on Ice for 6 years, and most recently a partner at an environmental remediation/heavy construction firm for 10 years where my primary responsibilities were field crew management and technical writing for ecology reports. I would love your advice on how I could use these experiences to stand out on a resume or in a job interview. How can I indicate that I'm a hard worker and that I know just enough to know that I know nothing and am ready to learn? Thank you for your time, keep up the good work!

Ready to take your tech career to the cloud and build those awe-inspiring systems you see? Then you're in the right place. This episode of AWS Bites is your blueprint for becoming a successful cloud architect. We're not just going to talk about it; we'll show you what worked for us, sharing the critical skills you need, and a practical path to build your expertise. Whether you're a beginner or looking to take the next step, join us as we equip you with the knowledge and tools to make your mark as a cloud architect! In this episode, we mentioned the following resources: Google Cloud Architecture Definition: https://cloud.google.com/learn/what-is-cloud-architecture Market data about the Cloud Professional Services market: https://www.gminsights.com/industry-analysis/cloud-professional-services-market EP 91 - Our Journeys into Software and AWS: https://awsbites.com/91-our-journeys-into-software-and-aws/ AWS Well-Architected Framework: https://aws.amazon.com/architecture/well-architected/ EP 68 - Are you well architected?: https://awsbites.com/68-are-you-well-architected/ Cloud Design Patterns: https://learn.microsoft.com/en-us/azure/architecture/patterns/ The art of scalability (book): https://www.amazon.com/Art-Scalability-Architecture-Organizations-Enterprise/dp/0134032802 Enterprise integration patterns (book): https://www.amazon.com/Enterprise-Integration-Patterns-Designing-Deploying/dp/0321200683/ Designing Data-Intensive Applications (book): https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321 AWS Networking Essentials (free guide): https://aws.amazon.com/getting-started/aws-networking-essentials/ Docker Curriculum (free): https://docker-curriculum.com/ How Linux works (book): https://www.amazon.com/How-Linux-Works-Brian-Ward/dp/1718500408/ Exercism coding challenges: https://exercism.org/ The tangled web (book): https://www.amazon.co.uk/Tangled-Web-Securing-Modern-Applications/dp/1593273886 Low Level YouTube Channel: https://www.youtube.com/lowlevellearning AWS - Best Practices for Security, Identity, & Compliance: https://aws.amazon.com/architecture/security-identity-compliance/ Supercommunicators (book): https://www.amazon.com/Supercommunicators-Unlock-Secret-Language-Connection/dp/0593862066/ An Elegant Puzzle (book): https://www.amazon.com/Elegant-Puzzle-Systems-Engineering-Management/dp/1732265186/ Staff Engineer (book): https://www.amazon.com/Staff-Engineer-Leadership-beyond-management/dp/1736417916/ EP 58 - What can kitties teach us about AWS: https://awsbites.com/58-what-can-kitties-teach-us-about-aws/ AWS User Groups: https://aws.amazon.com/developer/community/usergroups/ Do you have any AWS questions you would like us to address? Leave a comment here or connect with us on X/Twitter: - ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠

No episódio de hoje, exploramos o mundo da arquitetura de software e seu impacto nas finanças das empresas. Com a presença especial de um Staff Engineer experiente, vamos entender o que faz uma arquitetura ser eficiente e como decisões arquiteturais afetam diretamente os custos operacionais, desde a escolha de cloud providers até o uso de microservices. Além disso, falamos sobre FinOps e como essa prática pode ajudar a otimizar custos em ambientes de nuvem. Descubra as melhores estratégias para evitar armadilhas financeiras e como o futuro da arquitetura e a IA estão transformando o cenário! Edição completa por Rádiofobia Podcast e Multimídia: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://radiofobia.com.br/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ --- Nos siga no Twitter e no Instagram: @luizalabs @cabecadelab Dúvidas, cabeçadas e sugestões, mande e-mail para o ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠cabecadelab@luizalabs.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ou uma DM no Instagram Participantes: YOHAN RODRIGUES | https://www.linkedin.com/in/yohan-rodrigues/ CASSIO BOTARO | https://br.linkedin.com/in/cassiobotarohttps://github.com/cassiobotarohttps://www.instagram.com/cassiobotaro/ Links úteis: https://www.amazon.com.br/Fundamentos-Arquitetura-Software-Abordagem-Engenharia/dp/8550819859 https://www.amazon.com.br/Arquitetura-Software-Trade-off-Arquiteturas-Distribu%C3%ADdas/dp/8550819840 https://www.amazon.com.br/Cloud-FinOps-Edi%C3%A7%C3%A3o-decis%C3%B5es-colaborativas/dp/8575228978 https://www.amazon.com.br/Cost-Effective-Data-Pipelines/dp/1492098647 https://www.finops.org

Send us a textThis is a continuation in our ongoing series about How to Accelerate the Speed of Engineering. The discussion covers topics such as the importance of planning and execution, balancing problem-solving and asking for help, the role of checklists, the impact of leadership and team culture, effective communication and collaboration, risk management and building relationships, and lessons learned from past challenges.Main Topics:The balance between speeding up projects and avoiding unforced errorsThe use of tools like Notion and Loom to improve productivity and efficiencyThe role of leadership in building a strong team cultureApproaches to risk management and the value of building relationshipsLessons learned from implementing new processes and toolsAbout the guest: Brad Hirayama is an experienced engineer and program manager specializing in medical devices, with a focus on new product development (NPD), biomedical devices, and process validation. Currently a Staff Engineer, he drives innovation in electrophysiology (EP) products. Brad's background includes roles at Abbott and NuVera Medical, where he contributed to the development of catheters and other vascular technologies. He has expertise in design thinking, FDA compliance, and leadership, all while embodying a passion for connecting people and technologies in impactful ways.Links:Brad Hirayama - LinkedInAbout Being An Engineer The Being An Engineer podcast is a repository for industry knowledge and a tool through which engineers learn about and connect with relevant companies, technologies, people resources, and opportunities. We feature successful mechanical engineers and interview engineers who are passionate about their work and who made a great impact on the engineering community. The Being An Engineer podcast is brought to you by Pipeline Design & Engineering. Pipeline partners with medical & other device engineering teams who need turnkey equipment such as cycle test machines, custom test fixtures, automation equipment, assembly jigs, inspection stations and more. You can find us on the web at www.teampipeline.us

On this episode, I'm joined by Joel Hawksley, Staff Engineer at GitHub for a discussion of code ownership with regards to a 3-year WCAG (Web Content Accessibility Guidelines) project at GitHub, benevolent dictatorship, collective ownability, terrible code vs acceptable code vs the viability of a project, writing good code vs solving problems, defining quality code, quality code resulting from clear conceptualization, the desirability (or not!) of perfect adherence to standards, reducing defect rate, and meaningful testing goals. Code Complete by Steve McConnellJoel Hawksley at GitHubJoel Hawksley at TwitterHawksley.orgEpisode 88 - ViewComponent with Joel HawksleyLive From Ruby Conf 2021, Joel Hawksley Tells Me About His DrinkEpisode 130 - ViewComponent with Joel Hawksley

In this episode of the Maintainable Software Podcast, Robby is joined by Noel Rappin, Staff Engineer at Chime Financial, and the mind behind the latest edition of the classic Programming Ruby book, affectionately known as the "Pickaxe." Noel delves into the intricate process of modernizing a legacy technical book and the lessons learned along the way.Episode Highlights[00:05:32] A Legacy Revisited: Noel Rappin reflects on the process of updating the Programming Ruby book, navigating the balance between preserving its legacy and making it relevant for today's Ruby community.[00:10:17] The Challenges of Modernizing: Noel discusses the complexities of working on a legacy book, including maintaining a consistent tone, updating technical content, and making strategic decisions about what to include or omit.[00:16:12] Parallels with Legacy Code: Noel shares his insights on the similarities between updating a legacy book and maintaining legacy software, emphasizing the importance of understanding past decisions before making changes.[00:21:00] Curating Ruby's Evolution: How Noel approached the task of deciding which Ruby features and practices to highlight in the new edition, considering the evolution of the Ruby community since the book's last update.[00:27:00] The Ruby Ecosystem as a Legacy System: Exploring the idea that the entire Ruby ecosystem can be seen as a legacy system, shaped by past decisions and community standards.[00:33:47] Advice for Aspiring Technical Authors: Noel offers practical tips for those interested in contributing to or updating legacy technical books, including how to pitch ideas to publishers and navigate the challenges of working on established projects.[00:40:00] Maintaining Relevance: Strategies for keeping both software and technical books up-to-date, including Noel's thoughts on the importance of documentation and regular updates.Key TakeawaysUpdating a legacy technical book requires a deep understanding of the community's current needs and the ability to balance respect for the original work with the necessity of modern relevance.The process of modernizing a book like Programming Ruby shares many similarities with maintaining legacy software, including the importance of understanding past decisions and the challenges of working with outdated practices.Community standards play a crucial role in both software maintenance and technical writing, guiding the evolution of both fields.Noel emphasizes the importance of documentation in legacy projects, whether in software or publishing, as a tool for preserving context and aiding future contributors.Resources MentionedProgramming Ruby 3.3 (5th Edition) - The latest "Pickaxe" book, authored by Noel Rappin. Use promo code maintainablefm2024 to get 35% off the ebook.Chime FinancialMurderbot Diaries by Martha WellsWayfarers series by Becky ChambersRubular - Ruby Regular Expression EditorNoel Rappin's WebsiteNoel Rappin on LinkedInNoel Rappin on TwitterFor more episodes like this, be sure to subscribe to the Maintainable Software Podcast.Thanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

Allen Wyma talks with Andrew Lamb about InfluxDB's rewrite. InfluxDB is an open-source time series database. As a Staff Engineer at InfluxData, he works on InfluxDB 3.0, a new time series database written in Rust, focusing on query processing and the Apache Arrow DataFusion and Apache Arrow ecosystems. In that capacity, he is a member and past chair of the Apache Arrow PMC and actively contributes to Apache Arrow DataFusion and the Apache Rust implementation query engine. Andrew was a professional C/C++ programmer for 10 years before switching to Rust. His experience ranges from startups to large multinational corporations and distributed open source projects, and has paid leadership dues as an architect and manager/VP. He holds an SB and MEng from MIT in Electrical Engineering and Computer Science. Contributing to Rustacean Station Rustacean Station is a community project; get in touch with us if you'd like to suggest an idea for an episode or offer your services as a host or audio editor! Twitter: @rustaceanfm Discord: Rustacean Station Github: @rustacean-station Email: hello@rustacean-station.org Timestamps [@0:52] - Meet Andrew Lamb, Staff Engineer at InfluxData, working on InfluxDB IOx [@2:57] - Transitioning from C++ to Rust: Andrew's story [@11:24] - InfluxDB rewrite and its use cases [@22:13] - Compatibility of InfluxDB [@26:58] - Downsides of using Rust and other languages [@32:40] - Plans for the 3.0 alpha/beta release and different versions [@34:54] - Unique use of the async runtime Tokio [@55:28] - Rust as a tool for recruitment [@58:16] - Closing discussion Other links Andrew's X Account Using Rustlang's Async Tokio Runtime for CPU-Bound Tasks Using the FDAP Architecture to build InfluxDB 3.0 RustASIA Conf 2025 Credits Intro Theme: Aerocity Audio Editing: Plangora Hosting Infrastructure: Jon Gjengset Show Notes: Plangora Hosts: Allen Wyma

Dan Neciu, technical co-founder and tech lead of CareerOS, shares intriguing production horror stories, discusses the importance of rigorous testing, and provides valuable insights into preventing and managing software bugs in both backend and frontend development. Links https://neciudan.dev https://www.youtube.com/@NeciuDan https://www.linkedin.com/in/neciudan https://x.com/neciudan We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Dan Neciu.

Just because the AWS Cloud hangs above our heads, doesn't mean your bill needs to be just as sky-high. In this Screaming in the Cloud Summer Replay, Corey is joined by Airbnb Staff Software Engineer Melanie Cebula. Her job is to ensure they keep their monthly cloud bill low, and that the cost isn't just there for a temporary stay. Hear Melanie and Corey chat about the vital role engineers play in helping balance the company books, tricks to optimizing your organization's cloud spending, how inexperience can have a dangerous effect on cost-cutting, and the growing pains facing today's world of data infrastructure. We hope you enjoy this trip down memory lane (just be sure you checkout on time to avoid any fees).Show Highlights: (0:00) Intro to episode(0:27) Backblaze sponsor read(0:54) The role of a Staff Engineer(2:09) Working for a large company reliant on the cloud(3:59) Melanie's Area of Expertise(5:58) Efficiently Managing AWS Bills(11:33) Optimizing cloud spend(14:50) The harmful hesitancy to turn things off(18:17) Inexperience and cost-saving measures(21:17) Firefly sponsor read(21:53) How to avoid snowballing cloud bills(23:40) Kuberentes and cloud billing(27:12) The perks of compounding microservices(29:19) Misconceptions about Kuberentes(31:10) Growing pains of data infrastructure(34:44) Where you can find MelanieAbout Melanie CebulaMelanie Cebula is an expert in Cloud Infrastructure, where she is recognized worldwide for explaining radically new ways of thinking about cloud efficiency and usability. She is an international keynote speaker, presenting complex technical topics to a broad range of audiences, both international and domestic. Melanie is a staff engineer at Airbnb, where she has experience building a scalable modern architecture on top of cloud-native technologies.Besides her expertise in the online world, Melanie spends her time offline on the “sharp end” of rock climbing. An adventure athlete setting new personal records in challenging conditions, she appreciates all aspects of the journey, including the triumph of reaching ever higher destinations.On and off the wall, Melanie focuses on building reliability into critical systems, and making informed decisions in difficult situations. In her personal time, Melanie hand whisks matcha tea, enjoys costuming and dancing at EDM festivals, and she is a triplet.Links Referenced:Twitter: https://twitter.com/melaniecebulaMelanie Cebula's website: https://melaniecebula.com/SponsorsBackblaze: https://www.backblaze.com/Firefly: https://www.firefly.ai/

In this episode of the Maintainable Software Podcast, Robby Russell sits down with James Socol, a Staff Engineer at Fastly, to discuss the art of maintaining legacy code and the nuances of technical debt versus technical depreciation.Key Topics Discussed:Characteristics of Well-Maintained Code: James shares his insights on what defines well-maintained code, emphasizing the importance of continuous maintenance, testing, and encapsulation.Technical Debt vs. Technical Depreciation: James introduces the concept of technical depreciation, distinguishing it from technical debt and explaining how time affects software maintenance.Balancing Old and New Patterns: The discussion explores the challenges of integrating modern standards into legacy systems and finding a healthy balance.20% Time for Maintenance: James advocates for dedicating a portion of engineering capacity to maintenance tasks, drawing parallels to Google's 20% time concept.Onboarding Strategies: James offers valuable advice for new hires, emphasizing observation, gradual involvement, and building social capital within the team.Continuous Delivery and Big Changes: Insights into managing significant changes in a continuous delivery environment, with practical strategies for maintaining stability.Resources Mentioned:Riot Engineering Blog: A Taxonomy of Tech DebtSilicon Valley Product GroupLaura Hogan's Donut TheoryBooks:Getting to Yes by Roger Fisher & William UryTurn the Ship Around by L. David MarquetThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and soon, other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

In this episode of Maintainable, Robby chats with Paola Ducolin, Staff Engineer at Datadog. Paola shares her insights on the characteristics of well-maintained software, the common struggles teams face, and effective strategies for working with stakeholders to prioritize refactoring.Key Topics Discussed:Characteristics of Maintainable Software: Paola explains the importance of well-documented code and having tests that automatically detect breaks.Challenges in Maintaining Software: The impact of business pressures on maintaining code quality and how teams can navigate these challenges.Working with Stakeholders: Strategies for communicating the importance of refactoring and measuring the impact of technical debt on business objectives.Role of Staff Engineers: Paola's journey to becoming a staff engineer and the responsibilities that come with the role, including coordination and networking.Documentation and Design Systems: The power of documentation and how design systems can serve as a model for well-documented and maintainable code.Observability and Monitoring: An overview of Datadog's tools for observability and monitoring, and how they help in maintaining software quality.Resources Mentioned:DatadogMy Path to Staff EngineerSarah Drasner: The Art of Code CommentsBook RecommendationsRadical CandorCrucial ConversationsBe sure to follow Paola on LinkedIn and stay tuned for more insightful conversations on Maintainable.Thanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and soon, other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

Join us in this episode as we dive into the world of scalable and resilient backend infrastructure with Konrad Reiche. A Berlin-transplant living in San Francisco, Konrad is a seasoned software engineer who brings a wealth of experience and insight into designing abstractions that add immense value. Currently a Staff Engineer at Reddit, Konrad's initial background is in audio and video streaming, where he made significant contributions to backend systems. His work, largely inspired by the Go programming language, reflects his dedication to innovation and excellence. Konrad is also a regular speaker at conferences and meetups, sharing his knowledge and passion with the broader tech community. Tune in to learn more about his journey and challenges along the way.00:00 Introduction01:04 What is Konrad Doing Today?12:07 First Memory of a Computer24:30 Going to University43:50 Joining the Workforce 53:40 Working with Go1:07:40 Getting Hired Through the Gopher Slack1:23:50 Working at Reddit1:30:43 Contact Info  Connect with Konrad: Twitter: https://twitter.com/@konradreicheKonrad's Website: https://konradreiche.com/Mentioned in today's episode:Reddit: https://www.reddit.com/Gopher Slack: https://gophers.slack.com/Want more from Ardan Labs? You can learn Go, Kubernetes, Docker & more through our video training, live events, or through our blog!Online Courses : https://ardanlabs.com/education/ Live Events : https://www.ardanlabs.com/live-training-events/ Blog : https://www.ardanlabs.com/blog Github : https://github.com/ardanlabs