Vivek Roushan

Engineer by code 💻 | Dreamer by mind 🌌
Exploring Generative AI, LLMs & intelligent systems | #AI #ML #DSA

[Vivek Roushan @VivekRoushan4]

@AIatMeta The real benchmark isn't generating code—it's understanding large codebases, making safe changes, validating them, and earning a developer's trust.

Can't wait to see how Muse Code performs on real-world repos and complex engineering workflows. 🚀

[Vivek Roushan @VivekRoushan4]

If you've been using Whiteboard like I have—for brainstorming, interview prep, DSA, system design, or study notes—don't wait. Export your boards before it's too late.

Sometimes a random warning popup ends up saving years of notes. Hopefully this post saves yours too. 🙌

(4/4)

[Vivek Roushan @VivekRoushan4]

📥 Until Sep 5, 2026: You can still view and export your existing whiteboards.

The good news?
✅ Microsoft Whiteboard is NOT going away for Microsoft 365 Business, Enterprise, and Education users.
❌ This retirement mainly affects personal Microsoft accounts.

(3/4)

[Vivek Roushan @VivekRoushan4]

For a second, I thought Microsoft was shutting down Whiteboard completely. 😅

After digging into it, here's what I found:

🗓️ After Aug 22, 2026: Personal Microsoft accounts can no longer create or edit whiteboards.

(2/4)

[Vivek Roushan @VivekRoushan4]

Today I opened Microsoft Whiteboard to continue my notes and practice—as I usually do alongside OneNote.

Instead of a blank canvas, I was greeted with this warning:

"Microsoft Whiteboard is being retired."

(1/4)

[Vivek Roushan @VivekRoushan4]

@finkd The era of "AI writes functions" is quickly becoming the era of "AI ships features." 👀

[Vivek Roushan @VivekRoushan4]

@satyanadella Congratulations on a remarkable year—excited to see Microsoft continue setting the pace for the future of AI and cloud innovation!

[Mark Zuckerberg @finkd]

(1) Today we're releasing Muse Spark 1.1 -- a strong agentic and coding model at a very low price. It's available through our new Meta Model API and in Meta AI.

[Vivek Roushan @VivekRoushan4]

@finkd Ah, finally! The moment we've all been waiting for—your arrival.

[Vivek Roushan @VivekRoushan4]

Resume: https://t.co/swTeFl0rWI

(4/4)

[Vivek Roushan @VivekRoushan4]

Looking for my next opportunity!

I'm currently working at TCS as a Java Backend Developer with 1.6 years of experience and am actively exploring new roles.

(1/4)

[Vivek Roushan @VivekRoushan4]

Alongside backend development, I completed a Generative AI internship and worked on:

• LLMs
• RAG
• Python
• AI Applications
• API Integrations

Open to:
✅ Java Backend Engineer
✅ GenAI / AI Engineer

Referrals and opportunities are greatly appreciated!

(3/4)

[Vivek Roushan @VivekRoushan4]

Why design it this way?

Because it makes systems:

✅ Easier to scale
✅ Easier to distribute across servers
✅ More reliable

Any server can handle the request—no previous memory needed.

Stateless = no memory of past requests.

Simple rule. Powerful design.

[Vivek Roushan @VivekRoushan4]

Why is REST stateless?

In REST, every request is treated as completely independent.
The server does not remember previous requests.

Think of it like ordering food:
Every time you order, you must
- give your name
- give your address
- say what you want

[Vivek Roushan @VivekRoushan4]

The restaurant doesn’t remember your last order.

That’s stateless.

In REST, each request must include:

- Authentication (e.g., a token)
- Required data
- Context

The server doesn’t store session information.

[Vivek Roushan @VivekRoushan4]

HTTP defines:
GET
POST
PUT
DELETE

REST says:
- Use GET to fetch data
- Use POST to create
- Keep it stateless
- Structure URLs properly

In short:
HTTP = how data travels
REST = how we design the journey

Interviewers love this distinction.

[Vivek Roushan @VivekRoushan4]

REST vs HTTP
Many people think REST and HTTP are the same.

They’re not.

Think of it like this:
HTTP is the road. 🛣️
It’s the system that allows communication between client and server.
REST is the traffic rules. 🚦
It tells you how to properly use that road.

[Vivek Roushan @VivekRoushan4]

One-line memory trick:
Autoboxing = wrap
Unboxing = unwrap

But here’s the catch
Integer can be null.
int can never be null.

So Java tries to unbox null → 💥 NullPointerException.

Looks harmless.
Breaks production code.

Interviewers love this trap.

[Vivek Roushan @VivekRoushan4]

Java Gotcha ⚠️ — Autoboxing & NullPointerException
Below code line compiles perfectly…
but crashes at runtime

Integer x = null;
int y = x;

Why does this happen?

Java silently converts Integer → int.
This is called autoboxing (int → Integer) / unboxing (Integer → int).