Codemotion Tech pills

Later this May Codemotion, the biggest of the software conferences in the whole Europe, is landing in Amsterdam! While you will have to still wait a few weeks before enjoying awesome speakers with great content, we will keep your mind warm with some inspirational night outs.

Agenda:

18:30 -- Doors open / food & drinks are served

19:00 -- Presenting Codemotion

19:15 -- Bert Jan Schrijver and Tim van Eijndhoven - Continuous performance: load testing for developers with Gatling

20:00 -- Stefano Masini - Dependency inversion principle i.e. frameworks considered harmful

20:45 -- Raffle for a free Codemotion conference pass

21:00 -- Networking / borrel

Our Talks:

Continuous performance: load testing for developers with Gatling

Performance testing is traditionally a task for specialists that takes place at the very end of the software delivery life cycle. But how does this fit in with a DevOps way of working, where continuous feedback is one of the key points? It doesn't. 

In a world where scalability and performance are just as important as delivering new features, you need to embed performance testing in your daily development workflow: it needs to become a natural part of development. And this is where Gatling comes in: an open source load testing framework based on Scala, Akka and Netty.

In this session, you will learn how to use Gatling to incorporate performance testing in development and how to provide your team with continuous feedback on your application's performance.Subjects include an introduction to Gatling, automated recording and processing of performance tests with the Gatling Scala DSL and integration with Jenkins for automated execution, bench marking and reporting of load tests.

Dependency inversion principle i.e. frameworks considered harmful

The Javascript ecosystem is evolving at an incredible pace. Using new great libraries is fun, but we suffer from dependency hell. A real-world product easily depends on thousands of node modules, many of debatable quality. It's hard to make a long term commitment to any framework. And yet, we're supposed to write code that should last longer than 6 months. Fortunately, good old software engineering principles shed light on how to build a well decoupled, easily maintainable product. I will talk about my recent experience, lessons learned and an unpopular choice that paid back surprisingly well.

Our Speakers:

Bert Jan Schrijver is a Software craftsman at JPoint and Java User Group leader for NLJUG, the Dutch Java User Group. His focus is on Java, Continuous Delivery and DevOps.

He loves to share his experience by speaking at conferences, writing for the Dutch Java magazine and helping out Devoxx4Kids with teaching kids how to code. Bert Jan is a speaker at Codemotion Amsterdam

Tim van Eijndhoven is a Software Craftsman at JPoint. His main interests are Java, application-architecture, software security and open source. He likes to share his knowledge by publishing articles in the Dutch Java Magazine. 

Stefano Masini has been writing code professionally for more than 20 years. A long time Python user, he finds today more intellectual stimulation in the vibrant Javascript community. 

Full-stack developer, his interest lingers over anything that sits in between Docker and React. From owning his own company to working for Balsamiq, he's always been passionate about listening to the customers and building a great product for them.

Our Sponsors: