Hello!

This is a collection for mypersonal notes for Vue 3 Composition AI course from VueSchool.io, there is an attempt to collect the most important bits from the course and mix it together with another known sources to help getting the hands on the composition API.

Recently listening to the podcast Agile for humans that I often listen to, as I like to understand different aspects of software development. In both hosts have a series in which they answer questions from the audience, usually the episodes are fast and to the point, without much details or talking through the subject. The episode “YDS - Should the Scrum Events Be Entertaining?” was a mix of bouncing ideas (in the short time both of them had) and trying to focus on an outcome for the audience and the conclusion was a straight - they should be effective. In...

As I navigate towards other approaches of testing software, I see that there are some arguments in favor of testability. For example, cucumber names ports and adapter as a testable architecture. In the fourth edition of the book software architecture in practice the chapter 12 dedicated to tstability elaborates on what might be a testable architecture and list its attributes rather than name a single architectural style. The importance of listing attributes depicts a broader picture which leads to other architectures also being labeled as “testable” besides the ports and adapters.

Difficult conversations is a book that anyone at any stage of their life could read, this is not just a book about leadership or management, it goes a step further into the relationships that we have. Relationships that requires difficult conversations, be it with your children, your boss, your parents and even yourself. You should be the most interested in the feelings you might go through when a challenging idea is put in place and when disagreements occur. In that case, what should we do?

Vitest was born from vuejs ecosystem and rapidly started to evolve to other communities, such evolution, leads to a friction when migrating or even when trying to make tools to work together. In Jest, testing-library works automatically, no much effort needs to be done. On the other hand, trying to combine, testing library and vite, might bring some challenges. The aim here is to go step-by-step to configure vite and testing-library in an environment that uses typescript.

As opinionated as it can be Escape velocity gives some insights on metrics that can be used in “agile” (whatever agile means in a given context) teams. From the start a distinction is made from velocity and value. On one hand, the way the author depicts the chasing for speed rather than added value is surrounded by his examples that he might have faced in the real life, while on the other hand, he also makes clear that story points are relative to a given context and that the team can also game this metric (as any other).

Measure what matters is a collection of success stories from different businesses that adopted OKRs (Objective-Key-Results) in order to get people aligned and focus on what matters the most for the business. Believe or not this is not as easy as we think, as we will see later on companies struggle with that. John Doer worked at Intel when he was first introduced to OKRs by Andy Grove (as he labelled him the OKRs father) and in this book he describes what the OKRs are made of and why you should use them.

In an agile environment the way that stories get sliced are key to deliver value and increment the product the team is working on. As such the technique used to split the work and get a continuous flow is key. The story slicing focuses on the vertical slice that can give the most value to the end product as possible.

Microservices have gotten attention in the industry since its inception. The idea of having independent deployment, scalable services, and rapid interaction was quickly spread across developers and among decision takers in the software community. Therefore, such advantages took more attention than its counterparts, leading to the microservices hype and later on to the reflection on the learning that the community got. For example, some interesting things happened when a big open source project tried adopting microservices and had to go back to the monolith.

Recently I’ve been working on a side project called “Social publisher”, the goal is to allow developers to schedule posts and then having a tool to publish the scheduled content automatically. Some of the tools already in the market does that, but they require paid subscription whenever a limit of scheduled posts has been reached (talking about hootsuite). The idea with social publisher is to avoid such limitations and offer seamlessly sharing tools.