Well if he met me, he could add one more person to his list of people he has met over the years that meet his expectations of "full stack developer." To be hon

Well if he met me, he could add one more person to his list of people he has met over the years that meet his expectations of "full stack developer." To be honest, I'm getting sick of the front-end/back-end bifurcation that I see literally everywhere now. I'm even guilty of it. It has this notion that you are either back-end only or front-end only. It really leaves no room for actual expertise that allows a software engineer to actually build software. In fact, the terms back-end developer and front-end developer imply neither person on his or her own can actually build working software without the other. And that's total crap. These terms started appearing more frequently in the mid-to-late 2000s and nowadays they seem to be all over. But back in the early and/or mid-2000s, "Web Developer" or "Software Engineer" or "Application Developer" sufficed and it was implied that you could build software from scratch, soup to nuts. Of course, in a large organization you had multiple "Web Developers" who surely specialized in one thing or another in order to help their comrades out so not everyone was doing everything at the same time to maintain sanity. But still, as a "Web Developer" it would be expected that you could build software and everything that entailed for the web. Not "Oh well I built the backend... now you just need one other person to do the rest."