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.
Get the Field Guide — free.
Workflows covered in the guide:
- Build your first small project this week — a webpage, a script, a tidy spreadsheet
- Follow a technical meeting without Googling every other word
- Read code, a pull request, or a terminal without freezing
instant download + emailed copy · no spam · unsubscribe anytime
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 the guide covers.
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”Choose a workflow that fits your task, then check the requirements before trying it.
Choose a workflow you can put to use.
Start with one task and the matching chapter. Gather the inputs, try the example, and check the result against your requirements. The guide is a reference for that process. Your tools, access and experience determine what is practical for you.
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?
Examples to consider. Choose one that fits your tools, available time and experience.
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.
What should I check before using the guide?
Read the chapter list and examples to see whether the guide fits your task. The documents describe a June 2026 snapshot. Product features, access and pricing can change, so confirm any setup instructions against current vendor documentation.
Do I need paid software?
The download is free. Some workflows may require a product account, subscription or hardware. Check the requirements for the workflow you choose before buying or installing anything.
Will a prompt always produce the right answer?
No. Check factual claims, calculations, citations and any output you plan to publish or act on. Use information you are permitted to share and keep consequential decisions under human review.
How do I get the full guide?
Enter your first name and email in the download form. The guide is offered as a download and an emailed copy. No payment card is required. You can unsubscribe from subsequent emails.
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. Downloadable guide snapshot: June 2026. Landing page revised 2026-10-14. Check product instructions against current vendor documentation. Unofficial: product names are trademarks of their respective owners, none of whom reviewed or endorsed this guide.