4 ms·

Almost no full stack developers are expected to work with assembly (unless explicitly stated) so that seems more than a little hyperbolic. Full-stack in its co

Almost no full stack developers are expected to work with assembly (unless explicitly stated) so that seems more than a little hyperbolic. Full-stack in its common usage doesn't mean "everything and nothing." People might disagree about where the exact boundaries are, but there are a lot of people who definitely don't count by any definition so it does convey information. Those who only work with HTML & CSS & client-side javascript are definitely not doing full-stack development. Nor or those doing purely server-side work, database administration, cloud computing, systems/network programming, etc. that never involves a UI with user interaction of any kind. That's quite a lot of people who would immediately understand that they don't meet the qualifications for a position that requires experience as a full stack developer.

EliRivers 6y ago
there are a lot of people who definitely don't count by any definition That is the typical answer I see; the opinion of anyone who disagrees with your opinion is inherently invalid. YOU know what "full stack" means, anyone who thinks it's something else is wrong.
com2kid 6y ago
> Almost no full stack developers are expected to work with assembly (unless explicitly stated) so that seems more than a little hyperbolic. In the embedded world, a full stack developer would be someone who can read electrical schematics, write drivers, write libraries, and by the time you've done all of that the UI part is, comparatively, trivial. Been there, done it, would 100% recommend it. You feel much closer to your code than when 10 abstraction layers are in the way.