Mario Fernandez

Being properly prepared for a negotiation is a skill that is useful in many situations. Software development is about humans, after all

Either types are great for error handling. Rust has the Result type. It's tightly integrated into the language, and simplifies robust code

Technical stories are misused. If used correctly, they help shape the technical vision. If not, they just enable skipping essential work

Rust is a trendy pick for a programming language these days. There is no better book to get started than this one

Diagrams is a neat tool to visualize your infrastructure using code. Using code allows easy modification and is version control friendly

A well-run dev huddle increases the alignment among the developers of a team. I'm going to share my experience preparing for and running it

In his newest book, Rands talks about leadership using his experience in different management roles in Silicon Valley companies

Using VPC endpoints helps keeping your network traffic away from prying eyes. I'm showing you how to provision them using Terraform

This book is an excellent source to be an effective architect bringing enterprises closer to be digitally native

How do you structure your components in a React application? I like to group mine around features close to the domain enforced by convention