Brand new fancy frameworks appear quite often nowadays. Sometimes we as developers are trying to keep up to date by blindly chasing them. But is the investment worth?
What business expects from us? Fancy frameworks or solid delivery pipeline?
How can we focus on writing line of business code?
How can we postpone architectural decisions about frameworks?
How to make sure that your project structure reflects the business, not the technical brainfuck?
Artur has been digging this topic for years and has a lot of real-life examples to share.
Artur is a seasoned, independent consultant, who went through enterprise applications of all kinds. He is enthusiastic about building and leading strong teams, revealing their potential and making smart people working with other smart people.Artur’s peers know how pragmatically he combines business-oriented thinking and fanatic passion for software development best practices like Domain-Driven Design, TDD, paired programming, writing clean code, etc. Before he went independent, he worked as an architect and a tech lead. In addition to that Artur is an active OSS contributor and blogs at Craftsman at Work.