DEV Community

Discussion on: Why you should become a Full-Stack Developer

 
petertorres profile image
Pete Torres • Edited

Hey @jonrandy , I completely agree with you here. This "front end"/"backend"/"full stack" is what is generally considered Web development. To label backend as databases and APIs is an oversimplification. I haven't met many programmers that can explain the basics of DNS and routing, storage management or security/auth, let alone build out the pipeline to stand up all this software and infrastructure. I can sympathize that more of that responsibility has found its way back to the developer since these tasks can now be created and committed to source control. And for sure, the amount of tooling and frameworks available today to stand up a simple web presence "by hand" is a complicated affair, but the benefit of experience will tell us that all this is a repackaging of the old. I used to rag on distributed computing - it was called the mainframe then. "Who's going to pay for that when I have all this computing power on this desktop". Interesting enough, mainframe is as strong as ever. IT has always been complicated. What I mean here (and what I think @jonrandy and @andrewbaisden were sharing) is don't paint yourself into a corner with job titles. Those change faster than the technology they attempt to contain. Imagine yourself beyond a job title.