Content provided by Jeffrey Palermo. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jeffrey Palermo or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

People love us!

User reviews

"Love the offline function"
"This is "the" way to handle your podcast subscriptions. It's also a great way to discover new podcasts."

Jeffrey Palermo: The Process of Architecture - Episode 207

31:35
 
Share
 

Manage episode 338566632 series 2446935
Content provided by Jeffrey Palermo. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jeffrey Palermo or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

This is a special episode. I wanted to interrupt our fabulous stream of expert guests to talk about a topic that I think needs to be talked about, and that is architecture. What is it? What should we think about it, and how do we approach the process of architecture? To derive the verb, how do we go about determining and implementing a fitting architecture? To architect. If you are in this role, what is it that you do? What thought progression do you use? I’ll share some thoughts on that from 25-plus years of programming, and then I have a very special announcement at the end, so be sure to check that out.

Topics of Discussion:

[2:19] Architecture is the intersection of the process that we use for software and the structure we want the software to be. Right there in that intersection is where leadership is required.

[4:22] What are the building blocks of architecture, and what is the progression from the smallest building block up to the most complex and large software system?

[9:24] If you’re creating a very, very small piece of software, you don’t need much architecture.

[11:08] Jeffrey breaks down the term “monolithic” and how it relates to code.

[11:15] If monolithic is bad, isn’t “polylithic” bad too?

[15:18] What makes an application an application, and not just a library? An application is greater than a library because it has abstractions, and then it has configurations.

[28:12] Special announcement: new video show is launched! Check out Programming with Palmero.

Mentioned in this Episode:

Architect Tips — New video podcast!

Azure DevOps

Clear Measure (Sponsor)

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

Jeffrey Palermo’s YouTube

Jeffrey Palermo’s Twitter — Follow to stay informed about future events!

Programming with Palermo

programming@palermo.net

Want to Learn More?

Visit AzureDevOps.Show for show notes and additional episodes.

  continue reading

264 episodes

iconShare
 
Manage episode 338566632 series 2446935
Content provided by Jeffrey Palermo. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jeffrey Palermo or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

This is a special episode. I wanted to interrupt our fabulous stream of expert guests to talk about a topic that I think needs to be talked about, and that is architecture. What is it? What should we think about it, and how do we approach the process of architecture? To derive the verb, how do we go about determining and implementing a fitting architecture? To architect. If you are in this role, what is it that you do? What thought progression do you use? I’ll share some thoughts on that from 25-plus years of programming, and then I have a very special announcement at the end, so be sure to check that out.

Topics of Discussion:

[2:19] Architecture is the intersection of the process that we use for software and the structure we want the software to be. Right there in that intersection is where leadership is required.

[4:22] What are the building blocks of architecture, and what is the progression from the smallest building block up to the most complex and large software system?

[9:24] If you’re creating a very, very small piece of software, you don’t need much architecture.

[11:08] Jeffrey breaks down the term “monolithic” and how it relates to code.

[11:15] If monolithic is bad, isn’t “polylithic” bad too?

[15:18] What makes an application an application, and not just a library? An application is greater than a library because it has abstractions, and then it has configurations.

[28:12] Special announcement: new video show is launched! Check out Programming with Palmero.

Mentioned in this Episode:

Architect Tips — New video podcast!

Azure DevOps

Clear Measure (Sponsor)

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

Jeffrey Palermo’s YouTube

Jeffrey Palermo’s Twitter — Follow to stay informed about future events!

Programming with Palermo

programming@palermo.net

Want to Learn More?

Visit AzureDevOps.Show for show notes and additional episodes.

  continue reading

264 episodes

Alle episoder

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Player FM - Podcast App
Go offline with the Player FM app!

Quick Reference Guide