Stop Punching Yourself in the Face • Hannes Lowette • GOTO 2020

This presentation was recorded at GOTOpia November 2020. #GOTOcon #GOTOpia

Hannes Lowette - Performance Coach with Exceptional Skills around Databases, Distributed Systems and Large Scale Apps

ABSTRACT
Making choices is hard. As developers, we make choices all the time: architectures, frameworks, libraries, cloud providers, etc. So, if you have been around for a while, you probably ended up regretting at least some of those choices.
In this talk, you will learn how to make choices responsibly and what to look out for if you want to minimize the chance of regretting them later. I dive into several situations where the choices we made as a team have gone horribly wrong. Luckily, I learned these lessons the hard way, so you don’t have to!
Now, if only there was a way to prove your newly acquired skills to your peers and superiors. Well, there is: RAD Certification! I will conclude my talk by telling you about this. And as a bonus, if you get certified during the conference, you can score your RAD certificate [...]

TIMECODES
00:00 Intro
00:43 What we do
01:01 The magpie
01:37 The software developer
02:18 Is this surprising?
03:18 Our education
04:12 We look for guidance...
05:10 ...until we run into a wall!
05:18 An adventure with CHAD
05:53 The RavenDB story
09:42 The Agatha story
15:06 The EventStore story
18:45 The Entity Framework story
23:09 The "big old project" story
26:40 The Microservices story
32:16 Summary

Download slides and read the full abstract here:

RECOMMENDED BOOKS

#SoftwareArchitecture #RavenDB #Programming #SoftwareDevelopment #AgathaRRSL #MVC #EventStore #ASPNET #EntityFramework #SQL #Microservices #Agular #Docker #k8s #Kubernetes #MongoDB #SOLID #TeamSkills #Culture #Axxes

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[anlongdus]

Key takeaways:
1. Best technical fit at reasonable costs
2. Check for warning signs in future dependencies
3. Educate your team
4. Thoroughly understand your tools („take away the magic“)
5. When making architecture changes, refactor old code to avoid chaos
6. Trim your stack, every tool in your belt has a price
7. Evolve your stack, replacing one component at a time - with good reasons and a time/budget
8. Architecture follows the requirements, as simple as possible
9. Microservices can be a good fit when requirements include scaling development, multiple clients, different technologies
10. Structure code with SOLID

Be a responsible developer, not care- or helpless.

[chewbaccarampage]

This guy's been through developer hell and back. Thanks for sharing all your experiences.

[craigriecke]

A very useful presentation with actionable advice. Greatly appreciated. One small thing - not all programmers are "he". Thanks!

[kunalsoni]

Feeling is to this video is so informative and full with motivation 😊