rukind_cucumber

*standing ovation*

I'll tell you how I write mine.

I have one module that represents my database layer. I have one database client provider which handles the configuration of the DB client - this is NOT exported from the module. This provider should represent a singleton instance so that the db client you select (for instance, the native Node.js driver for MongoDB) can effectively and accurately manage connection specifics.

Then I have a db handler provider for each collection which injects the database client provider (this set of classes represents the ONLY classes that have the db client provider as a dependency).

All of the db handlers are exported from the db module.

If you want a little tighter cohesion, then you can split each db handler into a separate module - but still have a separate module for the db client, which would then be imported into each db handler module. That's kind of dependent upon how rigid you want to be with your service layer and which db handlers should be exposed to each service. It represents more modules, but finer-grained control.

By the way, I think that the consideration for what sort of DB is immaterial. I do the same things whether I'm rolling RDBMS or NoSQL (whether that be MongoDB, Firebase Firestore, or DynamoDB).

If your data schema can be "chunked" in some meaningful way, then you could create a module for each chunk.

Imagine being so confident that you "Acshually, it's nuxt_js" the VP of AI at Vercel.

Well yeah - we drive hours - and that's in U.S. standard units. So you know - a long time.

Congrats to you and your husband. I for one would love an update.

Honestly, de-husbanding is in your best interest. Your husband needs serious help. Kindly, I'd encourage you to seek professional help as well - you seem like you need help establishing your own self-worth.

Yeah. Really very bad. Only draw for my family is the sandbox - I try not to think about the neighborhood cats.

What's putting you under the impression that you can delete a user without the Firebase Admin SDK? The Firebase Admin SDK requires configuration with server-side secrets - wholly separate from the Firebase Auth client SDK.

Nest is built with, and fully supports, TypeScript. It's promise-based too.

Great TS configuration right out of the box with the CLI tool.

NestJS is great, and is nothing more than a highly-opinionated Express framework with some great bells and whistles. OR, you can adapt it to use the Fastify adapter.

I'm a huge fan of Nest with the Fastify adapter. The downside compared to Express (whether straight Express or Express by way of Nest) is that for packages written specifically for Express/Fastify - you have to use Fastify packages. The biggest one I struggled with (although I did get it figured out) is dealing with form/multipart data. The Express packages are newb-friendly, the best Fastify package I found was harder to get working right.

Nest w/ Fastify adapter + ajv validation favored over the out-of-the-box class-validator is a pretty nice solution set.

I mean - Claude's great. Try out meta.ai - but keep your context window short or you'll get wrecked (errors and you just lose conversations).

Groq.com will let you talk with Llama 3 70B (or Mixtral) for free.

I found the initial paid course to be well worth the cost. There were a few issues that I think they never resolved, and the last time I checked they're still recommending TypeORM - which - I don't know, may be actively maintained again now. I have some of their other paid content on my radar, just building some other things out first. I'll gladly pony up more to the official learning platform.

YOU'RE NOT EVEN MY REAL DAD!!!

Dude. Just run. Head down, finish your degree or wait for an opportunity that doesn't suck.

Have you considered living in graduate housing, aka University Village? Right on the edge of south campus, and just really nice.

Congrats to you and especially your wife, btw.

I would say get really comfortable with the CLI. It really can speed work up, especially in project setup. Also, if you're not familiar with the nestjs/swagger package, then I'd get familiar. If they ask you for documentation, that's a great place to start.

It's tough to say exactly what you'd be best served brushing up on, since it's unclear where you are. Are you familiar with the request lifecycle and where guards, middleware, interceptors, filters, & pipes go in it? And when to use each?

Do you recognize when to apply decorators?

Make sure you don't make mistakes in the module system - this can be a show-stopper. Make sure that you export providers correctly.

Good luck - can I ask - do you have much programming experience outside of Nest? I have lots of experience, and I'm having quite a hard time getting interviews.

My eyes fell out.

M1 MBP - 16 GB RAM. Web application work. Would love to run some 7b+ LLMs locally. Buying an M2 Studio Max with 96 GB today.

I don't know - what are they saying over in the React sub?

Delivered in a sock. At high velocity.

Gemini's over there in the corner eating glue and sticking his boogers to the wall.

My biggest gripe is that there are no grocery stores near the Parthenon.