Tech terms explained for non-technical founders

Languages

1. HTML

   Short for HyperText Markup Language. The skeleton of every web page. It's what tells the browser what's a heading, what's a paragraph, what's an image. The bricks of a house. Without them, nothing stands up.

2. CSS

   Short for Cascading Style Sheets. The styling - colours, fonts, spacing, layout. CSS is what makes a site look like something instead of looking like a Word document from 1998. The paint, the wallpaper, the furniture. The bricks were HTML; CSS is everything you actually see.

3. JavaScript

   The language that makes web pages do things. Click a button and a menu opens? That's JavaScript. The electrics in the house. The walls are up, the paint is on, but flick a switch and that's JavaScript turning the lights on.

4. TypeScript

   JavaScript with safety rails. It catches mistakes before the code runs, so fewer bugs make it to your customers. Same car, but with seatbelts and airbags fitted.

5. Python

   A general-purpose language used everywhere - websites, AI, data analysis, automation. Easy to read, which is why it's the most popular language in the world right now. A Swiss Army knife. Not the prettiest, but it does almost everything.

6. Ruby

   A language famous for being pleasant to write. Most people meet it through Ruby on Rails (used by Shopify, GitHub, Airbnb early on).

7. PHP

   Short for Hypertext Preprocessor. An older language that still runs a huge chunk of the internet - WordPress, Facebook's early days, most of your local plumber's website.

8. Java

   A heavyweight language used by big banks, big enterprise software, and Android apps. Not the same as JavaScript - totally different thing.

9. Kotlin

   The modern way to build Android apps. Replaced Java as Google's preferred language for Android.

10. Swift

    Apple's language for building iPhone, iPad, and Mac apps. If your dev says they're "writing it in Swift," they mean a native iOS app.

11. Objective-C

    The old language for iPhone apps before Swift came along in 2014. Still hanging around in legacy codebases.

12. Go

    A language built by Google for fast, server-side software. Loved for being simple and quick.

13. Rust

    A modern language obsessed with safety and speed. Used where performance matters - browsers, operating systems, infrastructure tools.

14. C

    The granddaddy language. Operating systems, embedded chips, the foundations of almost every other language are built in C.

15. C++

    C with more features. Used for games, browsers, and anywhere you need raw speed.

16. C#

    Microsoft's main language. Big in enterprise software, Windows apps, and Unity (game development).

17. Dart

    Google's language. You'll only run into it if you're using Flutter to build apps.

18. R

    A language built specifically for statistics and data science. Used by analysts, researchers, and academics.

19. MATLAB

    A language and tool for engineers and scientists doing heavy maths and simulations. You'll rarely see it in normal product work.

20. SQL

    Short for Structured Query Language (often pronounced "sequel"). The language used to talk to databases. "Get me all customers in London who spent over £100" is one SQL query. Asking the librarian a question. SQL is how you phrase it so they bring back the right book.

21. Bash

    Short for Bourne Again SHell. The default scripting language inside Mac and Linux terminals. Used to automate file management, deployments, and admin tasks.

22. Zsh

    A fancier version of Bash. Default shell on modern Macs.

23. PowerShell

    Microsoft's version of Bash. The way Windows admins automate things.

24. Lua

    A small, fast scripting language. Mostly seen in games (Roblox runs on it) and embedded inside other software.

25. Perl

    An older scripting language. Powerful for text processing, but rare in new projects.

26. Scala

    A language often used at companies handling huge amounts of data - Twitter, LinkedIn, banks.

27. Elixir

    A language built for systems that handle millions of users at once - chat apps, real-time dashboards, messaging platforms.

28. Haskell

    An academic, mathematical language. You'll mostly see it in research, finance, or projects with very strict correctness requirements.

29. Clojure

    A modern take on a very old language (Lisp). Niche but devoted following.

30. Solidity

    The language used to write smart contracts on Ethereum and similar blockchains.

31. WebAssembly

    A way to run fast, compiled code (from C, Rust, etc.) inside a web browser at near-native speed. Letting a Formula 1 engine run inside the family car.

32. JSON

    Short for JavaScript Object Notation (pronounced "jay-son"). A simple text format for sending data between systems. The most common way two pieces of software talk to each other on the modern web.

33. XML

    Short for eXtensible Markup Language. An older data format, like JSON's clunkier older brother. Still used in legacy systems and some enterprise software.

34. YAML

    Short for YAML Ain't Markup Language (yes, that's the actual name). A clean, readable format used mostly for config files - telling tools what to do without writing code.

35. Markdown

    A simple way to write formatted text using plain symbols. # for a heading, ** for bold. This site's blog is written in something close to it.

Frontend Frameworks

1. React

   A tool for building website interfaces in reusable chunks. The most popular front-end framework in the world. Lego blocks. You build a button once, then snap it in wherever you need it.

2. Next.js

   A framework built on top of React that handles the boring stuff - routing, performance, SEO. This site is built in Next.js. React is the engine. Next.js is the whole car around it.

3. Vue

   An alternative to React. Smaller, often easier to pick up. Popular in Europe and Asia.

4. Nuxt

   What Next.js is to React, Nuxt is to Vue. Same idea - a framework that does the heavy lifting.

5. Angular

   Google's heavyweight front-end framework. Common in big enterprise apps. More structured (and stricter) than React.

6. Svelte

   A newer competitor to React. Loved for being lighter and faster, with simpler code.

7. SvelteKit

   What Next.js is to React. The full-app framework built on top of Svelte.

8. Solid

   A React-style framework focused on raw performance. Niche but growing.

9. Astro

   A framework optimised for content-heavy sites - blogs, marketing pages, documentation. Ships almost no JavaScript by default, so it's fast.

10. Remix

    Another React framework, similar territory to Next.js. Strong on forms and traditional web fundamentals.

11. jQuery

    The library that ruled the web in the 2000s. Still everywhere on older sites, but barely used in new builds.

12. Tailwind CSS

    A way of styling websites by adding short class names directly to elements. Faster than writing traditional CSS for most teams.

13. Bootstrap

    A pre-built design system. Drop it in and your site has buttons, forms, and grids ready to go. Why so many sites in 2014 looked the same.

14. Material UI

    A React component library based on Google's Material Design. Gives you ready-made buttons, modals, dropdowns out of the box.

15. shadcn/ui

    A modern set of copy-paste UI components for React. Not a library you install - you copy the code in and own it. Used on this site.

16. Storybook

    A workshop for building and testing UI components in isolation, before they get plugged into the live site.

17. Three.js

    The standard JavaScript library for 3D graphics in a browser. Product configurators, 3D previews and interactive models run on it, usually through React Three Fiber in a React or Next.js site.

Backend & APIs

1. Node.js

   JavaScript that runs on the server instead of in the browser. Lets one team write the same language across the whole stack.

2. Express

   The original tool for building servers in Node.js. Old, simple, still everywhere.

3. Fastify

   A modern, faster alternative to Express. Same job, better performance.

4. NestJS

   A more structured Node.js framework, popular with teams coming from Java or Angular backgrounds.

5. Django

   Python's biggest web framework. Comes with batteries included - admin panels, user logins, database tools, all built in.

6. Flask

   A lightweight Python framework. You build the bits you need; nothing comes pre-packaged.

7. FastAPI

   A modern Python framework focused on building APIs quickly. Popular for AI-related backends.

8. Ruby on Rails

   The framework that made Ruby famous. Get a working web app up in an afternoon. Built Shopify, GitHub, Basecamp.

9. Laravel

   The biggest PHP framework. The modern way to build PHP apps without it feeling stuck in 2005.

10. Spring

    The dominant framework for Java backends. Most big bank and enterprise systems run on it.

11. .NET

    Microsoft's platform for building backends, mostly in C#. Common in big corporate environments.

12. Phoenix

    Elixir's main web framework. Great for real-time stuff like chat and live dashboards.

13. API

    Short for Application Programming Interface. A way for two pieces of software to talk to each other. When your site "connects to Stripe," it's using Stripe's API. The waiter at a restaurant. You don't go into the kitchen - you tell the waiter what you want, they bring it back.

14. REST API

    REST is short for Representational State Transfer. The most common style of API. Predictable URLs, standard verbs (GET, POST, etc.). Probably what your dev means when they just say "the API."

15. GraphQL

    Short for Graph Query Language. A different style of API where the front-end asks for exactly the fields it needs, instead of getting everything back. Ordering off a menu vs. a buffet. REST gives you the buffet; GraphQL lets you order the exact dish you want.

16. gRPC

    Short for Google Remote Procedure Call. A faster, stricter way for servers to talk to each other. Common inside big systems where speed matters more than browser-friendliness.

17. WebSockets

    A way to keep a live connection open between the browser and the server. Used for chat, live notifications, multiplayer. A normal API is a phone call where you hang up after each question. WebSockets is leaving the line open.

18. Webhook

    A way for an external service to notify your app when something happens. Stripe pings your server when a payment succeeds - that's a webhook. A doorbell. Stripe rings; your app answers.

19. OAuth

    Short for Open Authorization. The standard way to "Sign in with Google" or "Sign in with Apple." Lets users log in without giving you their password. A bouncer at a club. You don't show your bank card - Google vouches for you and the bouncer waves you in.

20. JWT

    Short for JSON Web Token (often pronounced "jot"). A small, signed token a server gives you to prove you're logged in. Sent with every request so the server doesn't have to ask "who are you?" each time. A festival wristband. You got it at the gate; now flash it everywhere inside.

21. API key

    A long secret string that proves your app is allowed to use someone else's service. Treat it like a password - never put it in public code.

22. Rate limiting

    Capping how many times someone can hit your API in a window of time. Stops bots, abuse, and runaway costs. The bouncer letting people in one at a time so the club doesn't get crushed.

23. CORS

    A browser rule about which websites are allowed to talk to which APIs. When your dev says "I've got a CORS issue," the browser is blocking a request.

24. Endpoint

    A specific URL on an API that does one thing. /users gets the user list; /orders gets orders.

25. Middleware

    Code that runs between a request coming in and the response going out. Used for things like checking logins, logging, or rate limiting.

Databases

1. Database

   Where your app stores its data - users, orders, posts, anything that needs to stick around. A really, really good filing cabinet.

2. PostgreSQL

   Short for Postgres Structured Query Language. The most popular serious open-source database. Reliable, powerful, the default choice for most modern apps.

3. MySQL

   Short for My Structured Query Language (named after the founder's daughter, My). Another major open-source database. Older than Postgres, still hugely popular, especially with WordPress and PHP apps.

4. MariaDB

   A fork of MySQL run by the open-source community after Oracle bought MySQL. Very similar in practice.

5. SQLite

   A lightweight version of SQL - short for Structured Query Language Lite. A tiny database that lives in a single file. Used in mobile apps, browsers, and small projects where you don't want to run a server. Postgres is a warehouse. SQLite is a notebook in your back pocket.

6. WatermelonDB

   A local database library for React Native and web, built on SQLite. Handles offline-first apps: data is read and written on the device and synced to the server when a connection returns. The app keeps its own copy and posts the changes when it gets signal.

7. MongoDB

   Short for "Humongous DB" (database). A NoSQL database - stores data as flexible documents instead of rigid rows and columns. Popular with Node.js apps.

8. Redis

   Short for Remote Dictionary Server. A super-fast in-memory database. Used as a cache, for queues, and for real-time features. Postgres is the warehouse. Redis is the shelf right behind the till.

9. DynamoDB

   Amazon's NoSQL database. Scales to enormous size; popular inside AWS-heavy stacks.

10. Firestore

    Google's real-time database, part of Firebase. Loved by mobile and prototype builders for syncing data live.

11. Firebase

    Google's all-in-one backend: database, login, file storage and hosting without running a server. Quick to start; it bills per document read, so list-heavy apps can get expensive, and moving off it later means rewriting your data layer.

12. Supabase

    An open-source alternative to Firebase. Postgres under the hood, with auth and APIs included.

13. Prisma

    A tool that makes talking to a database easier in code. Most modern Node.js apps use it.

14. Drizzle

    A newer, lighter alternative to Prisma. Same idea - write database queries in your code without raw SQL.

15. ORM

    Short for Object-Relational Mapper. A layer that lets you talk to a database using normal code instead of raw SQL. A translator between you and the librarian. You speak English; the ORM speaks SQL on your behalf.

16. Schema

    The blueprint of a database - what tables exist, what columns they have, what type of data goes in each. The form you fill in at the council. The schema decides which boxes exist and what goes in them.

17. Migration

    A controlled change to the database structure - adding a column, renaming a table. Versioned so the team stays in sync.

18. Index

    An extra structure that makes database lookups fast. Without one, finding a record means scanning every row. The index at the back of a book. Don't read every page - jump to the right one.

19. Sharding

    Splitting a database across multiple servers when one is too small. Used at very large scale.

20. Replication

    Keeping a live copy of your database somewhere else, in case the main one fails or for faster reads.

21. Query

    A request to a database. "Get all customers from London" is a query.

22. Backup

    A saved copy of your database. If something goes wrong, you restore from a backup. If you don't have one, you have a problem.

Mobile

1. iOS

   Apple's mobile operating system. Runs on iPhone and iPad.

2. Android

   Google's mobile operating system. Runs on most non-Apple phones.

3. Native app

   An app built specifically for one platform using its native tools - Swift for iOS, Kotlin for Android. Best performance, but you build twice.

4. Cross-platform

   One codebase that runs on both iOS and Android. Cheaper to build; sometimes feels slightly less polished than native.

5. React Native

   Facebook's cross-platform tool. Lets you build iOS and Android apps using React. Powers Instagram, Discord, Shopify's app.

6. Flutter

   Google's cross-platform tool. Build iOS, Android, web, and desktop apps from one codebase. Uses Dart as the language.

7. Expo

   A toolkit on top of React Native that handles a lot of the painful setup. Most React Native apps these days use it.

8. SwiftUI

   Apple's modern way of building iOS interfaces. Less code, more readable, the way new iOS apps are built today.

9. Jetpack Compose

   Android's equivalent to SwiftUI. The modern, recommended way to build Android UIs.

10. Xamarin

    Microsoft's older cross-platform mobile tool. Largely replaced by .NET MAUI now.

11. MAUI

    Microsoft's current cross-platform tool for mobile and desktop apps in C#.

12. Capacitor

    A tool that wraps a web app inside a mobile shell so you can ship it to the App Stores. From the team behind Ionic.

13. Cordova

    The original "web app in a phone wrapper" tool. Mostly replaced by Capacitor.

14. Ionic

    A framework for building mobile apps using web tech (HTML, CSS, JavaScript) inside Capacitor.

15. App Store Connect

    Apple's portal for uploading, testing, and publishing iOS apps.

16. TestFlight

    Apple's beta-testing tool. Send your app to a small group before going live on the App Store.

17. Play Console

    Google's portal for publishing Android apps to the Play Store.

18. Push notification

    A message sent from a server straight to a user's phone, even when the app isn't open.

19. Deep link

    A link that opens a specific screen inside an app instead of the home screen. Tap a product link in an email, land on the product page.

Web Concepts

1. WebGL

   The browser technology that lets a web page use the graphics card. It is what Three.js sits on top of, and what makes 3D on a website possible without a plugin.

2. SSR

   Short for Server-Side Rendering. The page is built on the server and sent to the browser fully ready. Fast first load and great for SEO. The waiter brings the plate from the kitchen, fully cooked. You sit down and eat.

3. CSR

   Short for Client-Side Rendering. The browser gets a near-empty page and JavaScript builds it on the fly. Slower first paint; feels app-like once running. The waiter brings raw ingredients. You cook at the table.

4. SSG

   Short for Static Site Generation. Pages are built once, ahead of time, and served as plain files. Fast and cheap. Best for content that doesn't change much. Meals prepped on Sunday for the week. Heat and serve.

5. ISR

   Short for Incremental Static Regeneration. A Next.js trick - pages are static (fast) but quietly rebuild themselves in the background when content updates.

6. Hydration

   After a server-rendered page loads, JavaScript wakes it up so buttons, menus, and forms work. The set is built and dressed; hydration is when the actors walk on stage and start moving.

7. SPA

   Short for Single-Page Application. A site that loads once, then swaps content in and out without full page reloads. Feels app-like.

8. MPA

   Short for Multi-Page Application. A traditional site where every link loads a new page from the server. Most marketing sites still work this way.

9. PWA

   Short for Progressive Web App. A website that can be "installed" on a phone like an app - works offline, sends push notifications, lives on the home screen.

10. CDN

    Short for Content Delivery Network. A network of servers around the world that serves your site from whichever one is closest to the user. Makes everything faster. Corner shops in every neighbourhood instead of one giant warehouse hours away.

11. Edge

    Code that runs as close to the user as possible - at the CDN, not in one central server. Lower latency.

12. Serverless

    Code that runs on someone else's infrastructure, only when needed. You don't manage a server. Pay per request. An Uber instead of owning a car. It shows up when you need it and disappears after.

13. Lambda

    Amazon's serverless service. "A Lambda" usually means a single function that runs on demand.

14. Cold start

    When a serverless function hasn't been used in a while and takes a moment to wake up. The first request feels slow.

15. Latency

    How long a request takes to travel and come back. Measured in milliseconds. Lower is better.

16. Caching

    Saving a copy of something so you don't have to fetch or build it again next time. Makes everything feel faster. Keeping the kettle warm so the next cup of tea is ready in seconds.

17. Cookies

    Small bits of data the browser stores for a website. Used to remember logins, baskets, preferences.

18. Session

    The state of a logged-in user across page loads. Sessions are usually tracked with cookies or tokens.

19. Token

    A short string that proves who you are or what you're allowed to do. Sent with requests to skip logging in every time.

20. DNS

    Short for Domain Name System. The phonebook of the internet. Turns "google.com" into the actual server address (an IP).

21. HTTPS

    Short for HyperText Transfer Protocol Secure. The encrypted version of HTTP - the padlock in your browser. Non-negotiable in 2026; sites without it get punished.

22. TLS / SSL

    TLS = Transport Layer Security. SSL = Secure Sockets Layer (the old name). The encryption that makes HTTPS work. People still say "SSL certificate" even though it's been TLS for years.

23. Domain

    Your address on the web - calljoe.co, example.co.uk. You rent it yearly from a registrar.

24. Subdomain

    A prefix on a domain that points somewhere else. blog.example.com is a subdomain of example.com.

25. Hosting

    The service that runs your site on the internet. Without hosting, your domain points to nothing.

26. VPS

    Short for Virtual Private Server. A rented slice of a server you fully control. Cheaper than a dedicated server, more flexible than shared hosting.

27. IP address

    The actual numerical address of a server on the internet. DNS turns names into IPs.

28. Port

    A specific door on a server. Web traffic goes through port 80 (HTTP) or 443 (HTTPS) by default.

29. Localhost

    Your own computer, when running code on it. localhost:3000 is the dev server running on your machine.

30. Browser

    Chrome, Safari, Firefox, Edge. The program that loads and shows websites.

31. User agent

    A label every browser sends saying what it is. Used for analytics and to detect mobile vs. desktop.

32. Render

    To turn code into something you can see on screen. "How long does it take to render?" = how long to draw the page.

33. Website builder

    A hosted platform where you assemble a site from templates rather than code it: Wix, Squarespace, Webflow, GoDaddy. Fast to launch, and you rent rather than own. The usual reasons people leave are page speed you cannot fix, SEO limits you cannot lift, and a monthly fee that rises while the site stays the same.

DevOps & Hosting

1. Vercel

   A hosting platform built for Next.js (made by the same team). Deploy by pushing to GitHub. This site runs on it.

2. Netlify

   Vercel's main competitor. Same idea - push to GitHub, get a live site.

3. AWS

   Amazon's cloud platform. The biggest in the world. Runs a huge chunk of the internet.

4. GCP

   Google's version of AWS. Strong on data, AI, and Kubernetes.

5. Azure

   Microsoft's cloud. Dominant in big enterprise and corporate environments.

6. Cloudflare

   A CDN, security layer, and now a hosting platform. Sits in front of millions of sites and blocks bad traffic.

7. Heroku

   An older platform-as-a-service. Simple to deploy to. Pricier than newer options.

8. Render

   A modern Heroku-style hosting platform. Easy deploys, fair pricing.

9. Railway

   Another modern hosting platform. Loved by indie devs for being fast and friendly.

10. Fly.io

    A platform that runs your app close to your users around the world. Strong for global apps.

11. Docker

    A way of packaging your app and everything it needs to run into a single "container" that works the same everywhere. Sending a meal in its own takeaway box. Same dish whether it's eaten at the restaurant, in the office, or at home.

12. Kubernetes

    A tool for running and scaling lots of Docker containers across lots of servers. Powerful, complicated, mostly for big systems.

13. CI/CD

    CI = Continuous Integration. CD = Continuous Deployment (or Delivery). Automated pipelines that test your code and ship it to production every time you push a change. A conveyor belt from your laptop to your live site, with quality checks built in.

14. GitHub Actions

    GitHub's built-in CI/CD. Write a config file, GitHub runs your tests and deploys on every push.

15. Deployment

    The act of pushing your code live so users can see it.

16. Build

    The step where source code gets compiled and bundled into the files that actually run in production.

17. Environment variables

    Settings that change between environments - usually secrets like API keys and database passwords. Never put them in code.

18. Staging

    A near-identical copy of production used for final testing before going live. "Let me check it on staging first."

19. Production

    The live, real-customers-using-it environment. "It's broken in prod" is the worst sentence in tech.

20. Rollback

    Reverting a deployment back to the previous version when something's gone wrong.

21. Uptime

    The percentage of time your site is up and working. "Three nines" (99.9%) means about 8 hours down per year.

22. Load balancer

    A traffic cop that spreads incoming requests across multiple servers so no single one gets crushed.

23. Logs

    Records of what your app did and when. Where you look first when something breaks.

24. Monitoring

    Tools that watch your app in real time and tell you when things are slow or broken.

25. Server

    A computer that runs your code and answers requests over the internet. Could be a real machine or, more often these days, a slice of one.

AI & Data

1. AI

   Software that can do tasks normally needing human judgement - writing, image recognition, decision-making.

2. LLM

   Short for Large Language Model. The kind of AI behind ChatGPT and Claude. Trained on huge amounts of text. Generates writing, code, summaries. An incredibly well-read assistant. Knows a lot, occasionally makes things up.

3. GPT

   Short for Generative Pre-trained Transformer. OpenAI's family of language models - "GPT-4," "GPT-5" etc. Often used as a general label for ChatGPT-style AI.

4. Claude

   Anthropic's family of AI models. The one writing this guide.

5. Gemini

   Google's family of AI models.

6. OpenAI

   The company behind ChatGPT and the GPT models.

7. Anthropic

   The company behind Claude.

8. Prompt

   What you type into an AI to get a response. "Write me a marketing email" is a prompt.

9. Token

   How AI models count text - roughly a chunk of word. AI usage is billed and limited per token.

10. Embedding

    Turning a piece of text into a list of numbers that represents its meaning. Used for search and "find similar" features.

11. Vector database

    A database built to store and search embeddings - find the closest match in meaning, not just keywords.

12. RAG

    Short for Retrieval-Augmented Generation. Giving an AI access to your own documents so it answers based on them, not just its training data. Letting the assistant grab a folder of your notes before answering, instead of going off memory alone.

13. Fine-tuning

    Taking a general AI model and training it further on your own specific data to make it better at one job.

14. Training

    The process of teaching an AI model by showing it huge amounts of data. Done once, can take months and cost millions.

15. Inference

    The act of using a trained AI to generate an answer. Every time you send a prompt, that's inference.

16. Hallucination

    When an AI confidently makes something up - a fake citation, a wrong fact. The biggest weakness of LLMs.

17. Agent

    An AI that can take actions, not just chat - search the web, edit files, call APIs, run tools on your behalf.

18. MCP

    Short for Model Context Protocol. A standard way to plug tools and data sources into AI agents. Lets Claude or ChatGPT talk to your apps in a structured way.

19. Multimodal

    An AI that handles more than just text - also images, audio, video.

20. Machine learning

    The broader field AI sits inside. Software that learns patterns from data instead of being explicitly programmed.

21. Neural network

    The structure inside most modern AI. Loosely inspired by how brain cells connect.

22. Dataset

    A collection of data used to train or test a model.

23. Big data

    Datasets so large they need special tools to process. The buzzword peaked in 2015; the work is still everywhere.

24. ETL

    Short for Extract, Transform, Load. The pipeline of pulling data out of one system, cleaning it up, and loading it somewhere else for analysis.

25. Data warehouse

    A massive central database for analytics - Snowflake, BigQuery, Redshift. Different beast from the database your app uses.

Design & UX

1. UI

   What the user sees and clicks - buttons, layouts, forms, colours.

2. UX

   How the whole product feels to use. Easy or frustrating, fast or sluggish, clear or confusing. Bigger than just looks.

3. Figma

   The design tool every modern team uses. Where mockups, design systems, and prototypes get made before code.

4. Blender

   Free, professional 3D software. Used for modelling, animation and rendering, and the usual starting point for both 3D on a website and models sent to a 3D printer.

5. glTF

   The standard file format for 3D models on the web, exported from Blender and loaded by Three.js. GLB is the single-file binary version. Compressed properly, a whole product model fits in a couple of megabytes.

6. Wireframe

   A rough black-and-white sketch of a page's layout - boxes and labels, no colours, no polish. Used early.

7. Mockup

   A polished, full-colour design of what a page will look like. Static - doesn't actually do anything yet.

8. Prototype

   A clickable version of a mockup. Looks real, links work, but no real data or backend behind it.

9. Design system

   A documented set of components, colours, and rules so every page looks like it belongs to the same product. A brand bible. Everyone working on the product follows the same recipe.

10. Component

    A reusable piece of UI - a button, a card, a navbar. Build it once, use it everywhere.

11. Accessibility

    Making sure your site works for everyone - screen readers, keyboard-only users, low vision, colour blindness. Also a legal requirement in many places.

12. Contrast

    How much the text stands out from the background. Too low and lots of people genuinely can't read it.

13. Semantic HTML

    Using the right HTML element for the job - <button> for buttons, <nav> for navigation. Helps screen readers, SEO, and your future self.

14. ARIA

    Extra labels in HTML that help screen readers describe parts of a page that aren't obvious from the visuals.

15. Responsive design

    A layout that adapts to whatever screen it's on - phone, tablet, desktop. Bare minimum these days.

16. Mobile-first

    Designing for phones before desktop, since most traffic is mobile.

17. Breakpoint

    A screen size where the layout changes - e.g. switching from a one-column phone view to a three-column desktop view.

18. Above the fold

    What the user sees on a page before scrolling. The most valuable real estate on any site.

19. Hero section

    The big top section on a homepage - usually a headline, subline, and call to action.

20. Skeleton loader

    Grey placeholder shapes that show while content is loading. Feels faster than a blank screen or a spinner.

21. Microinteraction

    Small UI moments - a button pressing, a heart filling in, a checkbox bouncing. Adds polish.

Business, SEO & Acronyms

1. SEO

   Short for Search Engine Optimisation. Getting your site to rank higher on Google. A mix of fast loading, good content, clean code, and links from other sites.

2. SERP

   Short for Search Engine Results Page. The page Google shows after a search. The whole game in SEO is getting onto page one of the SERP.

3. Meta tags

   Bits of info in your HTML that don't show on the page but tell Google and social media how to display it.

4. OpenGraph

   The meta tags that control how your link looks when shared on social - title, description, preview image.

5. Sitemap

   A file listing every page on your site so Google can crawl it efficiently.

6. robots.txt

   A small file telling search engines which parts of your site they can and can't look at.

7. Schema.org

   Extra hidden info you add to a page so Google understands what's on it - articles, products, reviews, businesses.

8. Backlink

   A link from another site to yours. The single biggest signal Google uses to decide who's trustworthy.

9. Anchor text

   The clickable words in a link. "Click here" tells Google nothing; "London plumber" tells it a lot.

10. Keyword

    A word or phrase people search for. Pick the right ones and your site gets found.

11. Long-tail keyword

    A specific, multi-word phrase. Less traffic per keyword, but the people searching it actually want what you sell.

12. Alt text

    A short description of an image. Read by screen readers, used by Google, shown when an image fails to load.

13. Lighthouse

    A free tool from Google that scores your site on speed, accessibility, SEO, and best practices.

14. Core Web Vitals

    Three speed metrics Google uses to judge your site. Score badly and you rank lower.

15. LCP

    Short for Largest Contentful Paint. How long until the biggest thing on your page (usually the hero image or headline) shows up. Should be under 2.5s.

16. FID

    Short for First Input Delay. How long until the page actually responds when you click something. Being replaced by a metric called INP.

17. INP

    Short for Interaction to Next Paint. How quickly the page reacts to clicks and taps. Replaces FID. Should feel instant, under 200ms.

18. CLS

    Short for Cumulative Layout Shift. How much things jump around as the page loads. Buttons moving as you go to click them = high CLS = bad.

19. Conversion rate

    The percentage of visitors who do the thing you want - buy, sign up, contact you. The number that actually matters.

20. CTA

    Short for Call To Action. The button or link telling people what to do next. "Get a quote," "WhatsApp me," "Buy now."

21. A/B test

    Showing version A to half your users and version B to the other half, then keeping whichever wins. Removes guesswork.

22. Funnel

    The journey from "never heard of you" to "paying customer." Each step loses some people; the funnel narrows.

23. Lead

    A potential customer who's shown interest - filled in a form, sent a WhatsApp, joined a list. Lead gen is getting more of those.

24. MVP

    Short for Minimum Viable Product. The smallest version of your product that's actually useful. Ship that, learn, then add more. Open the chippy with chips and a fryer. Add the kebabs once people are coming through the door.

25. KPI

    Short for Key Performance Indicator. The metrics you actually track - revenue, signups, retention. The numbers that tell you if you're winning.

26. ROI

    Short for Return On Investment. What you get back for what you put in. Spent £500 on ads, made £2,000 in sales - strong ROI.

27. SaaS

    Short for Software as a Service. Software you rent monthly instead of buying once. Notion, Slack, Spotify. The dominant model in software.

28. B2B / B2C

    Business-to-business (selling to companies) vs. business-to-consumer (selling to people). Two very different games.

29. Churn

    The rate at which paying customers leave. High churn kills SaaS businesses faster than anything.

30. LTV

    Short for Customer Lifetime Value (sometimes CLV). How much a customer is worth to you in total over the time they stay.

31. CAC

    Short for Customer Acquisition Cost. What it costs you to get one new customer. If CAC is bigger than LTV, you're losing money on every sale.

32. Bounce rate

    The percentage of visitors who land on a page and immediately leave without doing anything.

Security

1. Row level security

   Rules held in the database deciding which rows each logged-in user may read or change. In Supabase and Postgres it is the only thing stopping one user querying everyone else's data, because the key in your app is public by design. The most common thing missing from AI-generated apps.

2. XSS

   Short for Cross-Site Scripting. An attack where bad code is sneaked into a page and runs in your visitors' browsers. Prevented by sanitising user input.

3. CSRF

   Short for Cross-Site Request Forgery. An attack where a user is tricked into making a request they didn't mean to, like submitting a hidden form on a dodgy site.

4. SQL injection

   An attack where someone types SQL into a form field and tricks your database into running it. Easy to prevent; embarrassing if you don't.

5. CAPTCHA

   The "I'm not a robot" check on forms. Stops bots from spamming you.

6. Brute force

   An attack where bots try millions of password combinations until one works. Rate limiting and 2FA shut this down.

7. Encryption

   Scrambling data so only the right key can unlock it. What HTTPS does to your traffic. Sending a letter in a sealed safe instead of a postcard.

8. Hashing

   A one-way scramble. You can hash a password but never un-hash it. That's why a proper site never "recovers" your password - it resets it. Mincing meat. Easy to mince a steak; impossible to un-mince it back into one.

9. Salt

   A random string added to a password before hashing, so two people with the same password get different hashes. Stops bulk attacks.

10. 2FA / MFA

    Logging in with more than just a password - usually a code from your phone too. Turn it on everywhere.

11. Zero-trust

    A security model that assumes no request is safe by default - every action gets verified, even from inside your network.

12. GDPR

    Short for General Data Protection Regulation. European data protection law. If you collect data from EU/UK users, you've got rules to follow about consent, storage, and deletion.

13. Cookie banner

    The "accept cookies" pop-up. Required by GDPR and similar laws. Don't pre-tick the boxes.

14. Penetration test

    Hiring someone to legally try to hack your system and report back what they found. Standard for serious products.

15. Firewall

    A filter sitting in front of your servers, blocking traffic that shouldn't be there.

16. DDoS

    Short for Distributed Denial of Service. An attack where thousands of bots flood your site with fake traffic to take it offline. Cloudflare and similar services help block these.

Tools & Workflow

1. Git

   The version-control tool every dev uses. Tracks every change to a codebase so you can go back, branch off, and merge work together. Track changes in Word, but for entire projects, with a full history forever.

2. GitHub

   The biggest place to host code with Git. Where most modern open-source and team projects live.

3. GitLab

   A GitHub competitor. Often used by companies who want to self-host their code.

4. Bitbucket

   Atlassian's GitHub competitor. Common in teams already using Jira and Confluence.

5. Repository

   A project's codebase plus its full history. "Push to the repo" = save your changes to the shared project.

6. Branch

   A separate line of work in a project. You branch off, do your changes, then merge back when ready.

7. Commit

   A saved snapshot of changes with a message. The unit of work in Git.

8. Merge

   Combining one branch into another. Usually when a feature is finished and going back into the main project.

9. Pull request

   A request to merge your branch into the main one, usually reviewed by another dev first. Where most code review happens.

10. Rebase

    Replaying your commits on top of the latest main branch. Keeps history tidier than merging.

11. Fork

    Your own copy of someone else's repository. The starting point for contributing to open-source projects.

12. Clone

    Downloading a copy of a repository to your local machine.

13. npm

    Short for Node Package Manager. The package manager for JavaScript. Where you install libraries (React, Express, anything).

14. yarn

    An alternative to npm. Same job, originally made by Facebook.

15. pnpm

    A faster, more disk-efficient alternative to npm. Used in this project.

16. Bun

    A new, very fast all-in-one tool for JavaScript - runtime, package manager, bundler. Trying to replace Node + npm.

17. package.json

    The file at the root of every Node.js project listing dependencies and scripts.

18. Dependency

    A library your project relies on. "It depends on React" = React must be installed for it to work.

19. Semver

    The 1.2.3 versioning system. Big number = breaking changes, middle = new features, last = bug fixes.

20. Monorepo

    Keeping multiple projects in a single repository. Big at companies like Google, Meta, and Vercel.

21. IDE

    Short for Integrated Development Environment. The program devs write code in. Has a text editor plus tools for running, debugging, and version control built in.

22. VS Code

    Microsoft's free code editor. The most popular IDE in the world.

23. Cursor

    A fork of VS Code with deep AI integration baked in. Popular among devs in 2026.

24. Terminal

    The black window where devs type commands instead of clicking buttons. Faster for almost everything once you know it.

25. Linter

    A tool that scans your code for likely mistakes and style problems before you even run it.

26. Formatter

    A tool that auto-tidies your code - spaces, line breaks, indentation. So no one argues about style.

27. ESLint

    The standard linter for JavaScript and TypeScript.

28. Prettier

    The most popular code formatter for web tech.

29. Unit test

    A small test that checks one tiny piece of code in isolation. Fast to run; the foundation of testing.

30. Integration test

    A test that checks several pieces working together - your code plus a database, for example.

31. End-to-end test

    A test that drives the whole app like a real user would - clicks buttons, fills forms, checks the result.

32. Jest

    A popular JavaScript test runner, originally from Facebook.

33. Vitest

    A modern, faster Jest alternative built on top of Vite.

34. Playwright

    Microsoft's tool for end-to-end testing - drives a real browser like a user would.

35. Cypress

    Another end-to-end testing tool, very popular before Playwright caught up.

36. Refactor

    Changing the code's structure without changing what it does. Cleaning up.

37. Tech debt

    Shortcuts taken to ship faster that you'll have to pay back later. Some is fine; too much slows everything down.

38. Codebase

    The full set of code that makes up a project.

39. Open source

    Code anyone can read, use, and contribute to. React, Linux, Postgres are all open source.

40. Bug

    Something in the code doing what it wasn't meant to do. Every codebase has them.

41. Hotfix

    An urgent fix shipped straight to production because something is on fire.

42. Stack

    The full list of tools, languages, and frameworks a product is built on. "What's your stack?"

43. Frontend

    Everything the user actually sees and clicks - the browser side.

44. Backend

    The server side. Database, business logic, the bits the user never sees directly.

45. Full-stack

    A dev who handles both frontend and backend. What I do.

46. DevOps

    The discipline of getting code from a dev's laptop to running in production reliably. Servers, deployments, monitoring.

47. Pair programming

    Two devs working on the same code at the same time. One drives, one navigates.

48. Standup

    A short daily team meeting. What I did yesterday, what I'm doing today, what's blocking me.

49. Sprint

    A short, fixed chunk of work - usually 1 or 2 weeks. Common in agile teams.

50. Agile

    A way of building software in short cycles, adjusting as you learn, instead of planning everything upfront.

51. Scrum

    A specific flavour of agile with sprints, standups, and defined roles. Loved by some, hated by others.

52. Backlog

    The list of features and bugs waiting to be worked on.

53. Ticket

    A single unit of work - a feature, a bug, a task. Tracked in tools like Jira, Linear, or GitHub Issues.

54. Jira

    Atlassian's ticket-tracking tool. Common in big teams. Powerful and famously fiddly.

55. Linear

    A modern, fast Jira competitor loved by startups.

56. Slack

    Team chat. Where most modern companies actually communicate.

57. Code review

    Another dev reading your changes before they merge in. Catches bugs and shares knowledge.

58. Documentation

    Written guides for how a system works. Future-you will thank past-you for writing them.

Questions

More from the blog

Book a call