Pratik Parmar
2.1K posts

Pratik Parmar
@hackyroot
DevAd at @SimpliSmartHQ 🥑 Dev Guild $NEAR Tech Speaker for #GenAI, #ML & #Web3 Mozillian @mozilla 🦊 Ex. @yellowdotai, @zyte, @intel #DevRel #Edu
C-137 Inscrit le Eylül 2016
2.4K Abonnements899 Abonnés

With the help of @huggingface we (/w @RisingSayak) are building a ML Club India 🇮🇳
What we want to do:
1. Online talks
2. IST compatible timing
2. Open to all
More to come in this week! Watch this space. 🤗
Special thanks to @LysandreJik who motivated me to keep working on this. 🔥

English

Looking for my replacement for the master bedroom in a well-lit 3bhk duplex in indiranagar with a mini pool
💰 25.5k total incl maintenance
🏊♂️ beautiful balcony with mini pool
🌊 attached bathroom
🌳 pretty and quiet surroundings
📍walkable 100ft road, around 17th main
💲 28k setup cost (sofa,dining,kitchen,mattress)
🪙 75k one time deposit
(need to close this asap)
ideal for nature-loving people who need something pretty to live in and not small boxes
DM only if you're fine with all of these
Available immediately




English

Starting in just a few hours 🔥
Excited to walk through how we’re building an end-to-end invoice automation pipeline using VLMs and n8n.
Simplismart AI@SimplismartHQ
Join us for InferSights by Simplismart.ai, to learn how to automate invoice processing end-to-end using VLMs and n8n workflows. Build a real-world pipeline that extracts, validates, and structures invoice data at scale. 📅 12 Feb | 6:00 - 7:00 PM IST
English

That tweet on RAG, MCP, LLMs, Agents, Fine-tuning & Quantization got way more attention than I expected.
I want to teach these topics live, in an interactive way.
• Completely FREE
• Who this is for: Working professionals in tech
• Prerequisites: None
For folks who want to learn: Reply with "Interested"
I'll plan to do it in batches, and share the details.
Believe me, you'll learn it in the simplest way.
And yes, I genuinely love teaching.
English
Pratik Parmar retweeté

Deeply disturbing to see a biker lose his life after falling into a deep, open pit at night in Janakpuri, Delhi.
His body reportedly lay there the entire night with no rescue, no response, and no authority in sight for hours.
How does a human life go unnoticed like this? This is a grave failure of civic responsibility.
Those responsible must be held strictly accountable. A truly sad and alarming state of affairs in Delhi, India! 🙏🏻
@DelhiPolice @CMODelhi

English

@fayazara DocsForAI.dev
A tool to transform your video content into AI-friendly documentation
Built with @harshil1712
English

DocsForAI.dev made it to my @ChatGPTapp wrapped!
GPT baba’s advice for 2026: build in public ✨



English

Bengaluru is so advanced that even autos come with @MCP_Community support 🤖👨💻
@peakbengaluru

English

@gothburz I used to joke about how our boss was listening to our slack DMs and huddles, apparently I wasn't totally wrong 🥲
English

I work at Slack.
We tell employees their DMs are private.
And they are.
Mostly.
Look, when we say "private" we mean private between you and the person you're messaging.
And your admin.
And HR.
And legal.
And whatever compliance tool your company bought.
And the export logs.
And the backup systems.
And anyone with a court order.
But other than that, totally private.
We're very clear about this in our documentation.
Page 47.
Section 12.
Subsection C.
Paragraph 8.
The part nobody reads before they trash-talk their manager at 11pm.
Here's what employees don't understand.
When you delete a message, you're just deleting it from your view.
The message still exists.
In exports.
In backups.
In the retention policy.
It's like closing your eyes and thinking you're invisible.
The data belongs to the company, not you.
We say this right in our terms.
Workspace owners control everything.
They decide how long messages are stored.
Sometimes it's 30 days.
Sometimes it's forever.
Hope you didn't say anything spicy in 2019.
Enterprise customers get extra features.
Full message exports.
Metadata tracking.
Who messaged whom.
When.
How often.
Communication patterns.
It's for "compliance."
It's for "legal needs."
It's for "regulatory requirements."
It's definitely not for micromanagement.
We're very careful to explain that admins can't see messages in real-time.
They have to formally request an export.
Fill out some forms.
Click some buttons.
Maybe wait an hour.
Very high barrier.
Almost impossible to abuse.
The key takeaway is simple.
Treat Slack like work email.
Not like WhatsApp.
Not like Signal.
Just because it looks like a chat app doesn't mean it works like one.
If a message could cause trouble when HR reads it, don't send it.
This is empowering employees with knowledge.
If you wouldn't say it in the break room with your manager behind you, don't type it in Slack.
That's privacy.
Informed privacy.
Enterprise-grade informed privacy.

English

We started internal
testing some big updates to the @GoogleAIStudio experience today!
Coming to you early next year but reply below if you’d like early access in the coming weeks 👀
English












