<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Manohar Papasani</title>
    <description>The latest articles on DEV Community by Manohar Papasani (@technaom).</description>
    <link>https://dev.to/technaom</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4219229%2Fea62ee7d-53d6-4f5a-a1c6-5dc75a4fe857.png</url>
      <title>DEV Community: Manohar Papasani</title>
      <link>https://dev.to/technaom</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/technaom"/>
    <language>en</language>
    <item>
      <title>You ship agent to production &amp; 3 days later internal user says it's not answering well - next move?</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Thu, 19 Nov 2026 08:01:26 +0000</pubDate>
      <link>https://dev.to/technaom/you-ship-agent-to-production-3-days-later-internal-user-says-its-not-answering-well-next-move-4c1</link>
      <guid>https://dev.to/technaom/you-ship-agent-to-production-3-days-later-internal-user-says-its-not-answering-well-next-move-4c1</guid>
      <description>&lt;p&gt;Asked in an AI agent developer interview.&lt;/p&gt;

&lt;p&gt;What they are really testing: whether you treat a vague complaint as a debugging problem backed by evidence, not a prompt-tweaking exercise, and whether you can protect users while you investigate.&lt;/p&gt;

&lt;p&gt;A strong answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Stabilize first: determine whether the complaint is isolated or systemic. If it looks like a regression, roll back the last change (prompt version, model version, tool config or retrieval index) behind a feature flag.&lt;/li&gt;
&lt;li&gt;Make runs observable: trace every interaction with prompt version, model, retrieved context, tool calls with arguments and results, latency and token usage. Without this you are guessing.&lt;/li&gt;
&lt;li&gt;Reproduce and classify: pull the failing sessions, replay them against the same inputs, and bucket the failures as retrieval miss, wrong tool or bad arguments, instruction-following error, stale or missing data, or provider-side model drift.&lt;/li&gt;
&lt;li&gt;Turn failures into a versioned regression suite: combine deterministic checks (schema valid, required tool called, citation present) with graded checks for answer quality. Calibrate any LLM-as-judge against a sample of human labels before trusting its scores.&lt;/li&gt;
&lt;li&gt;Fix at the right layer: retrieval problems call for chunking changes, metadata filters or reranking, not a longer prompt. Tool problems call for stricter schemas and validation. Prompt changes come last, gated by the eval suite and a shadow or A/B run.&lt;/li&gt;
&lt;li&gt;Close the loop: add in-product feedback, alert on thumbs-down rate and tool error rate, and write a short postmortem that adds the failure modes to the eval set.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Common mistakes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Rewriting the system prompt immediately without reproducing the failure, which often fixes one example and breaks three others.&lt;/li&gt;
&lt;li&gt;Judging the fix on a handful of anecdotes instead of a labelled set with a baseline score.&lt;/li&gt;
&lt;li&gt;Blaming the model without checking data freshness, retrieval results or what changed in the last deployment.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;How would you structure the first 24 hours after a complaint like this, and what would you check before touching the prompt?&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:share:7529070383136903168/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-19-interview" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>aiinterview</category>
      <category>aiagents</category>
      <category>llmops</category>
      <category>genai</category>
    </item>
    <item>
      <title>Leaders who listen hear the doubt before it turns into quitting.</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Thu, 19 Nov 2026 04:01:13 +0000</pubDate>
      <link>https://dev.to/technaom/leaders-who-listen-hear-the-doubt-before-it-turns-into-quitting-4pan</link>
      <guid>https://dev.to/technaom/leaders-who-listen-hear-the-doubt-before-it-turns-into-quitting-4pan</guid>
      <description>&lt;p&gt;“All great achievers are given multiple reasons to believe they are failures. But in spite of that they persevere.”&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;John C. Maxwell&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Your engineers and AI teams hear signals all the time: a missed estimate, a failed experiment, a model that underperforms. Those signals pile up fast, and most people carry them quietly. Listening tells you which ones are real and which are noise, so you can keep people going on work that matters.&lt;/p&gt;

&lt;p&gt;This week, ask one person on your team which setback has been weighing on them most, then listen without offering a fix yet.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:share:7529014774647447552/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-19-leadership" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>leadership</category>
      <category>techleadership</category>
      <category>engineeringmanagement</category>
      <category>aileadership</category>
    </item>
    <item>
      <title>OpenAI's cheapest models per million tokens, and none can be ranked for business work yet.</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Wed, 18 Nov 2026 19:31:13 +0000</pubDate>
      <link>https://dev.to/technaom/openais-cheapest-models-per-million-tokens-and-none-can-be-ranked-for-business-work-yet-bko</link>
      <guid>https://dev.to/technaom/openais-cheapest-models-per-million-tokens-and-none-can-be-ranked-for-business-work-yet-bko</guid>
      <description>&lt;p&gt;gpt-5-nano has the lowest rate on OpenAI's pricing page, at $0.05 per 1M input tokens.&lt;/p&gt;

&lt;p&gt;Prices are from OpenAI's pricing listings as of August 21, 2026.&lt;br&gt;
No independent test results were found, so no model gets a tier yet.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What does each 1M tokens cost you?&lt;/li&gt;
&lt;li&gt;Is the answer good enough for the job?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;⏳ NOT RANKED YET&lt;br&gt;
gpt-5-nano (OpenAI)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;$0.05 input, $0.005 cached and $0.40 output per 1M tokens.&lt;/li&gt;
&lt;li&gt;Cheapest rate on the entire OpenAI pricing page.
gpt-5-mini (OpenAI)&lt;/li&gt;
&lt;li&gt;$0.25 input, $0.025 cached and $2.00 output per 1M tokens.
gpt-4o-mini (OpenAI)&lt;/li&gt;
&lt;li&gt;$0.15 input, $0.075 cached and $0.60 output per 1M tokens.&lt;/li&gt;
&lt;li&gt;Context window of up to 128K tokens.
gpt-4o (OpenAI)&lt;/li&gt;
&lt;li&gt;$2.50 input, $1.25 cached and $10.00 output per 1M tokens.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;📌 WHY NO TIER YET&lt;br&gt;
Independent results&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Only vendor pricing pages were found, so no model is ranked for quality or speed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What this means for your team:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Compare output prices separately, since output costs 4x to 8x more than input on these models.&lt;/li&gt;
&lt;li&gt;Check cached input rates, which are half the normal input price on gpt-4o and gpt-4o-mini.&lt;/li&gt;
&lt;li&gt;Wait for independent test results before choosing a model for customer-facing work.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Pick one task this week, run it on two of these models, and compare the cost per answer.&lt;/p&gt;

&lt;p&gt;P.S. gpt-4o-mini supports a context window of up to 128K tokens, according to its listing.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:ugcPost:7528880758611079169/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-18-learning" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>genai</category>
      <category>llm</category>
      <category>aitools</category>
    </item>
    <item>
      <title>Can't fit 750M vectors in RAM on one machine. How exactly are you sharding the Vector DB? By Candidate ID? By Tenant/Recruiter?</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Wed, 18 Nov 2026 18:11:30 +0000</pubDate>
      <link>https://dev.to/technaom/cant-fit-750m-vectors-in-ram-on-one-machine-how-exactly-are-you-sharding-the-vector-db-by-ol6</link>
      <guid>https://dev.to/technaom/cant-fit-750m-vectors-in-ram-on-one-machine-how-exactly-are-you-sharding-the-vector-db-by-ol6</guid>
      <description>&lt;p&gt;Asked in an AI engineer interview.&lt;/p&gt;

&lt;p&gt;What they are really testing:&lt;/p&gt;

&lt;p&gt;Whether you can reason about partitioning under a latency SLO instead of just naming a shard key. Strong candidates address fan-out, skew, and memory reduction before they add machines.&lt;/p&gt;

&lt;p&gt;A strong answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Start with the math: 750M vectors at 768 dims in float32 is about 2.3 TB of raw data. Compress first with product or scalar quantization (PQ at 64 bytes per vector is roughly 48 GB), and keep full-precision vectors on disk for reranking.&lt;/li&gt;
&lt;li&gt;Shard by a hash of candidate ID, not by tenant or recruiter. Hashing spreads data evenly, while tenant sharding creates hot shards when a few large customers dominate size and query load.&lt;/li&gt;
&lt;li&gt;Accept scatter-gather but keep it cheap: each shard returns its local top-k (for example 100 candidates for reranking) and a coordinator merges them. Latency is bounded by the slowest shard, so monitor p99 per shard, not averages.&lt;/li&gt;
&lt;li&gt;Prune shards where it is safe. Store location, seniority, and tenant as filterable attributes, or partition coarse IVF clusters by region. Be explicit about pre-filtering versus post-filtering, since aggressive post-filtering can return too few results.&lt;/li&gt;
&lt;li&gt;Size throughput with replicas, not extra shards. Each shard group serves reads from several replicas, so 10k QPS is divided across them. Use consistent hashing so resharding moves only a small fraction of vectors.&lt;/li&gt;
&lt;li&gt;Treat tenant isolation as a separate concern. Enforce access control in the query filter or with per-tenant namespaces, independent of the physical shard key.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Common mistakes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Sharding by tenant or recruiter without accounting for skew, which leaves one node holding the largest account.&lt;/li&gt;
&lt;li&gt;Treating scatter-gather as free and not budgeting merge time and tail latency across shards.&lt;/li&gt;
&lt;li&gt;Trying to keep full float32 vectors in RAM instead of quantizing first, then adding machines to compensate.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;How would you handle filters on fields that change daily, like candidate availability, without rebuilding the index? Curious how others would approach it.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:share:7528879953761738752/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-18-interview" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>aiinterview</category>
      <category>vectordatabase</category>
      <category>rag</category>
      <category>systemdesign</category>
    </item>
    <item>
      <title>Six things happened in AI today; the one worth your attention is Claude Fable 5.2.</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Sun, 15 Nov 2026 12:01:08 +0000</pubDate>
      <link>https://dev.to/technaom/six-things-happened-in-ai-today-the-one-worth-your-attention-is-claude-fable-52-3p2a</link>
      <guid>https://dev.to/technaom/six-things-happened-in-ai-today-the-one-worth-your-attention-is-claude-fable-52-3p2a</guid>
      <description>&lt;p&gt;Here is the rundown.&lt;/p&gt;

&lt;p&gt;🚀 1. Claude Fable 5.2: Anthropic announced Claude Fable 5.2 on 5 November 2026, claiming it is roughly 30% faster and 20% cheaper than the previous generation (announced).&lt;br&gt;
&lt;a href="https://cybermagazine.com/news/this-weeks-top-five-stories-in-cyber-week-2-november" rel="noopener noreferrer"&gt;https://cybermagazine.com/news/this-weeks-top-five-stories-in-cyber-week-2-november&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🔐 2. RAISE Act: New York opened a registration portal requiring large frontier AI developers to register by Jan 1 2027 and to publish safety frameworks and report critical incidents within 72 hours (announced).&lt;br&gt;
&lt;a href="https://techcrunch.com/2026/11/10/openai-anthropic-face-new-oversight-as-new-yorks-ai-safety-law-takes-effect" rel="noopener noreferrer"&gt;https://techcrunch.com/2026/11/10/openai-anthropic-face-new-oversight-as-new-yorks-ai-safety-law-takes-effect&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🌐 3. Hy4: Tencent announced the open‑source visual AI model Hy4, which can control computers and perform complex tasks; model weights and a safety‑testing report are slated for release later (announced).&lt;br&gt;
&lt;a href="https://www.tradingview.com/news/tradingview:16576f06fa5e9:0-weekly-recap-chip-leasing-deal-canceled-and-hy4-visual-ai-model-released" rel="noopener noreferrer"&gt;https://www.tradingview.com/news/tradingview:16576f06fa5e9:0-weekly-recap-chip-leasing-deal-canceled-and-hy4-visual-ai-model-released&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🚀 4. GPT-6 Sol: GPT-6 Sol and GPT-6 Luna were announced as available in ChatGPT Work and Codex for Plus, Pro, Business, Enterprise, and Edu users, while Free and Go users can use Luna in the desktop app (announced).&lt;br&gt;
&lt;a href="https://openai.com/index/introducing-gpt-6-sol-and-luna" rel="noopener noreferrer"&gt;https://openai.com/index/introducing-gpt-6-sol-and-luna&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💰 5. Mirendil: Mirendil reportedly raised $1 billion in a Series A round, with Kleiner Perkins and Clearlake Capital leading and participation from Battery Ventures, Doerr Capital, Google, M13, Pear VC and S32 (reported).&lt;br&gt;
&lt;a href="https://fortune.com/2026/11/13/life-after-jensen-nvidia-private-markets-ai" rel="noopener noreferrer"&gt;https://fortune.com/2026/11/13/life-after-jensen-nvidia-private-markets-ai&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💰 6. Indian startup funding: The article reported that Indian startups secured roughly $31.3 million across 12 deals this week (reported).&lt;br&gt;
&lt;a href="https://shattered.io/indian-startup-funding-31-3-million-12-startups-a2b-180-million-bodhi-tree" rel="noopener noreferrer"&gt;https://shattered.io/indian-startup-funding-31-3-million-12-startups-a2b-180-million-bodhi-tree&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;My read: Worth watching: whether Claude Fable 5.2’s claimed 30% speed boost and 20% cost reduction translates into lower inference cost per request. Also monitor if New York’s RAISE Act registration requirement nudges frontier developers toward more cost‑effective safety tooling.&lt;/p&gt;

&lt;p&gt;💾 Save this if you are tracking AI releases and funding.&lt;br&gt;
Daily AI digest, with a source link under every item.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:share:7527680429445771264/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-15-news" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>genai</category>
      <category>aiengineering</category>
      <category>machinelearning</category>
    </item>
    <item>
      <title>How would you balance this trade-off in practice?</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Sun, 15 Nov 2026 08:01:13 +0000</pubDate>
      <link>https://dev.to/technaom/how-would-you-balance-this-trade-off-in-practice-50kn</link>
      <guid>https://dev.to/technaom/how-would-you-balance-this-trade-off-in-practice-50kn</guid>
      <description>&lt;p&gt;Asked in an LLM inference systems engineer interview.&lt;/p&gt;

&lt;p&gt;What they are really testing: whether you can turn a vague throughput-versus-latency tension into concrete scheduler controls, separate traffic classes, and measurable SLOs, rather than optimising one number in isolation.&lt;/p&gt;

&lt;p&gt;A strong answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Start from SLOs per tier: time to first token (TTFT) and inter-token latency for interactive traffic, and completion-time deadlines for bulk traffic. Maximise throughput only within those constraints.&lt;/li&gt;
&lt;li&gt;Use continuous (iteration-level) batching so new requests join the running batch between decode steps instead of waiting for a full batch to drain. Cap the batch by a token budget and KV-cache memory, not just request count.&lt;/li&gt;
&lt;li&gt;Use chunked prefill, or split prefill and decode onto separate pools, so a long prompt does not stall decode for every active user and tail latency stays bounded.&lt;/li&gt;
&lt;li&gt;Separate capacity by class: a low-latency pool with smaller batches for interactive traffic, and a high-batch pool for offline work. Add priority queues and admission control that defers or sheds bulk work first when load spikes.&lt;/li&gt;
&lt;li&gt;Make batching adaptive: raise the batch token budget when queue depth is high and p95 latency is within target, and lower it when TTFT or inter-token latency breaches the SLO. Sweep batch budgets against load and plot tokens/sec against p95 latency to find the knee.&lt;/li&gt;
&lt;li&gt;Track goodput, meaning tokens/sec that meet the SLO, rather than raw throughput. Re-run the sweep when the prompt-length mix or model version changes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Common mistakes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Quoting a throughput figure without the latency percentile it was measured at.&lt;/li&gt;
&lt;li&gt;Using a fixed static batch size, which wastes GPU capacity under light load or inflates latency during bursts.&lt;/li&gt;
&lt;li&gt;Putting interactive and bulk requests in one unprioritised queue, so bulk jobs starve or real users see inflated latency.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Which split would you pick first for a mixed chat and batch workload, and which metric would you alert on? Curious how others would answer.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:share:7527619473877590016/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-15-interview" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>aiinterview</category>
      <category>llminference</category>
      <category>genai</category>
      <category>mlops</category>
    </item>
    <item>
      <title>In 1994, Jeff Bezos read that web usage was growing at 2,300% a year and decided to start an online bookstore.</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Sun, 15 Nov 2026 04:01:10 +0000</pubDate>
      <link>https://dev.to/technaom/in-1994-jeff-bezos-read-that-web-usage-was-growing-at-2300-a-year-and-decided-to-start-an-online-2bn5</link>
      <guid>https://dev.to/technaom/in-1994-jeff-bezos-read-that-web-usage-was-growing-at-2300-a-year-and-decided-to-start-an-online-2bn5</guid>
      <description>&lt;p&gt;That decision became Amazon. He founded the company in mid-1994 on a road trip from New York City to Seattle, and it began as an online bookstore.&lt;/p&gt;

&lt;p&gt;Over the next decades, the business expanded into video and audio streaming, cloud computing, and artificial intelligence. Its Amazon Web Services branch became the largest provider of cloud infrastructure services.&lt;/p&gt;

&lt;p&gt;In July 2021, Bezos made another key leadership move. He stepped down as CEO and president, became executive chairman, and handed the top job to Andy Jassy, who had been CEO of Amazon Web Services.&lt;/p&gt;

&lt;p&gt;Bezos has described the drive behind this kind of work:&lt;/p&gt;

&lt;p&gt;“That kind of divine discontent comes from observing customers and noticing that things can always be better.”&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Jeff Bezos&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For leaders of engineering and AI teams, start small. Pick one customer behavior this week, such as support tickets, session recordings, or failed model outputs, and ask your team what would make it better. Then give ownership of the next big bet to the people closest to that problem.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:share:7527559127842234368/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-15-leadership" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>leadership</category>
      <category>techleadership</category>
      <category>aileadership</category>
      <category>teams</category>
    </item>
    <item>
      <title>8 AI doc tools ranked by real codebase tests.</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Sat, 14 Nov 2026 19:31:01 +0000</pubDate>
      <link>https://dev.to/technaom/8-ai-doc-tools-ranked-by-real-codebase-tests-3699</link>
      <guid>https://dev.to/technaom/8-ai-doc-tools-ranked-by-real-codebase-tests-3699</guid>
      <description>&lt;p&gt;The most expensive options did not guarantee top sync speeds.&lt;/p&gt;

&lt;p&gt;Independent labs tested these platforms across 40+ engineering codebases.&lt;br&gt;
Focus: sync speed, AST accuracy, and API playground features.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does it sync with code changes automatically?&lt;/li&gt;
&lt;li&gt;Is the pricing transparent for team scaling?&lt;/li&gt;
&lt;li&gt;Can it handle complex API structures?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;🔴 S TIER&lt;br&gt;
Mintlify&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Ranked top in the 2026 benchmark for code-to-docs sync.&lt;/li&gt;
&lt;li&gt;Strong interactive API playground capabilities.
GitBook&lt;/li&gt;
&lt;li&gt;High score for AST accuracy in complex microservices.&lt;/li&gt;
&lt;li&gt;Widely regarded for cross-team collaboration.
Swimm&lt;/li&gt;
&lt;li&gt;Top tier for maintaining internal architecture diagrams.&lt;/li&gt;
&lt;li&gt;Effective for developer-facing REST APIs.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;🟠 A TIER&lt;br&gt;
Document360&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Solid performance for standard documentation needs.&lt;/li&gt;
&lt;li&gt;Clear pricing tiers that scale with team size.
Archbee&lt;/li&gt;
&lt;li&gt;Good for process-based SOP and how-to docs.&lt;/li&gt;
&lt;li&gt;Supports both reference detail and human-friendly text.
ReadMe&lt;/li&gt;
&lt;li&gt;Strong API integration assistance features.&lt;/li&gt;
&lt;li&gt;Reliable for interactive customer knowledge bases.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;🟡 B TIER&lt;br&gt;
Slite&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Functional for basic doc generation tasks.&lt;/li&gt;
&lt;li&gt;May require more manual upkeep than top tiers.
Docusaurus (Meta)&lt;/li&gt;
&lt;li&gt;Open-source option with strong community support.&lt;/li&gt;
&lt;li&gt;Requires more configuration for AI features.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What this means for your team:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Prioritize tools with automatic code-to-docs sync to reduce manual upkeep.&lt;/li&gt;
&lt;li&gt;Verify AST accuracy if your team maintains complex microservice architectures.&lt;/li&gt;
&lt;li&gt;Check if the tool supports interactive API playgrounds for developer-facing products.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Audit your current doc workflow against these benchmarks today.&lt;/p&gt;

&lt;p&gt;P.S. LLM-based tools explain function bodies, but output still requires human review.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:ugcPost:7527430771695837184/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-14-learning" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>devtools</category>
      <category>documentation</category>
      <category>techlearning</category>
    </item>
    <item>
      <title>Eight things happened in AI today; the one worth your attention is Mercor.</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Sat, 14 Nov 2026 12:01:11 +0000</pubDate>
      <link>https://dev.to/technaom/eight-things-happened-in-ai-today-the-one-worth-your-attention-is-mercor-1jfd</link>
      <guid>https://dev.to/technaom/eight-things-happened-in-ai-today-the-one-worth-your-attention-is-mercor-1jfd</guid>
      <description>&lt;p&gt;Here is the rundown.&lt;/p&gt;

&lt;p&gt;💰 1. Mercor: Mercor reportedly secured $750 million in a Series D round, valuing the San Francisco AI‑developer platform at $20 billion (announced).&lt;br&gt;
&lt;a href="https://tradersunion.com/news/business-wealth/show/4238771-us-ai-startups-top-funding" rel="noopener noreferrer"&gt;https://tradersunion.com/news/business-wealth/show/4238771-us-ai-startups-top-funding&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🚀 2. GPT-6 Cyber: OpenAI’s GPT-6 Cyber, limited to vetted Daybreak Red teams, reportedly outperformed its predecessor in spotting high‑severity vulnerabilities (reported).&lt;br&gt;
&lt;a href="https://cryptobriefing.com/openai-anthropic-reveal-new-ai-models-products-in-week-45-of-2026" rel="noopener noreferrer"&gt;https://cryptobriefing.com/openai-anthropic-reveal-new-ai-models-products-in-week-45-of-2026&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💰 3. Mirendil: Mirendil reportedly secured a $1 billion Series A round, led by Kleiner Perkins and Clearlake Capital (announced).&lt;br&gt;
&lt;a href="https://news.crunchbase.com/venture/biggest-startup-funding-rounds-agentic-ai-infrastructure-mirendil-mercor" rel="noopener noreferrer"&gt;https://news.crunchbase.com/venture/biggest-startup-funding-rounds-agentic-ai-infrastructure-mirendil-mercor&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🚀 4. Gemini 4 Hydrogen: Google announced Gemini 4 Hydrogen, a speed‑focused model that reportedly outperforms Gemini 4 Argon at its default thinking level (announced).&lt;br&gt;
&lt;a href="https://mashable.com/tech/google-gemini-4-hydrogen-ai-model-launch" rel="noopener noreferrer"&gt;https://mashable.com/tech/google-gemini-4-hydrogen-ai-model-launch&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💰 5. Future Secure AI: Future Secure AI reportedly raised $82 million in convertible notes, valuing the start‑up at $1.2 billion and giving it unicorn status in Australia (reported).&lt;br&gt;
&lt;a href="https://www.cxnetwork.com/cx-experience/news/every-cx-start-up-funding-deal-you-need-to-know-november-13/amp" rel="noopener noreferrer"&gt;https://www.cxnetwork.com/cx-experience/news/every-cx-start-up-funding-deal-you-need-to-know-november-13/amp&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🔐 6. FedRAMP: FedRAMP announced new vulnerability management rules that will affect over 550 certified cloud providers, shifting from monthly scans to an exposure‑based approach (announced).&lt;br&gt;
&lt;a href="https://federalnewsnetwork.com/cybersecurity/2026/11/fedramp-pushes-new-cyber-vulnerability-rules-to-keep-pace-with-ai" rel="noopener noreferrer"&gt;https://federalnewsnetwork.com/cybersecurity/2026/11/fedramp-pushes-new-cyber-vulnerability-rules-to-keep-pace-with-ai&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💰 7. Agile Robots: Agile Robots reportedly raised $500 million in a round led by SoftBank, valuing the Munich‑based firm at $8.5 billion (7.7 billion euros) (reported).&lt;br&gt;
&lt;a href="https://techxplore.com/news/2026-11-german-ai-robotics-startup-valued.html" rel="noopener noreferrer"&gt;https://techxplore.com/news/2026-11-german-ai-robotics-startup-valued.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💰 8. UFORCE: UFORCE reportedly secured €630 million in financing, with Valor Equity Partners and the UK National Wealth Fund co‑leading the round and new backers such as URIF, Menlo Ventures, Xantium and Hiro Capital (reported).&lt;br&gt;
&lt;a href="https://www.therecursive.com/cee-startup-tech-weekly-13" rel="noopener noreferrer"&gt;https://www.therecursive.com/cee-startup-tech-weekly-13&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💾 Save this if you are tracking AI releases and funding.&lt;br&gt;
Daily AI digest, with a source link under every item.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:share:7527317919223934976/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-14-news" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>genai</category>
      <category>aiengineering</category>
      <category>funding</category>
    </item>
    <item>
      <title>How do you handle conflicts between teams or disagreements on the design?</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Sat, 14 Nov 2026 08:01:00 +0000</pubDate>
      <link>https://dev.to/technaom/how-do-you-handle-conflicts-between-teams-or-disagreements-on-the-design-552o</link>
      <guid>https://dev.to/technaom/how-do-you-handle-conflicts-between-teams-or-disagreements-on-the-design-552o</guid>
      <description>&lt;p&gt;Asked in an AI engineering manager interview.&lt;/p&gt;

&lt;p&gt;What they are really testing:&lt;/p&gt;

&lt;p&gt;Whether you can turn a heated technical argument into a decision people will stand behind, without settling it by seniority or by whoever argues loudest.&lt;/p&gt;

&lt;p&gt;A strong answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Agree on criteria before options: quality on a shared eval set, latency and cost targets, data handling and compliance constraints, and the operational burden over the next year.&lt;/li&gt;
&lt;li&gt;Write the options into a short design doc with the trade-offs for each, so the debate is about evidence rather than preference.&lt;/li&gt;
&lt;li&gt;Where the disagreement is empirical, settle it with a time-boxed experiment, such as comparing a retrieval-based and a fine-tuned approach on the same golden set with the same grading rubric.&lt;/li&gt;
&lt;li&gt;Name one decision owner and a deadline. Escalate with the options and evidence, not with a request for someone to referee.&lt;/li&gt;
&lt;li&gt;Classify the choice as reversible or hard to reverse. Reversible decisions get made quickly and revisited on defined triggers; irreversible ones, like vendor lock-in or data residency, deserve more scrutiny.&lt;/li&gt;
&lt;li&gt;Record the decision, its rationale and the conditions that would reopen it, then communicate it to every affected team, including the ones who lost the argument.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Common mistakes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Mediating indefinitely, so the disagreement becomes the default state while the roadmap slips.&lt;/li&gt;
&lt;li&gt;Deciding by seniority or volume, which costs buy-in from the team that lost.&lt;/li&gt;
&lt;li&gt;Reopening a settled decision in every review because the rationale was never written down.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;How would you handle a case where the evidence favours one team but the other holds a veto on compliance grounds? Curious how others would sequence that.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:share:7527256960128217088/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-14-interview" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>aiinterview</category>
      <category>aiengineering</category>
      <category>genai</category>
      <category>engineeringmanagement</category>
    </item>
    <item>
      <title>Build inclusive teams like a bridge</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Sat, 14 Nov 2026 04:01:02 +0000</pubDate>
      <link>https://dev.to/technaom/build-inclusive-teams-like-a-bridge-546j</link>
      <guid>https://dev.to/technaom/build-inclusive-teams-like-a-bridge-546j</guid>
      <description>&lt;ul&gt;
&lt;li&gt;Seat people with different backgrounds at every design review.&lt;/li&gt;
&lt;li&gt;Make room for quiet engineers to finish their thoughts.&lt;/li&gt;
&lt;li&gt;Judge ideas by evidence, not by who suggested them.&lt;/li&gt;
&lt;li&gt;Hire for a range of experience, then invest in onboarding.&lt;/li&gt;
&lt;li&gt;Ask what a teammate from another background would notice first.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A strong bridge carries many loads, and an inclusive team carries more ideas.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:share:7527196630991937536/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-14-leadership" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>leadership</category>
      <category>techleadership</category>
      <category>inclusiveteams</category>
      <category>engineeringmanagement</category>
    </item>
    <item>
      <title>5 sales forecasting tools, ranked by data transparency and fit.</title>
      <dc:creator>Manohar Papasani</dc:creator>
      <pubDate>Fri, 13 Nov 2026 19:31:05 +0000</pubDate>
      <link>https://dev.to/technaom/5-sales-forecasting-tools-ranked-by-data-transparency-and-fit-2h3d</link>
      <guid>https://dev.to/technaom/5-sales-forecasting-tools-ranked-by-data-transparency-and-fit-2h3d</guid>
      <description>&lt;p&gt;The most accurate enterprise tool has no public pricing.&lt;/p&gt;

&lt;p&gt;Accuracy depends on your data quality, not just the tool.&lt;br&gt;
Here is how the top platforms compare on integration and cost.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does it integrate with your existing CRM?&lt;/li&gt;
&lt;li&gt;Is pricing transparent or hidden?&lt;/li&gt;
&lt;li&gt;Does it handle complex enterprise pipelines?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;🟠 A TIER&lt;br&gt;
Clari (Salesloft)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Enterprise platform for 50+ reps with dedicated RevOps.&lt;/li&gt;
&lt;li&gt;Strongest dedicated forecasting layer, now bundled with Salesloft.
Gong&lt;/li&gt;
&lt;li&gt;Adds buyer conversation intelligence to pipeline data.&lt;/li&gt;
&lt;li&gt;Rated 4.7/5 on G2, leading in ease of use.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;🟡 B TIER&lt;br&gt;
Salesforce Sales Cloud&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Keeps forecasting within the existing Salesforce ecosystem.&lt;/li&gt;
&lt;li&gt;AI features available via Einstein, dependent on data hygiene.
HubSpot Sales Hub&lt;/li&gt;
&lt;li&gt;Forecasting integrated directly into the HubSpot CRM.&lt;/li&gt;
&lt;li&gt;Best for teams already standardized on HubSpot.
Pipedrive&lt;/li&gt;
&lt;li&gt;Lightweight forecasting for smaller sales teams.&lt;/li&gt;
&lt;li&gt;Focuses on simplicity over complex enterprise governance.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What this means for your team:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Clari is best for enterprise pipeline governance and accuracy.&lt;/li&gt;
&lt;li&gt;Gong is superior if rep coaching and conversation analysis are priorities.&lt;/li&gt;
&lt;li&gt;CRM-native tools like Salesforce and HubSpot reduce integration overhead.&lt;/li&gt;
&lt;li&gt;Verify data hygiene before deploying AI-driven forecasting models.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Audit your current forecast variance today.&lt;/p&gt;

&lt;p&gt;P.S. AI models underperform if reps do not log activities consistently.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally shared on &lt;a href="https://www.linkedin.com/feed/update/urn:li:ugcPost:7527068240896815104/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=2026-11-13-learning" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An AI interview question every day, leadership for tech people and hands-on AI learning:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/manohar-papasani-b89916aa" rel="noopener noreferrer"&gt;Follow me on LinkedIn for daily AI updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/TechNaom" rel="noopener noreferrer"&gt;Follow me on GitHub for the AI projects I build&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bsky.app/profile/manoharpapa.bsky.social" rel="noopener noreferrer"&gt;Follow me on Bluesky for AI in short&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://x.com/ManoharPap91329" rel="noopener noreferrer"&gt;Follow me on X for quick AI takes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/technaom"&gt;Follow me on Dev.to for full AI articles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.facebook.com/ManoharPapasani1982" rel="noopener noreferrer"&gt;Follow me on Facebook for every post, every day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://manoharpapasani.pages.dev" rel="noopener noreferrer"&gt;Visit my AI R&amp;amp;D lab website&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>revops</category>
      <category>ai</category>
      <category>b2b</category>
      <category>forecasting</category>
    </item>
  </channel>
</rss>
