Last updated Jun 11, 2023 Published Jul 9, 2016

Hello!

As a hobby he likes to play with Raspberry PI, to dive into the IoT world and sometimes to give talks. Besides that he's an aspiring researcher focused on software testing and gamification. Testable, is a gamified tool that aims to improve the unit test teaching, trying to change the boring perception that developers have in learning how to test their code, you can find more things related to that in the playlists I share on youtube and also on my side projects page. Currently he's working as a Software craftsperson at Codurance, changing the way people build systems and trying to close the gap between academia and the industry. Want to stay tuned on software development? Sign up on my newsletter "Papers of the week".

Academic background

EN publications

PT-BR publications

E-books

Books

Certifications

Current tech stack

Keep in touch

Recent posts

Code retreat 2023 - a debrief

Unleash your coding potential with a code retreat, an immersive day of learning, collaboration, and technical growth. Join fellow developers as you tackle coding challenges, master new techniques, and forge valuable connections. Experience the transformative power of refactoring and emerge with enhanced skills, ready to elevate your coding prowess.

The history of test doubles

Test doubles are objects that are used to replace real objects in tests. They are used to isolate the code being tested from its dependencies, to simplify the code being tested, or to speed up tests. There are five main types of test doubles mocks, stubs, fakes, dummies, and spies. Mocks are used to simulate the behavior of real objects. Stubs are used to provide canned responses to method calls. Fakes implement the same interface as real objects, but with simplified or simulated behavior. Dummies do nothing. Spies track how real objects are being used.

Live coding with web workers an experimental code kata

This article describes a coding dojo about web workers and test-driven development (TDD). The authors started by introducing web workers and their benefits and drawbacks. Then, they implemented a simple example and a more complex example to explore the limitations of JavaScript and how web workers can improve performance. In the second part of the dojo, the authors applied TDD to refactor their code to use web workers.

Tidy first? Software design by Kent Beck

The book starts with the tydings which are a decent of refactoring but with a focused area and not that much of showing concrete code, the key is to understand the concept. In the second part Beck goes towards a more professional point of view talking about managing the tydings, the chapters in this section provides tips on how to go to start, and keep tyding the code base. Many of us (programmers) usually get lots of changes and forget about the focus of why we are tyding things, this part is to help programmers to avoid this situation. The...

Cracking the Code: Unveiling the Traits of a Great Software Engineer - Paper Review

Contribution of the paper is the understanding of software engineering expertise as viewed by experts software engineers.

A Deep Dive into Vue.js Composition API: My Personal Handbook

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.

The lack of leadership and the focus on process in an agile environment

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...

Is there a testable architecture?

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.

See more