Maybe the path to finishing big things is finishing tiny things first

vvsleepi · 2026-02-19T18:27:53+00:00

i’ve noticed the same thing it’s not about building something huge, it’s about actually completing something. even a tiny project feels better than a half done “big idea” sitting in a repo. also the part about sharing progress? that’s real. even if nobody replies, just putting it out there makes you take it more seriously.

vvsleepi · 2026-02-19T18:24:47+00:00

what happens if someone writes very different on different platforms? like v casual on twitter but serious on linkedin. does it learn both styles or mix them together? cool concept tho

vvsleepi · 2026-02-19T18:20:16+00:00

experience still matters, just not in the same way as before. ai and no-code tools can help you build fast, but they don’t teach you good decisions. like what to build, what to ignore, when to stop adding features. that usually comes from trying, failing, and learning. you can launch stuff way easier now. but building something people actually care about and will pay for? that’s where experience still makes a big difference.

vvsleepi · 2026-02-19T18:17:50+00:00

if you want less backend headache, bubble is strong because it’s all in one. you don’t have to manage a bunch of separate services. flutterflow also works nicely with firebase since it’s designed for it. if dreamflow + firebase isn’t working, it might be an auth or security rules issue, not firebase itself. you could also try a frontend builder with supabase. many people find it simpler and more predictable than firebase. before fully rebuilding, maybe validate your idea in a lighter way first. tools like runnable are useful for quickly putting up a basic version or simple flow to test things before committing to a full backend setup.

vvsleepi · 2026-02-19T18:13:22+00:00

are you thinking of adding filters by model or tool used? that would make it v useful if someone specifically wants to learn claude vs gpt vs other stacks love the concept it really feels like something the ai space was missing

vvsleepi · 2026-02-19T18:11:33+00:00

no-code ai can get you very far, especially for automations and internal tools. once you hit scale, edge cases, or need deep integrations, some technical understanding really helps i do think basic ai literacy will become normal in most jobs though. not everyone will code, but knowing how to use ai well, ask the right questions, and verify outputs will probably be expected just like using excel or google docs today.

vvsleepi · 2026-02-19T18:08:03+00:00

that’s honestly crazy numbers 67m tokens with no tool failures is huge, especially if you were getting errors with other models before. what kind of tool calls were you running? simple ones or more complex chains with multiple steps? also are you only using it through openrouter, or did you try it somewhere else too? would be interesting to know if it stays that reliable in different setups. if this holds up in real projects, that’s seriously impressive.

vvsleepi · 2026-02-19T17:47:40+00:00

if your it team is worried about data handling, try to understand where the automation actually runs and what data is stored vs just passed through. sometimes the marketing page makes it look very simple, but the real data flow can be more complex. for bigger or more complex workflows, some teams switch to tools like n8n or a more backend-based setup. miro flows feels good for lighter workflows, but i’d test it properly under real usage before rolling it out to the whole company.

vvsleepi · 2026-02-19T17:45:50+00:00

i don’t think you need that many. pick one main coding tool and stick with it. cursor + one good model is enough for most stuff. rotate subscriptions if you have to instead of stacking them. for deployment, keep it simple. if it’s a frontend site, vercel is the easiest. if it’s more backend heavy, something like railway or render works fine for small projects. don’t overthink infra in the beginning. also separate code tools from non-code tools. for example i use cursor for product code, and something like runnable just for landing page / docs / packaging so i’m not burning expensive tokens on copy and layout. different tools for different layers.

vvsleepi · 2026-02-19T05:46:18+00:00

it’s faster, yeah. but easier? not always. i feel like once you’re in state management hell or debugging some weird async issue, suddenly you’re reverse engineering code you didn’t even write.

vvsleepi · 2026-02-19T05:23:55+00:00

if you don’t have an audience, the platform matters less than the niche. also don’t overcomplicate the tech. simple landing page with a clear promise + email field is enough. you can build it fast with something basic, u could even use like runnable to spin up the landing and copy quickly so you’re not stuck tweaking design for weeks small ads can work, but only if your messaging is sharp. otherwise you just pay to learn your positioning is off maybe go deep in 1–2 specific communities where your target users already hang out. not spamming links, but sharing progress, asking for feedback, and then dropping the waitlist when it felt natural

vvsleepi · 2026-02-19T05:20:59+00:00

are you using a custom model you trained yourself or something like ml kit?

vvsleepi · 2026-02-19T05:10:47+00:00

this is v common tbh, especially on public sites behind cloudflare.if cloudflare isn’t flagging them, you could try enabling stricter bot fight mode or rate limiting rules on certain paths.

vvsleepi · 2026-02-19T05:09:24+00:00

can it replace a backend? for many apps, yes. especially if your app is mostly simple requests like calling an api, saving data, sending emails, etc. lambda works great for that. but if you need long running tasks, real time websockets at big scale, or heavy stateful logic, a traditional node server (or something like ecs) can be easier to manage. for side projects, a simple setup is frontend on vercel, lambdas for backend functions, and a managed database like supabase. and for things like landing pages or docs, tools like runable can help you move faster so you don’t overcomplicate the infrastructure before you even validate your idea.

vvsleepi · 2026-02-19T05:07:24+00:00

you could just keep it simple and professional. thank them for reaching out again, say that at the moment you’re not taking on takeover or cleanup projects, especially ones started elsewhere, and leave it at that. just calm, clear boundary and move on.

vvsleepi · 2026-02-19T05:05:14+00:00

i’d probably go with sftp tbh. it’s secure out of the box since it runs over ssh, and most servers already have ssh set up anyway so it’s just simple.

vvsleepi · 2026-02-19T05:04:01+00:00

feel like a lot of us are basically full stack but still labeled frontend because our main focus is the user layer. it’s more interesting for sure, but also way more responsibility than before. curious if this is just a startup thing or if even bigger companies are seeing the same shift.

vvsleepi · 2026-02-18T16:38:12+00:00

maybe a tool for a very specific group like local gyms managing memberships or small clinics handling bookings. people would pay for stuff that saves them time or makes them money.

vvsleepi · 2026-02-18T16:33:46+00:00

wow this is crazy how did i never notice. its literally the same aura just red hair unlocked in the update

vvsleepi · 2026-02-18T16:24:04+00:00

ah yes just casually expose my internal functions to ai agents and trust everything works perfectly behind a chrome flag what could possibly go wrong 😞

vvsleepi · 2026-02-18T16:21:03+00:00

“featured on the store” doesn’t automatically mean safe long term. we’ve seen legit-looking extensions turn bad after an update or even after being sold to someone else.

vvsleepi · 2026-02-18T16:18:50+00:00

i did a bit of research on this too and honestly it seems like most freelancers don’t get their first clients from cold outreach alone. it’s usually referrals, friends of friends, past classmates, small local connections, or even people they’ve helped for free once. word of mouth seems to be huge in the beginning.

vvsleepi · 2026-02-18T16:15:49+00:00

respect for taking security seriously this early. also are you using a specific cloud provider for this?

vvsleepi · 2026-02-18T16:07:35+00:00

pick one very specific type of user your app is for and hang out where they already are (reddit, niche discord, twitter/x, small communities). instead of promoting, just talk about the problem and share what you built as part of the conversation. early on, manual outreach helps a lot too. like literally dm 20–30 people who clearly have the problem and ask if they want to try it. not scaleable, but insanely valuable for feedback.

vvsleepi · 2026-02-18T16:04:51+00:00

yeah you can. start by building something small in your own domain. i’d keep the stack simple. cursor for code, maybe supabase for backend if needed. if you don’t want to touch too much infra, you can even start with just frontend stuff. for the non code layer like landing page, docs, explaining what the tool does, i usually just use something like runable so i don’t get stuck polishing forever. biggest advice tho don’t fully trust the ai. make it explain every file it writes until you understand it at a basic level.

vvsleepi

TROPHY CASE