Artwork

เนื้อหาจัดทำโดย Fahad Shoukat and Andrew Wolfe, Fahad Shoukat, and Andrew Wolfe เนื้อหาพอดแคสต์ทั้งหมด รวมถึงตอน กราฟิก และคำอธิบายพอดแคสต์ได้รับการอัปโหลดและจัดหาให้โดยตรงจาก Fahad Shoukat and Andrew Wolfe, Fahad Shoukat, and Andrew Wolfe หรือพันธมิตรแพลตฟอร์มพอดแคสต์ของพวกเขา หากคุณเชื่อว่ามีบุคคลอื่นใช้งานที่มีลิขสิทธิ์ของคุณโดยไม่ได้รับอนุญาต คุณสามารถปฏิบัติตามขั้นตอนที่แสดงไว้ที่นี่ https://th.player.fm/legal
Player FM - แอป Podcast
ออฟไลน์ด้วยแอป Player FM !

Demystifying Software Architecture

30:22
 
แบ่งปัน
 

ซีรีส์ที่ถูกเก็บถาวร ("ฟีดที่ไม่ได้ใช้งาน" status)

When? This feed was archived on August 01, 2022 22:00 (1+ y ago). Last successful fetch was on February 23, 2022 13:41 (2y ago)

Why? ฟีดที่ไม่ได้ใช้งาน status. เซิร์ฟเวอร์ของเราไม่สามารถดึงฟีดพอดคาสท์ที่ใช้งานได้สักระยะหนึ่ง

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 288353625 series 2423156
เนื้อหาจัดทำโดย Fahad Shoukat and Andrew Wolfe, Fahad Shoukat, and Andrew Wolfe เนื้อหาพอดแคสต์ทั้งหมด รวมถึงตอน กราฟิก และคำอธิบายพอดแคสต์ได้รับการอัปโหลดและจัดหาให้โดยตรงจาก Fahad Shoukat and Andrew Wolfe, Fahad Shoukat, and Andrew Wolfe หรือพันธมิตรแพลตฟอร์มพอดแคสต์ของพวกเขา หากคุณเชื่อว่ามีบุคคลอื่นใช้งานที่มีลิขสิทธิ์ของคุณโดยไม่ได้รับอนุญาต คุณสามารถปฏิบัติตามขั้นตอนที่แสดงไว้ที่นี่ https://th.player.fm/legal

In this episode, Andrew and Fahad demystify software architecture, discussing what defines architecture, how to make it less complicated, what the real goals of architecture should be, why patterns and technical debt are important, and how company execs can use this knowledge to empower their business.
Show Notes

  • Software systems are becoming increasingly sophisticated and complex and business expectations are driving that complexity.
  • Go back to first principles
    • Earn Your Complexity
    • Abstract for that which changes. You can know what changes if you study and understand your industry.
    • Think of the problem before the solution and patterns will naturally be revealed.
  • Architecture is business enablement which helps you to understand your product, its implementation, and its real world consequences.
  • Technical debt is a vehicle for growth and not having it means that you are stagnant and not investing in anything toward the future. Leverage your technical debt by looking forward and understanding your product roadmap.
  • Software is constantly evolving and you should be constantly leveraging technical debt to enable the business in the future.
  • There are no "best patterns' to use as you accumulate and use technical debt. Patterns are tools and as a hammer has a specific job, so does a pattern.
  • The goal is to refactor and pattern toward the simplest possible system.
  • You can often abstract away compliance. Architects have to know about the product as well as how to be legal and compliant.
  • Can CFOs, CTOs, and CEOs identify things that can help them with this or should they simply just truth the technical people? The best architects are going to help executives understand the decisions being made and why they are making them.
  • Ownership requires a lack of ignorance in the entire process. It is all about connecting with people and trying to help people.

People and Resources Mentioned

Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing.
Check out the Insights page for a library full of Thoughtful Articles.
We’d love to know what you took away from our conversation. Follow us at @fahsho12 and @andrewwwolfe and share your insights and questions with the #thoughtful software.

  continue reading

72 ตอน

Artwork
iconแบ่งปัน
 

ซีรีส์ที่ถูกเก็บถาวร ("ฟีดที่ไม่ได้ใช้งาน" status)

When? This feed was archived on August 01, 2022 22:00 (1+ y ago). Last successful fetch was on February 23, 2022 13:41 (2y ago)

Why? ฟีดที่ไม่ได้ใช้งาน status. เซิร์ฟเวอร์ของเราไม่สามารถดึงฟีดพอดคาสท์ที่ใช้งานได้สักระยะหนึ่ง

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 288353625 series 2423156
เนื้อหาจัดทำโดย Fahad Shoukat and Andrew Wolfe, Fahad Shoukat, and Andrew Wolfe เนื้อหาพอดแคสต์ทั้งหมด รวมถึงตอน กราฟิก และคำอธิบายพอดแคสต์ได้รับการอัปโหลดและจัดหาให้โดยตรงจาก Fahad Shoukat and Andrew Wolfe, Fahad Shoukat, and Andrew Wolfe หรือพันธมิตรแพลตฟอร์มพอดแคสต์ของพวกเขา หากคุณเชื่อว่ามีบุคคลอื่นใช้งานที่มีลิขสิทธิ์ของคุณโดยไม่ได้รับอนุญาต คุณสามารถปฏิบัติตามขั้นตอนที่แสดงไว้ที่นี่ https://th.player.fm/legal

In this episode, Andrew and Fahad demystify software architecture, discussing what defines architecture, how to make it less complicated, what the real goals of architecture should be, why patterns and technical debt are important, and how company execs can use this knowledge to empower their business.
Show Notes

  • Software systems are becoming increasingly sophisticated and complex and business expectations are driving that complexity.
  • Go back to first principles
    • Earn Your Complexity
    • Abstract for that which changes. You can know what changes if you study and understand your industry.
    • Think of the problem before the solution and patterns will naturally be revealed.
  • Architecture is business enablement which helps you to understand your product, its implementation, and its real world consequences.
  • Technical debt is a vehicle for growth and not having it means that you are stagnant and not investing in anything toward the future. Leverage your technical debt by looking forward and understanding your product roadmap.
  • Software is constantly evolving and you should be constantly leveraging technical debt to enable the business in the future.
  • There are no "best patterns' to use as you accumulate and use technical debt. Patterns are tools and as a hammer has a specific job, so does a pattern.
  • The goal is to refactor and pattern toward the simplest possible system.
  • You can often abstract away compliance. Architects have to know about the product as well as how to be legal and compliant.
  • Can CFOs, CTOs, and CEOs identify things that can help them with this or should they simply just truth the technical people? The best architects are going to help executives understand the decisions being made and why they are making them.
  • Ownership requires a lack of ignorance in the entire process. It is all about connecting with people and trying to help people.

People and Resources Mentioned

Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing.
Check out the Insights page for a library full of Thoughtful Articles.
We’d love to know what you took away from our conversation. Follow us at @fahsho12 and @andrewwwolfe and share your insights and questions with the #thoughtful software.

  continue reading

72 ตอน

ทุกตอน

×
 
Loading …

ขอต้อนรับสู่ Player FM!

Player FM กำลังหาเว็บ

 

คู่มืออ้างอิงด่วน