Being Full-Stack Difficulties

I started working in the field of web design about 6 years ago as a full stack developer.

To become a full-stack web developer, I had a long way to go. First, I started with learning Front-end part, html, css and js, and then I learned php and its popular framework, Laravel for back-end development. I learned these parts all by myself, which I do not recommend this model for any programmer who intends to learn a technical field, cause this model is not flawless and it made me skip some of the basic concepts. In my opinion, a programmer who seeks to enter a field, at least at the beginning of his career, should be under supervision of an expert of that field, to show him the path and to guide him through difficulties he/she might face.

Another thing I would have done if I could go back was that I would have gone ahead with project-oriented web design, because I learned topics sporadically and I didn’t noticed them until starting my first project.

After a few years, being a full-stack became a difficulty for me because:

• The bigger and more complex the project was, the more energy and time it consumed from me.
• Considering the wide range of technologies I used for both front and back-end, it was difficult for me to catch up with them all.
• There were many new topics to learn that made the previous topics more elusive.

All these problems made me turn more to specialization and team work in the field of web design, and according to the background of my interest, I chased front-end development and this even absorbed me to UI/UX design and made me active in this field.

Now, I work and use more dedicated frameworks and libraries in front-end and I’m aware of the latest tech news or updates as well.

Of course, being a front-end developer doesn’t mean that programmer doesn’t need to know any basic back-end design fundamentals, and on the contrary, in my opinion, back-end web developer needs to know the basics of front-end design.