TL;DR: Just want the results? Check my profile at Github.

I believe the use of assertions is very important during the software development process. It prevents //TODOs from becoming just a memory sent to the code repository and forever deposited on the shelf.

Is not uncommon to create apps that are similar or even work in apps that apply different layouts, be the reason cultural adaptation, accessibility, dark vs light theme, etc. No matter the reason you would be creating mechanisms for allowing your app to quickly changing between layouts, a well-architected code may be the difference between success and subsequent refactoring or even worse total garbage code that someone will question “may we drop this and start anew?”.

You can read it in portuguese 🇧🇷 here

This is one is a blazing fast tip, did you ever stumble in a .jks (keystore) file from a client while trying to submit to Google Play that precious app you just finished? Well sometimes, or always…. who knows, your client simply does not have the alias name and has a list of possible passwords.

Next step for me is composed of two things:

The title speaks truthfully, remote work is good but ain’t easy as people are used to thinking. Most of the current companies don’t know how to deal with it and some of them even spread horrible lies difficulting the adoption of this wonderful working style.

Being a remote developer isn’t an easy task and as such having tools to make things going as smooth as possible is a must.

Configure properly .gitignore for each project can be a huge problematic job, even more when messed up he comes back to bite us.

I’m used to classify myself as a generalist and I receive lots of odd looks from the people around me: