Gui Ferreira

The 80/20 Rule (Pareto Principle) is the secret weapon of the world's most efficient dev teams. Here's why you're likely wasting 80% of your energy.

Every line of code you subtract is a line you don't have to debug, document, or maintain. Subtraction isn't "losing" work, it's "winning" focus.

The 80/20 Rule (Pareto Principle) is the secret weapon of the world's most efficient dev teams. Here's why you're likely wasting 80% of your energy.

Yet, we spend months building "edge-case" features that are used once a year. We add layers of "just in case" code that nobody ever reads.

The 80/20 Rule (Pareto Principle) is the secret weapon of the world's most efficient dev teams. Here's why you're likely wasting 80% of your energy.

System design for Agentic AI. A helpdesk triage agent that retrieves facts, calls tools, and knows when to hand off.

The biggest mistake in tech: Starting with the "How." Dev: "I want to use Rust/Microservices/AI." Lead: "Why?" Dev: "Uh... because it scales?" (This is retrofitting).

The Master's Path: 1. Start with Why (The mission). 2. Define How (The technology). 3. Only then choose What (The outcome).

The biggest mistake in tech: Starting with the "How." Dev: "I want to use Rust/Microservices/AI." Lead: "Why?" Dev: "Uh... because it scales?" (This is retrofitting).

We pick our favorite "toys" (the How) and then hunt for an excuse (the Why) to use them. Simon Sinek calls this the Golden Circle, and most devs have it backwards.

In 2014, WhatsApp had 900 million users. How many engineers do you think it took to handle that scale? 5,000? 1,000? Not even close. It was 50.

Because their vision was simple, their software could be simple. And because it was simple, it was reliable. You cannot have 99.9% reliability on a system that no one understands.

In 2014, WhatsApp had 900 million users. How many engineers do you think it took to handle that scale? 5,000? 1,000? Not even close. It was 50.

They had a singular mission: provide the best, most reliable end-to-end communication experience. Period.

In 2014, WhatsApp had 900 million users. How many engineers do you think it took to handle that scale? 5,000? 1,000? Not even close. It was 50.

System design for Agentic AI. A helpdesk triage agent that retrieves facts, calls tools, and knows when to hand off.

Statistics that should worry everyone in IT: 30% of software developers have a diagnosed mental disorder.

When we are stressed, we don't reason well. We don't find creative solutions. We just add more "blocks" to the pile, making the system even harder to maintain.

Statistics that should worry everyone in IT: 30% of software developers have a diagnosed mental disorder.

If you're in a team of 10, 3 of them are struggling. Our industry isn't just building complex systems, it's building a culture of burnout.

Most developers are addicted to complexity. We applaud "clever" systems and put them on our CVs. But complexity is a liability, not an achievement. Let's talk about why we get it wrong.

The problem? We choose the Easy path to get to the finish line faster. But when you avoid the challenges of a design phase, you're just front-loading technical debt. Eventually, you hit a wall where you can't move at all.

Most developers are addicted to complexity. We applaud "clever" systems and put them on our CVs. But complexity is a liability, not an achievement. Let's talk about why we get it wrong.

My daughter plays the violin. For her, a new piece of music is hard. For a professional, it's easy. "Easy" is subjective and changes with experience.

Most developers are addicted to complexity. We applaud "clever" systems and put them on our CVs. But complexity is a liability, not an achievement. Let's talk about why we get it wrong.

An AI agent is not a chat response. It is a loop. Load context, reason, execute tools, update memory, repeat. Once you design the loop, agentic AI becomes just system design again.

AI agents aren't just chatbots. They're loops. Here's the agentic loop explained 👇

The best part: once the loop is designed, adding new tools or capabilities becomes so simple. Your AI agent scales with your architecture.

AI agents aren't just chatbots. They're loops. Here's the agentic loop explained 👇

Tool Executor: Calls systems or APIs as needed (databases, REST APIs, knowledge base, vector stores, etc.), returns results to the Planner, and the loop continues.

AI agents aren't just chatbots. They're loops. Here's the agentic loop explained 👇

Planner: Receives input, loads context (conversation memory, previous tickets), and prompts the AI model.