Just a concurrent programming or a occupation interview subject in the past, day to day class plan practice now. For many teams “immutable first” becomes the norm not only for Value Objects or functional paradigm. It’s a natural consequence of constructors’ existence. Software is more and more complex, there is no place for additional effort just for objects’ state tracking. Despite everything, you can hear objections or whispers of temptation:
“It can’t be immutable due to the framework”,
“Don’t do it here, it is just an entity/service/DTO”,
“We don't request another annotation, 5 on each field is enough”.
I'll dispel these myths and show how to make popular Java libraries large tools again (persistence, serialization, mocks and other). They won’t tell you more how to code. alternatively of writing God Classes, be a god of your code and compose immutable classes whenever you want.
Lecture took place on Wednesday, 22nd June 2022 at 18:10 in area 4B
Software engineer for over a decade with experience in a wide variety of systems (from mobile to aviation). associate of Resilience4J improvement team. Java Virtual device languages enthusiast, and the Application Programming Interfaces explorer and traveller. A friend of penguins and androids. Allergic to JavaBeans, but addicted to good coffee beans and clean code. presently develops aviation strategy for drones.
Twitter: https://twitter.com/DevoxxPL
Instagram: https://www.instagram.com/grzegorz.duda.official/
Join us besides here:
Technology Radar Review: https://dworld.pl/radar
Developers planet Academy: https://dworld.pl/akademia
Devflix: https://devflix.pl
#IT #Development #SoftwareDevelopment