1 of 32

About:�Call for Papers

Lightning Talk ___ Markus Tacker ___ @coderbyheart�Global Diversity CFP Day 2019 ___ Frankfurt

2 of 32

3 of 32

Content

Structure of a Proposal

Where to find CfPs

Submitting

#paytospeak

Code of Conducts

4 of 32

Structure of a Proposal

5 of 32

Speaker Profile

6 of 32

Speaker Profile

Less than 100 words.

Third person.

Mix of background and interesting trivia.

Why should I talk to you?

7 of 32

Markus Tacker

Markus is a coder by heart and an organizational hacker by passion. As a software crafter he uses his 20+ years of experience working as a software developer, consultant, coach, mentor, and founder to build cloud-based solutions for the Internet of Things using JavaScript. His professional career has been greatly influenced by taking an active role in communities, whether as a participant, contributor, initiator, or speaker. He especially enjoys the diverse and deep discussion of the Software Craft Community. He lives in Trondheim, Norway and enjoys plowing through deep snow on snowshoes.

https://www.papercall.io/speakers/coderbyheart

8 of 32

Abstract

9 of 32

Abstract

Titel (<100 characters).

The main idea in one Tweet (~280 characters).

10 of 32

Integration testing a cloud-native application with JavaScript

In this talk I will take you through the challenge of testing a cloud-native application. I will cover the challenges when developing solutions on top of serverless components which you cannot run on your own machine and how I designed a BDD driven approach to run the integration tests.

11 of 32

5 key learnings

12 of 32

5 Key learnings

5 or fewer bullet points on the main takeaways of your talk, the most important one first.

  • If you had one thing to learn this is it.
  • I spoke about this because it really helps to understand the topic.
  • This is also important, but might not apply everywhere.
  • If you were really listening this is a cool bit to remember.
  • Stretch goal!

13 of 32

5 Key learnings

  • How the cloud native test-pyramid looks like
  • Infrastructure as code is key, because configuration of cloud-native services are part of the solution
  • how BDD can be used to write re-usable test instructions
  • to write tests that behave like real users (retry if failed multiple times) instead of programming shortcuts, because this will give better information to system design
  • use “real” test doubles backed by queues to monitor outcome of test cases

14 of 32

Keywords

15 of 32

Keywords

5-10 Keywords.

Help organizers to group talks.

Some conferences publish them.

Not all ask for them.

16 of 32

Keywords

JavaScript

IoT

BDD

Serverless

AWS

17 of 32

Notes

18 of 32

Notes

Provide more context to the organizers.

Do not appear in the public talk listing.

Use it to highlight special aspects about your talk!

19 of 32

Notes

In my current project I am building a RESTful API for interacting with the next generation of IoT devices. This solution is build on top of AWS using serverless components. Not only the implementation of the business logic is done in JavaScript, but I have developed the entire CI/CD solution in JavaScript. In this talk I will cover the challenges when developing solutions on top of serverless components which you cannot run on your own machine and how I designed a BDD driven approach to run the integration tests. It showcases that JavaScript can be used in a truly full stack manner today and that we can cover Development, DevOps and Testing with the one language we love.

20 of 32

Where to find CfPs

21 of 32

Where to find CfPs

22 of 32

Submitting

23 of 32

Oversubmit!

24 of 32

Track you submissions

25 of 32

26 of 32

#paytospeak

27 of 32

#paytospeak

If you are not getting reimburst for your expenses as a speaker there is a high chance that you are benefiting off someone who cannot afford to attend.

nataliewarnert.com/askforpay-instead-of-paytospeak/

www.cassandrahl.com/blog/why-i-dont-pay-to-speak/

28 of 32

Code of Conducts

29 of 32

Code of Conducts

There are Code of Conducts

  • “Don’t be a jerk.”

and there are good Code of Conducts

  • concrete
  • enforcible
  • and everyone has been trained

https://2019.jsconf.eu/code-of-conduct/

30 of 32

31 of 32

Links

32 of 32

Happy to help!

Twitter: @coderbyheart

LinkedIn: linkedin.com/in/markustacker

Should I review your proposal?�Send me a Google Doc!