Hello there, this is the second episode of the dataviz-project where I am trying to record the steps I take to bring a legacy app into a better state. If you haven’t seen the intro, you can have a look at it here. For this episode I started to change a bit how the test strategy is approached in the code. In the previous episode one of the goals was related to the testing library - here we will start to do that.
Building software is hard, building software that users love and actually deliver value is even harder. For long, the software industry suffered (and still suffers) for lack of communication between technicians and business, leading to different approaches of how to get them on the same page and build. Even with the advent of the agile manifest it alone, can’t do the job. Tools and techniques are needed to fill in this gap. Impact mapping is a book that focus on the impact, regardless of the business, and by that, the author means impact, not features.
In this blog post we are going to focus on four more of them, named The mockery, The inspector, The generous leftovers and The local hero. Each one of them focus on a specific aspect of code that makes testing harder.
Reading is part of my routine, I try to read as much as the time allows me and in 2021 I could finally achieve the goodreads challenge, reading 14 books along the year. In 2020, I shared the books I read, but I couldn’t meet my goal of 12 books. As I enjoyed writing about the 2020 books, I am doing the same style in 2021, here is a short list of the books I read and the references I came along the way. Some of those have its own blog post just to go through the details and what...
2021 was a different year for me, taking the time to write more than I did last year, code more and learn a bunch of things that I didn’t know. In this blog post I will try to resume what the year was for me in numbers. You might be asking, which numbers? From where? Those numbers are essentially from blog posts I wrote, goodreads, from wakatime and google analytics. Wakatime is a tool that I use on the daily basis to track where I am spending my time, in which projects and in which programming languages. Goodreads is the...
Recently I read the book Growing Object Oriented Software Guided by Tests and had a few ideas on how to approach things in a different way, thinking on testing from end-to-end, from the start - I relate this approach to the London school of TDD, also known as outside-in TDD. Even though the style is well known in the industry, getting a proper setup is not something standardized - at least, I couldn’t find any. On one hand, it vary for different programming languages, for example, java uses junit and selenium whereas in PHP it could be PHPUnit and Behat,...
Currently, I am working on a project that uses vue.js + nuxt.js. This project itself triggered me back to this data-viz (data visualization) project of mine that could help me get familiar with vue.js ecosystem again and bring me back the joy of using it daily. In a nutshell, I am writing this post to expose my intentions and what I will do along the way, in this episode 1, we are going to dive into the adventure.
In this post, I am going to share the main topics that I picked from the book and try to exercise my brain while I do it. Feel free to leave a comment with any feedback you might have. I will try to keep this post up to date as I find new information that adds to the content. Note - Felienne recorded a podcast focused on the book on the tech lead journal podcast.
Microservices are a popular subject among developers and business, the idea of scaling and moving different streams of work forward at the same time shines in the eyes. Therefore, with the shift of how we architect applications, the challenges and tread offs should be carefully analyzed. I personally like books about strategy to migrate legacy systems and bring them up to date in terms of technology. I wrote about testing strategies for code bases that are big but without any tests. On the other hand, having a book describing possible migrations related to databases is something that I value as...
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.
