If anyone knows us inside out it's our Father! ❤️

He can sense the right or wrong even before we do. He has a special kind of sixth sense and why not, he's our DAD of course! 😅

Happy Father's Day to the Superheros

Do you ever feel like you developed a sixth sense for hunting the source of bugs on your or other people's code?

I was at university, and I didn't really feel like I was understanding C++ or C#, I'd gotten to my final year through two repeated years, skipping the work experience​, practicing as often as I could (even if it wasn't making sense).

In my final year after needing to install windows for the sixth time in a month (sometimes my machine, sometimes friends machines) I got sick of having to install the same utilities over and over again.

So I decided to write a tool to download and install them, also keeping them up to date, I did it in python, teaching myself as I went and it became my final year project! I should have scored 85% but I was marked down for going over the word count.

Apparently I work better on my own and when I've got a problem I need to solve!

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.