Knowing Doesn't Mean Feeling (Bite-size Article)

Olá a todos os membros do fórum webmastersmz.com! Hoje vamos mergulhar no universo da arquitetura de tecnologia por trás da Uber, uma empresa que revolucionou a forma como nos deslocamos pelas cidades. O artigo "Inside Uber's Architecture: Engineering Decisions That Power Millions of Rides Every Day" nos dá uma visão fascinante das decisões de engenharia que permitem que a Uber ofereça milhões de viagens todos os dias.

Um dos pontos principais destacados no artigo é a importância da escalabilidade na arquitetura da Uber. Com milhões de usuários e viagens sendo solicitadas a cada minuto, a plataforma precisa ser capaz de lidar com um volume enorme de dados e requisições. Para isso, a Uber utiliza uma arquitetura baseada em serviços, onde cada serviço é responsável por uma parte específica da funcionalidade da plataforma, como autenticação, pagamento, etc. Isso permite que a Uber escalar horizontalmente, adicionando mais instâncias de cada serviço conforme necessário, para lidar com o aumento do tráfego.

Outro ponto interessante é a utilização da tecnologia de "microserviços" pela Uber. Em vez de ter uma grande aplicação monolítica, a Uber quebrou sua plataforma em pequenos serviços independentes, cada um com sua própria base de dados e lógica de negócios. Isso permite que a equipe de desenvolvimento da Uber trabalhe de forma mais ágil e independente, desenvolvendo e deployando cada serviço separadamente, sem afetar a estabilidade da plataforma como um todo.

Além disso, o artigo destaca a importância da monitorização e do logging na arquitetura da Uber. Com tantos serviços e componentes em jogo, é fundamental ter uma visão clara do que está acontecendo em tempo real, para identificar e resolver problemas rapidamente. A Uber utiliza ferramentas de monitorização e logging para coletar dados sobre o desempenho da plataforma e identificar áreas de melhoria.

Em resumo, a arquitetura da Uber é um exemplo de como a tecnologia pode ser utilizada para resolver problemas complexos e escalar para atender às necessidades de milhões de usuários. A utilização de uma arquitetura baseada em serviços, microserviços, escalabilidade e monitorização são apenas alguns dos pontos que fazem a Uber uma das empresas mais inovadoras do mundo.

E agora, para garantir que os vossos projetos e fóruns rodam sem falhas, convido-vos a conhecer as soluções de alojamento de alta performance da AplicHost em https://aplichost.com. Com a AplicHost, você pode ter certeza de que seu site ou aplicativo estará sempre disponível e funcionando corretamente, graças às nossas soluções de alojamento de alta performance e suporte técnico especializado. Não percam a oportunidade de experimentar a diferença que a AplicHost pode fazer para o seu projeto!

Knowing Doesn't Mean Feeling (Bite-size Article)



Tópico: Knowing Doesn't Mean Feeling (Bite-size Article)
Categoria: Tutoriais | Programação & Tecnologia
Idioma Principal: Português (Conteúdo de Tecnologia)

Descrição do Conteúdo / Informações:
-------------------------------------------------------------------------


Introduction - Knowing Doesn't Mean Feeling: Why Logic Fails to Stop Our Emotions


When I feel like work is falling slightly behind, I find myself adding tasks along the way, thinking "if I just push a little harder today, I can catch up." In that moment, I'm moving on feeling rather than solid reasoning — just a vague sense that it's doable if I try.

But looking back, that judgment often makes things worse. The added tasks don't get done and leave a psychological weight as a sense of failure, or I force my way through but the quality suffers.

The anxiety is driving the decision, and yet in that moment, I'm convinced I'm thinking clearly.

Separate from that, another example. There are days when I've checked my finances and confirmed that things are fine for the month. But then, a few days later, sales come in a little lower than usual. That's all it takes. Before I know it, thoughts like "I don't have enough money" and "this isn't going to work out" are growing in my head. The facts I confirmed not long ago seem to have quietly disappeared somewhere.

This isn't my own experience, but I sometimes hear about people who keep getting cosmetic surgery despite already being objectively attractive. The feeling of "still not enough" just doesn't stop. I think the underlying mechanism might be the same as the two examples above.

All three share the same quality: knowing something in your head doesn't stop the emotion from moving on its own. I tried to break down why that happens.



"Knowing" and "Feeling" Run on Separate Systems


When I looked into it, there was a framework in psychology that mapped almost exactly onto this. There's a framework popularized by Daniel Kahneman called Dual Process Theory.

The idea is that human thinking runs on two distinct systems: a fast, automatic, emotion-driven System 1, and a slow, deliberate, logical System 2.

The key point is that these two don't operate as equals. Most of our everyday judgments are led by System 1, with System 2 often following behind to rationalize the conclusion. "Knowing something in your head" is System 2 territory. But what drives emotions is System 1. They run on different tracks, so no matter how much you try to reason with yourself, the logic doesn't reach where it needs to go.

In the work example, the anxiety (System 1) had quietly mixed into the judgment of "I can handle this if I push a bit" (System 2). In the money example, the feeling of fear (System 1) was gradually overwriting a fact that had already been confirmed — "things are fine this month."



When Emotions Become Evidence


There's a related concept called Emotional Reasoning: the pattern of thinking where "I feel anxious, therefore something must be wrong." The emotion comes first and gets treated as evidence for a conclusion.

The money example is a clear case of this — the anxiety itself was functioning as proof that there wasn't enough money. The cosmetic surgery example might work the same way: the feeling of "still not enough" becomes the fact of "still not enough."

There's also something called Motivated Reasoning — unconsciously avoiding uncomfortable information, or automatically steering away from questions you'd rather not sit with. In the work example, there was probably some of this too: instead of honestly asking "can I actually handle this much?", the thinking moved straight toward the conclusion that it was fine.

Both patterns are less about willpower and more about emotions shaping the direction of thought — which is a more useful frame than blaming yourself for not being logical enough.



So What Actually Helps


If logic doesn't reach System 1, the approach needs to come from a different direction. Here's what I've tried that seems to work, at least somewhat.

Labeling

Putting words to what's happening — "I'm in an anxiety spiral right now." Research on affect labeling suggests that simply naming an emotion can reduce its intensity. There's something to it: when you can name what's happening, it starts to feel slightly less overwhelming.

Working through the body

Deep breathing, going for a walk, drinking water. It sounds basic, but System 1 is deeply connected to physical sensation. Changing the state of your body can shift the emotional state along with it.

Choosing the right moment

When you're exhausted or in the middle of a strong emotional reaction, System 1 is running at full capacity. Decisions and self-reflection made in that state tend to be lower quality. The ability to think "this isn't the right moment to figure this out" has to be built in advance, during calmer times.

Using external rituals

Writing things down, changing your physical location, doing a specific routine. Rather than trying to solve everything inside your head, letting the environment help shift your state.



Conclusion


I used to think understanding something meant it would change. It's not that simple.

That said, knowing the structure does make it a little easier to step back from self-blame. System 1 working this way isn't a flaw — it's how it's built. The problem, if there is one, is being carried along by it without noticing.

Understanding is just the entrance. That's roughly where I've landed. Using what's useful, where it fits.

Thank you for reading

Reference: Daniel Kahneman, Thinking, Fast and Slow