Could not fucking sleep at all.

Spent the entire night in a combination of:

Weight lifting
Playing with NestJS(its fucking beautiful)
Watching seven deadly sins on Netflix(current fav anime)

And i am still not tired. Even then I am not in the mood for going to work.
Not sure if I want to risk it and drive there since I know I will be crashing at around noon.

I hate it when this happens.

During the week I would do crazy shit to try and get me to fall asleep.

I would wake up early. Work out, go to work, get back from work, kill myself at the gym and nope.

Still wide fucking awake.

To make it better, my stomach begins to act up and fucking kill me the more I don't sleep for some reason(although it could be related to me piercing my stomach years ago)

I really dislike being human. Such fragile bodies.

But yeah, NestJS is frickin amazing. Typescript is sexy as all hell with it. Just what i was looking for in terms of out of the box architecture for JS apps

So I am working on a cloud app, Angular on the frontend and NestJS with heavy AWS dependency at the backend. I took my time to learn the stack and I have a couple of years of experience with each piece involved.
Since I am a Level 1 developer, management thought (and I felt same way) it would be nice for me to work with a couple of Level 3 devs.

Well, they hired Level 3 devs:
- a senior Java developer who never touched AWS, any kind of frontend or Typescript
- a senior c++ dev with the same “never touched” as above

And guess what? I have to train them both in Angular, Typescript etc. Kinda defeats the whole purpose of L3, “they will help you to deliver stuff fast”, and adds load on me (I am already a shared resource on 3 teams).
Oh, and yeah, management already promised to release the app by the end of the year and so far I am the only capable and functional developer on the team who has to deliver everything.

I had so much hope for new hiring cycle lol

Opinions on Nest.js:

👏Go👏

A lot of this might be an assumption based on not enough research on both NestJS and TypeScript, so if something here is not well put or incorrect then please feel free to provide the necessary info to correct me since I care far more about getting dat booty than I do being right on the internet :D

Sooo, a year or so ago I got a hold on the Nest JS framework. A TypeScript based stack used to build microservices for node. Sounded good enough in terms of structure, it is based on the same format that Angular uses, so if you use Angular then the module system that the application has will make sense.

I attempted (last night) to play with the framework (which I normally don't since I am not that much of a big fan of frameworks and prefer a library based approach) and found a couple of things that weird me out about their selling points, mainly, how it deals with inversion of control.

My issue: This is dependency injection for people that don't really understand the concept of dependency injection. SOLID principles seem to be thrown out of the window completely due to how coupled with one another items are. Literally, you cannot change one dependency coming from one portion to the other(i.e a service into a controller) without changing all references to it, so if you were using a service specification for a particular database, and change the database, you would have to manually edit that very same service, or define another one....AND change the hardwire of the code from the providers section all the way into the controllers that use it....this was a short example, but you get the gist. This is more of a service locator type of deal than well....actual dependency injection. Oh, and the documentation uses classes rather than interfaces WHICH is where I started noticing that the whole intention of dependency injection was weird. Then I came to realize that TypeScript interfaces are meeheed out during transpilation.

Digging into the documentation I found about custom providers that could somehowemaybekinda work through. But in the end it requires far too much and items that well, they just don't feel as natural as if I was writing this in C# or Java, or PHP (actually where I use it the most)

I still think it is a framework worth learning, but I believe that this might be a bias of mine of deriving from the norm to which I was and have been used to doing the most.

What's the best nodejs framework for the MEAN stack? I need to do additional things to put TypeScript in node js and express. I have seen nestjs with a good directory structure and also uses TS by default. How about meteor or Koa?

Should I just add TS to my existing node and express? Or use nestjs or some other nodejs framework. What do you suggest?

My MEAN stack study is about 75% now but then I keep on getting some new cool things like integration of NestJS and Redux in the MEAN stack.

MEAN Stack - a very big steep learning curve but I like it.

I am learning NestJS + MongoDB stack after spending 5+ years as a Laravel + MySQL dev.

Wish me luck or give me advice. Thanks in advance!

I recon the new project is off to a good start...

Is there any language or framework I am guaranteed to get a job in if I learn right now?

I know this is a shot in the dark cuz if such did exist, every job seeking entrant would simply flock to it; but I don't know how developers switch between stacks. Off the top of my head, recommendation but what if such social capital is missing?

Some background: I built and published a php framework called Suphle (angry-cray-9c191b.netlify.app), which surprisingly neither got any users after a year nor impressed any php employer to hire me despite hundreds of applications sent out

Rather than throwing in the towel, I wish to switch to some other software stack but I don't know where to start, If with all my proven php experience, I'm unable to land any php roles. I have tried searching for nestjs and spring boot internships or junior but nothing comes up. I have run out of time to study a language I will never profit from

I have a flutter app on playstore, built together with a product designer who worked on the ui cuz my front end chops aren't strong. I will preferably continue in a back end environment but if I can solicit immediate employment, I don't mind brushing up on any available tech, be it devops or what have you. I've also worked with spring in a professional capacity, although a very turbulent one where the team we had issues ranging ranging from absence of adequate docs for something as basic as authentication, to using nosql (totally unnecessary), trying to separate codebase into different projects to mirror the real life department (this was my idea). I don't know if it's Conway's law but I decided project should be split into admin, user and common modules/repos since they were being worked on by different devs and had little in common. Unfortunately, there is no doc for importing/sharing local projects so we had more days chucked off

Anyway, I Built a react native app a lifetime ago. Been around the block a bit and pretty confident I won't take much time to get up to speed with a tech. Where do I go or how do I start? I stay in Nigeria so may be limited from on-site roles as well

Was surprised to stumble on somewhere I wrote,

"Doesn't matter whether they love it or not. It must be finished, either way "

I felt like crying. It's not dated so I don't know when, but it should be early 2023. I'd been working on suphle for two years with neither assistance nor guarantee that it'll turn out great. I noted that after running out of juice to energise myself till the finish line. I strived to finish it and launched to the php community in September /October 2023, with it reaching box office bomb acclaim

BUT I did keep to my pact with my younger self. The uncertainty was insufficient to hold me back. I know suphle was not trash because even as recent as last week, I saw a method "onErrorResume", in spring webflux that provides developers with an API for gracefully handling runtime errors. Suphle is ahead of its time cuz I had this built-in without ever seeing it elsewhere

I saw parallels with nestjs too when I used it last year. They just never gave it the opportunity to see light of day. The story would have been more complete but finishing it is enough for me. At least I tried. It wasn't abandoned and we aren't now talking about pending features and how I'd never make out time to work on them or dream of how great it would have been if the world got its hands on it. Or how I'm holding myself back. We know all those details now

So I'm new to NestJS, Node, etc. and I just noticed that the guy working on the API made every request call a different service class, instead of using a single service class. For example.

get() {
return await this.getObj.run()
}

post(myDto){
return await this.storeObj.run()
}

update(myDtoUpdate){
return await this.updateObj.run()
}

And I'm not sure why. He's also injecting the request into those classes, instead of passing the DTO to the method call. I mean, it's still injecting the data into it I guess, but it seems so roundabout. Something like this:

public constructor(
@Inject(REQUEST) private request: Request,
){}

I'm scared, but I'm not sure if it's just my own ignorance or a sixth sense telling me that this is gonna be a mess.

Have you seen APIs implemented this way? I can see the benefit of dividing the code into smaller classes, but it just seems overkill to me, specially when there's a big chance that code will be repeated (getting an entity by ID when updating it, for example).

I'm still in time to kill this with fire before a new monster is born though, so that's something.

Hey guys i am a javascript web developer who loves his stack lot sadly in my internship i was forced to learn php and Laravel and build a full stack website with auth cruds with predefined templates in less than two weeks .
i have to say Laravel sucks comparing it to something like aspnet, Nestjs, Nextjs or Express i found myself overwhelmed with learning in a very short period and what makes things worst is the fact that no one in the agency i am in is helping or speaking with me i asked help from a Senior guy and he was like "i am too busy"...
I also can't quit since this internship is for school purpose so yes rip for me

Was working on a nestjs api and building it on a starter template. After a year of work nest framework has been upgraded by two major version and api is unupgradable and in dependency hell.

Solved it by doing a transplant into new codebase built using cli. Only took two days. Everything went better than expected.

anybody likes/loves nestjs? I don't know why but every time I look at the folder structures, it creeps the hell out of me. And the learning curve, Ughh! I don't even know how people are this patient while learning new things.
btw, any advise for me regarding nestjs?

Is NodeJS + Express + Sequelize enough for an Enterprise app from scratch. Or should I use other Node frameworks like AdonisJS or NestJS?

Frontend will be Angular 9. Database will be MySQL. Thanks!

1. Create informative videos on YouTube about coding and grow my audience.
2. Quit my job and get one that pays better.
3. Learn NestJS/MongoDB stack good enough to finally add a new skill on my resume, hopefully resulting in a new job.

Any recommendations and tips for monorepo setups to share stuff between multiple typescript nuxtjs projects for the frontend and some nestjs backend ones? And all applications are deployed in docker containers.

I feel like I'm going crazy, everything I try is broken, or not fully implemented, or has a shitton of gotchas and customization that must be done on a case by case basis.

This is the most unfun shit I've done in a while.

Just asked our devops guy to create 2 environments for 2 repos (BE and FE). He said this would take around 10h. Is this normal? Nothing fancy just a NestJS API and a React FE. It’s in AWS.

Help me decide to choose between nestjs and Adonis js framework for node? I know laravel and angular so it makes hard for me to choose between the two.

Nestjs is angular inspired while Adonis js is laravel inspired. I only have experience with express framework. Thanks!