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!
I’m so confused, what JS framework should I learn?
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?
— 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.
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.
It was almost a year ago that I started building a self-destructing tweets app, just like Snapchat’s snaps…
… and nobody used it.
The not-so-short intro In 2017 I set out to create a self-destructing tweets application. Nothing impressive but it helped me learn a lot of things.
First, I set out to design it all by myself — failed miserably. At that point I reluctantly decided that the best thing to do is to use a ready-made theme.