Architects know how to solve these 5 kinds of tech debt скачать в хорошем качестве

Architects know how to solve these 5 kinds of tech debt

Tech debt is a pretty course term In general it’s technology choices or practices that may have initially allowed your application or architecture to move fast, but that now slow you down Coming through university I knew about reuse and polymorphism and once I got out into the industry, this was about 2002 I learned about design patterns and started to think clearly about the interactions between those structures that allow reuse, but it wasn’t until a few years later that I started to notice problems around me where rot had started to happen. When I think back, the first commercial position I took they had a pretty clear architecture, exceptionally high staff retention and some really talented programmers and really I didn’t get to see or experience technical debt until I got into the game industry a few years later, where the rush mindset and staff churn play a larger part There are different kinds of tech debt and they are all caused by different forces in your organisation. Unfortunately it’s not always obvious you’re creating tech debt until you see the friction that a particular solution causes, but 20 years of software architecture and design has taught me that there are some constants Here are 5 kinds of tech debt and what to do about them 00:00 Intro 01:22 Depreciation 02:23 Entropy and Mediocrity 03:23 Dependencies 04:11 Overengineering 05:15 Manual Processes