Few seats left for our Advanced Backstage Plugin Development workshop on December 7th. Secure your seat today!
In this episode of The Frontside Podcast, panelists Charles Lowell, Rob DeLuca, and Sam Keathley, discuss how much the distinction between frontend, backend, and fullstack developers matter in both personal and professional senses.
The differences in mindset between these categories are also discussed, for example, how does a fullstack developer solve a problem vs how a backend or frontend developer? And also, how clear (or fuzzy) is the line that separates them? What are the skills a frontend or backend developer needs to consider themselves fully fullstack? And finally, is there any sort of tribal separation between the factions?
Do you have opinions on this show? Want to hear about a specific topic in the future? Reach out to us at firstname.lastname@example.org or on Twitter at @thefrontside.
This show was produced by Mandy Moore, aka @therubyrep of DevReps, LLC.
CHARLES: Hello everybody and welcome to The Frontside Podcast Episode 101. My name is Charles Lowell. I’m a developer here at The Frontside and I’ll be hosting today’s episode. Today we’re going to be talking about the different developer profiles that are out there. You might have heard mention of them on Stack Overflow, on job boards, on the Twitterverse. Things like frontend, backend, full stack, half stack, short stack. [Chuckles] Things like that. With me to talk about these are Rob and Sam. Rob is our director of open source here at Frontside and Sam is a software engineer here at Frontside. So, hey y’all.
ROB: Hey yo.
CHARLES: Alright. So, before we get into the meat of the topic, there are a few announcements that we wanted to make. First and foremost, this is some really exciting news. This week, Taras Mankovski officially joined the team at The Frontside. And we are really, really excited about that. [Cheers]
ROB: That’s exciting.
CHARLES: Yeah. It’s super exciting. Not only is Taras an exceptional engineer, he’s got amazing code skills. He’s extremely empathetic and a great person to work with. He’s great working with clients and he’s also fantastic at really working with developers who are climbing that ladder and helping them level up. So, he’s been involved in mentorship literally since I’ve known him. I think that was the first time that we ever came into contact with him was through his mentorship work in the Ember community. And we’ve been collaborating with him for years on several open source projects. And so, we just are so excited and know that he’s going to come on and do some amazing things by helping us be better developers, helping us be better community emissaries. And so, lots of good stuff coming out of that.
CHARLES: Yeah, yeah. No, that’s really exciting. So, definitely wanted to throw that out there.
ROB: Too bad he didn’t join a little bit earlier. We would have had a good time with him on this podcast.
CHARLES: I know. Well he’s actually, I think he’s been on the podcast twice.
ROB: [Laughs] That’s true.
CHARLES: But yeah, there’s definitely a couple of topics where his input would have been absolutely critical. I think it would have been great to have him along when we were trying to run our own apprenticeship programs. Those would have worked out I think a lot better. Well, not to say that the outcomes haven’t been stellar in some cases. But I think having his expertise would have made it a lot smoother. That said, before we jump in then, just wanted to let everyone know that as always, if you want to work with us you can get to us at email@example.com or send a shout-out on Twitter @TheFrontside. Okay. Y’all, let’s jump into it. Like what is even a stack?
ROB: [Laughs] So, do you want to kind of set up where this came from, Charles? I think it came from you and I going back and forth on Twitter. And I was like, “You know what? We need to talk about this on the podcast.”
CHARLES: Yeah. I think I was actually on vacation.
ROB: [Laughs] That’s right. You were trying to ski.
CHARLES: [Laughs] I was on the ski lift. And I saw you tweeting and I was like, “No, no, no. I got to respond to that.” Probably because there was maybe a little bit of disagreement but also because I just needed something to do. Looking out the majestic scenery of the Rocky Mountains wasn’t enough. So yeah, what’s the backstory there?
ROB: So, I can’t remember what I was actually tweeting about. But I kind of feel like there is a distinction between a frontend developer, a backend developer, and at this point I don’t know if a full stack developer truly exists. I mean, it does. But it’s used more often than it really implies what they’re doing. Usually when you hear of a full stack developer, it’s like, “Man, I can sling some code on the backend and I can do a little bit of architecture stuff on the frontend. But CSS, keep that away from me.” And in my opinion, if you’re a full stack developer, you need to sling CSS, too.
CHARLES: No, no. I certainly agree. Because I was going to ask, is it fair to say that full stack developer is code for like, startup developer?
ROB: Yeah. That’s a good – like a utilitarian, like a jack of all trades but not a master of any?
CHARLES: Right, exactly.
ROB: I can take that. So, I guess the way we can start to dig into this one is like, how much distinction is there between a frontend, a backend, and a full stack developer? And does that matter in a professional sense?
But I know that you’ve got a perhaps more refined take on that, or a different take.
ROB: Yeah. Before I do, I want to know what Sam’s thoughts are on this. This would be a good one.
SAM: Where I come from in the understanding of frontend, backend, and full stack is I – background on me: I did a bootcamp before working here. So, I did a development bootcamp where they were really excited to tell you at the end of it that, “Oh, you’re a full stack developer because we’ve introduced you to everything. Like, touched on every sort of little topic. You’re full stack. Tell everyone you’re full stack.” And it’s like, “Well, you’re not really a specialist in any of the sense.” So, what makes a difference to me, I’m going to specifically talk about full stack, but it’s like before you can say you’re full stack, having knowledge of frontend and at backend, you need to have expertise in at least one of them first, or understanding of that mindset first. Like if I say that I like frontend work more then I need to understand frontend work more before I can say that I understand backend work, you know?
CHARLES: So, do you feel like the bootcamp was doing you a disservice? Or do you think they got…
SAM: So, I don’t think they did a disservice at all. I learned a lot. But I wouldn't say I’m full stack at all.
CHARLES: So, if you feel as though you’re not full stack, what do you feel that you are?
SAM: Definitely frontend.
CHARLES: Definitely frontend.
SAM: I gravitate more towards frontend.
ROB: Why would you feel that way? Is it because you’re more pulled towards the UI of things? Or is that where you feel like you’ve gotten most of your experience now?
SAM: Actually a little bit of both. I tend to like the UI of things a little bit more. It’s interesting. Whenever I was going to the bootcamp, I thought I was going to be more backend because I thought I really like working with the behind the scenes sort of. You don’t see this work but you know it’s there. But I definitely like the UI of frontend a lot more. Just personal.
ROB: I see that.
SAM: And it’s where my skillset is, because this is all frontend work that I’m doing here at The Frontside. So, it’s what I know most at this point.
CHARLES: Yeah. I’m curious too. Isn’t it true that there’s also a conception in the wider tech world that frontend is limited to CSS and HTML?
ROB: Ooh. Yeah, that could be.
CHARLES: Like when you see job posting for frontend developers, typically it’s like, we want someone…
CHARLES: Which is so bizarre to me.
SAM: [9:42 inaudible] a lot of places when a frontend developer who is also a UX designer. Someone who has the knowledge of designing things from the ground up and then only working in things that look good, rather than logic.
ROB: Yeah. This can be probably an entirely other topic. But that’s like the frontend of the frontend and the backend of the frontend, is like [10:03 inaudible] call it. Because there are [10:06 inaudible] developers. And single-page apps have gotten so complex these days, between your data layer and your testing and managing state on the frontend. There is a backend, an architecture, that you need to consider when you’re developing a single-page app. And I’ve worked on teams where there are developers that are working on the frontend but they still don’t like CSS. They don’t do CSS things and they don’t consider layout or any design. They just take the ticket and they get the data going. Get the data from the server, request it, display it on the page. And then another person would come through and style it up to the spec or the mock. But yeah, that’s interesting.
So for my take on this, and where this actually really came from, is we were going through some hiring. And we were trying to figure out how we can place somebody or hire someone that can be effective in the role that we immediately needed. And all of our immediate needs were in frontend-specific things. And we can actually talk about if they’re frontend-frontend or frontend of the backend. But where this kind of came from or was born was: if we’re hiring somebody that needs to fill a frontend role and they’re primarily a backend developer, there are gotchas and things you have to know to be an effective frontend developer. Like quirky browser things that happen or like how to set up a Babel transpilation setup. And what are the gotchas here? Kind of the history of the frontend web, because there’s a lot of things that are there that can cause a lot of headache if you don’t know the backstory.
And I know from your perspective Charles, you think – and this is isn’t wrong – but you think that if somebody has a really talented backend developer, it’s really just concepts that you can apply to the frontend. And I agree with that.
CHARLES: Right. But you have to want to do it. [Laughs]
ROB: Yes. That is also a key.
CHARLES: You have to be gripped by the problem set of the frontend. You want it to inspire you to leverage those solutions.
ROB: Yeah. So, would you say there’s a different mindset between a frontend, backend developer, and full stack? Does a full stack developer solve a problem that’s different from how a backend developer or a frontend developer would?
CHARLES: That’s a subtle question and probably one that might offend people, my answer to it. So, I’ll go ahead and answer it. [Chuckles]
ROB: Hashtag [12:23 inaudible]
CHARLES: Actually, maybe not. Just in my experience historically – I want to underline the fact historically – I think that it is people who gravitate towards the outside-in mindset, in other words the very first thing they’re thinking of is, “How is this going to feel to a person who’s going to use this?” If that’s your first question that you ask, then you probably are going to gravitate towards the frontend. Then in terms of the backend, I’d say historically – and like I said, I want to underline that, and I’ll get to that later – I think it’s people who are more drawn to: I want to attack the most complex problem that exists. Like distributing state over 10,000 nodes, managing huge deployment infrastructures that drive these massive websites that happen at this mind-boggling scale. And so, there you really are thinking computer to computer and, “What’s the ideal interface for doing that?” And then on the frontend you’re thinking more like human to computer, because that’s where the interface lies. Now the reason I say…
ROB: I feel so let down. Where’s the controversy?
CHARLES: Well, okay. Well, because I think that basically – I think the controversy is saying like people who are more naturally empathetic. I don’t know. That would be the controversy thing. But I want to say historical.
ROB: Yeah. I can see that. [Laughs]
CHARLES: So, I want to say historical too, because I feel like one of the things that’s been magical about the last two decades of software development is the dawning realization that no software you write exists in a vacuum and that it’s all interconnected. And so, I think that I for example feel very strongly while I try to think about the user experience first. And the developer, I’m also thinking about developer experience first. The way that you want a system to feel is going to inform the design of the UX workflow and that’s going to affect the architecture of your frontend. And if you’re interfacing with it through different media, like websites, phone, I don’t know, even text messages, Slack, what have you – that’s going to inform then the next level of how your APIs are shaped, your public-facing APIs. Which then inform the structure of your internal deployments.
So, recognizing that the decisions you make in one end of the stack and ripple through completely and that they’re not what we hold as dear these concepts of separation of concerns and complete and total isolation of layers. That really is false. But what it does is it enables us to change the individual layers to more – ironically the reason you want to have separation of the layers is so that it more easily lets you change them provide a more integrated experience. So, I think that’s a long way of saying that I think frontend developers are more aware of what’s going on in the backend and that they might be drawn into the backend. And the same thing goes for backend developers, realizing that the decisions they make are affected by the frontend and affect the frontend. And so, I think there’s been a dawning more of a collective responsibility for design, for operations, for developer experience. And I think it’s great.
ROB: Yeah. And to [think back off] that. So, I was kind of wondering where the controversy was, because that’s kind of my exact answer, too. Where do you gravitate towards on? The difference of mindset is like, if you’ve got a problem and let’s say you’re a full stack developer, so whatever that manes, but if you’re given a task where you have to implement the frontend and the backend, where you gravitate towards first I would say is how you would attack solving a problem.
For me, I would immediately go to the frontend and see how a user would immediately interact with it and then work out that way. Mostly also because I like having a tight feedback loop. And the frontend provides that nicely. I can change something and immediately see the difference there. And in the backend you can spend a little bit of time, unless you’re TDD which you should be – you can spend a little bit of time piecing together things and figuring out the architecture. And then you’ll have something that you could show for. It’s just nice to see UI get thrown on the page. And it’s real and you click a button and something happens. That’s a really nice feeling. And that’s kind of where I gravitate towards. And if yeah, if I had to attack the problem, I’m going there first. I get the endorphins from it. [Chuckles]
CHARLES: Right. So, if we want to add controversy to the other side, because you got to always be controversial, right? So, we said the really blunt horrible oversimplification is that people who are more naturally empathetic gravitate towards the frontend. You could also say that from the other perspective, people who are more internally validated will gravitate to the backend. Because if you need to get those endorphins from working on the frontend, basically what you’re saying is, “I want to put it in front of people and get the feedback from those people and know whether it’s good or bad.” Whereas you could say, “Actually, I don’t need validation from other people. I’ve got this concept of this architecture that is going to be the ideal thing. I know it. I’ve got this vision and I’m going to chase it, regardless of what’s going on.” I think you can more readily do that on the backend because you’re not as open to the feedback of a whole bunch of different users. And like I said, I think those are gross oversimplifications.
ROB: Yeah. I agree. And so, as a devil’s advocate towards the backend developer that is less empathetic, I think actually some of the best backend developers I’ve ever worked with were the most empathetic people ever. Because they know that software is for humans. And humans are going to be consuming the API that they build. And they take that into consideration.
CHARLES: Absolutely. And I actually think that empathy pervades good software development just wherever you find it. Because yeah, someone’s going to be using your APIs whether it’s software as a service or it’s a library. If it’s software as a service, it’s got to be easy to work with. It’s got to be performant. It’s got to have a nice command line. And so, you have to be thinking at all times, “What is it like to use this software? What is it like to consume it? What is it like to link it into my library? What is it like to call it from a web client?” So yeah, I think you’re absolutely right. I think it’s actually one of the great virtues of great software developers.
SAM: Yeah. So, something that I’ve always kind fo had a question with, especially coming from that bootcamp setting: is there any sort of tribal separation between what you would consider a frontend or a backend developer or even full stack? Like, “I’m better because I understand data layers than I understand how a button fits on a page,” that sort of thing.
CHARLES: I would say absolutely yes. If you at the, just do a quick poll of the Twitterverse, it seems like people tend to hang out in little circles of similar interest. So, there’s definitely a bunch of people that I follow that are always tweeting about backend stuff.
ROB: Yeah. Twitter is ‘build your own echo chamber’.
CHARLES: Yeah. And there are people who I follow that are tweeting nothing but mostly frontend – when I say frontend, I mean frontend of the frontend. Well basically, from CSS down to nothing deeper than React components. And then there’s people who are talking primarily about the backend of the frontend. So yeah, I do think that people – there are clearly, there are different areas of the stack and I think that people do tribalize around them. So, the question is: Who are the border agents? Because always cross-border trade. Any time you have borders, there’s an exchange of ideas and information and things that happen at those layers. And actually, one of the things I’m really curious about is: How does that happen?
CHARLES: I don’t know. I think it goes both ways. So, I can only speak to my own experience. And that was when I first started doing frontend development was back in 2003 I think. So almost 15 years ago. We were building a touchscreen interface for an electronics vendor in the UK. And it was just so much fun, because we were getting to build these interfaces that literally looked like nothing else. And you could touch them and you had support for rudimentary gestures and there was no keyboard. And basically the only interface was your fingers and like a price scanning gun. And everything, all the entire UI had to be developed out of that. And so, it was such a novel system and it was so fun to implement that I just gravitated towards it. I think the thing that was particularly compelling was it was very interactive UI. It was high-touch, literally. This is a clerk who’s sitting there using this thing as rapidly as they can to sell stuff and move people through the line. So, it was like a unique problem.
But the thing that was cool about it was I realized so many – we kind of already touched on this in this conversation – so many things that I had learned on the backend applied there. And there was in order to provide that experience, there had to be a pretty complex machine behind it. And that was fascinating, that machine. And so, we were able to apply a lot of the concepts. And so, in that time on the backend I’d just come off working off a backend that had basically an event bus – we would probably call them microservices now, although we didn’t call them that then – were coordinating based on all these events. And that translated over into the frontend really, really well. And I remember using a lot of the techniques for exception handling – doing it on the frontend and doing a lot of the multithreaded stuff that we were doing on the backend, trying to reconcile that with the frontend and really understanding. So, there were all these analogous concepts.
And it could be – so, there was an original exodus of backend development, for me personally. And so for me, it was like I felt like I moved onto the web pretty much exclusively in 2006. And it was a good – I would say 2013 maybe is when web UI development finally caught up with Java Swing. Like it was like, that whole time I was like, “I’m using the web because it’s an awesome deployment platform. And it’s got all this great stuff,” but man, the developer experience is not as good as like a stateful fat GUI was back then. And now, I would say it’s actually surpassed quite significantly. But now, I think there are a lot of people maybe who either – I think there’s a casting back of people who are in frontend development and casting back to the web.
So right now, my love affair with immutability and functional programming started by using a Clojure web framework which borrowed a lot of the ideas from Clojure. So, I guess there was an exodus there – people from Clojure wanting to develop apps, wanted to have their goodies. But then I found that and I was like, “Whoa, that’s awesome.” But then that really set the hook for me. And so now, I try and go back to the well, the backend well or the shared computational well, as much as I can. So, all of that stuff of basically discovering all this functional programming stuff, this highly formalized functional programming, all came from saying, “Wow. I got a taste of that. Let me get more.” So, it’s very much like trying to run through the village of the backend and ransack the stores and take as much as I can and bring it back, because I know that it’s good.
ROB: So earlier in the podcast, you said that you were a frontend developer. You described yourself as a frontend developer. And that’s funny, because I actually consider you a full stack developer. It’s because you can jump in on the backend and sling any kind of code as well as anybody could, and then you can also do the same thing on the frontend. So, the question I have here is: Do you think actually someone that truly is a full stack developer – and we can define that in a second – but do you think they’re at an advantage here, because they have all that experience? You can answer yes. But why? Why do you think they have an advantage?
CHARLES: I think they have an advantage in the same way that a person who’s bilingual has an advantage. So, if you are living in North America, it behooves you to speak Spanish because you are now open to an entire set of markets that were previously closed to you. Well, not entirely closed but like you can trade with Mexico and you can trade with South America. You can buy and sell goods. You have access to yeah, emerging technologies that might – something special might be happening in Mexico City, or in Medellín, Colombia, and you’re going to have first access to that. And so, if you don’t, if you’re not bilingual, then you’re going to have to go through an intermediary who is.
And so, there’s a premium: you get to be the middle man so to speak. Or you get to be, maybe that has kind of a negative connotation, but you get to be the broker of new ideas and new technologies. If you can, if you are fluent in backend so to speak, then you can go into backend-landia and you can talk with the developers there and see what kind of cool stuff they’re doing. And then you can take it across the border into frontend-land and sell it. And so, that’s – I think we’re very much first to the gun on – not first to the gun but we’re ahead of the pack in terms of functional programming. Because we’ve seen that. We’ve seen it proved out and we’ve now actually started to integrate it into your day-to-day routines. And we’re ahead of the pack on that, right? And so, I think that’s kind of a keystone analogy for me that I think really, really captures what is the advantage in being a full stack engineer.
ROB: So, well how do you define a full stack engineer or developer? What things do you have to possess to actually claim that title? In order to be a full stack developer I personally believe you have to know, you have to be comfortable with CSS. You can hate it. You can yell at it. But I think you have to be able to put together a layout if a designer gives you a comp in order to claim full stack. And in the same token, if you’re a full stack developer and you mainly came from the frontend, you should be able to implement backend features. I don’t actually have – so, I’m strong in the frontend, not so strong in the backend. What would be the analogous of CSS in the backend? Would it be like mocking your controller actions? [Chuckles]
CHARLES: I would say you should have a familiarity with HTTP and REST, would probably be the equivalent. Kind of like a foundational technology that just every single technology is oriented around it, or most. Regardless of the protocol you’re using – there are things like GraphQL which are not really RESTful, although it’s a blurry line there – but they’re still delivered over HTTP. And so, understanding things like CORS, understanding the things that are going to be universal to APIs.
ROB: I think a lot of people try to claim full stack. I try to claim it. And I know I’m not. I can put together a pretty crummy Rails API on my own for personal projects. But I’m not going to be the one that’s setting up indexes on a database to optimize a database or anything. I think that does come in time, but you have – borrowing from Brandon Haye’s talks about career development – if you’re a full stack developer, I think you end up having to be in the industry for a long time. Longer than what we consider a senior developer these days, I think. Because you could be a senior developer and be specialized. And we see that all the time, and that’s okay. But in order to amass that knowledge and experience, I think you have to be in the industry for a long time and done those things a couple of times to really know.
CHARLES: Yeah. I agree. So, can I add something there? To continue the analogy of being full stack is like being bilingual or multilingual. I go back to those analogies a lot because that’s what I – linguistics is what I studied in school. But when I was studying linguistics, one of the things that was going on there was they were kind of redefining what…
ROB: That makes so much more sense of your vocabulary. [Laughs]
CHARLES: What it means to be bilingual. There was kind of a reorientation of that definition that was going on while I was in school. And that was being bilingual doesn’t necessarily mean you’re able to converse about poetry or like deep technology or give speeches in another language. It really is, it’s as spectrum of…
ROB: Ooh, that’s quite interesting.
CHARLES: The definition of bilingual is like: Do you use another language in your life? So, if you are let’s say someone who is a recent immigrant to a country and let’s say you’ve got less than 1,000 words but you’re using them to buy groceries, to pay bills, to do things like that, then you are bilingual. Bilinguility is not an exclusive club. It’s really, are you actually using a language? So, if…
ROB: Ooh, so that actually gets my wheels turning. Does that mean that you can have a junior full stack developer? Because like, if you just merely speak the both languages, technically by that definition, I jive with that. You can speak two languages. You are bilingual. You can write in two different languages. You might be full stack. But does that mean in the software industry you are a junior full stack developer and then as you go on and get tasks that are full-stack-like, you get better on both sides? Or is it as an industry, we really have to specialize?
ROB: Yeah, that makes sense.
CHARLES: You will just naturally be drawn over borders throughout your career just because someone's got to do it, to do the thing that…
ROB: You got to solve a problem.
CHARLES: Right, when you’ve got to solve a problem. So, I think that people become more and more full stack over the course of their careers. But that said, I do think that there are clearly areas where functional specialization is absolutely a requirement. Like if you say, “You know what? We’ve got this API and we need to support 600 queries per second and we’ve got this huge, crazy deployment…”
ROB: I will not be your person to do that.
CHARLES: Yeah, exactly. That’s something you’re very much – that is something that you’re very much hiring for. And you want to be hiring for like you said, someone who has the skill and someone who, that’s what they want to do.
ROB: Yeah. If you need better state management and rendering performance and testability on the frontend, I’m your person. [Chuckles] If you need me to scale your API, to handle hundreds of thousands of requests a second, nope. [Laughs] So yeah, I agree with the specialization. So Sam, I want to know. Has this conversation swayed you any way? Are you more interested in being full stack or are you leaning to a side more? [Chuckles]
SAM: So, I think full stack is, it’s as much about skillset as it is about personality. So, like you were talking a little bit earlier on how someone who’s frontend might have more empathy towards the user. And someone who’s backend might have more empathy towards the computer and the developer, rather than the end user. I think someone who’s full stack has to have a wider range or empathy so they can empathize with all rather than just one or the other sets. I think personality-wise, I’d be a fine full stack developer. But I think professional-wise, I do gravitate towards the frontend because that’s just how I am. As a person, I like to see the visual rather than the concept. I do a lot of painting. I do a lot of drawings. So, I’m a very visual person. So, it’s really helpful to me, especially for someone who’s junior and who’s still learning and who came from that bootcamp experience, to be able to see what I’m changing. So, I think it does kind of go a little bit into experience as well. So, I think over time when I start touching on maybe some more backend work and I see some stuff that interests me, definitely I’ll gravitate towards it, just because I want to learn. But I don’t know that it’s like an intrinsic quality, you would want to be full stack or be backend or be frontend, you know?
ROB: That’s interesting. Yeah, I agree with that.
CHARLES: Yeah. That is actually a really interesting point. Because I think what I heard you say there is that when you have – software is a hidden world in many ways. You talked about it in the beginning of the conversation, the areas of the site unseen. Like you know it’s there but it’s hidden from view. So, there’s a certain amount of vision that needs to develop. So, you kind of internalize what software, like this hidden software, looks like. So what does a deployment of some load-balanced microservice clustered thing look like? Most people would not be able to answer that question. But the more time you’re exposed to it, the more it becomes burned into your inner vision.
ROB: Mental model?
CHARLES: Yeah. You develop a mental model. Your brain literally wraps around that. It takes time. But on the frontend, especially if you’re a visual person – but I would say even if you’re not – I think the same would apply to someone who’s using assistive technology. It’s still something that you can feel with your sense and you don’t have to develop a sixth sense to perceive it. So, there’s literally a problem of perception there. And so, maybe frontend work is a great on-ramp for everybody, because it’s so perceptual.
ROB: That’s exactly why I picked it. I was trying to do iOS dev before. And I could not do it for those reasons. I didn’t have that nice tight feedback loop of even though it was UI, in Objective-C you had to construct your UI and buttons out of Objective-C. Unless you wanted to use Apple’s Interface Builder and that was, meh. Everybody built it procedurally. And what I loved about HTML and CSS, was I could instantly throw something on the page, attach some CSS to it, and see it change immediately. And that felt so good. [Chuckles]
CHARLES: Yeah, yeah, no. And it’s important to get those really tight feedback loops, especially when you’re starting out.
ROB: So, if we had to tie this back together, did we decide that there is a distinction between frontend, backend, and full stack? And if there is, or isn’t, why?
SAM: I think there’s like…
CHARLES: I don’t know if we’ve… go ahead.
SAM: Kind of a distinction. But it’s also really fuzzy, I would say. So, if I’m going to explain what the difference is between frontend and backend to someone who maybe isn’t a developer, I would always go back to a video game. So, when you see your guy…
ROB: Ooh, this is interesting.
SAM: Yeah. [Chuckles] When you see your guy running around and you’re like, “Oh, this game looks really good. I’m really into these graphics,” but do you ever think about what it takes to save the game or what is actually being saved when you go to save it? So, if you’re more interested in making the guy run and making the guy and the environment look good, you might gravitate more towards frontend. But if you’re really interested in saving the data, like well what is being saved when I hit ‘save to this slot’ or whatever? Then you might gravitate more towards backend.
ROB: Or like the network layer of the online multiplayer?
SAM: Yeah, yeah.
ROB: [Laughs] That’s interesting. I’ve never used video games as an analogy. I always go like, you know, if you’re a frontend developer, you know that button that you click? That’s the button I create. And then the action that happens is usually what the backend developer does. I think I like the game analogy better. [Laughs]
SAM: I think the game analogy is something that most people can grasp. And most people can grasp. Like I’ll tell people the difference between frontend and backend if I’m talking about Facebook. Like what I do for a job is I’ll show you everything that’s on your Facebook page. And when somebody, or the backend is somebody who makes all of that come into play, kind of, you know? But I think video games are easier to conceptualize that abstraction of data being saved rather than trying to explain the intricacies of Facebook to somebody.
CHARLES: Yeah. No, I like that. I like that. So, I guess if we achieved consensus, would we say that these do exist as broad functional categories? And a full stack developer is someone who will move in between those functional categories through the course of their career. And that generally, the trend is that the longer the career goes, the more you will do that.
ROB: Yeah. I can get on board with that. I’m going to use your career as like the guiding post of that. The way you just explained it, it kind of made something click for me. You describe yourself as a frontend developer. And I think in our industry with software development and the way teams work, I think you end up specializing no matter if you call yourself a full stack developer or not. Because I do think you’re a full stack developer. But you’ve mainly been working on frontend for the past what, three years, four years? So, I think it’s okay to call yourself a frontend developer. But you are a full stack developer. But as you specialize around and amass that knowledge, that’s where you become that full stack developer, right? And so, at one point in your career, you were a backend developer. And then now at this point in your career, you’re a frontend developer. But now you have those experiences and you can draw on both of them and apply them across the fields, right? That’s super interesting to me.
So, maybe it is that you have to specialize in order to achieve the full stack. And you’re never truly a full stack developer in your role. But it’s possible, depending on the team and the team dynamics. It’s just interesting that you can be a full stack developer, also at the same time be specializing as a frontend developer at that current time, right? Yeah, that’s interesting.
CHARLES: Alright, so it sounds like consensus achieved. Let’s all virtually hug. [Chuckles]
ROB: Send the hug emoji.
CHARLES: Alright everybody. That is our show for today. We are The Frontside and we build software that you can stake your future on. We would love to hear from you, especially if you have an idea for a future podcast topic. Any news that you think is something that we should discuss, even if it’s not the theme of the whole episode. And we will see you next time. As always, you can give us a shout on Twitter at @TheFrontside or just drop us an email at firstname.lastname@example.org. If you enjoyed today’s podcast, it was produced by Mandy Moore, the inimitable @TheRubyRep. So thank you, Mandy. And see you all next time.