ndbroadbent

require 'fileutils'

# Warning: The following deploy task will completely overwrite whatever is currently deployed to Heroku.
# The deploy branch is rebased onto master, so the push needs to be forced.

desc "Deploy app to Heroku after precompiling assets"
task :deploy do
  deploy_branch   = 'heroku'
  remote          = 'heroku'
  deploy_repo_dir = "tmp/heroku_deploy"

max-mapper

Note: this rough draft has turned into https://github.com/maxogden/art-of-node#art-of-node

go to https://github.com/maxogden/art-of-node#art-of-node to view the newer versions of this document

Introduction to Node.js

Table of contents

• Understanding node
• Core modules

LindseyB

Node.js Resources

What is node.js?

Node.js is just JavaScript running on the server side. That's it. That's all there is to it.

Express

• Express Docs, if you want to get started and already know JavaScript this is the place to be

karpathy

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.