Learn from someone else’s mistakes. Why should you understand the system?

Today many frameworks, especially in Java, provide a really nice developer experience. From the outside, their work looks like magic. And we, as developers, tend to move more to sort of novice users of such frameworks. Move more to so-called "magical thinking". But understanding the framework architecture, its concepts and features not only makes the developer fast and productive but also helps to reduce the number of performance and security issues. In this presentation, we will try to find out what it means to "understand the system" and see how it helps write better code with examples for Spring Boot, Spring Data JPA and Spring Websockets.

Using several examples, I'd like to show why it's more important to understand framework architecture concepts rather than follow "getting started guides".

Speaker: Vitali Kviatkouski
Language : English

Working in IT for 14 years, he passed the career ladder from junior dev to team lead, mainly with Java as a primary language. He worked on different projects starting standard ones like bonus marketplace e-commerce application, high-loaded ETL for online ad exchange auctions, and ending with a rather exotic microservice-based fraud detection system for a room booking site or full-serverless migration solution for insurance platform. Actively works as Java/Architecture mentor, he participates in external and internal technical events.