𝐎𝐛𝐣𝐞𝐜𝐭-𝐎𝐫𝐢𝐞𝐧𝐭𝐞𝐝 𝐏𝐫𝐨𝐠𝐫𝐚𝐦𝐦𝐢𝐧𝐠 𝐖𝐢𝐭𝐡 𝐓𝐲𝐩𝐞𝐬𝐜𝐫𝐢𝐩𝐭 : 𝐚𝐤𝐚 “𝐍𝐨 𝐦𝐨𝐫𝐞 𝐦𝐞𝐬𝐬𝐲 𝐜𝐨𝐝𝐞, 𝐨𝐧𝐥𝐲 𝐜𝐥𝐚𝐬𝐬𝐲 𝐯𝐢𝐛𝐞𝐬”

SHAHNAWAZ SAZID — Wed, 07 May 2025 10:39:54 +0000

I finally sat down and decided it was time to face my fears and tackle Object-Oriented Programming (OOP) in TypeScript. And guess what? It’s not just buzzwords and confusing diagrams it actually makes sense

Checkout All Detailed OOP With Ts Concepts and Code In My GitHub Readme : https://lnkd.in/gG_9UEH9

Here’s a breakdown of what I’ve been learning with a sprinkle of chaos, caffeine, and curiosity:

𝑪𝒍𝒂𝒔𝒔 & 𝑶𝒃𝒋𝒆𝒄𝒕

Think of a class like your mom’s biryani recipe and the object is the biryani you make from it. The recipe doesn't change, but you can make as many plates as you want .

𝑰𝒏𝒉𝒆𝒓𝒊𝒕𝒂𝒏𝒄𝒆

Why write the same code twice when you can inherit your dad’s methods and your mom’s properties? OOP lets one class borrow another’s stuff. Just like real life but with less drama.

𝑻𝒚𝒑𝒆 𝑮𝒖𝒂𝒓𝒅𝒔 (𝒕𝒚𝒑𝒆𝒐𝒇 & 𝒊𝒏)

These are the bouncers of TypeScript. They check IDs at the door before letting values in. “Sorry buddy, only strings allowed here.”

𝘪𝘯𝘴𝘵𝘢𝘯𝘤𝘦𝘰𝘧 :
This one checks if an object is from a certain class. Great for those moments when you’re like, “Wait... what even are you?”

𝑨𝒄𝒄𝒆𝒔𝒔 𝑴𝒐𝒅𝒊𝒇𝒊𝒆𝒓𝒔

public, private, and protected the introvert/extrovert settings for your class properties. Finally, I can keep my variables from oversharing.

𝑮𝒆𝒕𝒕𝒆𝒓𝒔 & 𝑺𝒆𝒕𝒕𝒆𝒓𝒔

Why give direct access to your private stuff when you can negotiate with a getter? These let you control how your properties are viewed and changed like a velvet rope to your data.

𝑺𝒕𝒂𝒕𝒊𝒄 𝑴𝒆𝒕𝒉𝒐𝒅𝒔 & 𝑷𝒓𝒐𝒑𝒆𝒓𝒕𝒊𝒆𝒔

These belong to the class, not any specific object. It's like that one cousin who thinks they speak for the whole family.

𝑷𝒐𝒍𝒚𝒎𝒐𝒓𝒑𝒉𝒊𝒔𝒎

Different objects acting the same way. Like how every intern, no matter the department, somehow ends up making coffee.

𝑨𝒃𝒔𝒕𝒓𝒂𝒄𝒕𝒊𝒐𝒏

Hide the messy details and just show the clean interface. It’s like every cooking show ever: “And wooooh! I already made this off-camera!”

𝑬𝒏𝒄𝒂𝒑𝒔𝒖𝒍𝒂𝒕𝒊𝒐𝒏
Keep your internal logic locked up like it’s your browser history. Only show what’s necessary. Boundaries matter even in code.

TypeScript #OOP #ObjectOrientedProgramming

Setting Up a TypeScript + Express + MongoDB(Mongoose) Backend from Scratch

SHAHNAWAZ SAZID — Mon, 07 Apr 2025 05:27:19 +0000

If you're planning to build a scalable, type-safe Node.js backend, integrating Express, Mongoose, TypeScript, dotenv, and CORS, here's a clean and efficient way to set it up. We'll also configure a .env file and write some essential build scripts. Let's walk through the setup step by step!

🧱 1. Initialize the Project

npm init -y

This command creates a package.json file with default settings.

⚙️ 2. Install Core Dependencies

npm install express mongoose dotenv cors

These are the libraries we'll need for our application:

express: Minimal and flexible Node.js web framework.

mongoose: ODM for MongoDB.

dotenv: Loads environment variables from .env.

cors: Enables Cross-Origin Resource Sharing.

🛠️ 3. Install Dev Dependencies

npm install --save-dev typescript @types/node @types/express @types/cors

These packages are required for TypeScript support and type definitions:

typescript: The TS compiler.

@types/node, @types/express, @types/cors: Type declarations for Node.js, Express, and CORS.

📁 4. Initialize TypeScript

tsc --init

In the generated tsconfig.json, update the following two lines:

"rootDir": "./src",
"outDir": "./dist",

This ensures TypeScript will transpile source files from src/ to dist/.

🧪 5. Add Scripts to package.json
Inside your package.json, update the scripts section:

"scripts": {
  "build": "tsc",
  "start": "node ./dist/app.js",
  "dev": "ts-node-dev --respawn src/app.ts"
}

The build command compiles TypeScript, and start runs the built JavaScript. If you’re using ts-node-dev for development, you can hot-reload using the dev script.

🔥 Install ts-node-dev if using the dev command:

npm install --save-dev ts-node-dev

🌐 6. Create the .env File
At the root of the project, create a .env file and add your environment variables:

PORT=5000
DATABASE_URL=mongodb URI

📝 Note: Replace sensitive credentials before committing. Add .env to .gitignore!

🧠 7. Basic Project Structure
Create your folder structure:

project-root/
│
├── src/
│   ├── app.ts
│   └── server.ts
│
├── dist/
├── .env
├── tsconfig.json
└── package.json

💻 8. Sample server.ts

// src/server.ts
import express from 'express';
import mongoose from 'mongoose';
import dotenv from 'dotenv';
import cors from 'cors';

dotenv.config();

const app = express();
const PORT = process.env.PORT || 5000;

// Middleware
app.use(cors());
app.use(express.json());

// MongoDB Connection
mongoose
  .connect(process.env.DATABASE_URL as string)
  .then(() => console.log("MongoDB connected"))
  .catch((err) => console.error("MongoDB connection error:", err));

// Routes
app.get('/', (_req, res) => {
  res.send('API is running...');
});

app.listen(PORT, () => {
  console.log(`Server is running on port ${PORT}`);
});

🧪 9. Build and Run the Project

npm run build
npm start

Your server should now be live and connected to your MongoDB Atlas cluster!

🧼 Bonus Tips
Use ts-node-dev during development for hot reloading:

npm run dev

Always include .env in your .gitignore.

Use proper error handling middleware and structure routes/controllers separately for larger apps.

📌 Conclusion
You’ve now built a clean TypeScript backend setup using Express, Mongoose, dotenv, and CORS. This is a solid boilerplate for most backend projects — scalable, type-safe, and easy to maintain.

If you found this helpful, feel free to share it with your dev circle! 💙

DEV Community: SHAHNAWAZ SAZID

TypeScript #OOP #ObjectOrientedProgramming

Setting Up a TypeScript + Express + MongoDB(Mongoose) Backend from Scratch