Exposing the tailwind configuration to be accessible in in the javascript code. This blog post is an attempt to share the problems I faced trying to expose the tailwind config, for the reader that want to jump straight into the code, the commit I used to achieve that is available on github.
Recently I’ve experienced a scenario that made my git skill in check, I was wondering if I could see the files that changed for a list of commits. From that, I tried to expand some questions around git. The goal here is to share a few git commands that are not popular like commit, push or rebase.
Recently I have been working on a simple app with one goal in mind format json content locally, without the need to access a third party website for that. The answer that that is json-tool, a electron based app that formats json content with a click of a button, or just pasting the desired json. It offers a 100% offline experience once it’s installed and the most important there is no track, ads or anything related to data. Privacy first.
Infrastructure as code (IaC) is a growing trend as the devops became the standard to delivery applications. As such, cloud providers have each, their own way of offering infrastructure, in the past, administrators had to manually execute commands on the servers and manually provide resources (which it’s the case until today).
This post goes through my journey that started at least five years ago with testable code, specifically using Test-Driven Development (TDD). I remember when I found it out it was a moment of magic, even though, it took some time for me to realize that TDD changed my way of thinking. Not just about my code, but about software development in general. Throughout this post, there are references on the first TDD international conference, XP and agile, if some of them is not familiar to you, feel free to jump to the references.
Extreme programming (XP) is a methodology focused on the technical and social aspect of software development. It focuses on two main pillars - agile and technical excellence. Technical excellence is the structure that allows teams to be agile. On the other hand SCRUM is the methodology that got traction and is the most adopted by the industry as a means to “be agile”. Therefore, as already explored by Martin Fowler SCRUM has a place in the party, but is not the main course.
