Vikranth Kanumuru (@kanlanc) header
Vikranth Kanumuru (@kanlanc) profile picture

Building Harmony(https://xitter.gq/t.co/mzTFizXZUH) | @cornell alum | @joinodf Fellow | Featured in ABC Australia | 6xTop Writer Medium

San Francisco, CA
Joined October 2016
Photo by Vikranth Kanumuru (@kanlanc)Photo by Vikranth Kanumuru (@kanlanc)Photo by Vikranth Kanumuru (@kanlanc)Photo by Vikranth Kanumuru (@kanlanc)Photo by Vikranth Kanumuru (@kanlanc)Photo by Vikranth Kanumuru (@kanlanc)Photo by Vikranth Kanumuru (@kanlanc)Photo by Vikranth Kanumuru (@kanlanc)Photo by Vikranth Kanumuru (@kanlanc)Photo by Vikranth Kanumuru (@kanlanc)
I'll trade you a Claude code max subscription for a month if you recommend a 10 X Engineer. Infinite agent(s) for a human! DM's open BTW We are building the best AI native ERP for manufacturing You'll work in-person on real factory floors, build Al tools, and see your code used every day. 6-figure salary, equity, in-person team, travel Help rebuild American Manufacturing. Link to apply in the comments (Note: Must relocate to Chattanooga, TN /// In-Person only /// Forward-Deployed)
3
1
11
32,839
AI Employees are def gonna be a thing in 2027
1
1
7
140
Vikranth Kanumuru retweeted
It’s incredibly satisfying to see factories improve their operational metrics because of the software we’ve built.
1
3
14
653
I hate that fact that grokbot messages come in as my dm's in X Worst product decision
1
118
“In the old mythology, immortal youth and loveliness were the privilege of the gods; now, in Lucretius’ vision, our own world enjoys this blessing”
1
1
"Knowing how to read architecture means understanding how the peoples of the past have shaped the problems of their time. In this sense, architecture is configured as a 'complex' gesture: the work of art is an affirmation of thought." Luca Taddio
1
3
Vikranth Kanumuru retweeted
pantheon is a documentary
97
111
26
1,410
76,711
The world for the past week is going exactly like that pwd lol
The bug is like a joke. On Alpine Linux, type 257 to 1024 characters of anything and you get root. 💀
Readers added context they thought people might want to know
Exploitation requires specific conditions, not just typing a long string anywhere on Alpine: sshd built without PAM, password auth enabled, a target account with a '*' password field, and another local account with $5$/$6$ hashes. Root login also must be explicitly permitted. alpinelinux.org/posts/2026-11-… openssh.org/releasenotes.h…
2
92
Vikranth Kanumuru retweeted
ChatGPT and Codex are helping engineers build for the physical world. We’re sharing our progress across mechanical design, electrical engineering, and simulation—from helping our hardware teams iterate faster to testing new workflows with industry collaborators.
736
751
585
8,446
1,422,187
Vikranth Kanumuru retweeted
It's been a rough few weeks for security. I pulled together a guide of the highest-impact actions you can take today:
96
251
86
1,544
342,769
Vikranth Kanumuru retweeted
We asked GPT-6 Astra to edit Qwen3.5-0.8B weights to improve math. It directly changed only 0.016% of weights, fixing 0.8B's reasoning loops & improving math up to 6x and even instruction following 3x, without gradients or training. We call this Weight-Space Programming: frontier LLMs can now natively read/write neural network weights! 🧵 Blog: rikiyat.github.io/blog/weigh…
Readers added context they thought people might want to know
LLM was given weights explicitly as text in prompt and used code/forward passes (per authors' logs) to ablate Qwen looping direction, a known thinking-mode issue per model card. Primarily fixed repetition in that mode, not general 'natively' improving weights/math. rikiyat.github.io/blog/weight-sp… github.com/RikiyaT/lm_und… huggingface.co/Qwen/Qwen3.5-0… huggingface.co/RikiyaT/Qwen3.…
2,367
7,254
5,752
55,944
10,060,711
Vikranth Kanumuru retweeted
Spent the weekend hanging out with some of the team Indian food, team dinners, and some time to catch up outside of work!! 🦅 We spend a lot of our time at different factories, so getting everyone around the same table is pretty special! Pretty cool when the people you’re building it with are also people you want to spend your weekend with 🙂 WE ARE HIRING for Software Engineers and Sales... DM me! 🇺🇸 🦅
2
2
7
2,438
This is nuts!
Last night an AI agent performed brain surgery on a mouse. We gave it 19 gene therapy vectors in a spreadsheet, a mouse model of epilepsy, access to a motorize surgery rig with cameras and one goal: reduce seizures. It picked the drug. It picked the brain region. It derived the coordinates from three papers. Then it drove the stereotaxic arms into the brain and injected 250 nanolitres while watching the entry site through the rig camera for bleeding. A licensed vet gated every irreversible step and held a physical kill switch to stop the AI agent. Thread on what it decided, what it saw, and the moment it refused to let me override it. [Writing this on the spot out of excitement, but I've been 18hrs in front of my laptop coding and coordinating this, so keeping it brief and descriptive, more cohesive thoughts on this soon...]
1
1
77
Vikranth Kanumuru retweeted
I used to be the person companies called after they got hacked. And I noticed something early on. The hack almost never sank them. The cover-up did. Every time, the team’s instinct was the same: wait until we know more, wait until we're sure, wait until we have the perfect statement, etc. And some of the biggest companies in the world have learned what that waiting costs. In 2016, Uber got hacked. Instead of telling anyone, it paid the hackers $100K to delete the data and stay quiet, and labeled it a bug bounty. The truth came out a year later. Uber paid $148M to settle with all 50 states, and its former security chief was criminally convicted. That same year, Yahoo revealed that a 2014 breach had exposed 500M accounts. The news landed in the middle of Verizon buying the company. Verizon cut $350M off the price. And in 2017, Equifax discovered a breach affecting over 140M Americans, then waited 40 days to tell the public. During that window, an executive who'd figured out what happened sold nearly $1M in stock. He went to prison for insider trading. Meanwhile, hackers don't wait. They post your data. They email your customers directly. And when customers hear it from a stranger first, that trust is gone for good. Telling customers early doesn't mean admitting fault. It can be as simple as: "We found suspicious activity. We're investigating. Here's what you should do right now. We'll update you as we learn more." On Tuesday, I'm sharing the exact framework I'd use to write that email if I were in your shoes. Follow and turn on notifications so it's there when you need it. Customers will forgive you for getting hacked. Most of them expect it by now. What they won't forgive is finding out you knew and said nothing.
61
290
31
3,959
602,683
Vikranth Kanumuru retweeted
For four years, every video took my animator nine days. Then I asked him why. @AdamNeumann
12
27
3
288
35,198
Bang bang bang
𝗨𝗡𝗢𝗙𝗙𝗜𝗖𝗜𝗔𝗟 𝗕𝗢𝗔𝗥𝗗 𝗠𝗘𝗘𝗧𝗜𝗡𝗚 𝗨𝗣𝗗𝗔𝗧𝗘: • 713% MRR growth since January • Zero customer churn • Nearly 20 people, mostly software engineers LIVING IN FACTORIES for months Working with AMAZING MANUFACTURERS like Mossberg Firearms, MoonPie, Wellborn Cabinet, and more. Giving the people who build America the tools they deserve. If you run a factory and want an AI operating system, hit me up! Proud of this crew. LFG! 🦅🇺🇸
4
175
Vikranth Kanumuru retweeted
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
1,076
8,903
1,654
69,163
4,264,328
PSA: in light of recent cyberattacks and vulnerabilities, I recommend everyone: * use a good password manager (1Password) and do not duplicate passwords * use two factor auth for everything important (not via sms!! Google Authenticator or better yet YubiKey) * Auto-updates on, and restart weekly so they actually install * Freeze your credit * Get an IRS Identity Protection PIN * Get your cell carrier to give you a port-out PIN or number lock that makes the carrier refuse to move your number without the PIN You can ask your claude code to audit what on your laptop is out of date and needs updating.
83
339
42
4,133
773,146
Vikranth Kanumuru retweeted
As a Forward Deployed Engineer, you must build these projects. Systems that prove you can deploy, secure & prove ROI when AI hits legacy enterprise networks. 1.) Enterprise SSO & RBAC Bridge Build: An auth pipeline connecting your AI stack to Okta/Azure AD via SAML/OIDC with SCIM provisioning and row-level data scoping. Why: No single sign-on and strict data isolation means no enterprise contract. 2.) Air-Gapped Deployment Pipeline Build: Terraform and Helm scripts that deploy your entire AI stack into a customer VPC with zero egress to the public internet. Why: Banks and governments don't let your AI talk to the public cloud. You must deploy in their basement. 3.) Legacy ETL & OCR Ingestor Build: A pipeline using OCR and document parsing to turn 10 years of scanned PDFs and legacy database exports into a clean, queryable vector store. Why: Enterprise AI starves without clean data. The customer's data is always a mess. 4.) Permission-Filtered RAG Engine Build: A retrieval pipeline that enforces user-level RBAC, ensuring the LLM only retrieves and cites documents the specific user has clearance to see. Why: An AI that leaks restricted HR or financial docs is an immediate breach of contract. 5.) Legacy MCP Gateway Build: A Model Context Protocol server that lets an LLM safely query and write to a 15-year-old on-prem SAP or Oracle instance without exposing raw credentials. Why: Agents are useless if they can't touch the customer's actual systems of record. 6.) PII Redaction & Unmasking Proxy Build: Middleware that intercepts LLM traffic, swaps SSNs and credit cards for UUIDs before they hit the model and restores them post-generation with audit logs. Why: Compliance teams will kill the deal if a single PII token hits an external API. 7.) Durable HITL Approval Gate Build: A Temporal workflow that pauses high-stakes agent actions and sends a rich approval block to Slack/Teams, resuming execution only on human click. Why: Enterprises adopt AI only when humans remain legally accountable for the final action. 8.) On-Prem Edge Inference Node Build: A quantized 8B model served via vLLM or TensorRT-LLM on a single customer-owned GPU with MIG partitioning for local, zero-latency triage. Why: Sometimes the data is too hot to move. You must bring the model to the data. 9.) Customer Health & ROI Dashboard Build: A telemetry dashboard quantifying exact time saved, tasks automated and token spend per customer department this month. Why: If the customer doesn't see the ROI quantified, they will churn at renewal. 10.) Customer Data Eval Harness Build: A shadow-testing pipeline that runs 100 real historical customer tickets through your agent to prove accuracy before go-live. Why: Generic benchmarks don't close enterprise deals. Proof on their messy data does. 11.) Technical Discovery to SOW Translator Build: A structured interview framework converting vague "we want AI" executive requests into a scoped 4-week deployment plan with architecture diagrams. Why: FDEs are the translators between revenue (Sales) and reality (Engineering). 12.) Self-Serve Admin & Runbook Portal Build: A UI and documentation suite allowing the customer's internal IT team to manage prompts, view logs and update configs without calling you. Why: Your leverage is measured by how little the customer needs you for day-to-day operations. 13.) Chaos & Failover Suite for Customer VPC Build: A harness simulating network drops and API timeouts to test your AI stack's graceful degradation inside their unstable environment. Why: Customer networks are unpredictable. Your architecture must heal itself. 14.) Multi-Tenant Cost Attribution Engine Build: A FinOps engine tracking exact inference spend per customer, per department and per feature with anomaly alerts. Why: Enterprise finance teams demand strict budget visibility and zero surprise bills. 15.) Public Deployment Case Study Build: 3 published teardowns detailing how you navigated enterprise compliance, integrated legacy systems and delivered measurable business impact. Why: Proof of surviving enterprise complexity gets you hired faster than any resume. Systems that prove you can deploy, secure & prove ROI when AI hits legacy enterprise networks. Most people watch tutorials. Builders ship systems. Bookmark & Repost.
If you learn Forward Deployed Engineering, you will never be unemployed again. I’d do this. Stage 1: Enterprise Identity & Access (The Gatekeeper) - Learn: OAuth2, SAML, OIDC, SCIM provisioning, Row-Level Security (RLS) and multi-tenant data isolation. - Practice: Build an auth bridge connecting your AI app to a simulated customer's Okta/Azure AD, ensuring User A can only query data their specific RBAC role permits. - Why: No SSO and strict data isolation means no enterprise contract. Security review is the first gate. Stage 2: Air-Gapped & VPC Deployments (The Environment) - Learn: Kubernetes (K8s), Helm, Terraform, private container registries, air-gapped networking and egress filtering. - Practice: Script a one-click Terraform/Helm deployment of your entire AI stack into a simulated customer VPC with zero egress to the public internet. - Why: Banks, hospitals and governments don't let your AI talk to the public cloud. You must deploy in their basement. Stage 3: Legacy Data Extraction & ETL (The Fuel) - Learn: OCR, unstructured PDF parsing, mainframe DB connectors, Apache Airflow, dbt and data reconciliation. - Practice: Build a pipeline that ingests 10 years of messy, scanned customer invoices and turns them into a clean, queryable hybrid (vector + relational) store. - Why: Enterprise AI starves without clean data. The customer's data will always be a mess. Stage 4: Secure RAG & Permission-Filtered Retrieval (The Brain) - Learn: Hybrid search, document-level access control, citation grounding, metadata tagging and abstention logic. - Practice: Build a RAG pipeline where the LLM dynamically filters out retrieved chunks that the specific user asking the question doesn't have clearance to see. - Why: An AI that leaks HR salaries or M&A docs to a junior employee is an immediate breach of contract. Stage 5: MCP & Legacy System Integration (The Hands) - Learn: Model Context Protocol (MCP), SOAP/REST translation, web scraping, headless browsers and API rate-limit handling. - Practice: Build an MCP server that lets an LLM safely query and write to the customer's 15-year-old on-prem SAP or Oracle instance without exposing raw credentials. - Why: Agents are useless if they can't touch the customer's actual systems of record. Stage 6: AI Guardrails & PII Redaction (The Shield) - Learn: NER (Named Entity Recognition), deterministic regex filtering, LLM output validation, UUID masking, and audit logging. - Practice: Build a middleware proxy that intercepts LLM inputs/outputs, masks SSNs and credit cards with UUIDs before they hit the model, and restores them post-generation. - Why: Compliance teams will kill the deal if a single PII token hits an external frontier API. Stage 7: Human-in-the-Loop (HITL) Workflows (The Trust) - Learn: Temporal {dot} io, webhook routing, state machines, durable execution and UI approval gates. - Practice: Build a workflow where the AI drafts a $50k purchase order, but physically pauses execution until a human manager clicks "Approve" in Slack or Teams. - Why: Enterprises adopt AI only when humans remain legally accountable for the final action. Stage 8: Edge & On-Prem Inference (The Silicon) - Learn: vLLM, TensorRT-LLM, Ollama, GPU partitioning (MIG), and local quantized models (AWQ/GGUF). - Practice: Deploy a quantized 8B model on a single customer-owned GPU node to handle highly sensitive triage locally without network latency. - Why: Sometimes the data is too hot to move. You must bring the model to the data. Stage 9: Observability & Customer Health (The Pulse) - Learn: OpenTelemetry, Langfuse, custom Grafana dashboards, usage telemetry and cost-attribution. - Practice: Build a "Customer Health" dashboard showing the exact cost-savings, time-saved and token-spend the AI has generated for their specific team this month. - Why: If the customer doesn't see the ROI quantified, they will churn at renewal. Stage 10: Evals on Customer Data (The Proof) - Learn: Golden dataset creation, trajectory grading, shadow testing, and LLM-as-a-judge calibration. - Practice: Take 100 real past customer support tickets, run them through your agent in shadow mode, and prove to the VP of Support that it resolved 80% accurately. - Why: Generic benchmarks mean nothing to a buyer. You must prove the AI works on *their* messy data. Stage 11: Technical Discovery & Scoping (The Translation) - Learn: Stakeholder interviewing, architecture diagramming, SOW (Statement of Work) writing and expectation management. - Practice: Translate a vague "we want AI for supply chain" executive request into a scoped, 4-week technical deployment plan with defined, measurable success metrics. - Why: FDEs are the translators between revenue (Sales) and reality (Engineering). Stage 12: The Handoff & Self-Serve Admin (The Scale) - Learn: Technical writing, runbooks, admin portals, automated onboarding and chaos testing. - Practice: Write a deployment runbook and build an admin UI so the customer's internal IT team can manage the AI stack, update prompts and view logs without calling you. - Why: Your leverage is measured by how little the customer needs you for day-to-day operations. AI labs build the engine. FDEs build the roads. The modern Forward Deployed Engineer builds the secure, durable nervous system that connects frontier intelligence to legacy reality. Bookmark and Repost!
30
83
5
964
64,789