re: Why the term 'T-shaped' is better than the term 'full-stack'. VIEW POST

re: Nice 😄, But What would you call a guy who is good at both Front End and Back-end like server side programming language and DB ? I think full stack ...

If it's only front-end, back-end and DB, then you are still missing parts of the full stack. Infrastructure is also part of the stack, and there is other middleware which you should include.

Even if these things are not part of your current project, a full stack developer should have investigated the part to conclude if they are needed now, or in the future.
Otherwise you could say your are a full stack developer when you just create a static website. The webserver, etc., are also part of this stack.


Thanks, Can you give example of Infrastructure and middle-ware ? Also Can you explain what all a Full Stack Dev should know like front-end, back-end and DB etc... ?

Infrastructure is about (visualized) hardware, network management, storage, failover/load balancing, backups, etc. They are the things that you software runs on but which is not explicitly part of the software. Generally you can switch infrastructure without changing the software.

Middleware is basically every supporting software you use. Like, memory cache servers, message bus, API gateways, authentication servers. Things your software explicitly interacts with. You often cannot change these without also changing your software.

There are no rules for what a full-stack developer should, hence this article. It's a misunderstood term.


I missed parts of the stack to simplify the article because arguably there could be infinite sections in the stack. But sure.

Code of Conduct Report abuse