Bugs. We hates them. After all, we get this shiny box with blinky lights or download the latest version of this important software, and isn’t is just supposed to work?
When there’s a problem, we rage and complain and possibly even break things. (There might be a keyboard or two with my fist print on it. Just sayin’.)
What what do bugs look like from the vendor perspective? Why do bugs happen, and what do vendors do about them when they do?
On our show today, Ahmed Maged, an engineer in Programmable Networks at Cisco, joins us to discuss the bug issue, including how bugs happen, the bug lifecycle, and the different perspectives that vendors and customers have on bugs and bug remediation.
Talari creates a THINKING SD-WAN that makes the network smart and responsive, adapting in real time to changing conditions. Talari puts intelligence in every packet and at every endpoint, performing one-way measurement to identify packet loss, jitter, and the failure of any one network path—then rerouting packets to keep your data flowing. Mission-critical apps like VoIP and VDI take priority and always deliver. Visit talari.com for more details.
Topic 0: Murphy’s law. Bugs are interesting because when they happen, networks fails and/or attackers get rich
Topic 1: Why network engineers need to learn more about the software industry and bugs
Topic 2: Business impact vs line of code (customer vs developer perspectives)
Topic 3: Bug hunting
- Bug types, life cycles, priorities, and what goes into a bug report
- Why software has bugs, and how bugs are discovered and reported
- How do vendors miss bugs before a product/feature is launched?
Topic 4: The bug fix process, and why it takes time
Topic 5: Minimizing the impact of bugs