u/Dry-Hamster-5358

Great list. Here's what it actually means for those of us who just vibe our way through code:

1. DATABASES — Prisma + Postgres Postgres is a database. Prisma is a tool that lets you talk to it using JavaScript instead of learning SQL (a whole separate language). Without it you're writing raw SQL queries and one typo silently deletes everything.
2. FORMS — React Hook Form + Zod Forms seem easy until someone types their age as "banana." React Hook Form manages your form state without your app melting. Zod checks that the data makes sense before it goes anywhere. Together they handle the boring validation logic so you don't have to.
3. PAYMENTS — Stripe or Polar PCI compliance is a set of legal/security rules you have to follow if you store card details. It's a nightmare. Stripe handles all of it. You never touch the actual card numbers. Just use Stripe and go home.
4. SEARCH — Algolia or Typesense Building a search bar sounds easy. It is not. Typos, speed, ranking results by relevance — all hard. These services are just search engines you plug in instead of building your own.
5. BACKEND — Serverless + BaaS first BaaS = Backend as a Service (think Supabase or Firebase). Instead of setting up your own server, you rent one that scales automatically. "Serverless" just means someone else manages the server. Good for MVPs where you don't know how many users you'll get.
6. ERROR TRACKING — Sentry or LogRocket Console.log only helps if you're watching. Sentry automatically records every crash and error that real users hit, even when you're asleep. LogRocket also records what the user was doing when it broke. Both are infinitely better than waiting for a user to describe what went wrong.
7. ANALYTICS — PostHog or Plausible You want to know if anyone is actually using your app. Google Analytics is bloated and creepy. PostHog and Plausible are lighter alternatives that tell you which features get used, where people drop off, and whether that new button anyone is clicking.
8. UI — shadcn/ui or Radix Pre-built components (buttons, modals, dropdowns) that already look good and work correctly. Instead of spending a day making a dropdown accessible and styled, you install one that already is. Saves enormous time on things users won't even notice.
9. CONFIGS — env + dotenv Your app needs secrets: API keys, database passwords, etc. You never hardcode these directly in your code (especially if it's on GitHub). dotenv lets you store them in a separate file that stays off the internet. env is the concept, dotenv is the tool.
10. FILE UPLOADS — UploadThing or Cloudinary Handling file uploads yourself means dealing with multipart form data, storage limits, file type validation, and slow servers. These services handle all of that. You get a URL back, you store the URL. Done.
11. CI/CD — GitHub Actions + Preview Deploys CI/CD automates testing and deploying your code. Every time you push to GitHub, it can automatically run your tests and deploy a preview link. Future you will not remember why you changed that one line. Having automated checks means you catch it before it goes live.
12. PERFORMANCE — Lighthouse + Vercel Analytics Lighthouse is a free tool (built into Chrome) that scores your app on speed, accessibility, and SEO. Vercel Analytics shows real-world load times from actual users. Slow apps get abandoned. These tell you where to fix it.
13. ONBOARDING — Empty states When a new user opens your app and there's no data yet, show them something helpful instead of a blank screen. "You haven't added any tasks yet — create one here." Small thing, huge impact on whether people stick around.
14. FOLDERS — Modularize early Don't dump everything in one file. Group related code together from the start. If you wait until the app is big, untangling it takes ten times as long as just doing it right early.
15. DOCS — Write your README now A README is a text file that explains what your project is and how to run it. Write it while you remember. Come back in three months and you will have absolutely no idea what any of your own code does.

Credit: u/johns10davenport

been using Runable recently for structuring small workflows and quick iterations
mostly for breaking tasks into steps instead of doing everything in one go

It’s been useful for prototyping ideas and reducing back and forth, especially when things get a bit repetitive
still figuring out where it fits best though

Curious how others are using it in their workflows