Dev mode

Dev mode 👨‍💻 Life in DevMode
💡 Projects | Progress | Creativity
🎥 Dev vibes and Lifestyle
📍Building in public

**When collaborative coding goes sideways: The moment you realize you've been building different apps 🤝💻**Had one of tho...
23/08/2025

**When collaborative coding goes sideways: The moment you realize you've been building different apps 🤝💻**

Had one of those "wait, what?" moments today while reviewing my colleague's latest commits. We've been working on the same project for weeks now, dividing components and building in parallel. Everything seemed to be going smoothly until I pulled his recent changes this afternoon.

I'm staring at my screen, scrolling through beautifully written code that looks... completely different from everything else we'd built. Different design patterns, different naming conventions, different architectural approach. All excellent work, but it felt like we'd been building two separate applications without realizing it.

Picture this: I'm sitting there for a solid 15 minutes, trying to figure out how to bring this up without sounding like I'm questioning his expertise. Here I am, the less experienced dev, needing to address architectural inconsistencies with someone whose technical skills I genuinely respect. How do you even start that conversation?

The reality hit me - we'd been so focused on our individual components that we slowly drifted apart on the bigger picture. We had our initial planning sessions, but somewhere along the way we stopped syncing on architectural decisions. He'd been making changes that affected shared components without mentioning it, and I probably did the same without realizing.

Then came the awkward realization that as the project manager, I should have caught this earlier. Regular technical check-ins, documented architectural decisions, clearer boundaries - all the things that prevent exactly this situation.

By the end of the day, I realized this wasn't about right or wrong approaches - both of our code was solid. It was about the ongoing conversations we stopped having. Tomorrow I'm planning to suggest we get back to regular technical alignment sessions and maybe be more explicit about cross-component dependencies.

Fellow developers who've been in similar spots: how do you navigate these conversations when you're the less experienced person but need to drive alignment? And what processes keep collaborative projects architecturally consistent over time?

Currently feeling like I learned more about project management today than I did about coding 😅

“Sometimes the hardest decision as a founder is admitting you're the bottleneck 🚧”You know that event listing platform I...
22/07/2025

“Sometimes the hardest decision as a founder is admitting you're the bottleneck 🚧”

You know that event listing platform I've been posting about? The one that's been dragging on forever? Well, I finally made a tough decision today.

I'm stepping down as project manager.
Don't get me wrong - I'm still the project owner and creator. I still believe in this thing 100%. But I had to face the brutal truth: this project is taking way too long to complete, and a big part of that is on me.

Here's what was happening. We had no real development lifecycle pattern. No clear process. Team members didn't really know what they were supposed to be working on or when things were due. Everyone was just... floating around, waiting for direction that I wasn't giving consistently enough.

I was trying to wear too many hats - founder, product owner, project manager, and developer. Spoiler alert: I was doing none of them particularly well.

So today I handed over the project management reins to one of our team members. Someone who actually knows how to set proper tasks and timelines. Someone who can create structure where I was creating chaos.

We're also finally implementing Scrum methodology and using Trello for project management. You know, like actual professionals do. Revolutionary concept, I know 😅

My new role? I'll be the project owner and chief architect, plus I'll keep coding as one of the developers. Basically, I get to focus on the vision and the technical implementation without getting bogged down in the day-to-day management details that were clearly overwhelming me.
It's weird stepping back from something that's your baby. There's definitely some ego involved - admitting that someone else might manage your project better than you can. But honestly? I'm already feeling lighter. The team seems more energized knowing they'll have clear direction and accountability.

Sometimes the best thing you can do for your project is get out of your own way.

Fellow founders and side-project warriors, have you ever had to make a similar call? How did you know when it was time to step back from a role you thought you had to own?

“Day 1 of setting up a Laravel project after a year: When muscle memory meets brain fog 🧠💭”Started working on my one-mon...
22/07/2025

“Day 1 of setting up a Laravel project after a year: When muscle memory meets brain fog 🧠💭”

Started working on my one-month speed project today - the one I'm managing with AI assistance. Time to actually build this thing! The plan seemed simple enough: set up the backend API, pull the repo, create first controllers, resources, and routes. How hard could it be?

Well, turns out it's been almost a YEAR since I last set up a fresh Laravel project from scratch. My previous project took me that long, so I'm basically relearning the basics all over again.
Picture this: I'm sitting there, staring at my screen for a solid 10 minutes, completely stumped by why I had a table named "people" but a model named "Person". My brain just wouldn't connect the dots. Then it hit me like a truck - tables are plural, models are singular. Basic Laravel convention 101. How did I forget something so fundamental?!

The perfectionist in me kicked in too. Every time I start a new project, I want to do better than the previous one. Better architecture, cleaner code, smarter patterns. Sometimes this means overthinking the simplest things and second-guessing every decision.

Then came the AI assistant hunt. GitHub Copilot? Hit the request limit pretty fast (classic). GitLab Chat? Couldn't get it working properly in VS Code, which was frustrating. But then I tried this other AI coding assistant I'd heard amazing things about Black Box. Holy moly. Even on the free plan, this thing was incredibly helpful. It understood Laravel patterns and conventions better than my sleep-deprived brain did today.

By the end of the day, I managed to get the backend API structure set up, first controllers created, resources defined, and basic routes mapped. I also remembered why I love Laravel and why I hate setting up new projects in equal measure 😂

Tomorrow I'm planning to dive deeper into this Black Box AI agent. If day 1 was this promising, I'm genuinely excited to see what it can do with more complex tasks.

Fellow Laravel devs, tell me I'm not alone here - how long does it take you to get back into the groove after working on the same project for months? And what's your go-to AI coding assistant? Currently feeling like a Laravel noob and a seasoned dev at the same time 😅


That moment when a "quick fix" becomes a deployment nightmare because of your own procrastination 😅Got a call from a cli...
18/07/2025

That moment when a "quick fix" becomes a deployment nightmare because of your own procrastination 😅

Got a call from a client this morning about their app I maintain. Classic timezone bug - the kind that makes you question everything you know about time itself.
The Problem:
• Date conversion between timezones was broken
• Didn't account for European countries changing time zones during the year (DST)
• Some users had incorrect timezones based on where their accounts were created
• Result: Scheduling chaos and confused users

The "Simple" Fix: I identified and fixed the bug in about 2 hours. Not too bad, right?

The real problem i can't deploy it to production.
Why? Because I have pending updates from a MONTH ago that I never pushed to production. I was working on other projects and told myself "I'll deploy this later."
Now I have no clue what exactly was modified in those updates, and I can't risk pushing unknown changes to production just to fix this timezone bug.

Current Status:
• Bug is fixed ✅
• Client needs it ASAP ✅
• I'm stuck doing a full code review comparing my local changes with the last production commit 😭
• Manually checking every single modification before I dare push anything

Lessons I'm learning the hard way:
1. Deploy early, deploy often - "I'll do it later" is a lie we tell ourselves
2. Small, frequent deployments beat large, risky ones every time
3. Document your changes
4. Client emergencies don't wait for your deployment schedule

Fellow developer how do you handle this? Do you have a strict deployment schedule, or do you also fall into the "I'll push it later" trap?
Currently drowning in git diffs and commit messages. Send coffee and maybe a time machine ☕️⏰

When your project hits that wall where you need the collective wisdom of the dev community... Day 3 of rebuilding our as...
09/07/2025

When your project hits that wall where you need the collective wisdom of the dev community...

Day 3 of rebuilding our asset management system and I've hit a complexity that's making me question my database design choices.

I'm building a system where every single asset (laptops, pens, chairs, you name it) needs to track:

✅Origin tracking - Which warehouse/floor/room/shelf it came from
✅ Complete movement history - Immutable trail of every location change
✅ Real-time state management - Available → Assigned → In Transit → Returned
✅ Precise return location - Not just "returned" but "returned to Warehouse A, Floor 2, Shelf 3B"
✅ Concurrent user handling - Multiple people requesting/transferring the same asset

The heart of it: maintaining real-time, bi-directional accuracy across multiple storage sites and users.

At any moment, I need to answer:
- Where is laptop #12345 right now?
- Where did it originally come from?
- Who has had it and when?

# # Where I'm Stuck 🤔

Database design questions:
- How do I model the hierarchical storage locations efficiently?
- Should movement history be event-sourced or snapshot-based?
- How do I handle concurrent state transitions without race conditions?
- What's the best way to enforce "valid location" rules?

But I feel like I'm missing something fundamental...

Have you built similar asset tracking systems?
What patterns/architectures worked best for you? Any specific gotchas I should watch out for?

I'm particularly interested in hearing from folks who've handled:
- Multi-location inventory systems
- Real-time state synchronization
- Audit trail requirements
- Concurrent user management

Sometimes the best solutions come from the community. Drop your insights below - I'm all ears!

Adresse

Yaoundé

Téléphone

+237675120705

Site Web

Notifications

Soyez le premier à savoir et laissez-nous vous envoyer un courriel lorsque Dev mode publie des nouvelles et des promotions. Votre adresse e-mail ne sera pas utilisée à d'autres fins, et vous pouvez vous désabonner à tout moment.

Contacter L'université

Envoyer un message à Dev mode:

Raccourcis

Partager