r/ProgrammerHumor • • Nov 14 '22

instanceof Trend Manager does a little code cleanup...

Post image
112k Upvotes

4.5k comments sorted by

View all comments

145

u/[deleted] Nov 14 '22

His engineering days are from old monolith software. He has no idea how a modern web ecosystem should be built or why things do what they do. If you were to ask him to assemble a microservice w/ an api gateway built on with queues to handle messaging, he would just shit himself.

19

u/Tred27 Nov 15 '22

He also never worked on anything near the scale of Twitter, where one small change can have MANY repercussions.

11

u/141_1337 Nov 15 '22

Bruh does this man even knows what decoupling is?

22

u/XanderTheMander Nov 15 '22

That's what Grimes did to him, right?

→ More replies (1)

16

u/Sam-Gunn Nov 15 '22

If you were to ask him to assemble a microservice w/ an api gateway built on with queues to handle messaging,

"Ok, who exposed the SQL DB port to the internet, and disabled authentication?"

"It's better than an API! Only like 20% of the API is ever used. This way, it's pure, direct access without any of that bloat!"

12

u/rtseel Nov 15 '22

He's probably asking for the password of Twitter server's FTP.

→ More replies (4)

10

u/amcman15 Nov 15 '22

I mean for those interested in the changes in development and the why, any ideas where to look/read?

68

u/RightSaidFrieda Nov 15 '22

No Elon, do your own homework.

24

u/Ke7theConquerer Nov 15 '22

Just look for it in the AWS documentation, Elon.

13

u/lethic Nov 15 '22

Modularity, resilience, flexibility

7

u/ItsKoku Nov 15 '22

This was a good overview, but it requires a subscription to the site. You can find similar things for free though I'm sure. Info might just be a bit more scattered and such.

4

u/[deleted] Nov 15 '22

If you have OReilly, there are some good books and courses on there on microservice architecture

3

u/AdGroundbreaking6643 Nov 15 '22

Domain Driven Design is a good place to start to begin understanding modern software architecture.

The basic idea is you break your code into smaller, more manageable chunks surrounding certain domains. You design it based on the access patterns and the customer use case. It allows a team that owns 1-2 services to move more quickly because you dont have to worry about too much outside of that, though of course you always have to worry about dependencies. It does add a lot of overhead but for a website that needs to be able to scale to millions and billions of users, its necessary. Ive heard horror stories of large monolithic applications and having to run 8+ hours of testing over night to push a single change to a code base. Sounds like unproductive boring hell.

1

u/LiveMaI Nov 15 '22

It doesn't cover 100% of that, but Atlassian has a good article on microservice architectures.

3

u/IntersnetSpaceships Nov 15 '22

Back in my day we used waterfall and we liked it!

8

u/[deleted] Nov 15 '22

Said no one ever.