DEV Community: Philip Damwanza

Why React Components Will Change How You Think About UI

Philip Damwanza — Thu, 04 Jun 2026 11:50:12 +0000

When I first started learning React, I kept asking myself why everyone was so obsessed with components — then it clicked. A component is just a small, reusable chunk of your UI, like a button, a navbar, or a card, and instead of writing the same HTML over and over, you build it once and drop it anywhere in your app. You pass in different data through props and the component adapts, which means your code stays clean, your files stay manageable, and when something breaks, you know exactly where to look. The real power shows up when you start composing them together — small components nested inside bigger ones, each doing one job well, until your entire app is just a tree of focused, predictable pieces. It sounds simple because it is, and that simplicity is exactly what makes React so powerful for building everything from a personal portfolio to a full production app.

React Components: The Building Blocks You Need to Know

Philip Damwanza — Thu, 04 Jun 2026 11:47:12 +0000

What Even Is a Component?
If you're learning React, you'll hear "component" thrown around constantly. Simply put — a component is a reusable piece of UI. Think of it like a LEGO brick. You build small pieces and snap them together to make something bigger.

Why Components Are Great:
1.Reusable — write once, use everywhere
2.Clean code — each component does one thing
3.Easy to debug — problems are isolated
4.Team-friendly — different devs can work on different components

Keep your components small and focused. If a component is doing too many things, break it up. A UserCard component shouldn't also be fetching data AND handling form submissions.

React components are simple in concept but powerful in practice. Start small, stay consistent, and before you know it you'll be building complex UIs like it's nothing.

LEARNING HOW DOCKER WORKS

Philip Damwanza — Tue, 02 Jun 2026 10:55:54 +0000

Recently i have been learning a bit about docker and how it works and operates ,its importance and just everything concerning .Eventhough i am still in the process of learning how it does i have managed to grasp a few concepts on it.
SO docker simplifies work by taking or putting your codes ,packages and settings into a standardized digital box.

So far i had experienced a situation where i write a code and it works perfectly on my computer but when i try to put the same code on my friends computer the code isn't working .So there now is where now docker comes through in handy , so docker has the container which includes the exact operating system and GO version required so it is able to run on any computer

HOW I MANAGED TO PUSH MY WORK TO MY PUBLIC GITHUB PROFILE FROM MY GITEA PROFILE

Philip Damwanza — Mon, 18 May 2026 06:38:20 +0000

Hey Dev community
As a beginnner in the tech world and coding world everything has been kind of confusing but one of the problem i had that now i have already solved is how i can push work to my github profile
So i kind of got a hang of it after doing research on it and now all the projects that i have been doing i can easily link them to my public profile from my private gitea profile

The first project i pushed to my profile is called git kahenda/git
This project consists of exercises designed to master version control, file staging, and branching. It was the perfect sandbox for me to practice navigating the command line without breaking a massive codebase.

So using a few commmands in my terminal which helped me disconnect my project from the old server to a new server where my work can be at .

The exact commmand sequence i used :

Remove the old private Gitea connection

git remote remove origin

Add the new public GitHub connection

git remote add origin https://github.com

Push the code up to the main branch

git branch -M main
git push -u origin main

now you can easily check my live repository here : kahenda/git