The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices

Episode 4 of The Software Engineering Podcast dives into a specific case: Sarah Chen, a senior infrastructure engineer at a mid-size SaaS company, reduced her team's monthly AWS bill from $47,000 to $4,700 over six months. Lucas and Luna unpack the concrete steps she took — right-sizing instances, switching to spot instances, implementing auto-scaling policies, and deleting orphaned resources. The...

In this episode of The Software Engineering Podcast, Lucas and Luna dive into a single operational decision that transformed a team's incident response. They examine how a senior engineer at a mid-size e-commerce company introduced structured severity levels, a dedicated on-call escalation channel, and a lightweight postmortem culture. The result: mean time to acknowledge alerts dropped from 12 mi...

Lucas and Luna examine why code reviews take so long, drawing on a 2020 study of Google's internal review process that found a median first-response time of 4.5 hours. They break down the cognitive cost of context switching, the difference between synchronous and asynchronous review, and practical techniques like review slop and size limits that teams at companies like Shopify and Netflix use to c...

Lucas and Luna launch their new podcast by dissecting a single infamous software bug — the 2018 Knight Capital trading glitch that cost $440 million in 45 minutes. They unpack how a missing line of code, a flawed deployment process, and a weak rollback plan turned a routine upgrade into one of the most expensive rollouts in history. Along the way, they explain what 'idempotency' means, why unit te...