Talk title

How to hire frontend engineers

Abstract

When people don’t get job offers, they think, they are just not good enough. After working for three years in recruiting, I can assure you that often rejections happen due to randomness that you wouldn't believe is possible.
In this talk, I tell three stories where great applicants were rejected for reasons that had nothing to do with their engineering performance or cultural-fit. Based on that, I give antidotes to both job-seekers and hiring managers how to avoid these traps.

Your name

Iwan Gulenko

Means to get in touch with you

E-mail: [email protected]
Twitter: @iwangulenko

Similar talk that I gave: https://www.youtube.com/watch?v=u6PTaTDHUG4

Speaker: Mehmet Yatki
Twitter: https://twitter.com/mehmatrix
Github: https://github.com/yatki

Title of the talk:

How I accidentally fall in love with testing!

Abstract:

It may sound weird but I love testing, and I think testing has started to like me back. This is the story of my journey of accidentally becoming a real test advocate. We will explore the reasons why testing can be painful, and how to remedy them and also cover test types, test doubles and useful metrics

Motivation

This talk is mainly aimed for junior and mid-level developers.

My motivation behind this talk to share how I learned to listen to my tests, what did they say about my code and how they eventually made me a better developer.

I'd like to talk about real testing challenges and the possible ways to solve them with giving code samples.

I hope at the end of this talk, developers who are reluctant to write tests, will get excited, be more confident and have fun while testing their apps.

Draft Agenda:

3~5 minutes: my observations and findings on reasons that makes testing painful and how can we fix those reasons.
10 minutes: covering testing terminologies like test types, test doubles, useful metrics.
5 minutes: tools and the ecosystem that we currently have.
5 minutes: real world code examples, tips and tricks.

Duration: ~25 mins.

A11Y IRL (Accessibility in real life)

Abstract

The year is 2018, and accessibility is not a buzzword anymore. It’s now imperative that information is readily available to everyone, regardless of their disability or financial status.
In this talk, you’ll find out how to create accessible real-life objects, using run-of-the-mill JavaScript and the basic principles of Internet of Things.

Your name

Theodore Vorillas

Means to get in touch with you

You may catch up with me via twitter https://twitter.com/vorillas or via email [email protected]

Talk title

Abstract

Your name

Contact Details

Code of Conduct

• I've read and agree to the BerlinJS Code of Conduct

Hey y'all! It looks like I may be in Berlin in time for the August meet up. 🙌🏻 Will it be on August 16th?

Talk title

A sneak peek at BinaryAST

Abstract

Preparing this set of slides for July's TC39, so will fill in an abstract once that's done.

Your name

Lin Clark

Means to get in touch with you

https://twitter.com/linclark

Building high performance native mobile apps with Titanium

Abstract

A common misconception with cross platform tools like Titanium (or React Native) is that apps built using those technologies are less performant than native apps. And while this is often the case, the cause is rarely the technology, but how it is used.

But how do you achieve high performance for both iOS and Android? This talk will dive into common pitfalls which slow down the app or make it feel sloppy, and obviously how to avoid them and structure your Titanium app so you can avoid this.

Your name

Rene Pot

Means to get in touch with you

Twitter: @Wraldpyk
Email: [email protected]
BerlinJS Slack: Wraldpyk

ps: I'm available for December and later.

How to submit a talk to BerlinJS?

You can either comment on this issue or send us an email at (insert email address – we need an address everyone has access to)

When and where will it be?

• November 16th
• Adalbertstraße 8, 10999 Berlin, Germany

What should I talk about?

Anything JavaScript (JavaScript / JavaScript community related), that gets you excited.

Do I need to be an expert to talk?

Nope. This meetup is supposed to be fun and casual, so we want everyone to participate. We especially encourage people of underrepresented groups to apply.

How long should my talk be?

Between five and twentyfive minutes. There won’t be any formal Q&A.

What should be in my talk submission?

Your name, Twitter handle / email address, talk title and a few sentences describing what you want to talk about would be great.

What's the A/V situation?

We'll have a projector (Full HD / HDMI) and a mic for you to use. Adapters are available.

Applying visual automata-based programming to user interfaces

Abstract

1. What does it mean that user interfaces are stateful and how can we use state machines to decompose them?
2. A brief introduction to visual automata-based programming in functional JavaScript.
3. An overview of the codebase of a wizard

• The talk is around 20 minutes long.
• I gave a very similar talk a year ago at Angular Bolivia.
• All examples are written in Rosmaro.

Your name

Łukasz Makuch

Means to get in touch with you

Twitter: @zopsesen

Talk title

Talk to the customer!

Abstract

In big companies developers tends to be separated from the customers by customer support, managers, etc.

I would share a story on how a product could benefit from a direct communication between developer and customer.

Original talk in Russian is 25 minutes, but could be scaled down to 10.

Your name (and pronouns)

Roman Paradeev

• This will be my first tech talk (in English)

Contact Details

@sameoldmadness at twitter/telegram

Code of Conduct

• I've read and agree to the BerlinJS Code of Conduct

PWAs with Next.js : Configuration is king. Or is it?

Abstract

Next.js maintains a fine balance between configs and code and that helps us build websites with the important features like SSR, async data fetching and seamless integration with other libraries seamlessly. But with great unconfigurable internal config come great hurdles. Let's discuss the good and bad of the Next.js. And then talk about how we can overcome some of the hurdles or work around them to build great PWAs.

Bhargav Ponnapalli

Means to get in touch with you

Email
Twitter

Talk title

Property-Based Testing with JSVerify

Abstract

Writing tests can be tricky. How do you ensure appropriate coverage yet keep things straightforward and maintainable? Generative testing exists to reinforce your tests with hundreds of randomised checks, but it requires changing your test design mentality. This talk introduces JSVerify and its underpinnings, and will help you think less about expected results and more about general behaviour that you can test.

Your name

Luis Rodrigues

Means to get in touch with you

• Web
• Twitter
• Github
• Email

This talk is meant to drum up some interest in the upcoming tc39 panel!

Talk title

TC39: Language Design in the Open

Abstract

Have you ever wondered how JavaScript gets specified? Or been confused as to why certain decisions are made? A language like JavaScript, with a large diverse user space, is half designed, and half reverse engineered. Like all web standards, JavaScript is developed in conjunction with the realities of the web and user decisions in how the language is used and formed. This results in unique backwards compatibility issues such as the recent smooshGate discussion. This talk will discuss constraints, mediation strategies and issues that have arisen over the years.

Your name

Yulia Startsev

Means to get in touch with you

Twitter: @ioctaptceb

Talk Title

Accessbility, Inputs & JavaScript

Abstract

At the end of February, WebAIM published The WebAIM Million, an accessibility analysis of the homepages of the one million most visited websites.

The findings are depressing. The average site contains about 60 errors. Things went even more downhill when putting JS frameworks in the equation. As a reaction to those findings, this talk tries to shed light on some accessibility best practices regarding accessible inputs, as well as do soulsearching why we, as developers, have failed so badly.

Disclaimer: I have given a version of this talk at Vue.js Berlin. Slides can be found here: https://noti.st/ovl/OY4mvA/accessibility-inputs-vue

Your name

Oscar

Means to get in touch with you

o [at] ovl.design
_ovlb

Talk title

Fetch me if you can - How to handle third party API data in React, Vue, and Svelte

Abstract

Fetching and displaying third party API data has become a very popular coding challenge, either before or during interview processes. Having seen several candidates going through this exercise, I'd like to walk you through on how to do this in React, Vue and Svelte, show you pitfalls and common struggles, and explain what the interviewer wants to learn about your skill set with this approach

Your name

Marco

Contact Details

@MaPagni

Code of Conduct

• I've read and agree to the BerlinJS Code of Conduct

How to submit a talk to BerlinJS?

You can either comment on this issue or send us an email at (insert email address – we need an address everyone has access to)

When and where will it be?

• March 15th
• Adalbertstraße 8, 10999 Berlin, Germany

What should I talk about?

Anything JavaScript (JavaScript / JavaScript community related), that gets you excited.

Do I need to be an expert to talk?

Nope. This meetup is supposed to be fun and casual, so we want everyone to participate. We especially encourage people of underrepresented groups to apply.

How long should my talk be?

Between five and twentyfive minutes. There won’t be any formal Q&A.

What should be in my talk submission?

Your name, Twitter handle / email address, talk title and a few sentences describing what you want to talk about would be great.

What's the A/V situation?

We'll have a projector (Full HD / HDMI) and a mic for you to use. Adapters are available.

Handling a JSONP nightmare

Abstract

Based on this blog post (https://medium.com/@viniciuskneves/handling-a-jsonp-nightmare-3865c9d8bfdd) I want to show how I implemented a solution for a big problem I faced using JSONP once.
I know JSONP is quite an old topic but I think it is interesting and it shows how you could deal with some CORS issues in the past, especially for third-party integrations.

Your name

Vinicius Kiatkoski Neves

Means to get in touch with you

BerlinJS Slack: viniciuskneves
Twitter: @viniciuskneves

The CITGM Diaries

Note I'm already speaking in town this week, so I'd prefer that if there are other newer speakers who would like the opportunity that it be given to them, I wanted to offer some content just in case. It is not that I wouldn't love to talk, just don't need to hog the stage :P

Abstract

The Canary in the Gold Mine is a smoke testing utility that automates running
unit tests of various various modules in the Node.js ecosystem, it must pass for
all controversial changes and releases. CITGM has been incredibly successful,
finding all sorts of regressions across the ecosystem and in node core itself.

I have kept a diary of all the weirdness, lets examine how things break!

A bit more info

The Canary in the Gold Mine (CITGM) is a smoketesting utility used by the Node.js
project to test for ecosystem breakages. CITGM is able to download the source of a
module published to npm, install all the dependencies, and run it's test suite. When
the project is going to make a release or land a controversial change we are able to
automate the test suites of 70 of the top modules in the ecosystem to confirm we are
not causing unexpected breakages.

This talk will outline how CITGM works, how it fits within node.js CI, and some of
the interesting edge cases we have experienced. We will dig into the architecture of
the utility itself and look at how it is set up in Jenkins. We will also do 3
different case studies of major breakages that would not have been found with CITGM.

@rmehner I write some notes down, from our discussion after the last talk.

Primary goals:

• No dev setup of ruby or node for the user, ideally the users only needs a browser
• Ideally the user doesn't need any social account (github, twitter, etc.) at least an email
• A preview of the website with the submitting talk for the user
• Accepting the talk via a pull request on github (current state)
• Deploying website via github pages (current state)

Content the user can type in:

• title
• name (optinal with an link to twitter, etc)
• description with simple formatting (markdown)
  • regular, bold, italic, links, quotes

Please let me know if I misunderstand or miss something

How to submit a talk to BerlinJS?

You can either comment on this issue or send us an email at (insert email address – we need an address everyone has access to)

When and where will it be?

• February 15th
• Adalbertstraße 8, 10999 Berlin, Germany

What should I talk about?

Anything JavaScript (JavaScript / JavaScript community related), that gets you excited.

Do I need to be an expert to talk?

Nope. This meetup is supposed to be fun and casual, so we want everyone to participate. We especially encourage people of underrepresented groups to apply.

How long should my talk be?

Between five and twentyfive minutes. There won’t be any formal Q&A.

What should be in my talk submission?

Your name, Twitter handle / email address, talk title and a few sentences describing what you want to talk about would be great.

What's the A/V situation?

We'll have a projector (Full HD / HDMI) and a mic for you to use. Adapters are available.

I love components, but wherever they exist, good markup is: (a) often forgotten, (b) essential for accessibility. But which markup is ‘good’? It would be an honour to come and talk about this.

Keywords

components, accessibility, design systems, HTML

Abstract

It's the markup that matters

Modern JavaScript frameworks virtualise our DOMs. This allows us to focus on implementation, as data declaratively maps state into markup. While this is great in itself, the significance of the actual markup often gets overlooked. In this practical talk, Hidde will show how specific bits of markup provide real benefit to users.

About me

• Previous talks
• Freelance front-end developer / accessibility nerd, currently at Mozilla and the City of The Hague (Netherlands) (bio)

Talk title

Styleguide Driven Development

Abstract

Apps rapidly change and their UI is getting more and more complex. We constantly have to add more UI components. These components usually start as static sketch files from the designer. Developers then try to add them directly into the app while writing them. To accomplish this, they need to run the full application and dependencies like backend services. While a component is developed, there is also no way for the designers or POs to look at them.

With my talk I am proposing a development workflow that incorparates a "living" styleguide. I am going to show how easy it is to add the storybook styleguide to your project and how it makes our lifes as a developer easier while making others happy :)

Your name

Philip Stewart

Means to get in touch with you

Twitter: @sodoku

Suggestion: Community Mic

Last time I attended Berlin.js, other than enjoying the wonderful talks, I was hoping to come across someone to take over maintaining an npm package that I own.

Knowing the vibrant JS community of Berlin, I knew there is someone who would be interested. But, walking up to people one by one, and telling them about the npm package individually, was not the easiest way to find that person.

That's when I realized that maybe Berlin.js could benefit from the Community Mic idea that some other meetups have adopted.

Community Mic, is a short slot of time in the middle or end of the meetup, where a few of the attendees can take the mic for no longer than one minute each, and ask others to join them on an open source project, or help them with a technical challenge that they're stuck on, or get feedback on some code that they've written, or maybe just announce that they're new in town.

I've seen this idea working wonderfully at the DesignLab meetup for example. Out of about 50 attendees, usually only 2 or 3 come up to take the mic, and everybody so far has respected the time constraint. Plus, when people ask for help at the mic, they really do get support from the audience. So it's a great way to nurture the community.

As to whether it's okay for people to announce that they're looking for a job, or announce an open position, I do not have an opinion. Those announcements are allowed at DesignLab, and I haven't seen people abuse the opportunity.

Talk title

If you haven't use Ember.js before its the right moment to try.

Abstract

You might ask, isn't Ember.js dead now? Isn't it gone in vain and only crazy guys left supporting some legacy applications hoping to rewrite everything in React and Redux? Dead wrong.

Although Ember.js was around for 5 last years, it wasn't a mainstream ever. Mostly due to the fact that no big companies with unlimited marketing resources were supporting it. But last year, after LinkedIn invested a lot into Ember.js it starts gaining momentum. It used also in Netflix, Heroku, Digital Ocean, Intercom and Siemens.

Maybe you have make a closer look to this framework? And if yes, where to start?

Your name

Iaroslav Popov

Means to get in touch with you

chilicoder in berlin.js slack
https://twitter.com/chilicoder
@chilicoder

Talk title

Build More with WebAssembly

Abstract

You can build amazing apps in the browser, but there are some (like a video editor) you wouldn't dare to build - until now. WebAssembly (wasm) gives you the ability to push the limits of the browser. Together we'll learn how to integrate wasm into existing JS code to build new kinds of experiences.

We'll take a look at the various reasons to use wasm from improving existing JavaScript libraries to rewriting entire applications. We'll examine what the state of wasm tooling is and just how easy starting and maintaining a project in wasm can be. Finally we'll improve an existing JavaScript library by using a wasm module written in Rust.

Your name

Ryan Levick

Means to get in touch with you

https://twitter.com/ryan_levick

Talk title

Conducting Effective Code Reviews

Abstract

Code review is serious business. It is one of the defenses against introducing bugs into the codebase. In this talk, I will talk about:

• What can machines auto code review for us and why
• What should a human check while reviewing (common errors, best practices, etc.)
• How to communicate in the progress of code reviewing

I prepared a blog post about this, currently in editorial review to get published at Auth0 blog. I'll base my presentation out of that.

Your name (and pronouns)

Umut Benzer (he)

• This will be my first tech talk (in English)

Contact Details

@UmutBenzer
[email protected]
benzer.dev

Code of Conduct

• I've read and agree to the BerlinJS Code of Conduct

Talk title

Love your Junior

Abstract

Ninja-Rockstar-Senior recruiting madness is still very much alive despite how ridiculously hard it is to find available talent. The demand for developers is insane and at the same time there's a lot of smart but inexperienced people eager to work on something, but too few companies are looking in their direction. Everybody wants to hire the top notch devs and launch ASAP.

Fortunately, we are all seeing a slow but steady growing interest in Juniors and building teams from the ground up. In the last few years I've been working a lot with them and I'd like to share the many things I learned along the way. What should be our role as seniors and mentors? Why should we want juniors in our team? And how many of them are enough? How can we help them become productive as quickly as possible, in a healthy and effective way?

Your name

Luis Farzati

Means to get in touch with you

https://github.com/luisfarzati
https://twitter.com/luisfarzati

Talk title

Javascript ecosystem is bigger than it is used to be and there are a number of options. But what about if we choose the best/optimum alternatives to have something done or not?

Abstract

Sometimes it can be a problem to start from somewhere to immediately prove the concept of what we have on our minds in terms of architectural decisions, tech stack and the other tiny but critical details. Steps to deliver a new "thing" may be a problem if the choices are made in a wrong/immediate fashion. So I would like to tell the very first steps to know the balance what a greenfield project needs and how developer gets satisfaction from what she/he will build.

Your name

Baris Guler

Means to get in touch with you

[email protected]
https://twitter.com/hwclass
https://github.com/hwclass

Talk title

Cycle.js: UI as Pure Functions of Time

Abstract

What if we considered Time as a fundamental input of our programs

Your name

Thomas Belin

Means to get in touch with you

Twitter: @atomrc

This url http://lanyrd.com/2014/berlinjs-november

Don’t marginalize your hard work! or, a systematic approach to white space

Abstract

In this talk I'd like to highlight what's the cause of common white space issues and how proper naming, categorization, and separation of concerns leads to consistent and reusable white space.

Your name (and pronouns)

Łukasz Makuch (he/him)

Contact Details

https://lukaszmakuch.pl
@zopsesen
https://github.com/lukaszmakuch

I don't mind linking any of these, I think that'd very nice of you. 🙂

Code of Conduct

• I've read and agree to the BerlinJS Code of Conduct

Talk title

Improving User Experience using TensorFlow.js

Abstract

25 minute talk: I will a use case where machine learning directly in the browser makes sense. We will use TensorFlow.js to use neural networks for the model.

Your name

Oliver Zeigermann

Contact Details

@DJCordhose

Code of Conduct

• I've read and agree to the BerlinJS Code of Conduct

Talk title

Replacing Redux with React's Hooks and Context APIs

Abstract

The most common reasons for using Redux are:

1. Sharing state with deeply-nested components while containing global state in a single place.
2. Giving deeply-nested components the ability to apply "actions" to the global state.

Now that Hooks and Context APIs are stable, we can accomplish this without Redux.

Introducing use-flux: a light-weight package for declaring and consuming global stores using a flux-like pattern of state transformations.

This talk isn't really about convincing you to use use-flux, but it is about demonstrating the structure of a React Hooks package!

Your name

Spencer Rudnick

Means to get in touch with you

✉️ [email protected]
🐦 @spencerfordES
⚛️ https://spencerudnick.github.io/use-flux

Talk title

Feature Driven Architecture

Abstract

Large applications cannot be structured the same way as small applications. Many good decisions you make for a small application suddenly become bad once it grows in code and organization size. Let me walk you through a number of challenges and good decisions for scalable applications.

Your name

Oleg Isonen

Means to get in touch with you

https://twitter.com/oleg008
[email protected]

P.S. This is a dry run of a talk I will be doing at reactdayberlin, so I hope to get some feedback and improve it.

How to submit a talk to BerlinJS?

You can either comment on this issue or send us an email at (insert email address – we need an address everyone has access to)

When and where will it be?

• April 19th
• Adalbertstraße 8, 10999 Berlin, Germany

What should I talk about?

Anything JavaScript (JavaScript / JavaScript community related), that gets you excited.

Do I need to be an expert to talk?

Nope. This meetup is supposed to be fun and casual, so we want everyone to participate. We especially encourage people of underrepresented groups to apply.

How long should my talk be?

Between five and twentyfive minutes. There won’t be any formal Q&A.

What should be in my talk submission?

Your name, Twitter handle / email address, talk title and a few sentences describing what you want to talk about would be great.

What's the A/V situation?

We'll have a projector (Full HD / HDMI) and a mic for you to use. Adapters are available.

Talk title

Adaptive Image Loading

Abstract

The web has seen incredible growth over the past decade - an increase that enabled remarkable technological advancement. There are developer tools and frameworks out there that can do magical things and unfortunately, therein lies the problem. With this explosion of new tools as well as myriad device types, we are faced with another problem - performance.

In this talk, we'll explore a concept based on Network Information API, Service Workers and Cloudinary to enable web applications to serve lower quality images (if necessary) in order to speed up the perceptual load time of the web app when on a slower connection.

Your name

Tamas Piros

Means to get in touch with you

Twitter: @tpiros

Talk title

Property-based testing: You won’t look at your tests the same way ever again

Abstract

Property-based testing changes the way we look at our test suites. Instead of specifying test cases one after another, this advanced testing technique enables us to automatically generate a stream of inputs. Despite its potential, property-based testing still remains under the radar within the JavaScript community. Let’s try to uncover its strengths together.

The talk will discuss how property-based testing compares to traditional testing methods and demonstrate its principles with simple examples. In order to bust the myth of the inapplicability of property-based testing in a real-world setting we’ll bring up some use cases from industry. Finally, we’ll wander into the world of concurrency and the automation of race condition detection.

Your name

Jan Stępień

Means to get in touch with you

I'm at https://janstepien.com. On Twitter I'm @janstepien.

May 17th works! 😄

Talk title

Monorepos with lerna.js - 3 Examples

Abstract

With serverless, component based web architectures and other new 'hipster' tech, the use case for monorepos is strong - repositories encompassing whole projects are not so much the exception anymore and they keep the friction between teams and disciplines low. I want to present 3 usecases for lerna.js monorepo projects:

• a website project migrated to a mono repo
• serverless web application on AWS
• General web component application

Your name

Sebastian Schürmann

Means to get in touch with you

Respond to the GH issue pls. No problem with public comms

Talk title

What should I use - Static pages, SSR or SPA? Maybe Prerendering?

Abstract

Nowadays there are different approaches on how to ship frontend to a user -

• Static pages export;
• Prerendering;
• Server Side Rendering;
• Single Page Application;

In the talk, we can review them, discuss pros & cons (build time, release time, performance, cost) and match those approaches to popular frontend libraries.

Your name

Oles Maiboroda

Means to get in touch with you

[email protected]

Yet another talk about async/await and promises

Abstract

Based on this blog post: https://dev.to/viniciuskneves/yet-another-post-about-asyncawait-and-promises-49gg

Walk step by step on how Promises and asyc/await are connected with an example from a real question asked on Slack.

Your name

Vinicius Kiatkoski Neves

Means to get in touch with you

BerlinJS Slack: viniciuskneves

Talk title

Functional Programming + React = ❤️

Abstract

Everyone has heard about Functional Programming sooner or later but not many people have seen it in action. I'd like to show you some of our real React code examples that leverage the power of FP to become readable and reusable and make you a better programmer in general!

Your name

Sebastian Herrmann

Means to get in touch with you

Twitter: @herrherrmann
(Feel free to include it on the website!)

Doing this as an issue for now as index.html contains Februarys talks.

Potential description:

In the last couple of weeks I spent some time playing with Clojurescript learning about how to build UIs in a functional way.
Amazed by the things I encountered on that field-trip I want to introduce you to some of the basic patterns and ideas and compare them to more traditional approaches like MVC.
Probably there will be some code but I want to focus on the concepts rather than specific implementations.

Any feedback/suggestions appreciated :)

Talk title

Testing ES6 modules with Introscope

Abstract

Testing ES6 modules can be tuff, esp. if the module has small public API but rich internals. We in my team at Zalando developed a babel plugin (called Introscope) helping to look inside any module turning it into a factory function. This helped us develop some cool techniques for more or less robust side effects based testing with mocks, spies and Jest snapshots.

Your name

Peter Leonov

Means to get in touch with you

Here is my mostly abandoned Twitter: https://twitter.com/peterleonov
And just in case Github follows Skype: [email protected]

Talk title

You’re joining a project

Abstract

If you’re starting on new (for you) project it’s alway nice to enable “GPS” and see what the project is and how “healthy” it is.
In the talk we’ll go through some tips which can give you insights of the project's state:

• How big is it? Number of Lines of Code and comparison to popular libs/projects;
• How old is it? Date of first commit;
• How complex is it? Code complexity metric;
• Who was contributing in it? I.E. Github insights;
• Is it performant/accessible/seo-friendly? With Google Lighthouse;
• Is it easy to release? Build time of a project;
• Are the dependencies up to date? With npm outdated;

These and other metrics will give you a knowledge about the project you’ve joined and turn on the GPS, so you can navigate the project to success.

Your name

Oles Maiboroda

Means to get in touch with you

[email protected]

Talk title

Hooks everywhere - Apollo/GraphQL is no exception

Abstract

The fame of Apollo/GraphQL and React Hooks are increasing every day. Many have already started using both in production. Now React hooks are possible in Apollo Client as well. Anyone who used Render props pattern of Apollo client will definitely love the way how hooks make the code readable and elegant. My talk will be on how to use hooks with Apollo client.

Your name

Vilva Athiban P B

Means to get in touch with you

twitter - @vilvaathibanpb
email - [email protected]

You may link my twitter to your page.

Enforceable environment variable contracts at runtime

Abstract

A library that enforces a schema for enviornment variables that is enforced at run time (and also compile-time if using TypeScript). Able to use rich-types such as enforcing high-entropy passwords or real URLs, as well as grouping common envvars together.

https://github.com/freight-hub/TypedEnv

Your name

Brian Graham

Means to get in touch with you

I'm on GitHub more than social media.

LoveBits - using code poetically, by writing (runnable) code poems

Abstract

LoveBits is about writing code poems written in JavaScript, to show that code is more than just a functional language. It's about showing that code can even be used poetically, to tell stories.

Would tell a bit about how the project came to be, show pieces of code, and the interactive parts, when the code poems become interactive.

https://lovebits.bilebile.net/

Murat Kemaldar

@murimuffin5 (Twitter)
[email protected]

Let me know what you think, looking forward for some feedback :)

Grammar of Graphics and Functional Programming in Data Visualisation”

Abstract

Sometimes libraries with charts are not enough - they lack customisation or don’t support that one chart type you would like to render. You can always create a custom graph and I’d like to show the audience basics and tips on how to create such custom data visualisations.

Grammar of Graphics gives us a great framework and mental model for creating charts. We can learn how to encode data on screen using marks, scales and channels. All these abstractions could be implemented easily using UI components and functions.

The presentation would be targeted at data visualisation novices and I would use React for examples on slides, but these techniques are applicable to all common, component-based frameworks - I used this approach in React and Angular with great success.

The Audience will learn about Grammar of Graphics and obtain tools to create great custom visualisations. It will enable them to create impactful charts when common libraries won’t suffice.

About me

I’m a frontend developer who has worked with data visualisations for 5 years
and I've been a web developer for 8 years. Currently, I work for Allegro as the main maintainer of data exploration tool turnilo: github.com/allegro/turnilo

Details

It will be my first talk in English. My previous talks in polish are here with slides and few with recordings. The talk will take 20-25 minutes.

Hey! I'll be giving a variation of this talk at a conference in the US in September. I'd love the opportunity to give it a test run in August if y'all are interested :)

Talk title

Making Weird Physical Art + Games With Cross-Platform JavaScript

Abstract

How can we use JS to make weird games and interactive art installations? “Hello, Operator!” (https://lazerwalker.com/hellooperator) is a game made for a physical telephone switchboard from 1927. I'll talk about why prototyping both on- and off-hardware matters for projects like this, how I used JS to build a cross-platform game engine that runs anywhere from a CLI to an iPad to 100-year-old hardware, and at a high level how anyone with JS skills can get started with hardware.

Your name

Mike Lazer-Walker

Means to get in touch with you

https://twitter.com/lazerwalker
https://lazerwalker.com

Web frontend security

Abstract

An overview of frontend security related things that every web developer needs to know. It explains common attack methods and how to take precautions to prevent them. This presentation will explain what XSS, CSRF, Clickjacking are. It'll mention about preventative strategies and mention about CSP, HSTS, JWT, HTTP-Only Cookies on the way.

Your name

Umut Benzer

Means to get in touch with you

[email protected]

Talk title

How to connect 1980 and 2019 with a Chrome extension and Chrome Native Messaging

Abstract

At Doctolib, we need to interface with different kinds of softwares, from SAAS platforms to native softwares developed in 1980. Almost none of these are meant to allow communication with external tools. We've setup an API using a Chrome extension and a nodejs binary deployed on the machines of our clients to connect with these softwares.

During this talk, we'll speak about how to create a Chrome extension allowing to do such actions. We'll also talk about the deployment of a binary written in Javascript and embedding a Node.JS runtime with PKG to communicate using Chrome Native Messaging with the Chrome extension.

This is a 20min talk in two complementary parts (Chrome extension/native binary) with two speakers.

Your name

Matthieu Kern (@matthieukern)
Quentin Ménoret (@qmenoret)

Means to get in touch with you

Our emails:

• [email protected]
• [email protected]