Of course, being busy resulted in learning new stuff, so I want to share them with you, as always 😊
Here Riccardo presents us with a really interesting remark – just how performant are all Array methods that enable us to transform data in a readable way? It’s worth reading because the conclusion gives you really meaningful insight into how you should manage your data and what to watch for.
Sebastian presents us with basic concepts of memory leaks in our applications and what are the dangers when dealing with JS. We get to know how the memory is managed internally and what are the most common sources of memory leaks in JS. There we can also find a thorough tutorial on how to detect and track memory leaks with Chrome’s DevTools.
I was recently interested in finding a technology that enables creating interactive tour guides through your app. Shepherd.js is exactly that. Above link gives us a little demo of the library’s functionalities. You can use it with plain JS and with popular frameworks using corresponding wrapper library.
Nothing more misleading. We still have boundaries in our application, where unexpected data can slip in and destroy our delusion of safety. I experienced those situations myself. Those boundaries may be for example your services, that communicate with external REST API.
Lately, I found two solutions (libraries) to solve that problem. One of them is “io-ts”, that enables us to create runtime types, that decodes our objects and checks, whether they have the right structure during runtime.
Here we have another solution for the above problem – “ts.data.json” library. It introduces JSON Decoders concepts known from Elm. It allows us to manage a set of decoders for primitive data types and compose our own for decoding (validate) our data.
The article explains just how severe our problem might be and gives us a thorough example of how to use a custom JSON Decoder to our advantage.
Matias shows us an interesting concept of how to model an application’s state with TypeScript’s union types. It’s inspired by how The Elm Architecture works.
I wonder just how we could use those concepts in Angular. Leveraging Functional Programming concepts in Angular may result in something really interesting.
Here Max does a great job explaining core concepts of Svelte compiler. “Svelte” is a buzzword I hear a lot lately, so I wanted to try that technology myself. As always, I got a great tutorial, that is an intro to Max’s full course on the Udemy.
A great, enthusiastic and fun talk on how we can leverage machine learning in web development. We get to know necessary basics concepts of machine learning, available tooling and what are the use cases in web dev. I’m really glad Charlie presented us with so many interesting example apps that show entirely different use cases. Those just proved her point of how diverse the topic really is.
I was always wondering what all those people on Twitter use to create their pretty code snippet images. Now I finally got the answer! “Carbon” lets you set up your code snippet to share with others with little customization steps (like color theme and background) for the most popular languages.
Recently I heard the term “DX” or “Developer Experience”, read about it and found the concept really interesting. Developers being your client targets are a lot different from other applications’ users and there's a lot to do to make them happy. I wasn’t aware of those concepts but found insight to them within the article made by Sam.