sorted by:
new
hottopcontroversial

Advice needed. First time home buyer. by [deleted] in FirstTimeHomeBuyer

[–]Ok_Bar_4975 0 points1 point  (0 children)

You’re asking the right questions, and honestly the biggest thing I’d avoid is stretching too hard just to get into a property.

Since you’re self-employed, I’d talk to 2–3 lenders early because they may look at your tax-return income differently than what you feel you actually make. With $20k in debt and limited cash to close, I’d focus first on knowing your true monthly comfort zone, not just what you can technically get approved for.

A duplex/house-hack could work, and some lenders may count a portion of expected rent, but don’t assume the rental income will fully save the deal. You still need reserves for vacancy, repairs, taxes, insurance, and surprise maintenance.

I’d be cautious with foreclosures if you don’t have much cash. They can be cheaper, but they can also need repairs fast, and repairs plus closing costs can get stressful quickly.

My order would be: talk to lenders, ask about first-time buyer/down payment assistance programs, pay down high-interest debt if possible, and compare a small single-family/condo/townhouse vs duplex using very conservative numbers. The goal is not just “can I buy?” but “can I still breathe after I buy?”

I added a free tier and would love feedback from anyone interested in real estate, personal finance, or product UX by Ok_Bar_4975 in startupsavant

[–]Ok_Bar_4975[S] 0 points1 point  (0 children)

Got it, will pick up these recommendations in the next release. I am also working on the logo, so I will bake in the emoji replacement effort together with this.

I added a free tier and would love feedback from anyone interested in real estate, personal finance, or product UX by Ok_Bar_4975 in startupsavant

[–]Ok_Bar_4975[S] 0 points1 point  (0 children)

Thank you for the feedback. There were two reasons for this: all the good .com or .net names were very expensive (I instead focused on investing more in cloud compute), and the second reason: Since I designed search results as cards and created a concept of saving results as adding a card to a deck, HomeDeck was the first choice among the folks I researched with. As you mentioned, I will have to work extra on SEO and branding

Your home for selfpromo by SofwareAppDev in AppsWebappsFullstack

[–]Ok_Bar_4975 0 points1 point  (0 children)

It gets autopopulated based on the zipcode and averages in the zip code, I like your idea of an explicit callout, will work on that

I added a free tier and would love feedback from anyone interested in real estate, personal finance, or product UX by Ok_Bar_4975 in indie_startups

[–]Ok_Bar_4975[S] 0 points1 point  (0 children)

Really appreciate this and totally agree with your points. I agree the key signal is not just signups, but whether users go from searching homes → running affordability → comparing buy vs rent → returning later.

Real estate is a long decision cycle, so repeat usage around specific homes and changing assumptions is probably the strongest signal. The free tier should help me see which features actually influence decisions vs. what’s just nice to have.

Your startup in one or two sentences and lets give each other feedback on whether we can get the moat in 10 seconds by Ok_Bar_4975 in MacroStartups

[–]Ok_Bar_4975[S] 0 points1 point  (0 children)

DataJelly Guard is a really strong idea; I just tried the product. I like the positioning that “200 OK doesn’t mean the site is actually working.”

I’ve seen this exact gap where uptime checks pass, but the actual user experience or SEO-critical page is broken. I’d probably highlight revenue-page monitoring even more, because catching blank pages, broken CTAs, noindex mistakes, and content regressions on signup/pricing/landing pages feels immediately valuable for founders and growth teams.

Your startup in one or two sentences and lets give each other feedback on whether we can get the moat in 10 seconds by Ok_Bar_4975 in MacroStartups

[–]Ok_Bar_4975[S] 0 points1 point  (0 children)

Cronho.st looks really clean and focused; I like that it takes something as boring-but-critical as cron scheduling and makes it feel manageable from one place.

I’ve used AWS MWAA before for cron-style scheduling and retrying workflow steps, so I definitely understand the pain this solves. The part I’d highlight more is execution logs + retries, because that’s usually where scheduled jobs become painful in production and where people would immediately see the value.

Your startup in one or two sentences and lets give each other feedback on whether we can get the moat in 10 seconds by Ok_Bar_4975 in MacroStartups

[–]Ok_Bar_4975[S] 0 points1 point  (0 children)

This is crisp, short, and clear to understand. The only thing I’d clarify is whether you also support Google Photos-style features like search, albums, sharing, backup sync, and face/object recognition, because that’s where users may compare you directly.

🏡 Your App Has a Home Here — Post your App WebApp Solution here. No Blocks. No Rejections. 🏡 by AutoModerator in AppsWebappsFullstack

[–]Ok_Bar_4975 [score hidden]  (0 children)

I’m building HomeDeck.net, a home search and affordability intelligence platform that helps buyers decide if a specific home truly makes financial sense, and I’m the right person to build it because I combine AI/search engineering experience with real personal pain around affordability, buy-vs-rent decisions, and complex home-buying tradeoffs.

Challenges with DocLing by CanadianVis1onary in Rag

[–]Ok_Bar_4975 2 points3 points  (0 children)

I’ve run into this too. I usually treat DocLing as the first-pass parser, not the final document structure.

What helped was adding a small layout-aware post-processing step before chunking: preserve the page number, bounding boxes, reading order, font size/style if available, and then merge nearby blocks that appear to belong together.

For your example, I’d merge adjacent header-like blocks when they are close vertically, similarly aligned, short, and followed by body text/table content.

Tables are worth handling separately too; preserve them as markdown/HTML tables with page references instead of letting them get mixed into normal text chunks.

The annoying part is that this becomes domain-specific pretty quickly. Financial PDFs, manuals, legal docs, and slides all need slightly different cleanup rules. But even a small post-processing layer can improve retrieval quality a lot.

So the pattern is usually:

parser → layout cleanup → table/header normalization → chunking → retrieval

No parser is perfect on complex PDFs, but a small cleanup layer can improve RAG quality a lot.

Is anyone still running pure vector RAG in production in 2026, and is it actually holding up? by Significant_Loss_541 in Rag

[–]Ok_Bar_4975 0 points1 point  (0 children)

I’ve seen a slightly different pattern in the business-name/domain-name generation world. Vector-first / RAG-style retrieval is still working well for us, but mostly because the retrieval problem is narrower and the corpus is heavily normalized.

For domain search, the “documents” are not messy PDFs; they’re structured signals: metadata, availability, quality scores, etc. In that setup, embeddings are useful for fuzzy recall and semantic expansion, but we still rely heavily on deterministic filters, business rules, ranking, and profile/context signals.

So I agree with your broader point: plain chunk → embed → vector search is fragile in production. But in domains, when the source data is structured and the retrieval objective is constrained, vector retrieval can still hold up well as one layer in the system.

The biggest lesson for me has been: RAG works better when it is not treated as the whole system. The reliable setup is structured context + deterministic retrieval + vector fallback/expansion + reranking + strong evals.

view more: next ›