TL;DR
I'm Gavin Cettolo, a developer since 2017, builder and problem solver. I mainly work with React and Next.js, have experience coordinating projects and dev teams, and recently completed an MBA with honors to better understand the business dynamics behind every line of code.I’ve decided to start publishing on Dev.to to talk about React, Clean Code, AI in development, OOP patterns, system design interviews, and project organization. My goal is to share what I learn and, most importantly, to learn better by explaining things clearly. Ideally, you’ll read something here and think, “Ah, that’s interesting.”
Questo articolo è anche disponibile in Italiano
Who I Am
Hi everyone,
I’m Gavin, and this is my way of politely knocking on Dev.to’s door before diving into technical articles.
I consider myself a builder and a problem solver. I like creating solutions that are useful, well-structured, and maintainable. Coding officially became my job back in March 2017, but the curiosity started much earlier. As a kid, I used to take computers apart, copy code from random tutorials, and spend more time experimenting than actually playing games.
Over the years, I’ve worked with several technologies: Java, .NET, Angular, jQuery, and more. Each one taught me something valuable. Then I discovered React, and it won me over.
Its flexibility, mindset, and community made development feel cleaner and more modular. Next.js naturally followed: better project structure, easier SEO handling, elegant rendering strategies, and less friction between idea and production.
Today I move between frontend and backend with a strong focus on code quality. I’ve also coordinated projects and development teams over time. I genuinely enjoy working with people as much as I enjoy working with code: running constructive code reviews, improving communication, and helping projects stay structured as they scale.
The startup world taught me one simple thing: change is constant. New features, inevitable refactors, unexpected bugs. If you don’t enjoy continuous learning, this might not be the right field for you.
Clean Code as a Mindset
I don’t see Clean Code as an aesthetic preference. It’s a form of respect.
- Respect for the person who will read your code after you.
- Respect for your future self.
- Respect for the project.
For me, it means writing code that can be understood without decoding cryptic comments. Functions with a clear responsibility. Names that explain instead of confuse. Structures that don’t create anxiety three months later.
I follow classic principles, but I don’t treat them as dogma. Context matters. The real goal is always the same: readable, testable, maintainable code that doesn’t cause unnecessary friction.
AI in Development
I use AI as a support tool, not as an autopilot.
It helps me generate simple snippets, perform small refactors, and unblock ideas when I get stuck. But the responsibility remains mine. AI accelerates the process, it doesn’t replace reasoning.
In the coming years, I believe the real difference won’t be between developers who use AI and those who don’t. It will be between those who use it consciously and those who use it passively.
An MBA to Understand What’s Beyond the Code
I recently completed a Master of Business Administration with top honors.
It wasn’t a change of direction, but an expansion of perspective. Budgeting, strategy, organization, goal setting, resource management. Every piece of software lives inside a business context. Understanding that context changes how you make technical decisions.
Writing a feature is one thing. Writing it while understanding why it exists and what business impact it has is another.
Why I’m Writing Here
I write to share, but also to learn better.
There’s a simple rule I’ve always found true: if you can explain something clearly, then you truly understand it. This blog is also a personal exercise in clarity.
My plan is to publish one article per week, alternating topics. Some weeks will focus on React and Next.js, others on Clean Code, AI in development, OOP patterns, system design interviews, and reflections on organization and professional growth.
I want to keep a consistent and sustainable rhythm. No content overload, just thoughtful, practical, and concrete articles.
Here you’ll find content about:
- React and Next.js
- Clean Code and best practices
- OOP patterns
- System design interviews
- AI applied to development
- Organization, growth, and project dynamics
No guru mindset and no absolute truths. Just experience, experiments, mistakes, and continuous improvement.
If you made it this far, thank you.
Feel free to introduce yourself in the comments or tell me what kind of content you’d like to read.
See you soon.
Gavin 🚀
Top comments (0)