Been using nodejs for a rest API. It may be the old fart in me, but I'm regretting using it instead of a normal static typed language. I hope something changes my mind soon, or I'll go through a case of sunken cost fallacy.

MILF marketplace.
The audience seemed to enjoy it but I don't think I'd get any investment.

When do you know something is being overdesigned or overengineered?

The applications that the other programmer started building are killing me. He's using Clean Architecture and it has like a million different classes and shit. It's not messy or anything, but fuck it's overwhelming.

Just to figure out wtf was happening when getting the currently signed in user's email, I had to go through like 30 folder and files. Maybe more. All files were fairly simple on their own, but the entire flow was mindfucking me. Use cases, schemas, gateways, repositories, entities, models, etc etc

And that's the client facing application, I haven't checked the API yet, though it seems like that one is simpler.

The worrying aspect here is, any time anyone else has to mess with this, they'll also have to deal with this shit. This needs some really good documentation.

I'm not liking docker so far. I assume it gets better later, but I've had a miserable experience using it as part of my dev environment so far. Just now I updated it and it broke my db container, so now I'm looking to either downgrade docker or fix the issue, both beings things that take time away from coding.

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.

So I started using git submodules. It seems I've walked into something unexpectedly cumbersome.

Looking for some opinions here. Chatbot from scratch or use an existing service?

I have to work with a messenger chatbot. The company has been using chatfuel, so I'm trying to work with it but it's kinda buggy in some parts. Have any of you created a messenger bot from scratch? I flipped through the documentation and it seems like a pain in the ass, but it's obviously more flexible than using a third party service.

So yeah, I'm trying to weigh the convenience of the third party vs its limitations compared to coding my own. What's your take on it?

Every night, after all is silent and peace and calm reigns, I pray to Santa to bring swift death to WordPress.

Assuming you're working 8 hours a day, for how long do you manage to stay productive? I think I can't do more than 4 and a half. Maybe 6 on a good day.

It's not. But it's the only thing I get paid for.

"The client needs this feature by the end of the month."
Me: "Ok."
You can probably figure out what happened by the end of the month.

This Macbook Pro (2017 model I think?) is probably. the worst computer I've. purchased in my life. Really, the worst electronic device surpassed only by my old Xbox 360.

Not only is t he keyboard absolute shit. as. you can see from the way this was typed and riddled with extra spaces and dots, but apparently. the way the monitor was built doesn't. let y ou simply replace the flex cables if they kick the bucket, you have t o replace. the entire screen. Because reasons.

It seems it was a common issue but. they won't fix i.t without charging you for THEIR fuckup.

Never again.

I'm the only developer here. I'm also pretty bad.

I can't handle all this responsibility, every single fuck up will be my fault.