3 ms·
> Are we miseducating our so-called "full-stack" engineers by not offering them a basic understanding of telecom? Or are they not listening? What's that "stack
by perlgeek 11y ago
> Are we miseducating our so-called "full-stack" engineers by not offering them a basic understanding of telecom? Or are they not listening?
What's that "stack" anyway?
Usually I get the impression that people frontend (user-interface, so usually HTML, JS, maybe a thin web app) and backend (API service, business logic and storage in a database).
Is understanding of the OS, of the memory model, of networking protocols (and possibly even how they are implemented), specifics of file systems etc. part of it? What of the instruction set of the process, of the actual silicon layer? Understanding the physics of the embedded transistors? Understanding the quantum and thermodynamical problems that chip makers run into?
The answer is probably different for everybody who uses that term, since it's a term people use for self-marketing, or for vaguely describing requirements of a job.
- seiji 11y agoBefore nodejs people started calling themselves "full stack" for doing JavaScript on the fronted and the backend, full stack meant everything from knowing networking hardware to kernel insides to databases to application servers to front end html/css/javascript frameworks.
- bjterry 11y agoEvery time I've heard the term full stack used, it referred to web developers, and I think it just implies that someone could go from nothing to having a full website without outside help. That is, they can create HTML and JavaScript front-end and a back-end using a web framework and a database. Anything outside of that is pretty much ignoring common usage. Obviously it isn't a situation like "if you wish to create a website from scratch, you must first create the universe" because that would be a singularly unhelpful definition of full stack.