DEV Community: Ibtisam Ali

Reviving Shop-Control: Building a Modern POS & Inventory System with Laravel and GitHub Copilot

Ibtisam Ali — Fri, 29 May 2026 20:26:05 +0000

This is a submission for the GitHub Finish-Up-A-Thon Challenge

What I Built

I built Shop-Control, a lightweight, role-based Point of Sale (POS) and inventory management system designed for small retail businesses. Powered by Laravel and Tailwind CSS, it handles authentication, complex role management (Cashier vs. Manager views), live cart state management, checkout transaction tracking, and real-time sales performance analytics.

For many small retail businesses in my community, heavy enterprise software is too expensive or complex. I wanted to build a modern, fast, and accessible tool using SQLite that gives shop owners immediate clarity over their inventory and daily sales counts.

Demo

GitHub Repository: adventureibtisam111/shop-control

📸 Application Preview

1️⃣ Dashboard View: Real-time revenue tracking and total items sold metrics.

2️⃣ POS Cart / Checkout Screen: Live transaction calculations and item tracking.

3️⃣ Inventory Control: Complete CRUD setup for editing categories and tracking stock depths.

The Comeback Story

This project started out as a skeleton backend structure. It had a rough setup for basic authentication, but the core mechanics that actually make a POS system functional—the transactional logic, the active shopping cart state, and data consistency across related tables—were left completely unfinished. The codebase was fragmented, migrations were partially broken, and the routes were a mess of dead ends.

To complete the arc, I dove back into the code to finish what I started:

The Missing Links: I designed and executed all remaining migrations and structural relationships for products, cart states, and historical checkouts.
The UI Upgrade: I refactored the presentation layer into a beautifully clean, highly responsive Tailwind CSS layout that stays functional across mobile and desktop retail setups.
The Revenue Loop: I rewrote the transactional logic so checking out a cart properly debits stock levels, creates safe sales records, and aggregates live metrics directly to the main manager dashboard.

My Experience with GitHub Copilot

Reviving a half-finished app means spending hours tracing your own old logic. GitHub Copilot completely erased that friction. Here is exactly how Copilot helped me cross the finish line:

Writing Database Relationships Effortlessly: When joining the products, carts, and sales_history tables, Copilot contextually anticipated my Eloquent relationship methods (hasMany, belongsTo) based on my database schema naming conventions, saving me tons of manual configuration time.
Accelerating Controller Logic: Writing full CRUD controllers can get repetitive. Copilot speed-dialed my workflow by instantly auto-completing form validation arrays and standard resource controller methods.
Tailwind Class Autocomplete: Designing a compact, data-heavy layout for a POS cash register screen requires tight CSS work. Copilot predicted utility class patterns smoothly, drastically speeding up the layout process.

Instead of getting bogged down troubleshooting setup blocks, GitHub Copilot acted as a highly contextual peer programmer that kept me perfectly in my flow state from start to finish.

🧲 3 Things Building MediTrack Taught Me About Laravel (and Backend Development)

Ibtisam Ali — Tue, 26 May 2026 06:51:22 +0000

A few days ago, I built MediTrack, a Laravel-based hospital management system for managing doctors, patients, appointments, prescriptions, and lab tests.

This was one of the first projects where I moved beyond basic CRUD applications and started thinking in terms of real system design and relationships between features.

While building it, I realized something important:

Laravel starts making real sense when you stop following tutorials and start building complete systems.

MediTrack forced me to think about structure, data flow, and how different parts of a system actually connect together in production-style applications.

Here are 3 key lessons I learned:

1️⃣ Database Design Shapes Everything

At the beginning, I underestimated how important database design really is.

I had entities like:

doctors → appointments
patients → prescriptions
lab tests → patients

But as the project grew, I realized something critical:

If your database structure is wrong, everything built on top of it becomes harder to maintain.

I had to go back multiple times to:

restructure tables
adjust relationships
rethink migrations
fix design decisions that didn’t scale well

This is where Laravel relationships like hasMany and belongsTo started to actually make sense in a practical way.

Key takeaway:

Backend development is mostly about designing data structures correctly before writing logic.

2️⃣ Authentication Is About System Security, Not UI

Before this project, I thought authentication meant:

login
register
logout

But MediTrack introduced role-based access like:

Admin
Doctor
Receptionist

And that changed everything.

Each role needed:

different dashboards
different permissions
restricted routes
protected backend logic

This is where I learned about:

Laravel middleware
route protection
backend authorization logic

One important realization:

Hiding UI elements is not security. Backend rules are what actually protect the system.

Key takeaway:

Authentication is not a feature — it’s a system design decision.

3️⃣ Real Projects Teach What Tutorials Don’t

Tutorials helped me understand Laravel basics.

But MediTrack is where things became real.

I faced issues like:

features breaking after small changes
incorrect database query results
debugging unexpected behavior
spending hours fixing small logic mistakes

Unlike tutorials, there was no step-by-step solution.

I had to:

read documentation
debug systematically
test multiple approaches
learn through failure

And that’s where real growth happened.

Key takeaway:

You don’t learn development by watching — you learn it by building, breaking, and fixing.

🎯 Final Thoughts

MediTrack is still evolving, and there’s a lot I want to improve.

But it changed how I approach development.

Laravel feels much clearer now because I’ve used it to build a complete system, not just small examples.

If you’re learning backend development, my advice is simple:

Start building real projects early — even if they’re imperfect.

The learning that comes from debugging your own system is completely different from following tutorials.

That’s where real developer thinking starts.

💬 I’d love to hear from others:
What project taught you the most about development?

🔗 Open to feedback, collaboration, and backend engineering opportunities.

Speed Over Size: Why Gemini 3.5 Flash is the Most Important Update at Google I/O 2026

Ibtisam Ali — Sat, 23 May 2026 20:11:20 +0000

This is a submission for the Google I/O Writing Challenge

Introduction

Google I/O 2026 just wrapped up, and as expected, the announcements were packed with futuristic ideas—Android XR smart glasses, cinematic video generation, and other flashy demos that usually dominate the headlines.

But the update that actually stood out to me wasn’t the most visually impressive. It was something much more practical: Gemini 3.5 Flash.

As someone who spends a lot of time learning, coding, and building projects, I’ve used enough AI assistants to notice a pattern. Today’s models are incredibly powerful—but they’re also heavy. And that weight shows up in one very specific way: latency.

Whether you’re debugging code, generating scripts, or trying to understand a terminal error, there’s always that pause. The response slowly streams in token by token, and even a few seconds of delay can break your rhythm.

Gemini 3.5 Flash feels like Google’s answer to that problem.

What is Gemini 3.5 Flash?

Google introduced Gemini 3.5 Flash as the new default model powering parts of the Gemini ecosystem. It’s designed specifically for speed—especially for real-time, multi-step tasks where responsiveness matters.

According to Google, it runs up to 4× faster than other frontier models.

But speed alone isn’t the interesting part.

Normally, when a model gets faster, you expect it to lose some depth or accuracy. What makes Gemini 3.5 Flash stand out is that it doesn’t seem to follow that trade-off. Google claims it actually beats older “Pro” models on advanced tasks, including coding and autonomous workflows, with a reported 76.2% on Terminal-Bench 2.1.

So instead of being a “lite” version, it feels more like a model that was engineered from the ground up to reduce delay without sacrificing capability.

My Perspective: Protecting the Flow State

People often debate which model performs best on benchmarks, but in real-world development, something else matters more: momentum.

When you’re deep into debugging something—maybe a broken VM, messy logs, or a database query that refuses to behave—you’re thinking fast. Your brain is building a chain of logic step by step.

In those moments, AI is most useful when it behaves like an extension of your thoughts. You ask a question, you get an answer, and you keep moving.

But when there’s a 10–15 second delay, something breaks. You tab away. You lose focus. Sometimes you don’t even come back to the problem with the same clarity you had a moment before.

That’s why Gemini 3.5 Flash is interesting. If it really delivers consistent frontier-level reasoning at high speed, it doesn’t just make AI “better”—it makes it feel invisible. Like part of your development environment instead of a separate tool you wait on.

Final Thoughts & Critique

I’m genuinely excited to see Gemini 3.5 Flash roll out across Google AI Studio and developer tools. It feels like a very deliberate shift toward optimizing for real developer experience instead of just benchmark leadership.

That said, I still have some skepticism.

Speed always comes with a question: what’s the compromise? A faster model can sometimes feel more confident than correct, especially when handling complex, multi-file reasoning or long context chains. That’s where things like hallucinations or shallow analysis could show up.

The real test won’t be keynote demos—it will be how it performs in messy, real-world codebases where nothing is clean or predictable.

Still, if it lives up to the promise, Google has focused on something that actually matters to developers more than anything else: removing friction.

And honestly, that’s something worth paying attention to.

How I Built a Hospital Management System with Laravel

Ibtisam Ali — Tue, 19 May 2026 20:14:38 +0000

Hey everyone! I'm Ibtisam, a developer from Somaliland learning full-stack web development. Recently, I built MediTrack, a hospital management system with Laravel, and I want to share what I learned along the way.

Why I Built MediTrack

I wanted to understand how real-world applications work beyond simple CRUD projects. Healthcare systems seemed like a perfect challenge because they involve:

Multiple user roles (Admin, Doctor, Receptionist)
Complex data relationships (Doctors → Patients → Appointments)
Real business logic (managing prescriptions, lab tests)

So I built MediTrack to learn and create a solid portfolio project.

What MediTrack Does

It's a role-based hospital management system that helps clinics manage:

👨‍⚕️ Doctors
🧑‍🦽 Patients
📅 Appointments
💊 Prescriptions
🧪 Lab Tests

Features:

Secure authentication (login/register)
Real-time dashboard with statistics
Full CRUD operations for all modules
Search functionality
Responsive Bootstrap UI

The Tech Stack (And Why)

Laravel – Powerful yet beginner-friendly framework with great routing and authentication
MySQL – Handles complex database relationships easily
Bootstrap 5 – Build a clean UI without spending time on CSS
Blade Templates – Dynamic templating that feels natural in PHP

The 3 Biggest Challenges (And How I Solved Them)

1. Database Design

Problem: Connecting Doctors, Patients, Appointments, and Prescriptions without breaking things.

Solution: I learned about Laravel relationships (hasMany, belongsTo) and spent time planning my schema before coding. This saved me from major refactoring later.

Lesson: Plan your database first. It's harder to change later.

2. Authentication & Authorization

Problem: Different users (Admin, Doctor, Receptionist) need different dashboards and permissions.

Solution: Used Laravel's built-in middleware and route guards to check user roles before showing data.

Lesson: Never trust the frontend for security. Always validate on the backend.

3. Getting Real-Time Statistics

Problem: The dashboard needed to show live counts of doctors, patients, appointments, etc.

Solution: Used Laravel's query builders and Eloquent to aggregate data efficiently, then displayed it with simple JavaScript.

Lesson: Database queries matter. Bad queries slow down your app fast.

Here's What It Looks Like

Dashboard

Managing Doctors

Patients Overview

Appointments Management

Key Lessons for Beginners

Start with a real problem – Don't build random projects. Build something that solves a real need.
Plan before coding – Spend 30 minutes sketching your database. It saves hours later.
Use the framework's tools – Laravel has authentication, routing, and validation built-in. Use them instead of reinventing the wheel.
Test locally first – Make sure features work before pushing to production.
Document your code – Future you (and contributors) will thank you.

What's Next?

I'm planning to add:

Patient history tracking
Email notifications for appointments
Role-based dashboards for different user types
A REST API for mobile apps

Check It Out

Want to see the full code, contribute, or just browse around?

GitHub: github.com/adventureibtisam111/meditrack

If MediTrack helped you learn something or you find it useful, I'd love your support:

⭐ Star the repo – Shows other developers it's helpful

💬 Drop feedback** – Issues and suggestions are welcome

💰 Sponsor my work** – Helps me build more educational projects like this

That's it! Building MediTrack taught me that full-stack development isn't magic—it's just solving problems step by step.

If you're learning Laravel or building your first full-stack project, I hope MediTrack inspires you. Let me know if you have questions or want to collaborate!

Happy coding! 💻