Harshal

@yomaokobiah sent you dm maam. Could you please check your inbox??

If you’re an event promoter, I’d like to talk with you about a feature I’m working on. 🤲🏽 Reply or send me a DM.

@bercankilic Already applied! I hope i will make it.see you:)

Hi everyone, I have received hundreds of DMs regarding the positions. We really appreciate the enthusiasm and excitement. Unfortunately, it is simply not feasible to reply to all via DMs, but we have a process that will reply all if you apply via email careers@micro-agi.com

@dineshredy @vlmrun Hey @dineshredy sir. I am interested! I have sent an email regarding Devrel. Could please check my mail?

📍 Live from #NeurIPS! We're looking for the best minds to join us at @vlmrun. If you're passionate about building the future of Vision Language Agents, come say hi or slide into our DMs. We are hiring: app.dover.com/apply/vlm-run/… #AI #MachineLearning #Hiring #VLM #GenAI

@fuzailkazi_ Im waiting ser

I received a lot of messages & I will be reaching back to all of them

@fuzailkazi_ @armoriqio please check your DM sir

Hiring builders at @armoriqio 🛡️ • Software Engineers (1 yr exp min) • Software Engineering Intern (paid) Remote - Early-stage - AI security + Agentic systems No busywork. You’ll ship. DM me or drop a note 👇 #hiring #HiringNow

@shellscape Couldn’t agree more. Curious to learn more about the role if you’re open to sharing details. DMed you

It's wild that developer relations / advocate roles are making a comeback. Also very hard to hire experience for; seen and told those with talent are locked down. The company I work for is hiring. If you've got chops, this could be a nice Christmas present.

@fuzailkazi_ @armoriqio I am interested ser. Dmed you : )

@setofsevens Hi, I have Dmed you on Discord regarding founding engineer. Could you please check ur inbox? Thanks :)

Looking for a founding engineer. Rustaceans preferred. 🦀

@jawad_shreim @MilkStrawAI I want to work with you @jawad_shreim sir. i have emailed you regarding this. Could you please check that?

@jawad_shreim @MilkStrawAI Hi CEO, Nice thread! I have written a blog on How to get started with MilkStraw Ai within minutes. Please check it out here: harshalr.hashnode.dev/getting-starte…

I’m Jawad – CEO @milkstrawai Building the simplest way to access AWS’s deepest discounts (3-year Savings Plans & RIs) → No lock-in → No billing migration → Full control stays yours Story + how it works 🧵

@IbraheemTuffaha @MilkStrawAI @abderizik @alihfadel Lol 😅😅

The quality of PR titles at @MilkStrawAI 😂 "Remove previous bugs and add new ones" Big changes coming up 🔥 Shoutout to @abderizik & @alihfadel for keeping things fun 🚀

@Alexand65601285 Here we go milkstraw.ai

@harshalstwt Exactly — it’s rarely one big mistake. Usually data transfer, background jobs, or RDS/storage changes quietly creeping up over time. How do you usually spot them?

Cloud cost problems usually are not about bad engineering they are about lack of visibility. I wrote a short case study on how teams like Magnitt, Voltlines, etc. use #MilkStrawAI to make sense of AWS costs while scaling. No hype. Just real lessons. 🔗 harshalr.hashnode.dev/how-milkstraw-…

@Alexand65601285 You can solve these problems using Milkstraw Ai

Most data today is visual. Invoices, PDFs, screenshots, videos. But turning visual content into structured data is still painful. Here’s a beginner friendly breakdown of Visual AI and what VLM Run solves 👇 🔗harshalr.hashnode.dev/what-is-vlm-run

Introducing Xandeum Analytics - a real-time monitoring dashboard for the @Xandeum pNode network. What's inside: 👇

@Alexand65601285 Same here. Most of the time it’s not one big mistake, but a few small changes that quietly add up. Finding the spike is easy, understanding why it happened takes the real effort.

@harshalstwt Exactly and the frustrating part is that AWS doesn’t really answer the “why” without a lot of digging. Out of curiosity, what usually ends up causing the spikes when you look into them?

@Alexand65601285 yeah, got it

@harshalstwt Most teams I see only look when something spikes — the hard part is understanding why it changed, not spotting that it did.