Debasis Bhattacharjee

An LLM is a neural network trained on vast amounts of text to predict and generate language. Unlike traditional software with explicit rules LLMs learn statistical patterns from data and generate probabilistic outputs rather than deterministic ones.

Deep Dive: Traditional software follows explicit if-then rules written by programmers — the same input always produces the same output. LLMs are trained on hundreds of billions of text tokens using self-supervised learning (predicting the next word) developing internal representations of language knowledge and reasoning patterns. At inference time they generate text token by token each token sampled from a probability distribution. This means: the same input can produce different outputs (non-deterministic) the model can generalize to tasks it was never explicitly programmed for it can fail in unpredictable ways unlike traditional software which fails at known edge cases and its 'knowledge' is frozen at training time. Key components: transformer architecture attention mechanism tokenization and the pretraining + fine-tuning paradigm.

Real-World: When you ask a traditional search engine for 'Python list comprehension examples' it retrieves pages containing those exact keywords. When you ask an LLM it understands the intent generates an explanation tailored to apparent context (beginner vs expert) provides examples and can answer follow-up questions — all without having been explicitly programmed for your specific question.

⚠ Common Mistakes: Treating LLMs like databases that return facts reliably (they hallucinate). Expecting deterministic behavior (they are probabilistic). Assuming they have real-time information (they have a training cutoff). Building systems that rely entirely on LLM output without validation or grounding.

🏭 Production Scenario: A legal tech company built a contract review tool that used an LLM to check for specific clause types. In production the LLM occasionally hallucinated that clauses existed when they did not. The fix required adding a verification step that located the actual clause text in the document rather than trusting the LLM's claim.

Follow-up questions: What is the transformer architecture? What is the difference between GPT and BERT? What is fine-tuning versus prompting?

// ID: AI-BEG-001  ·  DIFFICULTY: 2/10  ·  ★★☆☆☆☆☆☆☆☆

AI is the broad field of making machines intelligent. Machine Learning is a subset of AI where systems learn from data. Deep Learning is a subset of ML using multi-layered neural networks. Each is more specific and powerful but also more data and compute intensive.

Deep Dive: AI (Artificial Intelligence) encompasses any technique that enables machines to simulate human intelligence — including rule-based expert systems search algorithms and ML. Machine Learning is the AI approach where systems improve through experience: instead of explicit programming they learn patterns from data. Traditional ML algorithms (decision trees SVMs linear regression) require manual feature engineering — humans decide what features to extract. Deep Learning uses neural networks with many layers that automatically learn hierarchical features from raw data. DL requires large amounts of data and GPU compute but achieves state-of-the-art performance on images text and audio. In 2025 when people say 'AI' in business contexts they usually mean ML or DL — specifically LLM-based systems.

Real-World: A spam filter using keyword rules is rule-based AI. A spam filter using logistic regression on email features (word counts sender history) is ML. A spam filter using a fine-tuned BERT model on raw email text is Deep Learning. All three are AI each progressively more powerful and data-hungry.

⚠ Common Mistakes: Thinking AI = Deep Learning = LLMs. Missing that many production 'AI' systems are traditional ML (gradient boosting random forests) which are often more interpretable cheaper and more appropriate for tabular data. Assuming more complex (deep learning) is always better — for structured/tabular data gradient boosting typically outperforms neural networks.

🏭 Production Scenario: A hospital wanted to predict patient readmission risk. A vendor proposed a deep learning solution requiring 10M training examples. The hospital had 50000 records. A properly tuned gradient boosting model (traditional ML) achieved 0.82 AUC on the available data while the deep learning approach overfit severely with only 0.68 AUC.

Follow-up questions: What is the difference between narrow AI and AGI? When should you use deep learning versus traditional ML? What is transfer learning?

// ID: AI-BEG-003  ·  DIFFICULTY: 2/10  ·  ★★☆☆☆☆☆☆☆☆

Prompt engineering is the practice of designing inputs to LLMs to reliably produce desired outputs. It matters in production because the same model with different prompts can produce dramatically different quality format and accuracy of responses.

Deep Dive: LLMs are extremely sensitive to how questions and instructions are phrased. A vague prompt produces vague output. A well-structured prompt with context constraints examples and a clear output format produces consistent usable output. Key techniques: zero-shot prompting (just the instruction) few-shot prompting (instruction + examples) chain-of-thought prompting (asking the model to reason step by step) system prompts (persistent instructions that frame all interactions) output format specification (JSON markdown specific structure) role prompting (giving the model a persona) and constraint specification (word limits forbidden content required elements). In production prompts are version-controlled tested and iterated on like code.

Real-World: A customer intent classification system was achieving 67% accuracy with a simple prompt. Adding three labeled examples (few-shot) specifying the output as a JSON object with confidence scores and adding a chain-of-thought instruction to 'explain your reasoning before giving the final category' raised accuracy to 89% on the same model.

⚠ Common Mistakes: Writing prompts that work once and assuming they will always work — LLMs are sensitive to small wording changes. Not version-controlling prompts making production debugging impossible. Using prompts that work on GPT-4 and assuming they work identically on GPT-3.5 or other models. Ignoring prompt injection vulnerabilities when building user-facing systems.

🏭 Production Scenario: A content moderation system was incorrectly flagging safe content as harmful at a rate of 12%. Prompt analysis revealed the system prompt was ambiguous about edge cases. Adding 10 examples of borderline-safe content with explicit reasoning reduced false positive rate to 3% without model retraining.

Follow-up questions: What is chain-of-thought prompting? What is the difference between system and user prompts? How do you evaluate and A/B test prompts?

// ID: AI-BEG-002  ·  DIFFICULTY: 3/10  ·  ★★★☆☆☆☆☆☆☆

Hallucination is when an LLM generates confident-sounding but factually incorrect or fabricated information. It happens because LLMs are trained to produce plausible next tokens based on patterns — not to retrieve verified facts.

Deep Dive: LLMs learn statistical patterns from training data and generate text that sounds fluent and coherent — but they have no mechanism for verifying that what they generate is factually true. The model predicts the most probable next token given context which may not correspond to reality especially for: obscure facts (low representation in training data) recent events (after training cutoff) precise numerical information (dates statistics) citations and URLs (commonly fabricated) and complex multi-step reasoning (errors compound). Hallucination is not a bug it is an inherent property of the probabilistic text generation approach. Mitigation strategies: RAG (ground the model in retrieved documents) chain-of-thought (forces the model to reason explicitly) output validation (verify claims against reliable sources) and citation requirements (ask the model to quote source text supporting claims).

Real-World: A legal AI assistant was generating case citations that did not exist — fabricated case names and citations that looked completely plausible. Lawyers who did not verify sources submitted briefs with non-existent precedents. Implementing a verification layer that checked all citations against a legal database before displaying them eliminated the problem.

⚠ Common Mistakes: Believing LLM outputs are inherently factual. Not validating LLM outputs before acting on them especially for medical legal or financial decisions. Using LLMs to recall specific numbers dates or citations without verification. Thinking that larger models do not hallucinate — they hallucinate less but still hallucinate.

🏭 Production Scenario: A medical information chatbot was confidently providing incorrect drug dosage information that contradicted official guidelines. The information sounded authoritative and patients followed it. This resulted in a product recall and regulatory action. The fix required implementing RAG against official medical databases for all drug-related queries.

Follow-up questions: What is grounding in AI and how does it reduce hallucination? What is the difference between closed-book and open-book question answering? How do you measure hallucination rate in a production system?

// ID: AI-BEG-004  ·  DIFFICULTY: 3/10  ·  ★★★☆☆☆☆☆☆☆