12 Nov 2026 Marian Kamenistak on Product Management for Software Engineers
As AI automates coding, engineers must master product management, focusing on customer value, rigorous validation, and business outcomes to remain valuable.
More Software Engineering Radio episodes
Published 20 May 2026
Recommended: Risk identification and management is a forgotten art
Duration: 52:31
Software development prioritizes risk management through frameworks like test-driven development and agile, addressing hidden risks, AI deployment challenges, open-source dependencies, and organizational prioritization to balance innovation with safeguards.
In this episode, Rob Moffat, author of Risk-First Software Development and chief technical architect at the FinTech Open Source Software Foundation (F...
The podcast emphasizes that software development is fundamentally an exercise in risk management, with features created to mitigate risks like user disengagement, operational failures, or financial losses. It highlights how traditional methodologies (e.g., Scrum, DevOps) inherently manage risks but often lack explicit focus on risk analysis. A proposed risk-first framework shifts priorities by identifying and categorizing risks based on project contexts, aligning practices like test-driven development (TDD), pair programming, or limiting work-in-progress (WIP) to specific risk categories. The framework advocates for proactive risk identification, prioritization, and ongoing evaluation of how technical practices interact with risks, rejecting rigid adherence to methodologies in favor of context-driven adaptation. Challenges include overlooked hidden risks, misaligned stakeholder priorities, and the complexity of quantifying software risks, which the podcast compares to broader organizational risk taxonomies and financial risk models like Value at Risk (VaR).
The discussion extends beyond software development to include AI deployment risks, such as hallucinations, bias, and data security, as well as the unique challenges of open source collaboration, including license compliance, supply chain vulnerabilities, and the risks of contributing or consuming open source code without oversight. The podcast also explores agency risk, where misalignment between individual and organizational goals can undermine project success, and advocates for frameworks that integrate risk awareness into workflows, such as time-boxing, reviews, and contracts. A central theme is the universal nature of risk management across professions, framing all workincluding finance, law, and AIas inherently involving risk mitigation. The podcast encourages adopting a risk-first perspective to improve decision-making, prioritize tasks, and align practices with organizational objectives, whether in software development or broader domains.
What if you re-prioritized your backlog using the "risk lens" approach?
What if you implemented a "risk register" for AI features in your project?
What if you used a "Git proxy" tool to audit open source contributions before publishing?
Conduct a Risk Assessment for Each Project
Begin every project by identifying key risks (e.g., technical debt, dependency vulnerabilities, or compliance gaps) and align your development practices (e.g., TDD, unit testing, or static code analysis) to mitigate them. Use tools like GitHubs security features or open-source scanners to automate risk detection.
Implement Unit Testing and Code Review Practices
Integrate unit testing into your workflow to catch implementation errors early and reduce long-term maintenance risks. For solo developers, use automated testing frameworks (e.g., Jest, PyTest) and schedule regular code reviews (e.g., with peers or AI tools) to ensure code quality and reduce oversight gaps.
Reassess Your Backlog Using a Risk-Based Lens
Regularly evaluate your project backlog to prioritize tasks that address high-impact risks (e.g., security vulnerabilities, regulatory compliance, or critical feature bugs) over routine feature work. Use a risk matrix to quantify the likelihood and impact of unresolved issues.
Manage Open Source Risks with Strict Controls
When using open source components, maintain an inventory of all dependencies and use tools like Git Proxy (from Finos) to enforce pre-contribution reviews, ensuring license compliance and preventing accidental data leaks. Avoid internal "forking" by contributing upstream to maintain influence over project direction.
Establish Iterative Feedback Loops for Communication Risks
Use lightweight practices (e.g., weekly check-ins, documentation updates, or peer feedback) to address communication risks, ensuring alignment with project goals and reducing misinterpretation of requirements. For solo developers, tools like Notion or Trello can help track stakeholder expectations and mitigate scope drift.
These takeaways are grounded in the texts emphasis on risk management, open source collaboration, and iterative practices, tailored for solo developers to balance innovation with safeguards.
The provided text is a comprehensive guide to risk management in software development, emphasizing the importance of understanding and addressing risks as a core aspect of the development process. Here are some key insights and takeaways, along with their potential relevance and usefulness to readers:
Risk Management as a Primary Concern:
Adapting Methodologies to Risk:
Risk Framework Overview:
Challenges and Opportunities:
Implementation Workflow:
Quantifying Software Risk:
Agency Risk:
Risk First Framework:
Risk Management in AI:
Open Source Collaboration:
12 Nov 2026 Marian Kamenistak on Product Management for Software Engineers
As AI automates coding, engineers must master product management, focusing on customer value, rigorous validation, and business outcomes to remain valuable.
29 Oct 2026 Danilo Krummrich on Rust in the Linux Kernel
"Nova GPU driver project integrates Rust into the Linux kernel to replace the aging Novo driver, leveraging Rust's memory safety for better reliability and performance while addressing firmware and architectural challenges through incremental, collaborative updates."
7 Oct 2026 Sahil Walia on Schema Changes and Data Migrations
Recommended: Schema as source of truth
"Schemas define data structure, apply across systems, and require careful evolution to avoid breaking changes, with best practices including additive updates, blue-green deployments, and stable identifiers."
30 Sept 2026 Raju Dandigam on Building Production AI Agents
"Explores production AI agents, their autonomy, safety, and engineering best practices, comparing workflows, tool design, orchestration, and memory systems while addressing challenges like cost, latency, and reliability."
16 Sept 2026 Milan Milanovic on the Laws of Software Engineering
"Explores key software engineering principles (like Conway's Law, Brooks' Law) and their impact on systems, teams, and decision-making, emphasizing context-dependent trade-offs, AI's role, and practical applications like measuring technical debt."