Post-it notes.

I recently had a discussion with an off-shore team mate who was supposed to add a new environment variable to a client-side app and re-deploy it. He had some trouble doing this, and after talking to him and illustrating how frontend apps use env vars in contrast with Node.js APIs, he finally understood the nuances His misunderstanding was about the way Webpack manages environment variables. Being an ops person, he assumed that environment variables work the same way they do for our Node.

So here’s the deal. I started listening to some podcasts related to content marketing and social media, since I want to up my game a bit. One of the things that bothered me the most is the continuous bickering of the podcast hosts about how they avoid to go to developers because it always takes a lot of time to get stuff done with devs. So I thought I would write an article detailing the struggles of developers when they get “work” that’s supposed to be ready yesterday.

This video shows you how to enable JWT authentication for the Wordpress REST API. You will first create a kickass Wordpress development using the official MySQL and Wordpress images from the Docker hub and then go through the whole plugin setup and testing process. Below are the links to everything used in this video Info about JSON Web Tokens and the JWT Authentication Plugin https://jwt.io/ https://enriquechavez.co/ https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/ https://wordpress.org/plugins/search/jwt/ How to access the Wordpress Rest API (permalink structure setup) https://stackoverflow.

Last week I saw this very interesting Twitter thread, about CI/CD strategies for multiple teams. The question was whether or not one should go on a centralized, or a decentralized strategy for setting up continuous integration for multiple teams inside the same organization. This article tries to distil the key points of that discussion. The centralized model You might be right, thinking that going centralized is the best choice. Everybody uses the same infrastructure, the same technologies and future, cross-cutting projects can look like a breeze.

Another clickbait title from yours truly. But you already got here, so stick around. This is all over the Internet! Which JavaScript frameworks should you learn in 2018? Top JavaScript Frameworks & Topics to Learn in 2017 Best JavaScript Frameworks To Learn in 2017 Top JavaScript Libraries & Tech to Learn in 2018 I’m so confused, what JS framework should I learn? Top JavaScript Frameworks & Topics to Learn in 2017

They’re not! They’re just different ways to solve a problem. Yes, you fell for the clickbait title! But you’re already here, so why not read on? Here’s an important question: Are microservices better than monoliths? Consultant answer: — It depends. The answer depends mostly on who you ask. If you ask someone solving problems with microservices, they’ll probably answer “YES”. If you ask someone working with monoliths, well, it depends whether they know about microservices or not.

You want to be a freelancer and you would like to have a stable stream of income. You read it all over the web that you need to specialise. But you’re afraid that if you work with only one front-end framework, you won’t be able to get enough clients. I totally understand where you’re coming from, I’ve been a generalist for the biggest part of my career as a JavaScript developer and it is precisely because of this.

I’ve been working a lot with microservices in the past couple of years. It is during this time that I found how many issues can arise from putting an accent on delivery while disregarding architecture. This is why I decided to create MONOLITHSPL/T. I want to help businesses migrate their monolithic Node.js applications to a microservices architecture, improve the quality of their products as well as their overall delivery. My goal is to provide clear, actionable steps, to move away from poor architectural decisions made under pressure.

Watch this video if you want to know how I implemented a related articles section on my GatsbyJS blog. I had an ugly bounce rate on this website, and the first step towards reducing it was to offer users more articles they can read, after going through the article they initially landed on. This article will be updated in the near future, and I will also go in detail about the reason I decided to implement this and what is the benefit of offering users more articles they can go through while they’re on your site.

I got the idea for this article after solving this problem for the team I was working with, for a client. So, what’s the problem? After wrapping up work on a Swagger configuration file, and successfully generating a client JavaScript library to consume the API, we ended up with the following problem: how do we make sure that we’re able to generate the client library and use the proper environment URL, so that we don’t end up calling UAT endpoints from production, or the other way around.