HTML to SQL and all needed in between.
Ask HN: What is “full stack” actually?
31–40 of 88 posts
Re: Ask HN: What is “full stack” actually?
#32HTML to SQL and all needed in between.
Re: Ask HN: What is “full stack” actually?
#33In my opinion "full stack" is what all developers actually should be. 15 years ago, it was normal that, as a developer, you know how to administer a server, know how Unix works, know how to setup/debug the database. Maybe know a bit of C. Fast forward to 2015. Lots of developers are purely frontend developers and don't know how to setup a server, or don't know how to administer the database. This is now the norm. The…
You do realize that not all developers work with the web, right? A lot of us actually don't even touch the web all day long, not even for fun.
While true, it's probably safe to assume that in the context of a "full stack" discussion, "developer" can be taken to mean "web developer".
Re: Ask HN: What is “full stack” actually?
#34[deleted]
Re: Ask HN: What is “full stack” actually?
#35Full stack = Frontend + Backend
Frontend = Think Consumer. He's the one that uses the backend, typically via browser. In the browser world, you have HTML + CSS + Javascript (add stuff like MVC framework, JS library etc). All these interact with backend to query or persist data on the backend
Backend - Think producer. Typically these are your servers. Bunch of those actually. You will have servers to simple serve the HTML/CSS and other assets as well as database to persist data. They can be built on a language of your choice - but these days Javascript since you can write both frontend and backend in the same language.
I think the simplest way to think fullstack is to think of an end-to-end experience and list all the components.
Re: Ask HN: What is “full stack” actually?
#36To me, full stack has always meant vertical coverage, not horizontal coverage.
That is, not necessarily experience in multiple web languages, but rather skilled in a particular stack from top (presentation) to bottom (database).
I consider myself, and look for jobs that are full-stack development, particularly because I like to work with JavaScript, CSS/HTML, server-side code, and database development.
Re: Ask HN: What is “full stack” actually?
#37When I hear the term "Full Stack" or someone working as a "Full Stack Engineer" all I can think is someone who can hack its way through the full development stack when need be in a multitier architecture. I sometimes joke around that when a company says they need a "Full Stack Engineer", they mean they want a "Software Architect" without the title,authority and a higher salary.
I wouldn't call it a joke, at least in the insular world of SV VC webapp companies. I view "full stack" as a phrase the same way I view "we want someone whose passion is programming": they're both indicators the company is looking for people to exploit and pay poorly for the amount of labor expected.
Re: Ask HN: What is “full stack” actually?
#38Earlier quoted context omitted.
You do realize that not all developers work with the web, right? A lot of us actually don't even touch the web all day long, not even for fun.
Where did the parent mention the web? I happen to agree with them that developers should be able to handle any level of abstraction, at any layer. But this doesn't have to be with web technologies - not all servers are web servers.
The OP said "In my opinion "full stack" is what all developers actually should be."
It's not what all developers should be. For a lot of us, it would be a complete waste of time to learn technologies that we do not use, let alone have access to.
Re: Ask HN: What is “full stack” actually?
#39HTML to SQL and all needed in between.
I'd say PSD to SQL.