Decline Attestor eSign with airSlate SignNow

Decline attestor esign

all right so welcome to the software design track and welcome to this particular talk about braking dependencies type erasure a design analysis so before we get started give me 10 seconds to introduce myself my name is claus eagleberger and i'm perfectly ok if you stick to the first name because i realized many people cannot pronounce my last name so i'm close and i'm actually working as a simple associate trainer consultant and so the topic i've chosen today is one of my favorite topics because it's actually indeed about dependencies which i perfectly feel is i actually feel is one of the most important things to talk about software design and yes there is many talks on taipeirasia out there how many good speakers have given talks and really good talks however many of these talks very very quickly dive into implementation details very quickly last into the tiniest details how to implement type erasure virtually none of these talks is talking about the thing that i feel is most interesting why typewriter actually helps you to break dependencies and from a software design point of view this is actually the most important aspect so this is what i want to do in this talk against your expectation however i will not directly jump into type erasure and actually first very quickly talk about the challenge of software design in general then we'll solve a problem very naively by just using inheritance then we improve the solution you reach for a couple of design patterns and then we finally last but at least go into type erasure the goal of my talk however is that after this talk you should of a very good idea about typewriter not about every single implementation detail this is what i leave away but about why this is something that you should be interested in from a design perspective and also you should have a pretty good idea um which design patterns are actually happening now which design patterns we use in order to make all of this magic work so let's start with the challenger software design in general because i believe this is actually indeed super important if you develop software you're always facing problems but interesting all of these problems have to do with change they all have to do with change if we wouldn't have to change things if everything would already work then well we would be fine absolutely but change is what actually really makes us realize that there's something imperfect and this is actually something that is expected software must be adaptable frequent changes that is the reason why software is called software in the first place it is supposed to be easy to change it's supposed to be adaptable to whatever changes i want to do however it's not that simple if it would be probably it would not be that interesting but indeed it's often very very hard to change things and...