This is a list of the articles I've published in the following platforms (not all of them are here, especially the old ones):
Vue 3 is coming with a some exciting new features. Composition API is the hottest one at the moment but there are others that excite me as much as it. One of those new features is called
Suspenseand it really excites me about the benefits it brings. You might have heard about it already but I will try to show some examples of the usage ofSuspenseand where it can be beneficial.
I'm going to walk you through the process of creating @Berlinglish, a Twitter BOT that tweets Berlin's news in English for non-German speakers. The project was developed using Javascript. It is an AWS Lambda function that has an AWS CloudWatch scheduler as trigger. The function crawls Berlin's latest news and tweets it =]
I've been doing Vue, professionally, for a while now. As usual, whenever I create/setup a new project, I use Vue CLI which abstracts a lot of the heavy weight of creating a new project, which is great, especially if you've ever tried to setup a full Webpack config by yourself. The same applies if you use other CLIs to generate your project. Nonetheless, I want to walk through the process of setuping a Webpack config by myself and highlight some benefits and drawbacks of using Vue CLI on the way. I will try to mimic as much as possible the behavior of Vue CLI but avoid the usage of its plugins for example.
How about building different versions of our applications targeting different browsers so each browser downloads only the "fallbacks" it needs? That is in short what I thought. Now I'm going to explore how is our current development lifecycle and where we can try to add this idea.
Building custom input components with Vue might sound simple but it has its gotchas and from time to time we end up going through the documentation to check some details. It can also get a bit complicated if we are not familiar with few Vue concepts.
I went through the process of creating a GitHub Action that posts a message as soon as a release happens (that is our use case) but the main topic is how you can automate things with GitHub Actions, how to reuse “things” across multiple actions and how to start “simple”.
In this article, I will summarize some understandings that I've about integrating all the tools above. The main focus is how to set up Prettier, how to set up ESLint, how to integrate both, and by the end how to add Typescript to it.
I want to highlight how we approached a migration in terms of infrastructure, which challenges we faced, and what we learned on the way.
I've always been curious about the following situation: most companies start setting up their infrastructure through AWS Console. At some point Infrastructure as Code is introduced. How do we close the gap between them? Shall we code everything from scratch?
Imagine the following scenario: you have a Bucket that will host your Frontend assets. Your Frontend lives in another repository and you use, in my example, GitHub Actions to deploy (move) those files to the Bucket. You want to give permission to your GitHub Actions to perform that and only that.