Resource hubLearn · Tools · Reference · Best practices · Tips

Everything you need to learn, build, and actually ship AI.

One honest hub instead of ten browser tabs — the courses that hold up, the tools people really use, the reference shelf worth bookmarking, and the practices that separate shipped systems from forever-pilots. No pay-to-rank, no course-mill upsell. Where a claim is a fact, it links to its source.

Curated picks
120+
Sections
5
Pay-to-rank
None
Updated
Monthly
01 · Learning

The courses serious practitioners actually study.

A path, not a credential mill — from the math under the hood to shipping LLM systems in production. Almost all free; all from primary sources.

Foundations

math · code · probability

Machine learning

the classics that still matter

Deep learning & LLMs

transformers · prompting · RAG

Agents, evals & production

the part that actually ships
02 · Tools

The mainstream stack — named, sorted, and linked.

Categories reflect how teams actually buy software in 2026, not who paid for placement. Multimodal is the default now; agents have moved from demo to production.

Assistants & chat

general-purpose models

Coding

where the productivity is real

Image & design

generate, edit, brand

Video & audio

the fast-moving frontier

Work & productivity

where AI meets the day job

Search & research

answers with sources
03 · Reference

The shelf worth bookmarking.

Where to track the field without drowning in hype — primary research, honest benchmarks, signal-heavy newsletters, and the communities that catch things first.

Research & papers

go to the source

Benchmarks & leaderboards

how good, really?

Newsletters & communities

signal, not slop
04 · Best practices

What separates shipped systems from forever-pilots.

The patterns the 5% who make it to production share — and the honest reasons the other 95% stall. Facts link to their sources.

01

Start with evals, not vibes

If you can't measure quality, you can't improve it — you can only demo it. MIT found ~95% of enterprise GenAI pilots delivered no measurable ROI; the ones that shipped built a scoring harness first.MIT ’25

02

RAG before you fine-tune

Most "we need a custom model" is really "we need better retrieval." Grounding answers in your own documents is cheaper, more accurate, and explainable — and it's become the enterprise default for 2026.RAG ’26

03

Engineer the context, not the prompt

The 2026 shift: from clever one-off prompts to governed context — what data the model sees, where it comes from, and who validates it before it reaches an agent. The stack is only as good as the data layer under it.

04

Keep a human on anything that acts

Agentic AI is surging, but only about one in five companies has a mature model for governing autonomous agents. If your AI can take an action, a human should be able to take it back — design the kill switch first.Deloitte ’26

05

Govern shadow AI before it governs you

About 35% of employees have pasted proprietary information into public AI tools, and most security leaders believe a leak has already happened. Give people a sanctioned tool — or they'll use an unsanctioned one.Writer ’26

06

Treat every prompt as untrusted input

Prompt injection, data exfiltration, and insecure output handling are the new top vulnerabilities. The OWASP Top 10 for LLM Apps is the checklist to run before launch — not after the incident.OWASP

07

Ship narrow, then widen

One workflow, end to end, with a measured outcome beats ten half-wired pilots. The gap between individual wins and org-level ROI is structural transformation — not more tools.

08

Buy the platform, not the press release

Plan AI as part of your enterprise architecture, with shared standards for data, identity, and audit — not as isolated department experiments that quietly multiply your attack surface.

05 · Tips

Field notes from the donkey chase.

Short, true, and occasionally rude. The things people learn the expensive way, so you don't have to.

01

A pilot that never ends isn't a pilot. It's a hobby with a budget.

02

If you can't measure it, you're not deploying it — you're demoing it.

03

The model is not the product. The workflow around it is.

04

RAG your own docs before you fine-tune. Most "custom model" projects are better-retrieval projects in disguise.

05

If your agent can take an action, make sure a human can take it back. Add the kill switch on day one.

06

Don't paste the contract into a chatbot you don't control.

07

"AI-first" with no eval harness is just "vibes-first" with a press release.

08

Pick the tool for the job, not the logo. Three sharp tools beat one that does everything badly.

09

Read the OWASP LLM Top 10 before the pen-test, not after the breach.

10

The demo always works. Production is where the friction lives — and where the value does too.

11

Cite your sources. An AI answer with no link is a confident guess.

12

If the roadmap is three slides and a vibe, it's not a roadmap.

Spotted something out of date, or a tool that earned its place? Tell us — this hub updates monthly. The AI Donkey Chase commentary is ours; every factual claim links to its source.

06 · AI models

Every model that matters — and when to actually reach for it.

The frontier labs, the open-weight challengers, and the tools to run them yourself. What each one is, what it’s good at, and the job it’s built for. Pick the tool for the job, not the logo.

Frontier / flagship

closed-weight · API & apps · the sharpest tools

Open-weight

download · self-host · fine-tune

Run it yourself

local runners, hubs & serving

Capabilities and model names move fast — treat this as a map, not a spec sheet. Every link goes to the source. The AI Donkey Chase commentary is ours.