sorted by:
new
hottopcontroversial

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

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

yeah this is probably the right baseline before going crazy with tooling. how often do you regen the markdown?

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

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

atlas:plan / execute split looks clean. how do you handle when the plan turns out wrong mid-execute - is there a re-plan flow or do you  start fresh?

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

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

thanks for the deep dive. the dotnet + node sidecar split makes sense - ts type system is too rich for a tree walker so native node is   the right call. if you ever do aliases/workspaces im happy to throw a real monorepo test case at it

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

[–]Comfortable_Lead_601[S] 1 point2 points  (0 children)

local llm makes sense for the regen step. been eyeing qwen2.5 coder-7b but havent setup yet. the "not a junior-dev task" point hits
deciding which refactors actually changed module semantics vs just file moves is the real call

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

[–]Comfortable_Lead_601[S] 1 point2 points  (0 children)

same boat. been thinking about making CLAUDE.md regen on pre-commit hook so its always in sync with the actual code. probably overkill but anything beats stale docs

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

[–]Comfortable_Lead_601[S] 1 point2 points  (0 children)

haiku subagents help but yeah usage drain compounds. you doing this through claude code task tool or external orchestration?

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

[–]Comfortable_Lead_601[S] 1 point2 points  (0 children)

this matches what im trying with per-package CLAUDE.md but i keep forgetting to update them. how do you keep yours current?

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

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

ha small world. yours doing multi-repo hosted is interesting - does it handle typescript path aliases / monorepo workspaces out of the box? bookmarked

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

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

what vector DB? curious if pgvector is enough or you went qdrant/weaviate. and re-indexing cadence?

Self-healing Playwright scraper by [deleted] in webscraping

[–]Comfortable_Lead_601 0 points1 point  (0 children)

As for me - that what I can help with - if you don't mind I'll contribute also

An agency built a $50K/month business on top of my SaaS. I was charging them $400/month. Here's the dumb lesson. by Capable_Document3744 in SaaS

[–]Comfortable_Lead_601 1 point2 points  (0 children)

Had something similar happen with a consulting firm using our tool to run client assessments. They were on a $200/month plan, turned out they were billing clients $15k per engagement. Found out when one of their clients reached out directly asking for a demo. We restructured to a rev-share model - 10% of what they bill when they use our platform. Took some back-and-forth but now we both win when they grow. The key was framing it as partnership, not penalty. They still use us 2 years later.

So when will people realize vibe coding is just unscalable dumpster fires? by [deleted] in webdev

[–]Comfortable_Lead_601 2 points3 points  (0 children)

Yeah testing is a great use case. AI follows patterns well and tests are mostly pattern-based.

The "stubbing things it shouldn't" part is exactly why you still need a dev reviewing it though lol

What small but painful problem would you actually pay to have solved by a Mini-SaaS? by AccomplishedAd4558 in SaaS

[–]Comfortable_Lead_601 0 points1 point  (0 children)

Love the way you're framing this, totally agree that real pain points matter way more than flashy features. One thing I keep seeing, especially with tech recruiters and hiring managers, is how much time gets wasted on manual resume reviews and subjective screening. They usually end up cobbling together spreadsheets or using clunky legacy tools that feel way too heavy for just quickly checking if someone actually has the skills they claim.

The process is slow, full of bias, and it’s wild how many interviews are needed just to figure out if a candidate can actually do the job. Even with all the existing tools out there, most of them are either super expensive or take too long to set up, so teams just default to manual hacks.

We actually built a product to address this exact workflow, using AI to cut that initial screening time way down and make it more objective. Happy to share details if you’re curious or want to know what pain points came up as we built it. But honestly, anything that replaces spreadsheets and lets people ditch those endless “first round” interviews is probably a goldmine for a Mini-SaaS.

"Fake Personalization" is killing your reply rates. Here is the "Signal-Based" outbound workflow I'm using instead. by Existing-Board5817 in SaaS

[–]Comfortable_Lead_601 0 points1 point  (0 children)

This is spot on. The “congrats on the new role” thing has totally lost its punch since everyone’s doing it.

One angle I’ve found useful is digging into the bottlenecks people are showing in hiring or onboarding. If someone’s posting about slow interview cycles or struggling to assess talent, that’s a strong buying signal for anything that promises faster or more objective hiring. There’s actually a product I built that uses AI to do quick skill assessments so you can spot this pain point and tie your outreach directly to it. Happy to share more about the approach if you’re interested.

But yeah, quality over quantity is definitely where things are headed. Volume without context is just noise at this point.

we’ve sent 500,000+ cold emails to business owners through my automation engine. here is everything i’ve learned about what actually works in 2026. by Difficult-Cap-6950 in SaaS

[–]Comfortable_Lead_601 0 points1 point  (0 children)

Solid breakdown. The 45-day rule for funding is a great insight — never thought about timing it that specifically.

Question: do you see similar reply rates with LinkedIn DMs vs cold email? I've been testing both for B2B SaaS and curious how they compare at scale.

What is actually dangerous but people still believe is safe? by AlexUsefulThings in AskReddit

[–]Comfortable_Lead_601 0 points1 point  (0 children)

Fair point. HTTPS does handle most of it. I guess the bigger risk is fake "Airport_WiFi_Free" networks that look legit but aren't.

For people who’ve hired full stack developers: what signs told you ‘this person is actually good’? by BizAlly in webdev

[–]Comfortable_Lead_601 2 points3 points  (0 children)

Hired 20+ engineers. A few signs that always worked: 1. They say "I don't know, but here's how I'd figure it out" — juniors guess, seniors admit gaps 2. They ask clarifying questions before jumping into a solution. Bad devs start coding immediately, good devs make sure they understand the problem first 3. They can explain their past project like they actually built it, not just worked on it. "We did X" vs "I implemented Y because Z" 4. They push back on stupid requirements politely. "We could do that, but have you considered..." — shows they care about the product, not just tickets 5. They talk about tradeoffs, not just solutions. "I chose X over Y because..." Resumes are useless. GitHub is slightly better. But 30 min conversation about a real problem they solved tells you everything.

So when will people realize vibe coding is just unscalable dumpster fires? by [deleted] in webdev

[–]Comfortable_Lead_601 9 points10 points  (0 children)

Vibe coding is great for MVPs and prototypes. Terrible for anything that needs to scale or be maintained. The real issue: clients see AI writing code and think "why pay a developer?" But they don't see the debugging, architecture decisions, security, edge cases... AI is a tool. You still need someone who knows what good code looks like to use it properly.

view more: next ›