Bar chart of p99 latency for a primary-key SELECT from Node.js 22: pg raw SQL 4.8 ms, Drizzle ORM 5.4 ms, Prisma 9.7 ms

pg vs Prisma vs Drizzle: PostgreSQL Driver Latency from Node.js 22, Measured with autocannon

Runtime choice barely matters once a database is in the path. pg, Drizzle and Prisma on the same Node.js 22 query: p99 from 4.8 ms to 9.7 ms.

Oct 8, 2026 performance, javascript

Beginner diagram showing three documents on the left, a prompt in the middle that pastes relevant snippets as context, and a JSON reply on the right with answer, source and confidence fields

Grounding a Model with Your Own Documents and Getting a Reply Your Code Can Check

Beginner guide to grounding a language model in your own documents (simple RAG) and asking for a JSON reply your code can validate.

Oct 8, 2026 software-engineering, beginner

Header card showing four metrics for an AI code-review agent: 71% precision, 22% ignored comments, 2 escaped defects and $0.11 cost per PR

AI SDLC: How to Measure an AI Code-Review Agent Before You Trust It

Five metrics for an AI code-review agent on a .NET repo: precision, ignored comments, escaped defects, turnaround and cost per PR, plus the dashboard.

Oct 8, 2026 ai

Bar chart of mean wall time for a 10 million element sum-of-squares loop: Python for loop 1,420 ms, Python generator 905 ms, NumPy 12.4 ms, Rust 3.1 ms, Rust with rayon 0.9 ms

Python vs Rust in a Hot Loop: What 10 Million Iterations Cost, Measured with hyperfine

Benchmark the same sum-of-squares hot loop in plain Python, NumPy, Rust and Rust with rayon. From 1,420 ms down to 0.9 ms, and when each step is worth it.

Oct 7, 2026 performance, rust

Beginner diagram showing a chat completions HTTP request with system and user messages on the left, an arrow, and the JSON response with the assistant message on the right

Calling a Language Model from Code: Your Prompt Is Just an API Request

A beginner walkthrough of calling a language model from a program: the HTTP request, system and user roles, max tokens, temperature and reading the reply.

Oct 7, 2026 software-engineering, beginner

Bar chart of mean serialization time per 1 KB order: Newtonsoft.Json 2,140 ns, System.Text.Json reflection 1,080 ns, System.Text.Json source generator 742 ns, source generator with Utf8JsonWriter 588 ns

System.Text.Json Source Generators vs Newtonsoft.Json: A BenchmarkDotNet Comparison on .NET 8

Benchmark Newtonsoft.Json against System.Text.Json with reflection and source generators. Serialization drops from 2,140 ns to 588 ns with zero allocations.

Oct 6, 2026 performance, dotnet

Beginner diagram showing the four steps a language model takes to answer a prompt, from splitting the prompt into tokens to predicting the next token and repeating until done

How a Language Model Answers You: Tokens, Prediction and Repetition

A beginner-friendly explanation of what happens between typing a prompt and getting an AI answer: tokens, next-token prediction and why models make things up.

Oct 6, 2026 software-engineering, beginner

Two charts, LLM cost per hour and p95 latency, each with a red SLO line that the cost series crosses near the end

Enterprise AI: Cost and Latency SLOs for LLM Workloads - Burn-Rate Alerts for Azure OpenAI in Production

Define cost and p95 latency SLOs per team and model for Azure OpenAI, compute burn rates in KQL, and page only when both windows are on fire.

Oct 6, 2026 ai

Bar chart of mean EF Core query time per request: tracking with Include at 42.3 ms, AsNoTracking at 29.1 ms, AsNoTracking with AsSplitQuery at 17.6 ms, compiled query with projection at 6.8 ms

EF Core Query Tuning: AsNoTracking, Split Queries and Compiled Queries Measured with BenchmarkDotNet

Tune EF Core read paths with AsNoTracking, AsSplitQuery, projections and compiled queries. Benchmark table shows a 42 ms query dropping to under 7 ms.

Oct 5, 2026 performance, dotnet

OData Query Performance Pitfalls in .NET - $expand, Paging and Payload Size Explained

Five OData query mistakes that slow down .NET clients talking to D365 or ASP.NET Core OData APIs, with before/after queries and a request-flow diagram.

Oct 5, 2026 coding, odata, dotnet, d365