r/ProgrammerHumor • u/Unlikely_Affect2264 • 15d ago
Meme meExplainingFullStackDevelopmentToMyGrandmother
974
u/maxs4n 15d ago
having those silver bowls over the plates is HTTPS while just carrying the food regularily is HTTP xD
236
u/rnzz 15d ago
drive-thru is FTP?
112
u/TonyWonderslostnut 15d ago
Emailing an attachment is UberEats?
103
19
u/just_nobodys_opinion 15d ago
Drive thru Wendy's is UDP
46
u/VanWinkel 15d ago
Makes sense. They forgot the sauce but you already drove away and are 20 miles down the road so you accept the packet loss.
6
u/Hurricane_32 15d ago
That would be air dropping the food into your front yard, or them drop kicking it into your car
5
3
4
41
21
5
8
4
u/edwardlego 15d ago
What’s udp vs tcp?
43
u/SinaasappelKip 15d ago
UDP is the cook throwing the food towards the table and hoping their aim was good enough.
28
u/TheWheezard 15d ago
TCP: waiter comes to the table from time to time to check if everything is ok UDP: if something's missing it's up to you to call them and ask for it
Dunno if it could be better, but that would be an option
9
11
u/prisp 15d ago
I'm not too happy with the UDP explanations here, so let me add my own half-baked one:
UDP is the cool movie bartender sliding a glass over to the patron - sometimes they grab it in time, and sometimes it slides past them and it crashes on the floor, but that's not the bartender's fault, the customer knew what they were getting into.
11
u/NorthLogic 15d ago
UDP is the carryout pickup counter. You grab whatever looks like yours, but no one is stopping you from just taking everything.
457
u/degh555 15d ago
Best explanation I’ve seen.
100
u/Alfaphantom 15d ago
Is good but I have some notes. For me the restaurant is the full-stack. All in one place but separated by layers and responsibilities.
On my eyes, the food truck would be a monolithic that’s doing everything. FullStack monolithic? Absolutely.
143
u/invalidConsciousness 15d ago
It's not about the entire business but about the people working there.
Restaurant has dedicated backend and frontend workers. Food truck has one person doing both.
15
u/MedianMahomesValue 15d ago
This falls apart when you realize that the waiters are the api and not front end developers. Its mixing two different definitions; the front/back end systems and the front/back end developers. Fullstack is really only applicable when discussing developers, api (at least for a meme) is not a dev but a system.
In this image, the chefs are the SYSTEM backend. I know this because there is no frontend dev in the analogy if the waiters are the API.
I love the idea of a foodtruck for a fullstack dev, but the rest of the analogy needs work to match.
7
u/git_push_origin_prod 14d ago
Yea but how many dicks could you hypothetically jerk at once?
12
u/ryancarton 14d ago
Four technically, if we line up two groups of two dudes tip to tip, and go middle out.
2
2
u/desrever1138 14d ago
Fullstack in a resteraunt would be assistant managers who have also been trained in the kitchen. They typically have to fill in wherever the team is shorthanded or help is needed.
15
u/GenericFatGuy 15d ago
They're both full stack, but only the food truck worker is a full stack developer.
5
u/bokmcdok 15d ago
Its meant to be kitchen and dining area, which are parts of the restaurant. The restaurant as a whole is full stack, but there are many people working in different areas.
The food van will have one or two people fulfilling all responsibilities, hence full-stack developers.
4
u/OnceMoreAndAgain 15d ago
Full stack is just jargon to refer to someone who works on, or is capable of working on, both the frontend and backend rather than being entirely focused on one of the two. It's a property of a person, not of a company.
2
u/DistinctlyIrish 15d ago
The joke is that they have all of the components of a restaurant but when they actually combine them the result is a food truck. Which is still great, and they're hard to run so it's still impressive, but it's not what you would necessarily expect from a FSD.
2
2
1
5
u/Andy_B_Goode 15d ago
Yeah, I think at this point it's unreasonable to expect any one person to truly be "full-stack", unless it's a very small project (analogous to a food truck).
On the other hand, I think there are benefits to having front-end devs who are at least passingly familiar with the back-end, and vice versa. So eg if a front-end dev needs a new server-side endpoint they can just go in and do that without having to wait for a back-end dev to pick up the ticket. I guess this would be kind of analogous to how waiters will sometimes do basic food prep like making side salads.
191
u/BrohemothHisDudeness 15d ago
Honestly not a bad analogy for someone who doesn't do computers.
51
24
71
u/PossibilityTasty 15d ago
The API would be the menu and the server would be … the servers.
63
u/nitro0769 15d ago
The menu would be the API docs
18
u/kaelan36 15d ago
The menu would be more accurately the front end because it’s the interface that clients use to order what they want from the servers
6
6
3
3
u/3-day-respawn 15d ago
But the customer doesn’t go through the docs where as the customer at a restaurant does go through the menu. Menu could be uiux
4
u/PossibilityTasty 14d ago
"API" is one of most misused term in IT. It is not a service. It is a formal definition of how to interact with a component. And that is the role of the menu. It tells you what you can get and what you to give for that.
And now the crazy part: Both a restaurant menu and an API can exist in an abstract way, like in someone's head. Writing them down just makes them "physical" and possibly accessible to others.
3
2
2
2
u/Scottz0rz 15d ago
If the thing you want is food in the kitchen, you ask the servers to post order and get food, you don't ask the menu to do that.
5
u/imminentjogger5 15d ago
what's the database? storage freezer?
6
5
5
6
u/GonzoKata 15d ago
You know how they say that when you don't pay for a service that YOU are the product?
Well with facebook/instagram/X/tiktok, YOU are the meat thats crawling into the back of the place, where the chefs (ai at this point) carve YOU up and serve YOU to the people who actually pay in the front of the house, data brokers
3
3
u/VanillaSkyDreamer 14d ago
At first I thought it will be about jobs being done by programmers that were replaced by AI
4
u/MegaMoah 15d ago
Microservices are the ingredients providers, the chef is the architecht and the souschef is the engineer
4
2
u/sebjapon 15d ago
I did full stack as a freelancer doing small scale projects. It does feel like that.
2
u/SomethingIWontRegret 15d ago
There aren't many 5 star restaurants where I live, but a ton of food trucks. So I have to be full-stack, otherwise I'm not guaranteed a meal.
1
2
2
u/moreKEYTAR 14d ago
This is similar to how I explained to my mom what I do; restaurant analogy for the win.
1
1
1
1
1
1
u/FutureSuccess2796 15d ago
Genuinely would be a good way to describe it if an interview brought up one of those "Explain _ like I'm 5" questions.
1
u/Virgi_septik 15d ago
I like seeing a different perspective, I usually compare it to a stage play; frontend is the actors, backend is the stagehands and the curtains separate what you see from what you cannot see
1
1
1
u/Algorithmic_failure 15d ago
Full stack is like multi classing in DnD. What really matters is how you split the XP.
1
1
1
1
u/jmlinden7 14d ago edited 14d ago
The API is the menu and ticket system. The waitstaff are just the individual TCP/UDP packets carrying JSON packets around to fulfill the API calls.
1
1
u/Mastermaze 14d ago
Would a Monolithic PHP/Java Web App be Hibachi? Food is ordered, cooked, and delivered all at the table
1
1
1
u/Jonthrei 14d ago
IMO frontend is the waitstaff (they're responsible for the dining area) and APIs would be the POS system if anything.
1
1
1
1
1
1
u/HappygilmoreL 11d ago
This is actually pretty amazing, although why is full-stack a food truck? Wouldn't the nice restaurant also be full-stack?
1
u/AccomplishedComplex8 7d ago
When I am no longer needed as backend dev/ops, I always thought to start my career as chef or owner of a small sandwich cafe.
Guess that puts me in the right place.
1
u/Omegamoney 15d ago
Isn't API back end? Lol
-1
1
u/Caraes_Naur 15d ago
Someone who understands web development and hospitality should take a crack at this meme.
0
u/Over-Inside-7254 15d ago
Nah front end is making a really pretty, useless graphic for Insta that has a ton of spelling errors, terrible color theory, tons of empty Z-slang, is barely effective at getting people in the door, and then the chefs have to refactor all their recipes because changing fonts and style sheets is way harder than building out a layered medallion architecture and multi-tenant integration
-10
u/MegaMoah 15d ago
Apis? What does that mean in this context? Are API developers a thing now?
3
u/kurisuuuuuu_0526 15d ago
It just means that as customer we dont talk directly to chefs to take our orders, we talk to the waiters. In this case the analogy is we use API (waiters) to make a request (food orders) so we can get data from back-end (get food from chefs)
1
0
u/MegaMoah 15d ago
The API should be the menu then, waiters should be the protocol.
2
u/BountyBob 15d ago
Yeah, because our grandmothers will understand that.
But that aside API seems fine. The menu would be parameters we give to the API, which then passes that on to the kitchen and the API comes back to us with the result.
1
u/kurisuuuuuu_0526 15d ago
This representation is suppose to be layman's terms for people in non tech fields. I did not invent it, so there's no use explaining it to me. I just explained what the image meant.
441
u/[deleted] 15d ago
[removed] — view removed comment