yogthos

yogthos OP , 2 months ago to memes in Self-Made

You must’ve used the power of both your brain cells to write that comment.

yogthos OP , 2 months ago to memes in Self-Made

you’re not the main character kiddo, get used to it

yogthos OP , 2 months ago to memes in Self-Made

Don’t let the door hit you on the way out.

yogthos OP , 2 months ago to memes in Self-Made

Nothing more hilarious than billionaire simps.

yogthos OP , 2 months ago to memes in Self-Made

aww, little muffin is seething and coping

yogthos , 2 months ago to memes in freedom!

them goalposts be moving

yogthos , 2 months ago to programmerhumor in Let's do micro service

If you have to deploy your service to test features instead of being able to test them locally while developing them then you have a really poor dev workflow.

yogthos OP , 2 months ago to memes in Self-Made

when you definitely know what the word meme means

yogthos , 2 months ago to memes in freedom!

People protesting aren’t voting for Biden, the ones who are are denouncing the protests while doing pearl clutching over property damage.

yogthos OP , 2 months ago to worldnews in Maldives’ representative backed Palestine’s UN admission, demanded action to stop the genocide

Honestly, I doubt anything would’ve substantially changed if UN passed resolutions against Russia. The power of UN mostly applies to smaller states that get bullied by the west.

yogthos , 2 months ago to memes in freedom!

we know you are

yogthos , 2 months ago to memes in freedom!

There’s no leap here, Biden regime is literally arresting students and faculty protesting a literal genocide that US is currently facilitating.

yogthos , 2 months ago to programmerhumor in Let's do micro service

The main problem with microservice architecture is around orchestration. People tend to downplay the complexity involved in making sure all the services are running and talking to each other. On top of that, you have a lot of overhead in having to make endpoints and client calls along with all the security concerns where it would just be a simple function call otherwise. Finally, services often end up talking to the same database, and then you just end up with your shared state in the db which largely defeats the point.

This approach has some benefits to it. You can write different services in different languages. Different teams can be responsible for maintaining each service. The scope of the code can be kept contained reducing mental overhead. However, that has to be weighed against the downsides as well. At the end of the day, whether this is the right architecture really depends on the problem being solved, and the team solving it.

I’ve worked on projects where microservices resulted in a complete disaster and that ended up being rewritten as monoliths, and ones where splitting things up worked fairly well.

What I’ve found works best is having services that encapsulate some particular functionality that’s context free. For example, a service that can generate PDFs for reports that can be reused by a bunch of apps that can send it some Markdown and get a PDF back. Having a service bus of such services gives you a bunch of reusable components, and since they don’t have any business logic in them, you don’t have to touch them often. However, any code that deals with a particular business workflow is much better to keep all in one place.

yogthos OP , 2 months ago to memes in Self-Made

this is one famous study scientificamerican.com/…/the-role-of-luck-in-life…

yogthos , 2 months ago to programmerhumor in Gotta use all those brain cells

The amount of human ingenuity that’s wasted on shit like figuring out how to make more intrusive ads, that could’ve instead been used to advance humanity is one of the biggest tragedies of capitalism.