DEV Community: Stanley Amaziro

It is the year 2026, stop saying "It works on my machine!"

Stanley Amaziro — Sat, 15 Nov 2025 18:07:02 +0000

If you're still fighting environmental conflicts, struggling with slow developer onboarding, or dealing with tricky deployments
, it's time for an upgrade.

Let's talk about Docker 🐳 and how it solves the biggest pain point in software development.

What is Docker? (The Shipping Container Analogy)

Docker is the shipping container for your software.
_

Just like a physical container can hold anything (electronics, clothes, food) and be shipped anywhere, a Docker container holds your entire application, its dependencies (Node.js, MongoDB, Redis), and its configuration, and can run flawlessly anywhere, from your laptop to the cloud server. 🤗

Think of it: Instead of installing three separate systems (Node, Mongo, Redis), Docker creates three isolated, pre-configured "boxes" (containers). You run one command, and they all start working together.

Understanding the Key Docker Files

Dockerfile (The Recipe) 🧑‍🍳 The blueprint for building one service (e.g., your backend API). It defines the base image, copies the code, installs dependencies, and specifies the start command.
docker-compose.yml (The Orchestra) 🎶 The master plan for your entire application stack. It defines how your multiple containers (Backend, Database, Cache) are linked, what ports they use, and how they share data.
.dockerignore (The Exclusions) 🗑️ A simple list that tells Docker what local files to ignore when building the image (e.g., node_modules, .git, temporary logs). This keeps your final image clean and secure.

**
Your 3 Daily Commands (The Automation)**

docker-compose up -d (Start the whole stack in the background)

docker-compose logs -f backend (Stream logs for troubleshooting)

docker-compose down (Stop and clean up the containers)

If you're building a multi-service app (like a web app with a database and cache), Docker is non-negotiable for efficiency.

What was the biggest headache Docker solved for your team? Share your experiences below! 👇 #Docker #DevOps #Containerization #SoftwareDevelopment #TechTips

It is the year 2026, stop saying "It works on my machine!"

Stanley Amaziro — Sat, 15 Nov 2025 17:14:12 +0000

If you're still fighting environment conflicts, slow developer onboarding, and tricky deployment, it's time for an upgrade.

Let's talk about Docker 🐳 and how it solves the biggest pain point in software development.

What is Docker? (The Shipping Container Analogy)

Docker is the shipping container for your software.
_

Understanding the Key Docker Files

Dockerfile (The Recipe) 🧑‍🍳 The blueprint for building one service (e.g., your backend API). It defines the base image, copies the code, installs dependencies, and specifies the start command.
docker-compose.yml (The Orchestra) 🎶 The master plan for your entire application stack. It defines how your multiple containers (Backend, Database, Cache) are linked, what ports they use, and how they share data.
.dockerignore (The Exclusions) 🗑️ A simple list that tells Docker what local files to ignore when building the image (e.g., node_modules, .git, temporary logs). This keeps your final image clean and secure.

**
Your 3 Daily Commands (The Automation)**

docker-compose up -d (Start the whole stack in the background)

docker-compose logs -f backend (Stream logs for troubleshooting)

docker-compose down (Stop and clean up the containers)

If you're building a multi-service app (like a web app with a database and cache), Docker is non-negotiable for efficiency.

What was the biggest headache Docker solved for your team? Share your experiences below! 👇 #Docker #DevOps #Containerization #SoftwareDevelopment #TechTips

How CDN Can Help You Deliver Speed and Save Cost for Your Business

Stanley Amaziro — Wed, 05 Nov 2025 18:32:36 +0000

In today's competitive digital landscape, speed and performance are crucial for businesses to stay ahead. A slow-loading system can lead to frustrated users, decreased engagement, and lost revenue. This is where a Content Delivery Network (CDN) comes in. It can help deliver speed, save cost, and improve user experience.

“A CDN is a network of distributed servers that cache and deliver content to users based on their geographic location. By storing content at edge locations closer to users, CDNs reduce latency, minimize bandwidth usage, and improve load times.”

Using CDN comes with loads of benefits;

Faster Content Delivery: CDNs cache content at edge locations, reducing the distance between users and content, resulting in faster load times.

Reduced Server Load: Serving static assets from a CDN reduces the load on your origin server, improving its performance and reducing the risk of crashes.

Cost Saving: CDNs minimize bandwidth costs by reducing the amount of data transferred between your server and users, improving cost efficiency.

Improved User Experience: Faster load times and reduced latency lead to increased engagement, conversion rates, and customer satisfaction.

If you're looking to improve your system’s performance, consider using a CDN to maximize your business's potential. With a CDN, you can deliver speed, save cost, and improve user experience.

Building My Movie Discovery App: A Full-Stack Journey of Challenges, Tools, and Growth

Stanley Amaziro — Sat, 11 Oct 2025 17:01:01 +0000

As a developer, every project is a stepping stone, but some feel like climbing a mountain. My Movie App was one of those mountain full-stack applications that taught me more about perseverance, debugging, and the intricacies of deployment than any project ever could. Over several days (and nights), I built, broke, and rebuilt this app, turning a simple idea into a live, functional platform. Hosted on Netlify for the frontend and Render for the backend, with MongoDB Atlas handling the data, it's now live at usemovie-app.netlify.app
The Project Overview
The Movie App is a user-friendly platform where movie enthusiasts can browse popular films, view detailed information, watch trailers, receive personalized recommendations, save favorites, and contact support. It includes secure user authentication with registration, login, password reset, and profile management. The app is responsive across all devices, ensuring a seamless experience on both mobile and desktop.
The idea started simple: integrate the TMDB API for movie data and build a backend for user features. But as I dove in, deployment and integration challenges turned it into a real-world learning lab.
The Tech Stack: Tools That Powered the App
I chose tools that balanced ease of use, scalability, and learning potential. Here's the breakdown:
Frontend
React 19 with Vite: For the UI and fast development. Vite's hot module reloading sped up iteration, and React's component-based structure made it easy to build reusable pieces like MovieCard and NavBar.
React Router DOM: Handled client-side routing, with the registration page at the root/route for a smooth user onboarding experience.
State Management: React Context API for global state (e.g., user authentication).

Backend
Node.js and Express.js: The runtime and web framework for building the API.
MongoDB Atlas with Mongoose: Cloud database for storing users, subscriptions, contacts, and reset tokens. Mongoose ODM simplified schema definition and queries.
Authentication & Security: JWT for tokens, bcryptjs for password hashing, and crypto for reset tokens.
Email Service: Nodemailer for password reset emails using Gmail with App Passwords.
Environment Management: dotenv for managing secrets like JWT_SECRET, MONGODB_URI, EMAIL_USER, and EMAIL_PASS.

Deployment & Other Tools
Netlify: Hosted the frontend as a static site, with automatic deploys from GitHub.
Render: Hosted the backend, handling Node.js execution and environment variables.
GitHub: Version control for the frontend and backend directories.
TMDB API: For movie data, recommendations, trailers, and reviews.
Debugging Tools: MongoDB Compass for local database visualization, Postman for API testing, and curl for endpoint checks.

The stack was full-stack, teaching me how frontend and backend integrate, with deployment adding real-world complexity.
I deployed the backend to Render, but hit immediate roadblocks. The initial logs showed ECONNREFUSED errors when connecting to MongoDB, as I was using a local mongodb://localhost:27017/movie_db URI. Switching to MongoDB Atlas seemed straightforward, but then came querySrv ENOTFOUND, bad auth, and MongooseServerSelectionError. These stemmed from incorrect connection strings, missing database names (/movie_db), and IP whitelisting issues.
One frustrating moment was when the backend connected briefly but defaulted to the 'test' database instead of 'movie_db', leading to duplicate key errors on an old username_1 index from a previous schema. I learned to drop indexes via Atlas Dashboard and use Mongoose's schema to automatically create collections on first save - no need for manual migration if data isn't critical.
Debugging these taught me to always verify environment variables in Render (e.g., MONGODB_URI, JWT_SECRET), and to use mongosh in the terminal to test Atlas connections. I also added robust error handling in server.js to prevent crashes, like catching err.code === 11000 for duplicate keys. Overall, the project added to my developer journey by teaching resilience - errors like ECONNREFUSED and MongooseServerSelectionError forced me to dive into docs, whitelist IPs, and debug environment variables. It also highlighted the importance of secure practices like bcrypt hashing and JWT authentication.
Conclusion
This movie app was more than code; it was a test of patience and problem-solving. From deployment headaches to API integration, I emerged with stronger full-stack skills. Check out my app at usemovie-app.netlify.app and source code at github.com/Webziro/movie-app. I'd love feedback - happy coding.

I have been learning the React framework for a while now. Here is what I understand:

Stanley Amaziro — Thu, 25 Sep 2025 12:32:07 +0000

React is a JavaScript framework, popular, lightweight, and compiles faster.
React is about writing reusable components as functions,
Exporting them and using them anywhere by importing.
These "<>…</>" are called fragments - they let you group multiple elements without extra HTML wrappers.

Here is how fragments differ from regular HTML tags

Fragments (<>…</>) let you group multiple elements without adding extra nodes to the DOM.
Useful when you want to return multiple elements from a component but avoid unnecessary wrappers like .
Keeps the HTML structure clean and minimal, and easily maintainable
You can also write <> as </> if you want to add keys or props. Basically, fragments are a lightweight way to bundle elements together inside your component without cluttering the DOM tree.

phpmailer Vs PHPMailer: My Windows and Linux server experience

Stanley Amaziro — Tue, 17 Jun 2025 20:43:59 +0000

Working on a client project in a distant country recently presented an interesting challenge.

They had a strict requirement, I needed to upload my progress every week so they could monitor the project in real-time. I agreed, though with some initial reluctance.

This setup quickly revealed unexpected bugs whenever I moved my code from my local development environment to the live server. One particular issue left me truly dumbfounded: the PHPMailer-powered "send mail" feature worked flawlessly on my local machine, but consistently threw errors on the live server.
After hours of intense debugging, I finally discovered the issue. My local setup, as I knew, ran on a Windows environment, while the live server operated on a Linux (Unix-based) system. The root of my problems stemmed from a fundamental difference in how these operating systems handle file names.
On Windows, you have the flexibility to name files and folders in various ways; "phpmailer", "PHPMailer", "PhpMailer", and the system treats them all as the same. However, Linux is case-sensitive. This means that "PHPMailer" is seen as entirely distinct from "phpmailer" or "PhpMailer". My code was referencing a folder with one capitalization, but the server expected another.

The solution was simple once identified: I had to rename the PHPMailer folder on the live server to match the exact capitalization used in my require statements. Once I changed it to PHPMailer, everything worked perfectly.

If you ever encounter similar "file not found" errors when deploying from a Windows to a Linux environment, always ensure your file and folder naming conventions are precise and consistent down to the capitalization. Adhering to conventional naming standards across both servers will save you countless hours of debugging and a lot of stress.

PHP keeps powering my productivity

Stanley Amaziro — Tue, 17 Jun 2025 20:28:41 +0000

Starting my career as a WordPress developer, I initially faced endless fears surrounding PHP's viability due to widespread claims of its obsolescence 😫

The constant barrage of criticism from various sources, including clickbait writers, views chasers on YouTube, and tech clout chasers, led me to question my career path😂

However, having worked extensively with PHP, I can confidently attest to its enduring relevance 💯

As a language that powers over 45% of the internet, PHP has consistently demonstrated its capabilities. 🔥

Through my journey, I have achieved significant success, leveraging PHP to craft high-performance solutions, consume APIs, build scalable products, collaborate with developers using other languages, manipulate web pages, integrate third-party functionalities, and develop e-commerce platforms for web and cross-platform applications.

We are in 2025, and PHP remains a vital tool for web and app development.

This experience has taught me that the effective utilization of a tool's knowledge is more crucial than the tool itself. 🔭

For those navigating similar crossroads, I’d say perseverance is key. 🔑 Continue on your path, and it will ultimately #MakeSense 🤗

Check out some of my projects:

https://github.com/Webziro

https://lnkd.in/dnD5kxdp

https://lnkd.in/dpqjmje5

Scared of Deadlines? We all are.

Stanley Amaziro — Sat, 27 Jul 2024 13:44:58 +0000

Feeling overwhelmed by your project? You're not alone. Many of us lose steam halfway through because projects aren't always as exciting as when we first started them. Here's how to reignite your focus and conquer deadlines.

Break projects into smaller parts: Breaking projects into smaller components can significantly reduce anxiety and improve drastically on productivity
Set clear goals for each stage: Use the SMART method, which is Specific, Measurable, Achievable, Relevant, and time-bound at every stage of the project
Time management: There are several time management techniques you can employ including the time blocking technique and the Pomodoro (work in focused bursts with short breaks) technique to be a master of your time.
Eliminate distractions: Distraction is a stealer of time it impacts a lot on our productivity. Make sure to use different possible means to minimize or eliminate every form of distraction, including turning off notifications and using website blockers.
Reward system: Celebrate milestones to stay motivated and learn to properly reward yourself for every win achieved by prioritizing play and rest.

The list is not exhausted however, by implementing these strategies, you'll not only meet deadlines but also enhance your overall project management skills.

How to write clean efficient codes

Stanley Amaziro — Tue, 21 Mar 2023 06:30:55 +0000

Use proper indentation and spacing to improve readability and maintainability of the code.

Follow a consistent coding style, such as PSR standards, to make it easier for others to understand and contribute to your code.

Use descriptive variable names that accurately convey their purpose and avoid abbreviations or overly short names.

Use comments sparingly but effectively to provide context and explanations for complex or non-obvious code sections.

Use built-in functions and libraries whenever possible, as they have been optimized and tested for performance and security.

Validate all input from users or external sources to prevent SQL injection attacks or other security vulnerabilities.

Keep your functions small and focused on a single task to promote reusability and modularity in your code.

PHP is not going soon

Stanley Amaziro — Thu, 16 Mar 2023 17:36:09 +0000

PHP, the popular server-side scripting language, has been around for over 25 years and has undergone numerous upgrades and advancements. Despite newer languages like Python and Node.js gaining popularity, PHP still holds a significant market share in web development.

One reason PHP is not going away soon is its widespread use in the web development community. Many popular content management systems (CMS) such as WordPress, Drupal, and Joomla are built using PHP, and a vast number of websites on the internet run on these platforms. As long as these platforms continue to be widely used, PHP will remain relevant.

Another reason for PHP's resilience is its versatility. PHP can handle a wide range of tasks, from simple scripts to complex web applications. It also has excellent database integration capabilities and supports a broad range of databases, making it a go-to choice for building dynamic web applications.

Furthermore, PHP has a massive library of open-source code and a vast community of developers contributing to its development, ensuring its continued improvement and relevance.

In conclusion, PHP's continued relevance can be attributed to its widespread use, versatility, and an active community. While newer languages may emerge, PHP's strong foundation and community support and ease of learning ensure that it will remain a vital part of web development for years to come.