- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or # to comment.
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.
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.
“Enterprise” software is always a jumbled mess of garbage written by a revolving door of the lowest-bidding morons. The marketing team just slaps a shiny label on it.
Taco trucks taste better anyway
They may have more flavor but there is an increased risk of food poisoning or stomach issues later. On the other side of the argument, this comparison only works with higher-end restaurants as the image appears to be alluding to. Food trucks can be and often are better than restaurants that just don’t give a damn because food trucks are generally works of passion. The problem is that it is really hard to keep a mobile environment sanitized.
Assuming you have enterprise software that actually has a budget and isn’t driven by suits then dedicated roles will get you superior software that can last a long time almost every time.
Full stack is also slightly dangerous since you can silo entire features to a single person. The same can be said to dedicated roles depending on the setup, but the points of failure are much narrower if that one guy wins the lottery or is but by a bus.
Somehow I always wind up being The Guy Who Had Better Not Get Hit By A Bus, and I have yet to win the damn lottery. Although I’m sure my chances would improve if I ever bought a ticket.
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.
where’s the rest?
