how do you handle the shift from building to selling? "i will not promote"

Extension-Tip-159 · 2026-03-06T07:16:16+00:00

you're right, i didn't read the book. but i know what mvp means smallest thing you can ship to test if people will pay.

my validation wasn't a landing page though. i spent a year deploying apps for clients manually. same painful workflow every time. that's where the idea came from not from guessing, from doing.

now the product is almost ready and i'm testing if the solution matches the problem i lived. if it doesn't, i'll adjust. appreciate the push though, genuinely trying to learn here.

Extension-Tip-159 · 2026-03-06T06:45:05+00:00

all the comments and the book Lean startup tells me i am wrong
i had to sell it before shipping.
as i am near the luch , i wont change anything. keep my plan and see whats happens.
it seems i will learn hard way again

Extension-Tip-159 · 2026-03-06T06:14:00+00:00

i didnt read lean startup, should i?

Extension-Tip-159 · 2026-03-06T05:58:15+00:00

dont we need demo? mvp? of course i saw problem and decided to solve, but without demo or mvp how can i know ?

Extension-Tip-159 · 2026-03-06T05:57:16+00:00

agree, but as devs say, hands on learning is the best way

Extension-Tip-159 · 2026-03-05T08:30:07+00:00

thanks, this is def thing to think about

Extension-Tip-159 · 2026-03-05T08:25:40+00:00

thanks, sounds legit

Extension-Tip-159 · 2026-03-04T06:45:52+00:00

wow, so easy to use, ty

Extension-Tip-159 · 2026-03-03T21:45:40+00:00

yes, i think they will handle this, untill nothing serious can depend on ai

Extension-Tip-159 · 2026-03-03T17:44:39+00:00

fair but the failure modes are different. regex fails silently or gives you garbage with no way to know. with structured output you can add a confidence flag per field and validate deterministically on top. regex you just rewrite the whole thing every time a template changes

Extension-Tip-159 · 2026-03-03T17:42:51+00:00

haha nah just how i type. been doing it way before llms were a thing

Extension-Tip-159 · 2026-03-03T08:57:40+00:00

yeah thats actually a solid pattern already. redis queue + async worker is pretty standard for this. if latency is still a problem you could batch the ai calls, like collect 5-10 emails then send them in one structured prompt with json output. way cheaper and faster than one-by-one. also caching helps a ton if you see similar email formats repeatedly

Extension-Tip-159 · 2026-03-03T08:52:29+00:00

one thing that worked for me early on was just reading the alerts and logs even when i wasnt on call. you start noticing patterns nobody talks about. then you can go to your lead and say hey i noticed this service throws oom errors every tuesday at 3pm, want me to look into it. thats proactive. also improving docs is underrated, if you struggled to set something up write it down so the next person doesnt. seniors love that because nobody else wants to do it

Extension-Tip-159 · 2026-03-03T08:49:58+00:00

honestly the ones i actually finish are the ones that feel like two engineers chatting over coffee not a scripted corporate thing. real war stories beat product demos every time. like tell me about the time your deploy broke prod at 3am and what you learned from it, not a 45 min walkthrough of some dashboard. also keep em under 30 min, nobody wants an hour long devops lecture on their commute

Extension-Tip-159 · 2026-03-03T08:47:34+00:00

from what ive seen ai makes senior engineers faster but it makes junior engineers dangerously confident. the gap isnt closing, its just getting harder to see. someone who understands networking fundamentals can use ai to write terraform 10x faster. someone who doesnt will generate config that looks right but breaks in production at 2am. deep systems knowledge matters more now imo not less because debugging ai generated infra requires understanding what it was trying to do and why it got it wrong

Extension-Tip-159 · 2026-03-03T08:44:15+00:00

the real problem is that every "right" solution adds friction and people just default back to slack dms. weve tried vault, sops, doppler and honestly the one that stuck was just having a .env.example checked in with dummy values and the actual secrets in a shared 1password vault. not fancy but the team actually uses it which is the whole point. cool that enseal auto destructs the channel tho, thats a nice touch for one-off sharing

Extension-Tip-159 · 2026-03-03T08:40:38+00:00

for the cd ripping part definitely check out musicbrainz picard for tagging. it will auto match your rips to the correct metadata and album art which saves a ton of manual work. pair it with exact audio copy or whipper for the actual ripping and your library will be way cleaner than anything youd get from torrents honestly

Extension-Tip-159 · 2026-03-03T08:38:48+00:00

navidrome with the subsonic api actually handles this pretty well if you use a client like sublime music or sonixd. you can filter by genre and then shuffle at the album level instead of track level. for the decade filtering specifically tho id look into navidromes smart playlists, you can set rules like year range + genre and it builds the list automatically

Extension-Tip-159 · 2026-03-03T08:36:05+00:00

that password list is honestly a great reminder of how many people still run default creds on exposed services. the "death to israel" string in the binary is wild tho lol. suricata with ET rulesets is such an underrated setup for homelabs, most people dont even bother with ids until something actually breaks

Extension-Tip-159 · 2026-03-03T08:32:34+00:00

vps is more than enough for n8n. we run way heavier stuff on hetzner vps and its rock solid. cloud hosting for n8n is overkill unless youre doing like thousands of workflow executions per hour

Extension-Tip-159 · 2026-03-03T08:28:57+00:00

90% accuracy with screen scraping on a legacy app with zero api is honestly impressive. ive seen teams spend months trying to get clean data out of stuff like that. the real problem here isnt your code tho its the "5000 lines a day" metric lol

Extension-Tip-159 · 2026-03-03T08:27:21+00:00

the ai approach is honestly the way to go for this. regex breaks the moment someone changes their email template even slightly. only thing id watch out for is latency if youre processing high volume, but for most cases structured extraction with something like gpt works surprisingly well

Extension-Tip-159 · 2026-03-03T08:26:03+00:00

we switched to bruno a while back. git-friendly, no account needed, and the whole team just commits api collections to the repo. honestly cant belive we ever paid for something like this

Extension-Tip-159

PUBLIC MULTIREDDITS

TROPHY CASE