It's a meme, but! This is an excellent analogy. A "full stack" dev will definitely make a taco truck app, but maybe that's all the customer needs.
maybe that’s all the customer needs
The food truck is often better than the restaurant experience in every dimension... The same is valid for the app analogies.
How many people worked on it is not a dimension that counts.
Yup. In addition to the above, "When I spend a Saturday evening adding a shitty perl hack to fix a critical system flaw in production", it can be illustrated by a UN emergency food drop. It may be 99% rice, but it'll keep you from starving and it'll have to do for now.
For anyone about to say API is more like a delivery driver an not a server, realize we are in Programmer_humor, not web_dev.
No joke that was the first thing I thought but realized it’s freaking perfect.
The entire meme is about web-dev. That split between backend and frontend isn't anywhere else. (And is stupid for the web too, but well, that's what web-dev do.)
I mean, not quite. There should be a split between backend (logic) and frontend (presentation) even for desktop applications. It's not mandatory, but simply much better design. The 'interface' with which your frontend code calls the backend is much like an API (as in an API is also an interface)
So there is no desktop program that calls to a remote server for information someplace? Maybe like a server database on what games you can join, player movements and speed who is online, maybe even what music you can play? Or maybe a mobile/phone app that does the same? A way to have a standard interface but get new and updated info delivered to you in that specific form? This information would be delivered from one specific place to another, maybe to your table/device.
Front end and back end happen in more environments than you think.
That being said I can get delivery to my terminal/cmd from a ton of places that have nothing to do with each other kind of like getting pizza and tacos delivered.
I never get these jokes. If you can fix a bug or add a feature across all layers of the stack by yourself that’s a valuable skill.
You can assign that bug to a single dev and they do it all themselves without having to involve multiple teams.
I don’t get the shit talk.
Who's shit-talking? They are all rough jobs in one way or another, and have their strengths and weaknesses. Some Devs specialise because the product/company is big, others generalise because the product/company is tiny and they barely have enough money to pay you, let alone seperate frontend and backend Devs, so you have to moonlight as a food van cook to make ends meet and also you live in the food van and sleep on the floor and stay warm from the exhaust of the meat fridge, every waking moment is a living nightmare and you haven't had a proper shower in weeks because the stalls in the gym are always packed with horny gay men who are terrible kissers and don't understand that you just want to be held for a minute jfc
Reminder to tip at food trucks, it's a ton of work.
where's the rest?
