DEV Community: gabrielly

clean code (chapter 2), coding is a social activity (?) & the relevance of simple topics

gabrielly — Mon, 23 Mar 2026 15:16:47 +0000

Writing code is, above all, a social activity.

I know this might sound repetitive or like it’s not a big deal, but I invite you to stick with me. I promise it won't hurt!

We spend way more time reading what’s already been written than typing out new lines, and that’s why picking names isn't just about making things look "pretty"—it's a survival move for any team.

When we stop to look at the impact of generic names, like using a single letter or some mysterious abbreviation, we realize just how much unnecessary mental load we’re dumping on our teammates and even on our future selves.

Code that forces the reader to decode what a variable represents is code that’s just wasting time and energy.

Clarity should always win over brevity. Names that reveal intention get rid of the need for comments and let the reading flow naturally, without those "wait, what?" moments. Plus, it's super important to create distinctions that actually mean something.

Using names that are too similar for different things is just asking for bugs and confusion. The goal is that when you read a function, the developer’s intent is crystal clear and not hidden behind misleading terms or names that are too generic for the system.

Another essential point is making sure names are pronounceable and easy to search for. If we can't even say a variable's name in a meeting, the team's communication takes a hit. If a name is too common, finding it in a huge project becomes an impossible mission. Finally, context plays a huge role. Instead of repeating prefixes everywhere, structuring your code into classes allows variables to gain meaning from the environment they’re in.

Mastering the art of naming takes practice and a shared culture, but it’s what separates a messy pile of instructions from professional, sustainable software.

Thanks for reading this far! May you find money on the ground today or have a million-dollar idea! If you want to dive deeper, I also recorded a video over on my YouTube channel.

https://www.youtube.com/watch?v=Sde1iDhFUcU&t=20s

clean code, the essence of programming & why technical foundations still matter

gabrielly — Thu, 19 Mar 2026 14:13:21 +0000

It’s been over a year since I bought Clean Code, and I’ve finally decided to read it.

Sometime after I bought it, I was talking to another developer about my new acquisition, and they told me the book was already outdated—that it didn’t make sense to read it anymore, especially with the rise of AI.

So, more than a year later, I decided to read it anyway and draw my own conclusions.

The verdict: If you’re a dev, read at least the first chapter. Uncle Bob really went off! (Or as we say in Brazil, he really delivered).

Chapter 1: Clean Code
He starts by talking about how programming will always exist. He addresses rumors—which were already circulating back in 2008—that programmers would lose their jobs to new ways of building applications. According to him, these are nothing more than speculation. As long as we need to translate requirements into a product, the bridge between the two is, and always has been, code.

He then dives into the obstacles that damage the coding process, like giving in to external pressures (usually management) to code faster.

This leads to "monstrous" code that fails to result in a durable or scalable product, eventually forcing a total refactor. He even cites a case where this entire mess took 10 years to fix.

The Doctor Analogy:
Imagine you’re a surgeon about to operate on a patient. You know you need to wash your hands first. But your "client" (the patient) says washing hands is nonsense and demands to be operated on immediately. As a doctor, you know the lethal consequences of operating with dirty hands. So, despite the patient’s complaints, you wash your hands before starting the procedure.

In this scenario, we—programmers—are the doctors. When it comes to code, we must "wash our hands" as many times as necessary to ensure quality.

Finally, this first chapter explores the definition of clean code from other tech legends. I won’t go through them all, but here are two that I found particularly beautiful:

"Clean code is simple and direct. Clean code reads like well-written prose..."
— Grady Booch, author of Object-Oriented Analysis and Design with Applications

"Clean code always looks like it was written by someone who cared."
— Michael Feathers, author of Working Effectively with Legacy Code

These two quotes reminded me of how cool and important writing code actually is. Reading this chapter made me want to find that "tech consciousness" in the market—the one Uncle Bob describes as existing within certain programmers and company cultures—which often feels very different from what most of us experience in our daily jobs.

This leaves me with the perspective that the battle of good code vs. bad code has always existed, and AI has only amplified the stakes. Perhaps now, universities and formal education will serve as vital knowledge validators—separating those who only know how to send a prompt from those who actually know how to study and build.

I’ll keep reading and sharing my thoughts on each chapter.

Thanks to everyone who read this far! Just so you know, I also recorded a video about this for YouTube: https://www.youtube.com/@gabizaor

layoffs, closing chapters & personal value

gabrielly — Wed, 11 Mar 2026 20:08:19 +0000

It’s been exactly one week since I was laid off from my job as a junior frontend developer.

My company had already been going through financial struggles; there were three rounds of layoffs, and in the last one, I was let go too.

When I asked my manager if there was anything in my performance or attitude that might have contributed to my dismissal, the answer was the most startling one possible: no.

What happened was that, with AI becoming increasingly prevalent, projects kept shrinking, and the company could no longer afford my salary.

This leads me to a question: is the development market absolutely terrible right now?

When I asked this same question to a senior dev who has mentored me since the start of my career, he said that the market has actually been rough since 2022. And—in his view—for things to improve, the AI bubble needs to burst and people need to realize that "AI isn't all that."

But then, I'm left wondering: is AI really not all that?

Anyway... that’s a question only time will answer. But within the sphere of things I can control, I have a clear conscience knowing I did my best work, and I remains optimistic about my income potential.

So, re-evaluating my life after this layoff, I decided to do all the things I’d put aside lately because my job took up so much of my time and mental energy.

I finished a book my girlfriend recommended three months ago and started coding v2 of Mentoriah (it's not finished yet, but keep an eye on the project to see how beautifully v2 is coming along).

mentoriahti.com

After a frantic period finishing all the tasks I’d left open over the last few months, I realized that I actually needed to stop for a bit—I, like many Gen Zs, have a thing with anxiety and "doing nothing."

By stopping, I saw friends I hadn't seen in a long time, and it was a very productive time to process the layoff itself. During one of these meetups, a friend told me how the most fruitful and high-growth periods of her life happened between jobs. Another friend mentioned how he has a side project that generates some income, even if it's small, and how that’s already enough to pay his electricity bill. And let's be honest, having the light bill paid every month is a win.

The thing is, in these moments, we never quite understand what’s happening. But as time passes, we realize that when life asks us to recalculate our route, we often end up in places much closer to where we actually wanted to be. (I told you I was an optimist).

As this first week comes to a close, I’ve listed three thoughts for anyone going through something similar:

Stay close to people you admire.
Don't let your brain think this is the end of the world—or at least, not for long.
This is your story; tell it in the best way possible.

Bye! For those who read until the end, just so you know, I also recorded a YouTube video about this. I'd love for you to watch it.

gabrielly - YouTube

oie ;)

youtube.com

IA, carreira e ansiedade

gabrielly — Mon, 09 Feb 2026 01:00:51 +0000

As coisas estão mudando muito rápido o tempo todo. Tenho a sensação de que quem está se saindo melhor é justamente quem consegue fluir de acordo com essas mudanças. Eu — como engenheira de software júnior — me sinto no meio do furacão. E, provavelmente, você também se sinta assim.

Oie, meu nome é Gabrielly, mas podem me chamar pelo meu vulgo de Gabi. Faço faculdade de Engenharia de Software e trabalho como desenvolvedora frontend há dois anos. Além disso, sou a criadora do Mentoriah, um projeto de incentivo à entrada de pessoas LGBTQIAPN+ no mercado de TI.

Como uma pessoa de mente inquieta e buscando me conectar com gente que seja como eu, quero te perguntar: como é estar no meio do furacão para você?

Porque é onde nós estamos kkkkk. Estamos no meio de uma revolução industrial maluca em que a IA vem ocupando cada vez mais espaço. Precisamos nos ajustar não só no trabalho, mas no ritmo da vida. A real é que a vida nunca mais será a mesma agora que temos IA.

Parece forte dizer isso, né? Mas entre impactos no meio ambiente e mudanças profundas na economia, fica cada vez mais claro que não existe "receita de bolo" para passar por esse momento.

Tem um livro salvo na minha lista da Amazon que me recomendaram e eu gostaria de compartilhar duas frases que me chamaram muito a atenção:

“O que a IA parece estar fazendo é pulverizar minha capacidade de concentração e contemplação. Meu cérebro agora espera receber informações da maneira como a IA as distribui: em um fluxo de partículas que se move rapidamente.”

"A memória é muito mais do que um reservatório de fatos; é o próprio fundamento da inteligência e da sabedoria. Quando começamos a usar a IA como substituta para a memória biológica, corremos o risco de esvaziar nossas mentes de sua riqueza e diversidade."

Você concorda? Faz sentido para você?

Bom... independente da resposta, eu preciso confessar: eu alterei as frases para provar um ponto.

O livro se chama The Shallows (A Geração Superficial), de 2011. Ele fala sobre como a internet mudou nossa forma de pensar. Nas frases originais, basta trocar "IA" por "internet".

O que eu quero dizer com esse exercício é que nós já estivemos aqui antes. Não faz tanto tempo, a internet surgiu e mudou o rumo do mundo. Hoje, pensar que a IA vai sumir ou que é só uma "modinha" beira o negacionismo.

Se a IA agora é protagonista, o nosso desafio é descobrir como trabalhar com ela sem que isso roube nossa capacidade de raciocínio. Eu não sei exatamente como fazer isso, mas estamos tentando.

Tenho tentado abraçar a ideia de que não tenho controle de nada, e isso me deixa mais tranquila em relação à pressão que essa tecnologia causa. É curioso ver o movimento contrário surgindo: esses dias vi um vídeo de Lofi no YouTube com o título: ‘Lofi feito sem IA - Human no AI lofi Music in a Real Poppy Field’. Já estão criando nichos sem IA.

Para entender a dimensão do que estamos enfrentando, olhem esses dois casos no nosso mercado:

O caso positivo (Wikipedia): A Wikipedia percebeu que as IAs bebem da base dela o tempo todo. Em vez de lutar contra, fechou acordos com gigantes (Amazon, Meta, Microsoft) para que esse treinamento seja pago. Isso ajuda a custear a infraestrutura e valoriza o conteúdo dos voluntários. É a adaptação dando certo.

O caso negativo (Tailwind): Se você é dev frontend, deve ter visto. O Tailwind precisou demitir 75% dos funcionários. O tráfego do site caiu porque as pessoas agora pedem o código direto para a IA. O irônico? O Tailwind nunca foi tão usado, mas a empresa não conseguiu capturar esse valor como a Wikipedia fez. Hoje, Google e Vercel patrocinam o projeto para ele não morrer.

Em uma palestra recente que fui na FIAP, vi exemplos que me deixaram pensando. O Itaú está estudando como fazer Pix via IA (ex: "IA, divide a conta do bar com a fulana"). É prático? Muito. Mas o Pix é gratuito e a IA custa caro. Como fecha essa conta?

Outro exemplo foi o atendimento ao cliente via WhatsApp substituindo pessoas por IA 24/7. O que acontece com essas pessoas? Como o mercado se reestrutura?

Minha conclusão (por enquanto): Enquanto as empresas avaliam o ROI (retorno sobre investimento), nós precisamos aprender a usar a IA sem depender dela. Ela deve ser o nosso rascunho, o nosso desenho inicial pra ganharmos tempo, mas não o nosso cérebro substituto.

Isso sem nem entrar no impacto ambiental colossal que o treinamento desses modelos gera...

Enfim, acho que deixei vocês com mais perguntas do que respostas. Foi mal! Pensei alto por aqui.