DevOps October meetup

18:00 - Doors open. Food & drinks provided by YACHT

19:00 - Talk #1: Joep Piscaer, Come listen to me, I’m a fraud! A story on success, impostor syndrome and self-inflicted, perpetually non-existent comfort zone.

19:45 - Break

19:55 - Talk #2: Sanne Kalkman, Who Takes Out Your Trash?

20:30 - Break

20:40 - Talk #3: Brian Langhoor, Test Driven Development

21:10 - Networking and beers

---------------------------
Hey you! You’re exposed! We know you are a fraud! You’re don’t deserve any of the success you’ve achieved!

Do you recognize the fear of being exposed as a fraud? I do. Even as I prepare and present this session, I feel that you’ll expose me of not being worthy of talking to you.

With fifteen years in IT and a successful career as a world-class infrastructure engineer, a speaker at many industry conferences, a blogger, analyst and technical marketing freelancer for Silicon Valley Startups and a CTO of a 1200+ infra and software engineering company, I can definitely say I suffer from impostor syndrome, and by extension, perfectionism.

And it doesn’t go away with success. The opposite seems to be true, actually. I’ve learned to harness it, spending a lot of time way out of my comfort zone to figure out how to come to terms with it and use it for good. Maybe the fact that I experience the syndrome makes me more humble, which makes me more valuable as a leader.

With small, incremental improvements, I now live in a self-inflicted, perpetually non-existing comfort zone. I’m constantly in the imposter zone, because I’m constantly doing new things, learning new skills, meeting new people. And I love it! It has brought me many smaller and larger victories, a career that’s led me to new and unexpected ventures and most importantly, a network of friends and relationships I otherwise would never have had.

----------------------
Even clean code creates garbage. Although most of us don't take out our own trash, we should still know how it's done!
In our daily development lives, most of us don’t have to worry about unused objects gathering cobwebs and filling up the memory. All we need to know is that our language has a garbage collector that just comes by and makes our trash disappear. Somehow it figures out what should stay and what can go, our program can keep going without running out of space, and we don’t have to do a thing. It is not in fact magic that takes care of the garbage, and this talk will show you how it’s done. First, we’ll explore how two of the most common garbage collection algorithms, reference counting and tracing, figure out what is ready to be collected. Next, we’ll see how we could get the garbage truck out of the way faster by using a generational algorithm, This friendly introduction to taking out the trash gives an overview of important aspects of garbage collection algorithms. It is specifically meant to be accessible developers of all levels and you’ll walk away with an understanding of and appreciation for all the hard work that goes on behind the scenes.

Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases, then the software is improved to pass the new tests, only. This is opposed to software development that allows software to be added that is not proven to meet requirements. TDD is for many a world in reverse: tests are written for code that does not yet exist. You write code until all tests are successful. During this tech talk Brain will give a hands impression of the writing of tests, the success of the tests, the required / resulting architecture and how to deal with external components where a database is taken as an example. The examples will be shown and made in a C#.Net environment. The talk will mainly focus on the TDD principle, not the programming language.