Full Stack Camp
144 subscribers
8 photos
16 files
89 links
Fullstack Camp | Learn. Build. Launch.
Welcome to the ultimate tech adventure!
Join us for a hands-on journey through HTML, CSS, JavaScript, React, Node.js, Express & MongoDB — all in one place.
Download Telegram
4️⃣How do you read route parameters in Express?
Anonymous Quiz
0%
a) req.query
50%
b) req.params
50%
c) req.body
0%
d) req.route
5️⃣Which request URL matches this route? app.get("/products/:id")
Anonymous Quiz
67%
a) /products?id=5
33%
b) /products/5
0%
c) /product/5
0%
d) /products?id=:id
7️⃣Which package helps log HTTP requests?
Anonymous Quiz
100%
a) cors
0%
b) dotenv
0%
c) morgan
0%
d) uuid
9️⃣Where should sensitive data like API keys be stored?
Anonymous Quiz
0%
a) In JavaScript files
0%
b) In package.json
100%
c) In .env file
0%
d) In routes
🔟How do you set an HTTP status code in Express?
Anonymous Quiz
0%
a) res.send(404)
50%
b) res.status(404).send()
50%
c) req.status(404)
0%
d) res.code(404)
1️⃣1️⃣Which situation will cause an Express app to hang (never respond)?
Anonymous Quiz
33%
a) Sending res.json()
67%
b) Forgetting to call next() in middleware
0%
c) Using app.get()
0%
d) Forgetting express.json()
1️⃣2️⃣ What is a common mistake when using res.sendFile()?
Anonymous Quiz
0%
a) Sending JSON
100%
b) Forgetting absolute path or __dirname
0%
c) Using HTTP instead of HTTPS
0%
d) Missing headers
1️⃣3️⃣ What happens if two routes match the same request?
Anonymous Quiz
50%
a) Express throws an error
0%
b) Both routes run
50%
c) The first matching route runs
0%
d) The last route runs
1️⃣5️⃣ What is the biggest downside of file-based storage (fs) APIs?
Anonymous Quiz
0%
a) Too secure
50%
b) Hard to read
50%
c) Not scalable & risk of data corruption
0%
d) Slow internet
1️⃣6️⃣ Why is fs.readFileSync() dangerous in servers?
Anonymous Quiz
0%
a) It uses callbacks
50%
b) It blocks the event loop
50%
c) It deletes files
0%
d) It crashes Express
2️⃣0️⃣ Are you liking the content so far 🤗?
Anonymous Poll
89%
👍
11%
👎
Forwarded from STEM with Murad 🇪🇹
Why So Many People Quit Coding (Even When They Love It)

Let’s be honest.

Nobody starts learning how to code and thinks,
“Yay! I can’t wait to be frustrated and overwhelmed!” 😩

But somewhere between writing your first hello world and facing your 10th error in one hour…

People start to tap out.

Here’s why people give up on their coding journey:

1. They want it fast, not deep.
They want to “learn fast and get a tech job in 3 weeks.”
But coding is a process. Not magic.
You have to understand the logic, not just memorize tutorials.

2. Tutorial Hell is real.
They hop from one YouTube video to the next without building anything.
It feels productive, but it's just digital procrastination.

3. Impostor syndrome creeps in.
They compare themselves to someone on LinkedIn who built an app in 1 month.
They forget that they’re on chapter 2, comparing it to someone else’s chapter 20.

4. No accountability.
When nobody is checking in on you, it’s easy to “rest” for one day...
Then that day becomes a month.
Then the dream dies a quiet death.

5. They don’t know why they’re learning.
If your only reason is “tech pays well,”
the first moment it gets hard, you’ll start asking yourself:
“Is this even worth it?”
But when you have a clear WHY you push through the discomfort.

Coding will stretch you. It will test your patience.
But it will also grow you. It will open doors.

Not everyone who starts finishes.
But everyone who finishes will tell you it was 1000% worth it.

So, before you quit, ask yourself:

Did I really give it my all… or did I give up when it got uncomfortable?

You’re not behind.
You’re not too late.
You just need to start again with clarity and consistency.

💻 Keep going. The future still needs your code.
4