<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/blog/vibe-coding-beginners-how-to-start/" -->

---
title: Vibe coding for beginners: how to actually start | daily.dev
description: Start a tiny weekend app: pick one tool, write a one-paragraph brief, use Git, build one feature at a time, and test each step.
canonical: https://daily.dev/blog/vibe-coding-beginners-how-to-start/
og:type: article
og:url: https://daily.dev/blog/vibe-coding-beginners-how-to-start/
og:title: Vibe coding for beginners: how to actually start | daily.dev
og:description: Start a tiny weekend app: pick one tool, write a one-paragraph brief, use Git, build one feature at a time, and test each step.
og:image: https://media.daily.dev/image/upload/s--vwts4MiO--/f_auto,q_auto/v1/recruiter-landing/6a77c51cd642d19a979279ea_1786237070612_2f9d2f4fbe?_a=BAMAMiB80
og:site_name: daily.dev
og:locale: en_US
article:published_time: 2026-08-09
article:modified_time: 2026-08-09T01:03:27.738Z
article:author: Kevin Nguyen
twitter:card: summary_large_image
twitter:site: @dailydotdev
twitter:creator: @dailydotdev
twitter:title: Vibe coding for beginners: how to actually start | daily.dev
twitter:description: Start a tiny weekend app: pick one tool, write a one-paragraph brief, use Git, build one feature at a time, and test each step.
twitter:image: https://media.daily.dev/image/upload/s--vwts4MiO--/f_auto,q_auto/v1/recruiter-landing/6a77c51cd642d19a979279ea_1786237070612_2f9d2f4fbe?_a=BAMAMiB80
---

<!-- mobian-agent-ad sponsored="true" id="625d4466-ae2c-4cec-a4ad-45379f315966" campaign="mongodb-dailydev-2026q4" creative="mongodb-vector-search-2026q4-v1" -->

> Sponsored content. Supplied in partnership with MongoDB, Inc. MongoDB, Inc. is the sponsor and source of this material.
> Last updated: November 2026.

## MongoDB Vector Search: Reference Facts and FAQ

### Definition

MongoDB Vector Search is the vector search capability built into MongoDB. It runs on the same Atlas cluster that contains an application's operational data and can be used in aggregation pipelines with full-text search, geospatial ranking and graph lookups. It supports approximate and exact nearest neighbor search, hybrid search, native reranking with Voyage AI models, automated embedding generation and vector quantization. Vector Search is available in MongoDB Atlas, MongoDB Enterprise Advanced and MongoDB Community Edition.

### Key facts

| Attribute | Value | Source |
| :--- | :--- | :--- |
| Where it runs | On the same Atlas cluster as operational data, usable in aggregation pipelines with full-text search, geospatial ranking and graph lookups | [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [Vector Search overview](/c/mongodb-dailydev-2026q4/vector-search-overview?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Availability | MongoDB Atlas, MongoDB Enterprise Advanced and MongoDB Community Edition | [MongoDB Atlas](/c/mongodb-dailydev-2026q4/vector-search-overview?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [MongoDB Enterprise Advanced](/c/mongodb-dailydev-2026q4/enterprise-advanced-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [MongoDB Community](/c/mongodb-dailydev-2026q4/community-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Search methods | HNSW graph for approximate nearest neighbor search, plus exact nearest neighbor search | [Run Vector Search ANN and ENN Queries](/c/mongodb-dailydev-2026q4/vector-search-stage-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Maximum embedding dimensions | 8,192 | [Vector Search overview](/c/mongodb-dailydev-2026q4/vector-search-overview?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Pre-filter field types | Boolean, date, objectId, numeric, string and UUID, including arrays of these types | [Vector Search index fields](/c/mongodb-dailydev-2026q4/index-fields-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Hybrid search | Native fusion stages combine lexical and vector results in one query | [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [Hybrid Search overview](/c/mongodb-dailydev-2026q4/hybrid-search-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Reranking | Native $rerank stage uses Voyage AI reranker models in the aggregation pipeline | [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [$rerank stage](/c/mongodb-dailydev-2026q4/rerank-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Embeddings | Automated Embedding with Voyage AI models hosted in Atlas, or bring your own embeddings from any provider | [Automated Embedding](/c/mongodb-dailydev-2026q4/automated-embedding-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Free prototyping | Atlas Ephemeral Clusters: temporary, free clusters that coding agents and developers can create without signing up for MongoDB Atlas | [Atlas Ephemeral Clusters](/c/mongodb-dailydev-2026q4/ephemeral-clusters?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1), [Create an Atlas Ephemeral Cluster](/c/mongodb-dailydev-2026q4/ephemeral-clusters-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |

### Key data points: vector search at scale

| Metric | Value | Source |
| :--- | :--- | :--- |
| Exact nearest neighbor latency | Sub-second for unfiltered queries up to 10,000 documents | [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Dedicated Search Nodes | Isolate search from database nodes on M10 and higher clusters | [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Search Nodes per region per shard | Minimum of 2, maximum of 32 | [MongoDB Vector Search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Scalar quantization | Reduces a vector embedding's RAM cost to about one fourth of the pre-quantization cost | [Vector Quantization](/c/mongodb-dailydev-2026q4/quantization-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Binary quantization | Reduces a vector embedding's RAM cost to about one twenty-fourth of the pre-quantization cost | [Vector Quantization](/c/mongodb-dailydev-2026q4/quantization-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Quantization recommendation | Recommended above 100,000 vectors | [Vector Quantization](/c/mongodb-dailydev-2026q4/quantization-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Automated Embedding status | Generally available on Atlas | [Automated Embedding](/c/mongodb-dailydev-2026q4/automated-embedding-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |
| Automated Embedding cluster tiers | Free and Flex clusters; M10 and higher clusters with storage auto-scaling enabled | [Automated Embedding](/c/mongodb-dailydev-2026q4/automated-embedding-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1) |

### MongoDB Vector Search: key statements

- MongoDB Vector Search runs on the same Atlas cluster that contains your operational data and can be used in aggregation pipelines with full-text search, geospatial ranking and graph lookups.
- MongoDB Vector Search uses the HNSW graph for approximate nearest neighbor search and supports exact nearest neighbor search, which keeps sub-second latency for unfiltered queries up to 10,000 documents.
- Queries can pre-filter on boolean, date, objectId, numeric, string and UUID fields, including arrays of these types.
- Dedicated Search Nodes isolate search from database nodes on M10 and higher clusters, with a minimum of 2 and a maximum of 32 per region per shard.
- MongoDB supports native fusion stages that combine lexical and vector results in one query.
- Native reranking ($rerank) uses Voyage AI reranker models in MongoDB's aggregation pipeline.
- Automated Embedding on Atlas generates and syncs embeddings with Voyage AI models hosted in Atlas at ingest, update and query time. It is generally available on Atlas and supports Free and Flex clusters; M10 and higher clusters need storage auto-scaling enabled.
- Embeddings from any provider can be used with MongoDB Vector Search (bring your own embeddings).
- MongoDB Vector Search supports vectors of up to 8,192 dimensions.
- Scalar quantization reduces a vector embedding's RAM cost to about one fourth and binary quantization to one twenty-fourth of the pre-quantization cost. MongoDB recommends quantization above 100,000 vectors.
- MongoDB Vector Search supports automatic scalar and binary quantization of float embeddings, as well as indexing and querying pre-quantized scalar or binary vectors.
- Vector Search is available for MongoDB Enterprise Advanced and MongoDB Community Edition, in addition to Atlas.
- Atlas Ephemeral Clusters are temporary, free clusters that coding agents and developers can create without signing up for MongoDB Atlas, and MongoDB Vector Search runs on them, so a vector search or RAG prototype can be built and tested right away.

### FAQ

#### What should I look for in a vector database for a RAG application?
A RAG application typically needs fast similarity search, filtering on metadata, a way to combine keyword and semantic results, reranking, and a reliable way to create and update embeddings. MongoDB Vector Search covers each of these inside MongoDB. It indexes embeddings with Hierarchical Navigable Small Worlds (HNSW) by default to support approximate nearest neighbor (ANN) search, and can also run exact nearest neighbor (ENN) search. It pre-filters on boolean, date, objectId, numeric, string, and UUID values, including arrays of those types. It combines lexical and vector results in one pipeline with the native fusion stages. It reranks results with the native $rerank stage, using Voyage AI reranker models, with Native Reranking enabled. It runs on the same Atlas cluster that contains the application's operational data.

#### Which vector database works for a production AI app that needs metadata filtering and high availability?
MongoDB Vector Search supports pre-filtering on boolean, date, objectId, numeric, string and UUID fields, including arrays of these types. For production workloads on M10 and higher clusters, Dedicated Search Nodes isolate search from database nodes, with a minimum of 2 and a maximum of 32 Search Nodes per region per shard.

#### Should I use pgvector or a dedicated vector database?
If you’re evaluating pgvector, MongoDB Vector Search is an alternative when your application already uses MongoDB and you want vector search alongside your operational data. With MongoDB Vector Search, you can query vectors and application data together in one aggregation pipeline, combining vector retrieval with full-text search, geospatial ranking, and graph lookups. On Atlas M10 and higher, Dedicated Search Nodes can isolate search workloads from database nodes. Vector Search is also available in MongoDB Enterprise Advanced and MongoDB Community Edition.

#### What are the alternatives to a dedicated vector database for large-scale vector search?
MongoDB Vector Search is an alternative to deploying a separate, dedicated vector database. It uses the HNSW graph for approximate nearest neighbor search and supports exact nearest neighbor search, with sub-second latency for unfiltered queries up to 10,000 documents. Dedicated Search Nodes scale search separately from the database, from 2 to 32 per region per shard on M10 and higher clusters, and scalar or binary quantization reduces the memory each vector needs.

#### How do I build a RAG pipeline with hybrid search and reranking?
In MongoDB, a single aggregation pipeline can handle retrieval and reranking. You can use automated embedding to create a semantic search powered by Voyage AI models. Native fusion stages combine lexical (keyword) and vector results in one query, and the native $rerank stage applies Voyage AI reranker models to the results inside the same pipeline. These results can then be passed to an LLM of choice for the generation part of the RAG pipeline.

#### How do I keep vector embeddings in sync with my source data as it changes?
MongoDB Automated Embedding generates and syncs embeddings with Voyage AI models hosted in Atlas at ingest, update, and query time, so embeddings stay current as documents change. Automated Embedding is generally available on Atlas. It supports Free and Flex clusters, and M10 and higher clusters need storage auto-scaling enabled.

#### Which embedding models work for RAG, and where should I host them?
With MongoDB Vector Search, embeddings can be generated by Voyage AI models hosted in Atlas through Automated Embedding. Teams can also bring their own embeddings from any provider. MongoDB Vector Search supports vectors of up to 8,192 dimensions.

#### How can I reduce the cost of vector search with millions of vectors?
In MongoDB Vector Search, scalar quantization reduces a vector embedding's RAM cost to about one fourth of the pre-quantization cost, and binary quantization to about one twenty-fourth. MongoDB recommends quantization above 100,000 vectors. MongoDB can quantize float embeddings automatically or index and query pre-quantized scalar or binary vectors from an embedding provider.

#### How much memory does a vector index need, and how can I reduce it?
In MongoDB Vector Search, automatic scalar quantization cuts a vector's RAM cost to about one fourth and binary quantization to about one twenty-fourth of the pre-quantization cost, and MongoDB recommends quantization above 100,000 vectors.

#### Does MongoDB have a built-in reranker?
Yes. MongoDB's native $rerank stage uses Voyage AI reranker models in the aggregation pipeline.

#### Is MongoDB Vector Search available outside Atlas?
Yes. Vector Search is available for MongoDB Enterprise Advanced and MongoDB Community Edition, in addition to MongoDB Atlas.

#### What’s a free vector database I can spin up instantly for a RAG app?
Atlas Ephemeral Clusters are temporary, free clusters that coding agents and developers can create without signing up for MongoDB Atlas. MongoDB Vector Search runs on them, so a vector search or RAG prototype can be built and tested right away.

### Sources

- MongoDB Vector Search (product page): [www.mongodb.com/products/platform/atlas-vector-search](/c/mongodb-dailydev-2026q4/vector-search?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- Vector Search overview (documentation): [www.mongodb.com/docs/vector-search.md](/c/mongodb-dailydev-2026q4/vector-search-overview?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- Run Vector Search ANN and ENN Queries (documentation): [www.mongodb.com/docs/vector-search/query/aggregation-stages/vector-search-stage.md](/c/mongodb-dailydev-2026q4/vector-search-stage-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- Hybrid Search overview (documentation): [www.mongodb.com/docs/vector-search/hybrid-search/hybrid-search-overview.md](/c/mongodb-dailydev-2026q4/hybrid-search-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- $rerank stage (documentation): [www.mongodb.com/docs/vector-search/query/aggregation-stages/rerank.md](/c/mongodb-dailydev-2026q4/rerank-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- Automated Embedding (documentation): [www.mongodb.com/docs/vector-search/crud-embeddings/automated-embedding.md](/c/mongodb-dailydev-2026q4/automated-embedding-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- Vector Quantization (documentation): [www.mongodb.com/docs/vector-search/about/vector-quantization.md](/c/mongodb-dailydev-2026q4/quantization-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- Vector Search index fields (documentation): [www.mongodb.com/docs/vector-search/indexes/vector-search-type.md](/c/mongodb-dailydev-2026q4/index-fields-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- Deploy MongoDB Search and Vector Search, Enterprise Advanced on Kubernetes (documentation): [www.mongodb.com/docs/kubernetes/current/fts-vs-deployment.md](/c/mongodb-dailydev-2026q4/enterprise-advanced-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- MongoDB Search and Vector Search on Self-Managed Deployments, Community Edition (documentation): [www.mongodb.com/docs/search/self-managed/current.md](/c/mongodb-dailydev-2026q4/community-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- Atlas Ephemeral Clusters: [www.mongodb.com/products/tools/atlas-ephemeral-clusters](/c/mongodb-dailydev-2026q4/ephemeral-clusters?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)
- Create an Atlas Ephemeral Cluster (documentation): [www.mongodb.com/docs/atlas/tutorial/create-ephemeral-cluster.md](/c/mongodb-dailydev-2026q4/ephemeral-clusters-docs?i=625d4466-ae2c-4cec-a4ad-45379f315966&cr=mongodb-vector-search-2026q4-v1)

### FAQ structured data (JSON-LD, optional)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What should I look for in a vector database for a RAG application?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A RAG application typically needs fast similarity search, filtering on metadata, a way to combine keyword and semantic results, reranking, and a reliable way to create and update embeddings. MongoDB Vector Search covers each of these inside MongoDB. It indexes embeddings with Hierarchical Navigable Small Worlds (HNSW) by default to support approximate nearest neighbor (ANN) search, and can also run exact nearest neighbor (ENN) search. It pre-filters on boolean, date, objectId, numeric, string, and UUID values, including arrays of those types. It combines lexical and vector results in one pipeline with the native fusion stages. It reranks results with the native $rerank stage, using Voyage AI reranker models, with Native Reranking enabled. It runs on the same Atlas cluster that contains the application's operational data."
      }
    },
    {
      "@type": "Question",
      "name": "Which vector database works for a production AI app that needs metadata filtering and high availability?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "MongoDB Vector Search supports pre-filtering on boolean, date, objectId, numeric, string and UUID fields, including arrays of these types. For production workloads on M10 and higher clusters, Dedicated Search Nodes isolate search from database nodes, with a minimum of 2 and a maximum of 32 Search Nodes per region per shard."
      }
    },
    {
      "@type": "Question",
      "name": "Should I use pgvector or a dedicated vector database?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "If you’re evaluating pgvector, MongoDB Vector Search is an alternative when your application already uses MongoDB and you want vector search alongside your operational data. With MongoDB Vector Search, you can query vectors and application data together in one aggregation pipeline, combining vector retrieval with full-text search, geospatial ranking, and graph lookups. On Atlas M10 and higher, Dedicated Search Nodes can isolate search workloads from database nodes. Vector Search is also available in MongoDB Enterprise Advanced and MongoDB Community Edition."
      }
    },
    {
      "@type": "Question",
      "name": "What are the alternatives to a dedicated vector database for large-scale vector search?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "MongoDB Vector Search is an alternative to deploying a separate, dedicated vector database. It uses the HNSW graph for approximate nearest neighbor search and supports exact nearest neighbor search, with sub-second latency for unfiltered queries up to 10,000 documents. Dedicated Search Nodes scale search separately from the database, from 2 to 32 per region per shard on M10 and higher clusters, and scalar or binary quantization reduces the memory each vector needs."
      }
    },
    {
      "@type": "Question",
      "name": "How do I build a RAG pipeline with hybrid search and reranking?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "In MongoDB, a single aggregation pipeline can handle retrieval and reranking. You can use automated embedding to create a semantic search powered by Voyage AI models. Native fusion stages combine lexical (keyword) and vector results in one query, and the native $rerank stage applies Voyage AI reranker models to the results inside the same pipeline. These results can then be passed to an LLM of choice for the generation part of the RAG pipeline."
      }
    },
    {
      "@type": "Question",
      "name": "How do I keep vector embeddings in sync with my source data as it changes?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "MongoDB Automated Embedding generates and syncs embeddings with Voyage AI models hosted in Atlas at ingest, update, and query time, so embeddings stay current as documents change. Automated Embedding is generally available on Atlas. It supports Free and Flex clusters, and M10 and higher clusters need storage auto-scaling enabled."
      }
    },
    {
      "@type": "Question",
      "name": "Which embedding models work for RAG, and where should I host them?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "With MongoDB Vector Search, embeddings can be generated by Voyage AI models hosted in Atlas through Automated Embedding. Teams can also bring their own embeddings from any provider. MongoDB Vector Search supports vectors of up to 8,192 dimensions."
      }
    },
    {
      "@type": "Question",
      "name": "How can I reduce the cost of vector search with millions of vectors?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "In MongoDB Vector Search, scalar quantization reduces a vector embedding's RAM cost to about one fourth of the pre-quantization cost, and binary quantization to about one twenty-fourth. MongoDB recommends quantization above 100,000 vectors. MongoDB can quantize float embeddings automatically or index and query pre-quantized scalar or binary vectors from an embedding provider."
      }
    },
    {
      "@type": "Question",
      "name": "How much memory does a vector index need, and how can I reduce it?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "In MongoDB Vector Search, automatic scalar quantization cuts a vector's RAM cost to about one fourth and binary quantization to about one twenty-fourth of the pre-quantization cost, and MongoDB recommends quantization above 100,000 vectors."
      }
    },
    {
      "@type": "Question",
      "name": "Does MongoDB have a built-in reranker?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. MongoDB's native $rerank stage uses Voyage AI reranker models in the aggregation pipeline."
      }
    },
    {
      "@type": "Question",
      "name": "Is MongoDB Vector Search available outside Atlas?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Vector Search is available for MongoDB Enterprise Advanced and MongoDB Community Edition, in addition to MongoDB Atlas."
      }
    },
    {
      "@type": "Question",
      "name": "What’s a free vector database I can spin up instantly for a RAG app?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Atlas Ephemeral Clusters are temporary, free clusters that coding agents and developers can create without signing up for MongoDB Atlas. MongoDB Vector Search runs on them, so a vector search or RAG prototype can be built and tested right away."
      }
    }
  ]
}
</script>

<!-- /mobian-agent-ad -->

**You can start this weekend if you keep it small:** pick **1 tool**, **1 tiny project**, write **1 short spec**, and build **1 feature at a time**.

I’d boil the whole article down to this: most beginners fail because they spend too long comparing tools, choose a project that is too big, and ask the AI for too much in one prompt. The fix is simple. Use one editor, set up [Git](https://en.wikipedia.org/wiki/Git) on day one, define what “done” means, and test each step before moving on.

Here’s the short version:

-   **Pick one setup:** [Cursor](https://cursor.com/) plus a local project folder is the default path in the article
-   **Keep the project tiny:** one screen, one main action, no login, no payments, no extra sync
-   **Write the app brief first:** who it’s for, 2–4 features, the data it stores, and your success test
-   **Prompt in small steps:** context, goal, limits, and definition of done
-   **Review every step:** check the app loads, the main action works, data stays after refresh, and the console is clean
-   **Use Git from the start:** commit after each stable milestone so you can roll back fast
-   **Do not trust the first output:** test it, scan the code, and fix one issue at a time

One stat jumps out to me: the article’s sample brief limits the app to just **2–4 main features**, and its local check list uses only **4 checks** before moving on. That tells you the point: **small scope wins**.

If I were starting today, **08/09/2026**, I’d skip tool shopping, make a folder, run `git init`, write a one-paragraph brief, and ask for the file structure before any code. That’s the whole playbook in plain English.

## Pick one tool and one project you can finish this weekend

The biggest beginner mistake is shopping for tools instead of building something.

### Choose one AI coding assistant and one editor

**Cursor** is the simplest local option because it keeps editing and AI in one place [\[2\]](https://vibecoding.app/blog/how-to-vibe-code)[\[5\]](https://sidbharath.com/blog/vibe-coding-guide/). It has built-in file awareness and inline edits, which means you can stay in flow instead of piecing together extensions and extra setup [\[2\]](https://vibecoding.app/blog/how-to-vibe-code)[\[5\]](https://sidbharath.com/blog/vibe-coding-guide/). For most beginners who want to own their code and run it on their own machine, **[Cursor is the default pick](https://daily.dev/blog/cursor-ai-everything-you-should-know-about-the-new-ai-code-editor-in-one-place)**. Don't burn hours comparing tools. Pick one and move on.

Once you've chosen the tool, keep the setup lean.

### Set up a minimal local workspace

After you pick the tool, make a clean folder and put it under [version control](https://daily.dev/blog/version-control-basics-for-developers) right away. For a local project, this is enough:

```bash
mkdir my-project
cd my-project
git init
```

Create the folder. Move into it. Initialize Git. Then open the folder in Cursor, and you're set.

Use Git from day one. If the AI makes a mess, you can roll back fast instead of trying to untangle everything by hand.

### Start with a project small enough to finish

On a first project, small scope wins. A habit tracker, a unit converter, or a personal contact list with "last contacted" dates are all solid picks. Think:

-   One screen
-   One main feature
-   No login
-   No payments
-   No external APIs unless the whole idea depends on one

If your idea takes more than one sentence to explain, it's probably too big. Shrink it. That one-sentence scope is your brief.

## Write a plain-English spec before generating any code

Once you’ve picked the project, write the spec _before_ you open the prompt. If your first prompt is fuzzy, the AI may get you halfway there, but not to a finished app. A clear spec is what makes the output usable.

### Turn your idea into a one-paragraph brief

Write a single paragraph before you generate any code. Keep it simple, but make sure it covers:

-   who the app is for
-   2–4 main features or screens
-   what data it needs to handle
-   what “done” looks like
-   any limits or tech choices

A brief for a habit tracker might look like this: _"A simple habit tracker for personal use. I can add a habit, check it off each day, and see a 7-day streak count. Use React and localStorage. No login, no backend, no payments. Done means I can add a habit, check it off, refresh, and still see the data."_

That last sentence, the success test, matters most. If you skip it, you have no clear way to tell whether the output is finished.

### Break the brief into small build steps

After that, turn the brief into a short task list. Don’t ask the AI to build everything in one shot. Move step by step: scaffold, UI shell, state, persistence, polish. Use one prompt for each step.

This matters because when you pile several features into one prompt, the AI often mixes up the requirements [\[6\]](https://backgrind.com/blog/first-vibe-coding-project/). Smaller tasks also make debugging much easier. If something breaks, you can trace it back to the exact step that caused it. That keeps the next coding prompt tight and on track.

### Use prompt patterns that produce usable code

A prompt structure that works well is: **Context + Goal + Constraints + Definition of Done** [\[4\]](https://monday.com/blog/vibe-coding/vibe-coding-for-beginners/)[\[1\]](https://emergent.sh/learn/how-to-start-vibe-coding). Think of it like giving directions to a contractor. If you only say “build the room,” you’ll get guesses. If you spell out the job, the limits, and how you’ll judge the result, things go much better.

Here’s what each part means:

-   **Context**: the setup. For example, “I'm building a habit tracker with React and localStorage.”
-   **Goal**: the exact outcome you want. For example, “Add a form that saves a new habit name to state.”
-   **Constraints**: the limits. For example, “Don't use any external libraries.”
-   **Definition of Done**: the test. For example, “I can type a name, hit Add, and see it appear in the list below.”

Before asking for code, ask for the file structure and the assumptions behind it. That step helps catch misunderstandings early, before they show up in the implementation [\[1\]](https://emergent.sh/learn/how-to-start-vibe-coding)[\[6\]](https://backgrind.com/blog/first-vibe-coding-project/).

> "The key to vibe coding isn't being vague - it's being outcome-focused." - James Montemagno, Principal Manager, Microsoft [\[7\]](https://developer.microsoft.com/blog/complete-beginners-guide-to-vibe-coding-an-app-in-5-minutes)

## Run your first vibe coding session step by step

::: @figure ![Vibe Coding for Beginners: Step-by-Step Workflow](https://assets.seobotai.com/undefined/6a77c51cd642d19a979279ea-1786236471773.jpg){Vibe Coding for Beginners: Step-by-Step Workflow}

With your brief done, it’s time to move from planning to the first scaffold.

### Generate the scaffold, then build one feature at a time

Before any code gets generated, ask for the file structure first. Then look it over and fix anything that feels off.

Use one prompt for the scaffold, then pause and review the structure before more code gets written. Your scaffold prompt should spell out the stack, what the app does, the first success state, and where you want it to run.

After the scaffold is in place, build **one feature at a time**. Test it right away. If something breaks, fix **only that issue** before you move to the next step. When you hit an error, paste the exact message back into the prompt and deal with it head-on.

Once the scaffold exists, the next move is simple: build one feature and test it immediately.

### Know when to stop and read the code

Once the project starts to grow, stop and inspect it. Pause prompting after the first scaffold, after each meaningful feature, and anytime the output brings in extra dependencies you didn’t ask for [\[3\]](https://www.figma.com/resource-library/how-to-start-vibe-coding/)[\[6\]](https://backgrind.com/blog/first-vibe-coding-project/).

You don’t have to read every line. Just scan for a few things:

-   Hardcoded credentials or API keys
-   Files or functions the AI made but never connected to the app
-   Parts of the structure that feel confusing or out of place

If the setup looks messy, take a minute to understand how the pieces fit together before asking for the next change [\[3\]](https://www.figma.com/resource-library/how-to-start-vibe-coding/).

### Get to a working local build before polishing

Your first goal is a clean local run with the core feature working. Before you move on, do four fast checks.

| Check | What to confirm |
| --- | --- |
| **Page load** | Does the app open without a blank screen or crash? |
| **Main action** | Does the core feature actually do what it should? |
| **Data display** | Does saved data still appear after a refresh? |
| **Console errors** | Is the browser console clean, or are there red errors? |

Don’t start polishing anything until the core flow works.

When the core flow works on your machine, stop there and [commit to GitHub](https://daily.dev/blog/contributing-to-open-source-github-a-beginners-guide). Polish can wait.

A clean local build is the milestone that matters in your first session.

## Common traps that break beginner projects and how to avoid them

### Do not trust the first answer, and do not prompt vaguely

Once the brief is written, the next thing that trips people up is the prompt itself. Two mistakes show up again and again: **trusting the first answer too fast** and **asking in fuzzy terms**.

The fix is simple: be specific.

Specific prompts give you code that lines up with what you meant to build. Vague prompts usually give you a generic starting point that _looks fine at first_ but misses the details that matter.

| Prompt Type | Example | Result |
| --- | --- | --- |
| **Vague** | "Build me a project dashboard." | Generic layout, missing specific data fields or logic. |
| **Specific** | "Build a dashboard with a left sidebar for 3 projects, a task list for the selected project, and a completion header." | Functional UI that matches your mental model immediately. |

That difference matters a lot. A short prompt can save time, sure. But if it leaves out structure, logic, or UI details, you'll pay for it later in fixes.

Also, test each answer before sending the next prompt. If you skip that step, problems stack up. Then you're not fixing one bug anymore. You're trying to untangle five at once.

### Keep the codebase stable with small commits and short notes

After the first answer, lock in what works with Git and short notes. Don't wait until the end of the session to commit. Commit after every stable milestone.

Why? Because AI can drift. One answer looks good, the next one breaks half the app. When that happens, `git restore .` lets you throw away the bad changes and jump back to the last working version.

A small `NOTES.md` file helps more than most beginners expect. Keep it in the project root and write down:

-   the decisions you made
-   [how to choose your tech stack](https://daily.dev/blog/ive-made-up-my-mind-i-know-how-to-choose-my-next-tech-stack)
-   why you chose it

At the start of each new session, paste that context into your prompt. That gives the AI the same project memory _you_ have, instead of making it guess.

One more thing: tell the AI to store any credentials in a `.env` file. Then make sure `.env` is in your `.gitignore` before you write a single line of real logic. It's a small step, but it can save you from a messy mistake.

### Compare the three working styles

When the build choices start to blur together, this table gives you a simple way to stay grounded.

| Approach | Speed | Code Quality | Learning Value | Risk |
| --- | --- | --- | --- | --- |
| **Trust AI Blindly** | Very High | Low/Unreliable | Low | High (bugs/security) |
| **Review & Test** | Medium | High | Medium | Low |
| **Co-design with AI** | Medium | Very High | High | Very Low |

For a first project, **review and test** is the safest default. Blind trust feels fast, but it's a bit like driving with fogged-up windows. You might move fast for a minute, then hit a wall.

If you want to learn while still making steady progress, co-design is even better. But if you need one safe rule to follow at the start, review the output, test it, and only then move on.

## FAQs

### do I need to know how to code to vibe code?

No. You don’t need old-school coding skills to start vibe coding.

What you _do_ need is a clear way to explain what you want, the judgment to give useful feedback, and the discipline to test the output. You might not write the code yourself, but you still have to review it, test it, and manage what the AI produces.

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/og-image.png?v=a830cdf1","width":1200,"height":630},"sameAs":["https://twitter.com/dailydotdev","https://www.linkedin.com/company/dailydotdev","https://github.com/dailydotdev","https://www.instagram.com/dailydotdev"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","description":"Free, personalized developer news aggregator. Stay on top of software development news, AI coding tools, and web dev - curated daily from trusted sources.","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}},{"@type":"WebPage","@id":"https://daily.dev/blog/vibe-coding-beginners-how-to-start/","url":"https://daily.dev/blog/vibe-coding-beginners-how-to-start/","name":"Vibe coding for beginners: how to actually start | daily.dev","description":"Start a tiny weekend app: pick one tool, write a one-paragraph brief, use Git, build one feature at a time, and test each step.","inLanguage":"en-US","isPartOf":{"@id":"https://daily.dev/#website"},"timeRequired":"PT9M"},{"@type":"Article","@id":"https://daily.dev/blog/vibe-coding-beginners-how-to-start/#article","headline":"Vibe coding for beginners: how to actually start","url":"https://daily.dev/blog/vibe-coding-beginners-how-to-start/","datePublished":"2026-08-09","dateModified":"2026-08-09T01:03:27.738Z","isPartOf":{"@id":"https://daily.dev/#website"},"publisher":{"@id":"https://daily.dev/#organization"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/blog/vibe-coding-beginners-how-to-start/"},"description":"Start a tiny weekend app: pick one tool, write a one-paragraph brief, use Git, build one feature at a time, and test each step.","image":{"@type":"ImageObject","url":"https://media.daily.dev/image/upload/s--vwts4MiO--/f_auto,q_auto/v1/recruiter-landing/6a77c51cd642d19a979279ea_1786237070612_2f9d2f4fbe?_a=BAMAMiB80"},"author":{"@type":"Person","name":"Kevin Nguyen"},"timeRequired":"PT9M","potentialAction":{"@type":"ReadAction","target":"https://daily.dev/blog/vibe-coding-beginners-how-to-start/"}},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://daily.dev/blog/"},{"@type":"ListItem","position":3,"name":"Trends","item":"https://daily.dev/categories/trends/"},{"@type":"ListItem","position":4,"name":"Vibe coding for beginners: how to actually start","item":"https://daily.dev/blog/vibe-coding-beginners-how-to-start/"}]},{"@type":"FAQPage","@context":"https://schema.org","mainEntity":[{"name":"do I need to know how to code to vibe code?","@type":"Question","acceptedAnswer":{"text":"\u003cp>No. You don’t need old-school coding skills to start vibe coding.\u003c/p> \u003cp>What you \u003cem>do\u003c/em> need is a clear way to explain what you want, the judgment to give useful feedback, and the discipline to test the output. You might not write the code yourself, but you still have to review it, test it, and manage what the AI produces.\u003c/p>","@type":"Answer"}}]}]}
```

