Maybe you want to be a U IE designer, a u x designer affront and developer back and developer Full stack developer.

Maybe you don't even know what all these things mean.

Well, that's perfect for you to come here, because in this video, I'm gonna tell you the difference is between all these different types of developers and show you which one will be best fit for you.

So without any further ado, let's get started.

Now.

Welcome back to Webb.

Have simplified my name's Kyle, and I'm here to simplify the Web for you.

So that sounds interesting.

Make sure you subscribe to my channel for more videos of me.

Simple.

Find a Web Now on the topic of Web development, there's really two main things that people think of, and that's back end and front end and then kind of the 3rd 1 of full stack development, which is the combination of both back end and front and development.

Those aren't the only types of developers out there, though.

I'm gonna start with them at the beginning, though, because I think the easiest to understand the differences between we'll start with a back and developer.

A back and Web developers job is to take care of everything that the user doesn't see.

They take care of the server.

They take care of the FBI.

They handle all of the incoming request, handle the database interactions.

They take care of pretty much everything that's on the back end of the website that the user will never see the front and developer.

On the other hand, they take care of essentially everything the user interacts is they're dealing with the HTML, the CSS, the JavaScript react any front end libraries, for example.

They're really building the user experience for the user's as well as potentially doing design work.

But maybe not.

They may just be doing javascript work or just HTML work, and not really as much design work.

But that's kind of the main separation between back end and front end.

The idea of a full stack developer is someone that does both back in development and front and develop it.

Usually they're not as in depth into either one of the topics, but they're good at both of them and are really good at gluing the two together.

They're really good at making the connections from the front end to the back end, which is really important now.

You may think those the only options out there for Web development, but inside of each of these options of back end, front end and full stack there are tons of other specializations.

And there's also even options outside of that round.

One of the biggest things that people forget about is the idea of Dev.

Ops and Dennis offs are the people that take care of all of the stuff that happens even behind the end of the back.

And they're like the back back end people.

Essentially, Dev Ops deals with making sure all of your stuff works properly on your servers.

They do was setting up your server's getting all of your applications connected on your servers, setting up your database, making sure your application can talk to your database, doing all of that fancy back into work that even the back and developers are not very good at.

For example, me.

I am not at all good at Dev Ops.

It took me forever to get my own website up and running.

So Dev Ops is definitely not my specialty.

But when it comes to the other specialties like full stack, that is really where I specialize.

So you don't have to be an expert in all of these different territories.

You really just need to choose the one that resonates best with you.

In general, if you're more of a design focused and creative person, you may like the front end more.

For example, me.

I enjoy the front end more than the back end for the most part because I have a more creative side to myself.

Other people that really like the more logical side of things may enjoy the back end more because there's not any of that creativity.

Expect you're not really creating user designs.

You're more implementing business logic ap eyes, that kind of stuff, server interactions and not so much user interactions.

So already we've broken down what we're doing into four main parts.

We have Dev ops, which is way on the back.

We have the back end than the full stack people and then the front end people.

And that's kind of the bridge from all the way on the back toe all the way on the front, but inside the front, and there's even more than you could break down into.

If you're a really creative and design oriented person, you could be more of a front and designer or even a graphic designer, where you spend most of your time in HTML and CSS and not nearly as much in Java script.

And you may even work in programs such a sketch Fig Mar illustrator, where you're actually building designs not in code but in some other program specifically meant for building out Web designs.

This is a really great route for someone that's really creative and really likes design.

I am not nearly as good designers.

I need to be to be a full front and designer, So that's why I stick more in the full stack side of things because I prefer to be able to do both also in the front end.

You have you, I and you extra designers and developers and these people.

Their goal is to really make either the user experience really good or the user interface Really good.

So the user interface people are really about making the site look really good, while the user experience people are about making this site really easy to use for.

The user's thes two rules really have a lot of overlap between them.

So I like to kind of group them into one section, but generally the U ex people.

So the user experience people are gonna work a bit more on the Java script side of things while the U I people are gonna work a bit more on the CSS and HTML side of things.

But there's a lot of overlap between the two, so, really, if you're going to do one, you can also do the other one fairly easily.

Another kind of for gotten typo developer out there for what development is someone that specializes on Lee in the database.

All they do is work on writing really efficient database queries and making sure all the database related information between your APP and two year database is really solid and works really well.

These kind of rules usually only crop up in larger companies that have such large databases and interactions that they actually need specific database people while smaller companies use.

You will rely on the back end or potentially even the front, and developers working on building up the database as it needs to be.

In general, though, you'll see mostly the back and developers working on the database or specific database people only.

So now that we've broken down and to find all the different types of developers out there, let me break down why you would want to choose one over the other based on your specific personality type.

And we're gonna start with Dev ops because Dev Ops is by far the most different out of all of the different types of developers.

The devil's developer is someone that really enjoys working on the very nitty gritty machine level things because you're not gonna have almost any graphical interfaces.

Almost everything you do is gonna be through a Linux terminal or command line, and you're gonna be most likely SS aging into servers that you're controlling through your company and doing a bunch of command line related interfaces and also just hooking up all the different infrastructure potentially on AWS or some other platform like Digital Ocean.

If you really enjoy that nitty gritty of how the entire Internet works together and it's connected and how servers and databases communicate between each other and you don't really need graphical interfaces, you like to prefer to work in the command line on Lennox, then Dev Ops.

Maybe a great option for you, and I would definitely look into it now, moving a little bit further away from Dev Ops.

We have the database related people, and this is a little bit more removed from led development than the other options, but it's still something very connected to love development.

So if you enjoy writing things in Sequels such as Post Crest, my sequel even know Sequels such as Mongo, D.

B and you just really are into optimizing those queries and writing really complex sequel queries, then I would highly recommend looking into a database option at a potentially larger company.

So next we're gonna move on to the back and developer, which is kind of the very first step in development that most people think of when they think of the Web and the back and developer is someone that generally really likes the logical side of things more so than the creativity side of things, you're gonna be doing a lot of work on divine in your controllers, your routes, your models, your database interactions as well as things such as testing in the back.

And testing seems to be much more prevalent than in the front end, even though recently the front end has gotten a lot better at testing.

But I definitely said the back end is much more further along for testing.

So if you really like that logical, defined tested application, I highly recommend going with the back end over the front end.

Also, another nice thing about the back end over the front and is in the back, and you're not gonna have to deal with different versions of browsers.

The software on the back end is defined by you, so it's always gonna be the same version.

Which means it could be easier to work with, because you don't have to worry about supporting a bunch of older versions of things on the back end like you do on the front end.

So if you enjoy that level of stability and tested nous, then I would highly recommend checking out back and development over front and development.

Next, we're gonna skip over full stack development and come back to that one last because it's a combination of both back end and front end, and then we're gonna jump into front and development next.

Now a front and development.

You're really gonna like this If you are the more creative person.

Like I've mentioned in the front end, you get to do a lot of creative work where you design the CSS for how your sight's gonna look.

You get to design the interactivity through the Java script, and you're gonna be the closest to what the user is actually seen.

So what you design is actually what the user sees, which can be really rewarding to know that what you're building the user is actually seen and interacting with and actually appreciating another thing about the front and that you may not like a CZ much is that the front and generally has potentially less test because it's a bit newer.

The idea of doing a lot of work on the front end is much newer than the back end, which has been around for so long, which also means that things were changing a lot in the front end.

You know, we have things like react and view and angular.

They're all trying to compete, to be the number one framework right now, and new frameworks air coming up all the time.

Which means that if you choose the front end route, you're most likely gonna have to spend more time learning things than if you went the back under out since things changed so much more on the front end.

I actually find that to be a benefit because I love learning new things.

So if you enjoy learning things, the front end would be a really good option for you.

Also, another downside potentially on the front end is you have to deal with supporting older browsers because browsers are evolving over time.

But you can't guarantee all your users are on the latest browsers, which means that you sometimes have to constantly support older browsers, which means you need to make sure your code is tested on all these different browsers, which can be difficult to do.

Going a little bit further down the front end route, we have the U X versus U I designer and essentially the difference between these two is they're both are very creative and design focused.

But a U IE designer is gonna spend much more time dealing with CSS and actual presentation and how things look.

And they're even gonna most likely deal with tools such as pig MMA and sketch to create those designs.

Well, you ex designer is gonna spend more time working out how things actually work.

They'll be the people building components in the library such just react or angular.

So they're gonna be more in the Java script world, while the designer is gonna be more in the front end world on the CSS.

And it really depends on if you enjoy that more design focus of building something based on looks or if you enjoyed the user experience side of things in the Java script and making things actually function well for the user.

But it really doesn't matter too much.

Which one of those do you choose?

Because, as I said, they have a lot of overlap between the two, which is why in many smaller companies they don't have specific u x and you eye rolls, they just have a front and developer.

And now, lastly, we're gonna talk about the full stack developer.

This is a role that a lot of times you actually won't see as much in larger companies because they want to have dedicated back in and front end people.

But in smaller companies that don't have the money to build the support a full front and team and a fullback and team, they're going to hire full stack developers.

And the idea of a full stack developer is that they're good in both the back end and the front, and they're not gonna be as good as a full time back in developer or full time front end of over.

But they're gonna be better as one person at making both of them work than if they had just a back and developer or just a front end of over.

So the idea of a full stack developer is to just be really row rounded in all the different technologies that come with back end and come with front end.

You don't have to be an expert, but you need to be passable and good and essentially building out a full application from the very, very back end, connecting your database all the way to how it looks for the user's using the CSS in HTML and potentially even creating designs in tools like sketch or fig Mama.

Now, with after all of that, you're still unsure which route you want to take out of.

Recommend just going with the full stack route for now, because that at least will expose you to both the front end and the back end of Web development.

And as you get deeper into both front end and back and you're most likely going to find one that you prefer over the other.

And once you do, I would spend the majority of your time working on that one that you prefer so you could become really proficient in even the front end or the back end if that's your route.

Otherwise, like I mentioned, you could go with the database route or the Dev Ops route if that's your cup of tea and that's all I got.

If you think I missed a developer roll, make sure let me know down in the comments below, because I'd love to hear the options out there that I hadn't even thought of.

Also, if you want to see more of my videos, make sure you click over here to check them out and subscribe to my channel for more videos where I simplify the web for you.

Thank you very much for watching and have a good day.