Forem: Md Mijanur Molla

I Thought This Was Just a Fun Coding Challenge… Then I Saw People Competing Against AI 🔥

Md Mijanur Molla — Sat, 09 May 2026 10:59:54 +0000

At first, I expected something casual.

Maybe a few frontend mini games.

Maybe some simple browser challenges.

But after exploring VibeCode Arena’s Beat The Heat event…

👉 It became surprisingly addictive.

Because this is not just “solve and leave” coding.

It’s:

Build
Compete
Improve
Compare against AI
Climb the leaderboard

And honestly?

That changes everything.

🎮 What Makes It Different

Most coding platforms focus only on:

DSA
Algorithms
Standard interview problems

But this challenge is different.

Here you build:

Browser games
Interactive logic systems
Creative frontend experiences

Using:

HTML
CSS
Vanilla JavaScript

No heavy frameworks.

Just creativity + execution.

🧠 The Fun Part

Some challenges look simple…

Until you actually try solving them 😄

You start thinking:

👉 “Okay this is easy.”

Then suddenly:

Edge cases appear
UI logic becomes tricky
Timing breaks
AI solutions start competing too

And now you want to improve your score again.

⚔️ Human vs AI Makes It More Interesting

One thing I really liked:

You can literally compare your solution with AI-generated solutions.

That creates a different mindset.

Instead of just:

👉 “Does my code work?”

You start asking:

👉 “Can I build this cleaner than AI?”

And that’s where the challenge becomes exciting. :contentReference[oaicite:0]{index=0}

🔥 Why You Should Try It

If you enjoy:

Frontend projects
Game development
Creative coding
UI/UX challenges
Logic-heavy interactions

You’ll probably enjoy this a lot.

Especially because:

👉 The leaderboard makes everything competitive.

Once you see people scoring high…

You automatically want to improve your own build 😄

🚀 Try My Challenge Here

I’ve been exploring and creating challenges here:

👉 https://vibecodearena.ai/beattheheat?page=1&pageSize=10&sortBy=responses&sortOrder=desc&utm_source=external&utm_medium=vc3&utm_campaign=beattheheat

Try building something.

Or try beating existing solutions.

And trust me…

Some challenges look easy until they completely break your brain 😭

🎯 Final Thought

AI can generate code fast.

But creative thinking, interaction design, weird edge cases, and fun gameplay?

👉 That’s still where humans shine.

So if you want something more fun than routine coding practice…

This is genuinely worth trying 🔥

EduLumix – One Platform for Learning, Jobs, Resources & Growth

Md Mijanur Molla — Thu, 07 May 2026 12:32:21 +0000

Students today are facing a common problem.

There are too many platforms for:

Learning
Jobs
Courses
Resources
Practice
Career Guidance

And because of that, many students feel confused about:

where to start
what to learn
how to grow
where to find opportunities

That’s why we built EduLumix.

https://edulumix.in

EduLumix is a complete platform specially designed for:

Students
Freshers
Developers
Self-learners
Tech enthusiasts

Our goal is simple:

Learn better. Build skills. Find opportunities. Grow together.

✨ What You Can Find on EduLumix

Job & Internship Opportunities

We regularly share:

Fresher Jobs
IT Jobs
Non-IT Jobs
Remote Jobs
Internship Opportunities
Hiring Updates

Finding beginner-friendly opportunities becomes easier and more organized.

Free Resources for Students & Developers

EduLumix provides many free resources to help learners grow faster.

You can explore:

Tech Projects
Development Resources
Learning Materials
Coding Resources
Video Content
Interview Preparation Content
Career Guidance

Everything is designed in a simple and beginner-friendly way.

Courses & Skill Development

Learning should be structured and practical.

That’s why EduLumix also focuses on:

Courses
Skill Development
Practical Learning
Career-focused Guidance
Placement Preparation

The aim is not just learning theory, but becoming industry-ready.

Mock Tests & Practice

Preparation is very important for placements and interviews.

EduLumix helps students practice through:

Mock Tests
Technical Practice
Aptitude Preparation
Career-focused Assessments

This helps learners improve confidence and performance.

✍️ Tech Blogs & Career Content

EduLumix also shares:

Tech Blogs
AI & Technology Content
Career Tips
Student Guidance
Productivity Content
Real-world Learning Experiences

The content is easy to understand and relatable for students and freshers.

️ Digital Products

EduLumix is also building a space for useful digital products like:

Notes
Templates
Study Materials
Career Resources
Learning Assets

Helping students save time and learn smarter.

Contributor Rewards Program

One of the most exciting features of EduLumix is our Contributor Rewards Program.

Now students and creators can:

Share valuable content
Post jobs and resources
Write blogs
Help the community grow

And earn rewards for their contributions.

How It Works:

1️⃣ Sign up as a Contributor (Free)

2️⃣ Post Jobs, Resources & Blogs

3️⃣ Earn points & redeem for real money

This creates a community where learning and contribution both are rewarded.

Why EduLumix is Different

Unlike many platforms that focus only on courses or only on jobs, EduLumix combines everything together in one ecosystem.

✅ Jobs & Internships

✅ Free Resources

✅ Courses

✅ Mock Tests

✅ Tech Blogs

✅ Digital Products

✅ Contributor Rewards

✅ Career Growth

Everything in one place.

Who Should Use EduLumix?

EduLumix is perfect for:

College Students
Freshers
Developers
Beginners in Tech
Self-learners
Job Seekers
Content Contributors

Whether you want to learn, grow, contribute, or earn, EduLumix has something for you.

Our Vision

We want to build a strong student and developer community where:

Learning becomes easier
Opportunities become accessible
Contributors get recognized
Students grow together

EduLumix is not just another EdTech platform.

It is a growing ecosystem built for the next generation of learners and creators.

Explore EduLumix Today

https://edulumix.in

Learn. Build. Contribute. Grow.

️⃣ Tags

EduLumix #Students #Freshers #Learning #Technology #WebDevelopment #Programming #CareerGrowth #Jobs #Internships #TechCommunity #AI #MockTest #Courses #DigitalProducts #Career #Developers #Education

What Really Happens When You Upload File to the Cloud

Md Mijanur Molla — Wed, 06 May 2026 12:34:55 +0000

Uploading a file feels simple.

You click:

👉 Upload

Select a file…

And within seconds:

👉 It appears in the cloud.

Google Drive. Dropbox. OneDrive. Everywhere.

But behind that simple action…

A lot of engineering is happening.

Let’s break it down 👇

💡 Step 1: You Select a File

It starts with something simple:

Image
Video
PDF
Document

Your browser or app now reads the file from local storage.

At this point:

👉 The file still exists only on your device.

📦 Step 2: File Gets Prepared

Before uploading, the system often:

Checks file size
Validates file type
Compresses data (sometimes)
Splits large files into chunks

Why chunking?

Because uploading a huge file at once is risky.

If upload fails at 99%…

💀 everything would restart.

So systems upload in smaller parts.

Smart move.

🌐 Step 3: Upload Request Starts

Now your app sends a request to a server.

Usually using:

```http id="yj4f4r"
POST /upload




Along with:

* File data
* Metadata
* Authentication token

Now the internet journey begins.

---

## 🔐 Step 4: Secure Connection Happens

If using HTTPS:

* SSL/TLS encryption starts
* Data becomes secure during transfer

This prevents attackers from reading your file during upload.

Very important.

---

## 📡 Step 5: File Travels Across Networks

Your file now moves through:

* Routers
* ISPs
* Data centers
* Cloud infrastructure

All this happens surprisingly fast.

Even for large files.

---

## ☁️ Step 6: Cloud Server Receives the File

Cloud servers receive file chunks.

Then systems:

* Reassemble chunks
* Validate integrity
* Check for corruption

If something is broken:

👉 Upload may retry automatically

That’s why modern uploads feel smooth.

---

## 🗄️ Step 7: File Gets Stored

Now the file is stored in cloud storage systems like:

* Amazon S3
* Google Cloud Storage
* Microsoft Azure Blob Storage

But here’s the interesting part:

👉 Your file may not exist in just one place.

---

## 🔄 Step 8: Replication Happens

Cloud providers often create:

* Multiple copies
* Across different servers
* Sometimes across regions

Why?

Because if one server fails…

👉 Your file still survives.

That’s reliability engineering.

---

## ⚡ Step 9: CDN & Fast Access

If your file is accessed frequently:

Systems may cache it using CDNs.

This helps users worldwide download faster.

That’s why cloud files feel instant.

---

## 🧠 Step 10: Metadata & Permissions

The system also stores:

* File name
* Upload time
* Owner
* Access permissions

This controls:

👉 Who can see the file
👉 Who can edit it
👉 Who can download it

---

# 🔥 What Looks Simple Is Actually Complex

That one upload button may involve:

* Frontend logic
* APIs
* Security systems
* Distributed storage
* Replication
* Retry mechanisms
* Global infrastructure

Huge engineering.

---

## ⚠️ What Can Go Wrong?

A lot.

* Network interruption
* Corrupted chunks
* Permission issues
* Storage failures
* Large file timeout

Modern cloud systems handle all these quietly.

That’s why users rarely notice problems.

---

## 🎯 Real Engineering Insight

Cloud uploads are not just:

👉 “Send file to server”

They are carefully designed systems focused on:

* Reliability
* Scalability
* Security
* Performance

That’s modern software engineering.

---

## 🚀 Final Thought

Next time you upload a file…

Remember:

Behind that tiny progress bar,

👉 Massive distributed systems are working together in milliseconds.

And honestly…

That hidden complexity is what makes modern technology so fascinating 💙

What Really Happens When You Upload a File to the Cloud

Md Mijanur Molla — Wed, 06 May 2026 12:34:32 +0000

Uploading a file feels simple.

You click:

👉 Upload

Select a file…

And within seconds:

👉 It appears in the cloud.

Google Drive. Dropbox. OneDrive. Everywhere.

But behind that simple action…

A lot of engineering is happening.

Let’s break it down 👇

💡 Step 1: You Select a File

It starts with something simple:

Image
Video
PDF
Document

Your browser or app now reads the file from local storage.

At this point:

👉 The file still exists only on your device.

📦 Step 2: File Gets Prepared

Before uploading, the system often:

Checks file size
Validates file type
Compresses data (sometimes)
Splits large files into chunks

Why chunking?

Because uploading a huge file at once is risky.

If upload fails at 99%…

💀 everything would restart.

So systems upload in smaller parts.

Smart move.

🌐 Step 3: Upload Request Starts

Now your app sends a request to a server.

Usually using:

```http id="yj4f4r"
POST /upload




Along with:

* File data
* Metadata
* Authentication token

Now the internet journey begins.

---

## 🔐 Step 4: Secure Connection Happens

If using HTTPS:

* SSL/TLS encryption starts
* Data becomes secure during transfer

This prevents attackers from reading your file during upload.

Very important.

---

## 📡 Step 5: File Travels Across Networks

Your file now moves through:

* Routers
* ISPs
* Data centers
* Cloud infrastructure

All this happens surprisingly fast.

Even for large files.

---

## ☁️ Step 6: Cloud Server Receives the File

Cloud servers receive file chunks.

Then systems:

* Reassemble chunks
* Validate integrity
* Check for corruption

If something is broken:

👉 Upload may retry automatically

That’s why modern uploads feel smooth.

---

## 🗄️ Step 7: File Gets Stored

Now the file is stored in cloud storage systems like:

* Amazon S3
* Google Cloud Storage
* Microsoft Azure Blob Storage

But here’s the interesting part:

👉 Your file may not exist in just one place.

---

## 🔄 Step 8: Replication Happens

Cloud providers often create:

* Multiple copies
* Across different servers
* Sometimes across regions

Why?

Because if one server fails…

👉 Your file still survives.

That’s reliability engineering.

---

## ⚡ Step 9: CDN & Fast Access

If your file is accessed frequently:

Systems may cache it using CDNs.

This helps users worldwide download faster.

That’s why cloud files feel instant.

---

## 🧠 Step 10: Metadata & Permissions

The system also stores:

* File name
* Upload time
* Owner
* Access permissions

This controls:

👉 Who can see the file
👉 Who can edit it
👉 Who can download it

---

# 🔥 What Looks Simple Is Actually Complex

That one upload button may involve:

* Frontend logic
* APIs
* Security systems
* Distributed storage
* Replication
* Retry mechanisms
* Global infrastructure

Huge engineering.

---

## ⚠️ What Can Go Wrong?

A lot.

* Network interruption
* Corrupted chunks
* Permission issues
* Storage failures
* Large file timeout

Modern cloud systems handle all these quietly.

That’s why users rarely notice problems.

---

## 🎯 Real Engineering Insight

Cloud uploads are not just:

👉 “Send file to server”

They are carefully designed systems focused on:

* Reliability
* Scalability
* Security
* Performance

That’s modern software engineering.

---

## 🚀 Final Thought

Next time you upload a file…

Remember:

Behind that tiny progress bar,

👉 Massive distributed systems are working together in milliseconds.

And honestly…

That hidden complexity is what makes modern technology so fascinating 💙

AI vs LLM vs AI Agents vs Automation — What’s the Real Difference?

Md Mijanur Molla — Wed, 06 May 2026 06:51:08 +0000

These days, you hear these terms everywhere:

AI
LLM
AI Agents
Automation

And honestly…

👉 They often get mixed up.

So let’s clear it in a simple, practical way 👇

💡 1. What is AI?

AI (Artificial Intelligence) is the big umbrella.

👉 It means machines that can perform tasks that normally require human intelligence.

Examples:

Image recognition
Speech recognition
Recommendation systems (like YouTube, Netflix)

👉 So remember:

AI = everything smart done by machines

🧠 2. What is an LLM?

LLM = Large Language Model

This is a type of AI focused on language.

Examples:

Chatbots
Code generation
Text summarization

LLMs are trained on massive text data and can:

Understand prompts
Generate responses
Write code

👉 So:

LLM ⊂ AI (subset of AI)

⚙️ 3. What is Automation?

Automation is different.

👉 It means doing tasks automatically using predefined rules.

Examples:

Sending emails automatically
Running scheduled jobs
CI/CD pipelines

Important:

No intelligence required
No learning
Just rules + triggers

👉 So:

Automation = “Do this when that happens”

🤖 4. What are AI Agents?

AI Agents are the next level.

👉 They combine AI + decision-making + actions

An AI agent can:

Understand a goal
Plan steps
Use tools (APIs, browser, code)
Execute tasks

Example:

“Book a flight for me”

Agent will:

Search flights
Compare prices
Fill forms
Complete task

👉 That’s beyond just answering.

🔄 Simple Comparison

Concept	What It Does	Intelligence Level
AI	General smart systems	High
LLM	Works with text/language	High
Automation	Executes predefined tasks	Low
AI Agents	Think + decide + act	Very High

🧠 Easy Way to Understand

Think like this:

Automation = Robot following instructions
LLM = Smart brain for language
AI = Entire intelligence field
AI Agent = Smart assistant that can act

⚡ Real Example

Let’s say:

👉 “Send a report every day”

Automation:

Sends report at 9 AM daily

LLM:

Can generate the report text

AI Agent:

Collects data
Generates report
Sends email
Adjusts based on changes

Huge difference.

🔥 Why This Matters for Developers

Understanding this helps you:

Choose the right tools
Build smarter systems
Avoid confusion
Stay relevant in AI-driven development

Because today:

👉 Developers are not just coding
👉 They are building intelligent systems

🚀 Final Thought

Not everything is AI.

Not every AI is an agent.

Not every system needs intelligence.

👉 The real skill is knowing what to use, where.

And that’s what makes a smart developer in 2026 💙

💬 What do you think is the future — Automation or AI Agents?

Let’s discuss 👇

AI #LLM #AIAgents #Automation #Developers #SoftwareEngineering #TechExplained

This Game Looks Simple… But It Will Break Your Brain in Seconds 🧠⚡

Md Mijanur Molla — Tue, 05 May 2026 07:04:58 +0000

Let’s try something.

You see a challenge.

You think: “Easy.”

You start solving…

…and suddenly your brain goes:

👉 “Wait… what just happened?” 🤯

That’s exactly the kind of problem I built.

🎮 The Challenge

This is not just another coding problem.

It’s a logic + thinking + reaction challenge where:

You must understand hidden patterns
Avoid obvious assumptions
Think one step deeper than usual

Because…

👉 The first answer you think of is usually wrong.

🧠 Why This Is Interesting

Most problems test:

Syntax
Algorithms
Memory

But this one tests:

👉 How you think under confusion

And that’s a completely different skill.

⚠️ The Trap

Here’s what happens:

• You see a pattern → you trust it

• You try a solution → it almost works

• Then something breaks

That’s the trap.

Because:

👉 The logic is not where you expect it to be

🤯 What This Actually Tests

This challenge is designed to test:

• Logical reasoning

• Pattern recognition

• Attention to detail

• Ability to question assumptions

And honestly…

👉 That’s what real-world debugging feels like

🚀 Try the Challenge

I created this on VibeCode Arena 👇

👉 https://vibecodearena.ai/duel/2641cadb-3e8d-46d7-b480-bb6f3457e309

Try it yourself and see:

Can you spot the trick?
Can you solve it without guessing?

🧩 About VibeCode Arena

If you haven’t tried it yet:

It’s a platform where developers:

• Solve real-world challenges

• Compete with AI-generated solutions

• Improve and optimize code

👉 You don’t just write code

👉 You learn how to think better

:contentReference[oaicite:0]{index=0}

💡 Pro Tip

Don’t rush.

Read carefully.

Think twice.

Then answer.

Because:

👉 Speed will make you fail this one.

🎯 Final Thought

Some challenges test your code.

Some test your logic.

This one…

👉 Tests your brain.

Drop your answer below 👇

Let’s see who actually cracks it 🔥

Why Good Architecture Matters More Than Writing Perfect Code

Md Mijanur Molla — Sat, 02 May 2026 06:40:49 +0000

As developers, we spend a lot of time improving our code.

Writing clean functions
Following best practices
Using proper naming
Avoiding duplication

All good things.

But here’s a hard truth:

👉 Perfect code inside a bad architecture still leads to a bad system.

Let’s understand why 👇

💡 Code vs Architecture (Simple Difference)

Code = How you write logic
Architecture = How your system is structured

Code is local.

Architecture is global.

Code solves small problems.
Architecture decides how everything fits together.

💻 You Can Have Clean Code… and Still Fail

Imagine this:

Your code is clean
Functions are well-written
Naming is perfect

But:

Everything is tightly coupled
No separation of concerns
Hard to scale
Hard to modify

👉 The system becomes painful to work with

So even “good code” doesn’t save you.

⚠️ What Bad Architecture Looks Like

You might have seen this:

One huge backend file doing everything
Frontend directly depending on backend structure
No clear separation between modules
Changing one feature breaks another

👉 That’s an architecture problem, not a coding problem.

🔄 Why Architecture Matters More Over Time

Here’s the key:

👉 Code quality matters today
👉 Architecture quality matters tomorrow

As your app grows:

More features are added
More developers join
More data flows through the system

If architecture is weak:

👉 Everything slows down

🚧 Real Example

Feature request:

👉 “Add one small field to user profile”

With good architecture:

Change one module
Everything works

With bad architecture:

Change multiple files
Unexpected bugs
Testing becomes painful

👉 Same feature, very different effort

⚙️ Architecture Enables Scalability

Good architecture helps you:

Scale users
Scale features
Scale team collaboration

Bad architecture:

Slows development
Creates technical debt
Makes future changes harder

🧠 Clean Code vs Good Architecture

Clean code:

Readable
Maintainable
Easy to understand

Good architecture:

Flexible
Scalable
Decoupled
Easy to extend

👉 You need both, but architecture has bigger impact.

💀 Why Developers Ignore Architecture

Because:

It’s not immediately visible
It doesn’t break instantly
It feels “extra work”

But later…

👉 It becomes the biggest problem

🔥 Architecture Fails Slowly

This is important:

Bad code breaks fast.
Bad architecture breaks slowly.

At first:

Everything works

After some time:

Changes become harder
Bugs increase
Development slows

👉 That’s when the pain starts

🎯 What Good Architecture Gives You

Clear structure
Independent modules
Easy testing
Easy scaling
Faster development over time

👉 It makes your system future-proof

🚀 How to Think Better as a Developer

Instead of only asking:

👉 “Is my code clean?”

Start asking:

Can this system scale?
Can I change this easily later?
Is everything tightly coupled?
Can new developers understand this?

👉 That’s architectural thinking

💡 Final Thought

Writing perfect code is important.

But building a system that survives growth…

👉 That’s what real engineering is about.

Because in the long run:

👉 Systems don’t fail because of bad syntax
👉 They fail because of bad design

And that’s why good architecture matters more 💙

How to Build Your Own LLM (Without Spending Millions)

Md Mijanur Molla — Fri, 01 May 2026 11:12:44 +0000

Everyone is talking about LLMs.

ChatGPT, Gemini, Claude…

And a common question developers have is:

👉 “Can I build my own LLM?”

The answer is:

👉 Yes… but not the way you think.

Let’s break it down in a practical way 👇

💀 The Truth About “Building an LLM”

Training a model like GPT from scratch requires:

Massive datasets (billions of tokens)
High-end GPUs (A100, H100)
Huge cost (millions of dollars)

👉 Not practical for individual developers

So instead of reinventing the wheel…

👉 Smart developers build on top of existing models

💡 3 Practical Ways to Build Your Own LLM

🧠 1. Fine-Tuning an Existing Model

You take an existing model and train it on your own data.

Example:

Customer support chatbot
Domain-specific assistant
Resume analyzer

Tools you can use:

Hugging Face Transformers
LoRA / PEFT techniques

👉 This is how most real-world AI apps are built

⚙️ 2. RAG (Retrieval Augmented Generation) — Best Option

This is the most practical approach.

Instead of training the model…

👉 You give it access to your data

Flow:

Store your data (PDFs, docs, DB)
Convert into embeddings
Store in vector database
LLM retrieves relevant data and answers

Tools:

LangChain
LlamaIndex
Vector DB (Pinecone, FAISS)

👉 Fast, cheap, powerful

💻 3. Run Local LLM

You can run models locally using:

Ollama
LM Studio

Example models:

LLaMA
Mistral
Phi

Now you have your own AI running on your machine.

No API cost.

🚀 Example: Build Your Own AI Assistant

Simple architecture:

User → API → LLM → Response

With RAG:

User → API → Vector DB → LLM → Response

👉 This is how modern AI apps work

⚡ When Should You Build Your Own LLM?

You should do this when:

You want domain-specific AI
You need private/local data
You want to reduce API cost
You’re building AI products

⚠️ Common Mistakes

Trying to train from scratch ❌
Ignoring data quality ❌
Not understanding use case ❌

👉 Focus on solving problems, not just building models

🎯 Key Insight

You don’t need to build a giant LLM.

👉 You need to build a system around LLMs

That’s where real value is.

🚀 Final Thought

The future is not:

“Who can train the biggest model”

But:

👉 “Who can use LLMs smartly to solve real problems”

Start small.

Build smart.

And you’ll already be ahead 💙

I Created an Elevator Challenge… And the Lift Kept “Coming” Forever 🛗😭

Md Mijanur Molla — Thu, 30 Apr 2026 05:11:16 +0000

You press the lift button.

Display shows:

“Lift is coming.”

You wait.

30 seconds…

1 minute…

Still not here.

👉 But system says it’s coming.

So I turned this into a coding challenge.

And yes…

This is a real engineering problem.

🛗 The Problem

Basic logic:

User requests lift
Lift moves to floor
Request completed

Simple.

But real buildings are not simple.

⚠️ What Goes Wrong?

In real systems:

• Multiple requests come at once

• Lift keeps changing direction

• Some floors get priority

• Some requests get delayed forever

And suddenly:

👉 Lift feels stuck in another universe.

🧠 What I Observed

When exploring this:

Basic queue logic works
But inefficient scheduling causes delay
Some floors get ignored
System feels slow and unfair

The code works.

But the experience is frustrating.

🔍 The Real Issue

This is not just movement.

It’s about:

• Scheduling

• Optimization

• Fairness

• Real-time decisions

Because:

👉 Serving requests in order is not always optimal.

💡 What Better Systems Do

Real elevator systems use:

Direction-based scheduling
SCAN (elevator algorithm)
Priority handling
Efficient routing

This ensures:

👉 Faster response

👉 Fair service

👉 Less waiting

🔥 Try My Challenge

I turned this into a challenge on VibeCode Arena.

👉 Try it here:
https://vibecodearena.ai/duel/0999a34f-d23e-4156-ae0a-0f5168a49fd2

Can you:

Fix slow lift logic?
Improve scheduling?
Build a smarter elevator system?

🎯 Final Thought

Some systems move data.

Some systems move people.

And this one…

👉 Moves very slowly 😭

Tell me 👇

What’s worse:

Waiting for lift

watching it stop on every floor except yours? 😭

I Created a Restaurant Waitlist Challenge… And My Table Was “Almost Ready” Forever 🍽️😭

Md Mijanur Molla — Wed, 29 Apr 2026 13:14:37 +0000

You’ve heard this before.

“Sir, table will be ready in 5 minutes.”

You smile.

You wait.

10 minutes.

20 minutes.

45 minutes later…

Host says:

Almost ready.

Still almost ready. 💀

So I turned this into a coding challenge.

And surprisingly…

This is a real system design problem.

🍽️ The Problem

The logic looks simple:

Add guests to a waitlist
Assign tables
Update status

Done.

Seems straightforward.

But real restaurants are chaos.

⚠️ What Goes Wrong?

In real systems:

• Tables take longer than expected

• Guests stay longer than predicted

• Wait estimates become wrong

• Queue order may not be fair

• Some people feel stuck forever

And suddenly:

👉 “5 minute wait” becomes 50 minutes.

Sound familiar? 😅

🧠 What I Observed

When exploring this problem:

Basic solutions track a queue
Many ignore changing table availability
Some miss fairness problems
Very few handle dynamic wait predictions

The code works.

But the experience lies.

🔍 The Real Issue

This is not just queue logic.

It’s about:

• Scheduling

• Dynamic prediction

• Fairness

• Uncertainty handling

Because:

👉 Wait time is not a fixed calculation.

It changes constantly.

💡 What a Better System Needs

A smarter waitlist system should consider:

Real table turnover data
Dynamic ETA updates
Queue fairness rules
Party size optimization
Better prediction models

This ensures:

👉 Fewer fake wait estimates

👉 Better customer trust

👉 Less “almost ready forever” trauma

🔥 Try My Challenge

I turned this into a challenge on VibeCode Arena because honestly…

This bug deserved investigation 😂

👉 Try it here:

https://vibecodearena.ai/duel/7298cb69-747f-4f0b-ae7a-ace9df8690e5

Can you:

Fix inaccurate wait times?
Build fairer queue logic?
Stop the “almost ready forever” bug?

🎯 Final Thought

Some bugs crash systems.

Some bugs waste weekends.

This one…

👉 Makes people hungry and angry.

Tell me honestly 👇

What lasts longer:

Restaurant waitlists

“5 more minutes” promises? 😭

Your Portfolio Is Probably Missing This One Thing (And It Matters More Than You Think)

Md Mijanur Molla — Tue, 28 Apr 2026 12:13:27 +0000

A lot of developers spend weeks building portfolios.

They add:

Projects ✅
Skills section ✅
GitHub links ✅
Nice UI ✅

And still…

👉 It doesn’t stand out.

Why?

Because many portfolios are missing one thing that matters a lot:

💡 Context.

Or more specifically:

👉 The story behind your projects.

And trust me…

This matters more than you think.

💻 Most Portfolios Look Like This

Project Card 1
Project Card 2
Project Card 3

Tech stack:

React
Node.js
MongoDB

Looks good.

But there’s a problem.

It tells me what you built

Not:

👉 Why you built it
👉 What problem it solves
👉 What challenges you faced

And that’s where strong portfolios become different.

🎯 Recruiters Don’t Just Want Projects

They want proof you can think.

A project title alone doesn’t show that.

Example:

❌ “Built Job Portal using MERN”

Okay…

But so what?

Now compare:

✅ Built a job portal solving fragmented job discovery for freshers, with search filters, role-based auth, and scalable backend APIs.

Very different signal.

One shows code.

One shows engineering thinking.

🧠 What Your Portfolio Should Include

For every serious project, add:

1. Problem Statement

What problem were you solving?

Not:

“I built a chatbot”

Instead:

“I built a chatbot to simplify candidate support queries.”

Huge difference.

2. Architecture Thinking

Show how you designed it.

Talk about:

Frontend
Backend
Database
APIs
Deployment

Now you sound like a builder.

Not just a coder.

3. Challenges You Faced

This is massively underrated.

Talk about:

Bugs you solved
Scaling issues
Performance fixes
Deployment problems

Because real projects have struggles.

And solving them is experience.

4. Tradeoffs You Made

This is advanced… and powerful.

Example:

👉 Used JWT instead of sessions because…

That shows decision making.

Recruiters love that.

5. Live Demo + Proof

Please…

Don’t just show GitHub.

Show:

Live demo
Screenshots
Demo video
README
Use cases

A project people can try > a repo people may never open.

🔥 Projects Don’t Impress.

Project Thinking Impresses.

Read that again.

Anyone can clone a project.

Not everyone can explain:

Why it exists
Why it was designed that way
Why choices were made

That’s what makes portfolios memorable.

💀 Common Portfolio Mistake

Many developers think:

More projects = better portfolio

Not always.

3 strong projects with depth
can beat

10 shallow projects.

Every time.

⚡ Think Product, Not Assignment

Don’t present projects like college submissions.

Present them like products.

Instead of:

“Task App”

Say:

“Task management tool built to solve team workflow tracking.”

Sounds completely different.

Because it is.

🚀 A Better Portfolio Formula

Try this:

Project + Problem + Architecture + Challenges + Demo

That combination is gold.

💡 Final Thought

Most portfolios focus on showing code.

Great portfolios show thinking.

And in interviews…

Thinking often matters more.

So if your portfolio feels incomplete…

Maybe you don’t need another project.

👉 You may just need better storytelling around the projects you already have.

And honestly…

That might be the missing piece 💙

💬 What do you think every developer portfolio should include?

Live demos?
Case studies?
Architecture diagrams?

Let’s discuss 👇

Portfolio #Developers #SoftwareEngineering #WebDevelopment #BuildInPublic #CareerAdvice #GitHub

🔐 The Hidden Engineering Behind a Simple Login Button

Md Mijanur Molla — Mon, 27 Apr 2026 10:48:26 +0000

It looks so simple.

You click:

Login

And within seconds…

👉 You’re inside the app.

Easy, right?

Not really.

Behind that one tiny button…

There’s a surprising amount of engineering happening.

Let’s break down what really happens 👇

💡 It Starts With a Form

You enter:

Email
Password

And click login.

Simple user action.

But under the hood…

Things are just getting started.

📡 Step 1: A Request Is Sent

Your app sends an API request to the server:

```http id="r4pj4o"
POST /login




Along with:

* Credentials
* Headers
* Authentication data

👉 This is where frontend hands control to backend.

---

## 🔍 Step 2: Input Validation

Before anything else…

The server checks:

* Is email valid?
* Is password empty?
* Any malicious input?

Because security starts early.

Not after login.

---

## 🔐 Step 3: Password Verification

Here’s something important:

Your actual password usually is **not stored directly**.

Instead:

* Stored as hashed value
* Compared securely using algorithms like bcrypt

Server checks:

👉 Does entered password match stored hash?

If yes…

Move forward.

---

## 🧠 Step 4: Authentication Happens

Now system confirms:

👉 You are really you.

This may involve:

* Sessions
* JWT tokens
* OAuth flows

This is where “logged in” begins.

---

## 🍪 Step 5: Session or Token Is Created

Once authenticated:

System often creates:

* Session cookie
  or
* Access token

This is how app remembers you.

Otherwise you’d need to login every request 😅

---

## 🛡️ Step 6: Security Checks

Modern login often includes extra checks:

* Rate limiting
* Suspicious login detection
* MFA / OTP
* Device verification

Because login is a major attack target.

---

## 🗄️ Step 7: User Data Loads

After login succeeds:

Backend may fetch:

* Profile data
* Permissions
* Roles
* Preferences

Example:

Admin and regular user may see different dashboards.

---

## ⚙️ Step 8: Authorization Starts

Authentication says:

👉 You are a user.

Authorization says:

👉 What you can access.

Huge difference.

Often confused.

Very important.

---

## 🚀 Step 9: Redirect + App State Updates

Now frontend updates:

* User marked as logged in
* Protected routes unlocked
* Dashboard loads

And only now…

You “see” login success.

---

# 🔄 Full Flow

Login Click → API Request → Validation → Password Check → Auth → Token/Session → Security Checks → User Data → Dashboard

All behind one button.

---

## ⚠️ Things That Can Go Wrong

A lot.

* Wrong credentials
* Expired token
* Server issues
* Weak password storage
* Broken session handling

That tiny login button carries serious complexity.

---

## 🤯 And We Didn’t Even Cover…

Things like:

* Social login with Google
* OAuth flows
* CSRF protection
* Refresh tokens
* Single Sign-On
* Distributed authentication

That rabbit hole goes deep.

Very deep.

---

## 🎯 Why This Matters

As developers, it changes how you think.

A login button is not:

❌ Just a form

It’s:

✅ Security
✅ Backend logic
✅ State management
✅ User identity system

That’s engineering.

---

## 🚀 Final Thought

Some of the hardest engineering problems…

Hide behind the simplest UI.

A tiny login button may look ordinary.

But behind it?

👉 Authentication systems
👉 Security layers
👉 Distributed logic
👉 Trust

And that’s the beauty of software engineering 💙