In this presentation, we will learn how to build highly composable, type-safe, and testable systems without the typical enterprise framework magic.
If you wish to unlearn years of practices such as using:
This presentation is for you.
Learning outcomes:
Or on a less serious note we’ll:
Learn more about feature flags: principles for real-world feature flags
Upper case Clean Code is one man’s aesthetics for writing code. It has a large number of devoted followers but also a growing number of critical voices.
Regardless where you stand, I always wished there was Clean Code 102 for grownups that:
Come join the rethinking cycle discovering the 2022 lessons for writing cleaner, more testable and more correct code.
You’ve just inherited a legacy codebase. Technical debt from static code analysis exceeds your mortgage. Let’s stop for a second.
What if we go beyond current snapshot of the code and analyze its Git history.
Come and learn how behavioural code analysis can help:
When Web Performance Optimization was emerging as a new field of engineering we had a handful of rules to follow. Gzip here, minify there, do some caching. This was 15 years ago.
This year’s Smashing Magazine performance checklist has 62 items with hundreds of links for further research.
Have we learned so much or has the Web become so complicated?
In this talk I will try to make sense of today’s most pressing Web Performance issues with easily digestible lessons about metrics, budgets, JavaScript frameworks, functional programming, browsers and plain old HTML.
What separates proficient and experts from the rest of us.
How do they think and how do they learn?
What should we focus on when everyone changes frameworks as often as their socks?
How to prepare for the life where deep work and knowledge will displace repeatable tasks.
I will try to answer those questions in the context of learning JS.
We will also cover less serious topics.
Why I stopped listening to self development coaches. What book should we take the photo with for Instagram. Finally I will reveal the connection I found between JS and drugs/gambling.
2 years with Node.js in production. Time for a summary.
During my talk I will talk about:
Carly Rae Jepsen will help me explain why we don't use callbacks and I will share why JS makes me fat.
Microservices, cloud, continuous delivery heavily influenced how modern teams build software systems. Come to this talk to learn how our team rebuild frontend stack of several newspapers significantly reducing cycle time and creating fun work environment that lets great developers be great.
Some of the things I’ll share:
Imagine you could go back in time.
What advice would you give your younger self about how to do Java Web Development in a simpler and more effective way?
What did you learn? What would you do differently? What would you like to forget?
In this talk we will go back in time and give my younger self some advice on building a crazy web stack that I’d find shocking back then.
A plethora of web frameworks, DI containers, template engines, build/deployment tools, dependency managers, web servers and testing strategies. Modern developers have more choice than ever before.
I’ll share my thinking process and explain how my decision making has changed over time. With a little help from behavioural scientists, psychologists, hot dog eating contestants and my programming mentors we’ll learn how to think like a freak.