It is often said that back-end developers are the witty ones who are willing to be the solution to problems in all situations. More like they're the "Messiah of web engines." Funny fact is Messiahs have similar stories.

Yes, a thousand back-end developers actually. They, almost similarly, go through that cunning path from wanting to learn a new programming language to wanting to solve problems and provide effective solutions to finally choosing a Framework { to catch feelings for } , to finally having to take some course on HTML and CSS.

To say that it doesn't even end there but continues where the Back-end developer spends a fortune of the day writing CSS and centering "painful divs". It is at this point they it feels very necessary to give themselves a new title of a "full stack developer."

Familiar uhn? Of course, it's the same path for us all. You're welcome. I'm welcome.

Generally, back-end developers are believed to be the type that love to solve problems,create impactful alternatives, want to be counted on when the planes are about to crash. They are :

• To learn the foundations and rudiments of databases.
• To master at least a framework based off one of any languages they know.
• To be well versed with the basics of Algorithms & Data Structures.
• To learn software version controls.
• To be conversant and fluent with CLI tools.
• To be entrusted with with the most effective solutions for engineering technology.
• To be fluent and confident verbally.

Amongst the top Back-end Technologies/Frameworks that exist, there are popular ones than the others for every programming language there are based on. Javascript - Node.js > Meteor.js, Express.js, Next.js. Python - Django > Flask, Hug, Bottle, Cherrypy etc. Java - Springs > JSF, ATG, Grails, Struts etc. PHP - Laravel > Laminas, Slim, Symphony etc. Ruby - Ruby on Rails > Sinata, Hanami, Camping etc.

But over the years, there has been misunderstandings as to who is completely back-end and who is full stack indeed. As it has been a common tradition for back-end developers to pick up some front-end languages at a point of development to test & integrate with the front-end architecture during individual programming.

There are honestly no full stack developers. They are either "front-end heavy" or "back-end heavy" full stack developers.

[image.png](cdn.hashnode.com/res/hashnode/image/upload/..

This actually means, either "front end heavy" or "back end heavy" full stack, they still have some "back end" in common and for some, its front-end. They have to create systems that can store previous versions of their codebases in repos accessible sometimes later in the future. Create or integrate APIs ( to communicate ) when and where necessary through clearly defined HTTP methods. Host ready projects on platforms that provide storage and other resources off of local machines over the internet ( cloud ). And many more.

In conclusion, it's obvious we tend to define Back-end developers as developers "behind-the-scenes", which even if true, doesn't completely describe the architecture all back-end developers get to be involved in day-to-day.

Most are usually left with no option but to drift a little to front-end. But still retain their inherent characters as a back-end developer. They play a critical role in the world of projects. They are a gem.

Thanks.

NOTE: This is a disclaimer. Contents therein in this article are all subject of personal views. They are not in anyway intended to appraise a group at the end of discriminating another.