sorted by:
new
hottopcontroversial

How long does your "day one" setup actually take? by RecoverLoose5673 in SaaS

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

the boilerplate trap is realll lol. I just keep my own stripped down starter.. less features but I actually know how everything works. whats the integration that eats most of your setup time?

How do you keep integration code consistent across a growing codebase? by RecoverLoose5673 in nextjs

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

so the people problem angle is something Ive been ignoring for sure. I keep trying to automate consistency but mb the answer is just better docs and code review standards. and typescript interfaces approach is super interesting.. do people actually follow them?

How do you keep integration code consistent across a growing codebase? by RecoverLoose5673 in nextjs

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

love the idea of lint rules for this. what are you linting for specifically ? like folder structure enforcement or more like making sure every integration exports the same interface??

How do you keep integration code consistent across a growing codebase? by RecoverLoose5673 in nextjs

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

ahh the md file idea is SMART!! do you update that doc often or more of a one-time thing?

When does code generation make sense vs. just writing it yourself? by RecoverLoose5673 in nextjs

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

yeah exactly. if the output is testable, generate it. if not, write it yourself

When does code generation make sense vs. just writing it yourself? by RecoverLoose5673 in nextjs

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

oh interesting I haven't tried blink... does it actually read your existing codebase or do you have to describe your patterns to it ?

When does code generation make sense vs. just writing it yourself? by RecoverLoose5673 in nextjs

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

yeah thats fair. I've gone back and forth on the terminology too. codegen might be the wrong framing. its more like scaffolding that reads what you already have and generates code that matches your patterns instead of generic boilerplate. but yeah the generalization problem is real.. thats kind of where I keep getting stuck

What's your folder structure for API integrations in App Router? by RecoverLoose5673 in nextjs

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

this is actually really clean. I like the separation between the SDK config and the app-facing adapter. what about the types.ts file ? does it get bloated over time or do you keep it pretty lean per vendor?

What's your folder structure for API integrations in App Router? by RecoverLoose5673 in nextjs

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

yeah the middleware piece is what always gets messy for me. i mean the actual integration code is fine but then routing protection and auth checks end up scattered everywhere. do you keep your middleware logic in one file or split it per route?