Browse 462 talks from our meetups. Covering everything from JavaScript fundamentals to cutting-edge frameworks.
Showing 12 of 462 talks (Page 17 of 39)
Tech is neither good or bad, it's the people behind them that choose the kind of impact they can make. Being a tech professional, how to contribute to shaping a better future for all of us? How to partcicipate in social impact and climate change fight efforts through your daily decision making at work and beyond? Van Anh will share with you practical advise on how you can play your role in saving the world as tech professional, trough small and giant steps. You choose which one you want to take first!
It seems that besides skills in technology the level of cooperation in teams is a strong predictor of the project's success. Many delivery issues could be avoided if the communication between team members was better. I would like to share some hints and observations on the patterns and anti-patters of working together in developing software.
There is a lot of guides like "Build Your first React Native app", but… the first application is always easy. The fun begins with the second one, when You want to build something more than just a simple todo app :) I will try to introduce You into the React Native development using my own experiences, and explain how it really differs from developing the Web application. Let's go trough the top components, real issues and some surprises that can (and surely will!) met You, when trying to write a real React Native application.
Tips and tricks how to use types to make your code better.
Most of us created some sort of to-do app in our life. Let's imagine we've been given a task to create one. Pretty simple huh? But there's a catch...
Can we count CPU instruction for JavaScript and websites? Can it be a more reliable performance metric? Could it be be a less noisy Lighthouse buddy? Can we wrap it into a CI feedback loop for a developer who cares? Why would we do that? RAIL like and Lighthouse metrics are amazing, but they depend on networking and can be noisy. Let's try to build a workflow where with every commit we can measurably improve performance for our users.
When developers are talking about scale issues, they usually mention auto-scaling groups, load balancing or shedding, bundle size, code splitting, chunks caching, availability zones, and so on: not everyday pieces of a codin' cake. The truth is that, however, scale issues are not so distant as they may seem. This talk tackles user experience and design patterns at scale, from the perspective of simple elements, like a picker (HTML select), in large applications. How does such a trivial element affect overall scalability?
Sometimes (well, always) products evolve, face the new requirements, and your legacy views designed in old good times start to work not so fine as customers expect. To solve this you have two ways - rewrite everything from scratch (which usually makes stakeholders furious) or try to improve the existing codebase to ensure it meets the new expectations. Here we will tell you how we started to suffer from performance problems in Wrike Workload - one of our most heavy and complex views in our product, how we improved its overall performance in a few months, and what tools and technologies we used for that.