Adrienne Braganza Tacke: Code Review Patterns & Principles - Episode 347

Adrienne Braganza Tacke is an accomplished author and software engineer with a passion for educating others about software development. Choosing a path distinct from the expected trajectory of nursing, she pursued a degree in management information systems at the University of Nevada, Las Vegas. Over the course of nearly eight years in the field, she has contributed her expertise across multiple industries, including healthcare and higher education. Currently, she serves as a software development engineer at DebtTrader, where she embraces the challenge of modernizing fintech workflows traditionally dependent on spreadsheets.

 

Beyond her professional work, Adrienne is an international speaker, instructor, and dedicated advocate for STEM education. Her first book, Coding for Kids: Python, has consistently ranked among the top-selling children's programming books on Amazon. She frequently visits schools to inspire students with insights into software engineering and the transformative power of coding. When she’s not engaging with young aspiring developers, she speaks at tech conferences throughout the U.S. and Europe. Follow her on Twitter and Instagram (@AdrienneTacke) to stay updated on her latest endeavors.

 

Topics of Discussion:

[3:20] Adrienne’s journey and the happy accidents and formative moments that led her to working in this field.

[5:46] What does a developer advocate do?

[7:04] Adrienne started teaching in 2017, when tech influencers were starting to become more popular.

[9:02] There is no one-size-fits-all about the code review process, and what it looks like will be different for every team.

[11:19] The price of ineffective communication.

[15:30] The power of fixing things during development and before the code review.

[19:10] Adrienne gives a few real-life examples of time wasters in code reviews.

[22:08] More about Adrienne’s book, Looks Good to Me: Constructive Code Reviews, and how it can help streamline and save time. 

[23:44] Like Adrienne’s chapter title, if you can automate it — do it.

[26:51] There are still errors that won’t be caught by static analysis.

[30:46] Some tips to remember when using AI, like making sure your titles are descriptive.

[36:17] Maybe an “auto-polite” button is coming soon? We wish.

 

Mentioned in this Episode:

Clear Measure Way

Architect Forum

Software Engineer Forum

Programming with Palermo — New Video Podcast! Email us at [e-mail].

Clear Measure, Inc. (Sponsor)

.NET DevOps for Azure: A Developer’s Guide to DevOps Architecture the Right Way, by Jeffrey Palermo

Looks Good to Me: Constructive Code Reviews

CodeRabbit

OFFER:
First listener to use the code gets a free copy of the book: "braganza-FBEE"Instructions:
1. Go to book link (