Everyone’s throwing tech words at you. Here’s the map.
150+ terms in plain English, quick cheat sheets, and five small projects you can build this week.
You nod along in meetings and look the words up afterward.
Repo, PR, endpoint, the command line, “just push to main.” The vocabulary moves faster than anyone bothers to explain, and asking in the moment feels like admitting you don’t belong. So you nod, then lose another hour later trying to work out what they actually meant.
And the explanations you find only make it worse.
Looked up one term and got a definition built from five more terms
Watched a “beginner” tutorial that assumed a computer science degree
Decided you were just “not technical” and left it there
You’re not non-technical. You were handed the jargon without a map. One plain-English companion — the words, the command line, version control, how websites talk to each other, and the AI ideas underneath it all — turns that wall of terms into something you can actually read.
Here’s what you walk away able to do.
Build your first small project this week — a webpage, a script, a tidy spreadsheet
from “Five starter projects”Follow a technical meeting without Googling every other word
from “The lay of the land”Read code, a pull request, or a terminal without freezing
from “Reading and writing code”Finally understand the AI words everyone throws around
from “AI, explained properly”Use the command line and save your work so nothing’s ever lost
from “The command line and saving your work”Ask AI for what you want and actually get it
from “Talking to AI well”You can put this off, sure — but a month from now you’ll still be doing it the slow way, wishing you’d started today.
We made this because we kept watching it not click.
Smart people — people who are genuinely good at their jobs — were paying for these tools and using maybe a tenth of what they could do. Not because they weren’t trying, but because nobody ever showed them the part that actually matters. So we sat down and wrote that part: the moves that work, the ones we’d hand a friend who asked. No filler, no hype, just the stuff we’d actually use ourselves.
The plain-English companion, no panic required.
Stop looking up every word after the fact. You get 150+ terms in plain English, quick reference sheets for the command line and version control, the Claude tools explained simply, and five small projects you can build this week.
150+ terms decoded — from REGEX and PR to RAG and MCP
Cheat sheets for the terminal, Git, HTTP, regex & prompting
The Claude ecosystem: skills, plugins, connectors & use cases
Five starter projects you can build this week
Three steps, and you’re reading in under a minute.
Tell us where to send it
Just your first name and email — that’s the whole form. No hoops, no credit card, nothing to install.
It’s yours in a second
The guide downloads right away, and we’ll pop a copy in your inbox too, so you’ve always got it when you need it.
Try one thing this week
Open it, pick one idea that fits your week, and actually use it. One small win is all it takes to see what this thing can do.
What will you create?
A dozen real things people build with this. Pick one — you could have it working by the weekend.
Build a one-page personal website and put it online
Turn your messiest spreadsheet into a clean summary with charts
Write a script that prints tomorrow’s weather nicely
Connect Google Drive and get a weekly digest of what changed
Build your own one-line command for a task you repeat
Turn messy notes into a polished one-page brief
Learn something like SQL one concept at a time, with quizzes
Make a clean site for your side hustle from six photos
Have AI explain a bug from the error before it fixes it
Compare three tools for your team and get a recommendation
Publish your first change to GitHub and watch it go live
Finally read an error message without panicking
…and that’s a fraction of it. Grab the guide and start building.
A few fair questions.
Am I actually going to be able to do this?
Yes. It’s written to be followed, not admired. Every step is plain, the examples are copy-paste, and a simple first-week plan means you’re never staring at a blank screen wondering what’s next.
Will it actually show me how to set it up?
That’s the whole point. It walks you through the setup step by step and assumes nothing — so you end up with the thing actually working, not just a list of features you read about.
Is it too advanced, or too basic, for me?
It meets you where you are. New to this? It starts from the ground and builds up. Already comfortable? Skip ahead to the prompts and plays — they’ll still earn their keep.
How much time is this going to take?
You can read it in an afternoon, and you’ll have something working the same week. It’s built around small wins, not a giant course you start and never finish.
Is this just hype, or does it actually work?
No fluff. It’s the real moves — the exact prompts, the steps, and the mistakes to skip — from people who use this stuff every day, not a recap of a press release.
Is it really free? What’s the catch?
Genuinely free. We ask for your first name and email so we can send it (and the next one when it’s ready). No card, no catch, and one click to unsubscribe.
Decode it this week.
Grab the Field Guide, keep it open next to your work, and look up the next word that trips you up. By the weekend you’ll be the one explaining them. Free, takes a second, yours to keep.
Get the Field Guide — free.
instant download + emailed copy · no spam · unsubscribe anytime
An independent guide from Prometheus Consulting, written for beginners, useful for everyone. Snapshot as of June 2026; tools move fast — check against current docs. Unofficial: product names are trademarks of their respective owners, none of whom reviewed or endorsed this guide.