3 ms·
What you are describing is not full stack, it's backend development. Full-stack adds the front-end, and that's why you won't find js devs that can configure ng
by pluc 3y ago
What you are describing is not full stack, it's backend development.
Full-stack adds the front-end, and that's why you won't find js devs that can configure nginx, because they've been surfing on that "full" part of "full-stack" for years but it really just means you can do node and JS.
- shagie 3y agoBack in lamp stack days, also involved front end development - though that was before even jQuery. Writing the page to do front end navigation was part of the expectations of the fulls tack developer. They may not be a web designer, but the "ok, this is what the designer wants the page to look like - here's the HTML that I need to write to realize this" was part of writing the perl (in my case) CGI to make it spit out the proper html in the proper spot... and you really can't do most php without doing front end development as an integral part of it. The definition of full stack has changed over the years as the stacks have changed and more emphasis is on the front end as front end libraries and frameworks have evolved to take more of the heavy lifting for presentation.
- thoughtpalette 3y agoGoing to echo Shagie. Even early 2010's full stack was WAMP, MAMP, LAMP stacks + HTML/CSS/JQuery. Or .net/webforms, java, etc.