This chapter goes through some points that you should know if you want to become a full stack developer or if you want progress further in your software-development career. We will also go through some best practices that are good to keep in mind when you're working in the field of software development.
In this chapter, we will look at the following:
To become a full stack developer, you have to be able to work with both the backend and the frontend. That sounds like quite a challenging task, but if you focus on the right things and don't try to master everything, it is possible. Nowadays, the technology stack available is huge and you might often wonder what you should learn next. There are multiple factors that might give you some hints about where to go next. One way is to browse job opportunities and see which technologies companies are looking for.
There are multiple ways, and no right path, to start learning a new technology. The usage of programming web courses is a really popular starting point and that gives you basic knowledge to start the learning process. The process is never-ending because technologies are developing and changing all the time.
The following technologies are necessary to understand if you want to become a full stack developer. This is not the complete list, but it is a good starting point...
Software development is always team work and therefore it is really important that everyone in a team is using common best practices. Here, we will go through some basic things that you have to take into account. This is not the whole list, but we try to concentrate on some basic things that you should know.
Coding conventions are guidelines that describe how the code should be written in a specific programming language. It makes code more readable and easier to maintain. Naming conventions define how variables, methods, and more should be named. Naming is really important because that helps developers understand the purpose of a certain unit in the program. The layout convention defines how the structure of the source code should look, for example, indenting and usage of spaces. The commenting convention defines how the source code should be commented. Quite often it is good to use some standardized ways for the commenting, such as Javadoc with Java.
Most...
In this chapter, we covered the technologies that you should be familiar with if you want to become a full stack developer. The amount of knowledge that you should have sounds like a lot, but you don't have to be the master of all the technologies that we described. It is also good to understand some best practices of software development because then you can avoid common mistakes and your source code will be more readable and easier to maintain.
Packt has other great resources for learning about full stack development:
© 2018 Packt Publishing Limited All Rights Reserved
