Debunking Full Stack Role

Over the years, IT roles have evolved accordingly to technological trends playing catch up at many junctions. As times passed, I have tried different types of roles in various forms of organisations. However, we have kindly seek to divide domain into project manager, business analyst, developer and tester. With emergence of Cloud technologies and Agile, these roles are gradually merging again into a role called Full Stack.

What is Full Stack role?

Full Stack role is nothing new but a rebranding of an old role I used to call Software Engineer! In fact, I would say that Software Engineer can do much more. That will be a debate in another article. To understand Full Stack, we need to delve into a bit of history. Back in Open Source days, a Stack is refers as a set of systems that is required to run the application. The most famous stack will be LAMP (Linux Apache MySQL PHP) in the Dot Com age. Basically, full stack role will involve a mastery of the solution stack e.g. LAMP stack.

3 Myths to Full Stack Role

For those who are in the Dot Com era, we will be de facto Full Stack! This also applies to techies who have worked in Startup. After all, you are expected to setup everything from end to end from Servers to Applications.

Myth 1: Full Stack is a specialised role.

As opposed, Full Stack role involves knowledge to set up end to end solution. This is actually a generalist role to configure the system architecture which is getting common in Cloud Technologies. Only then, the deployed application can be transferred to the Subject Matter Expert (SME) for engagement with users.

Myth 2: Full Stack role is difficult to find.

Once you understand the fundamental of Full Stack Role, you will realise Full Stack has existed in many parts of existing IT roles. This role can be easily found in Agile team or Startups as they are expected to handle a variety of solutions stacks. In many cases, SME or Solution Architect can often act as Full Stack developer.

Myth 3: Full Stack is a competitive advantage.

Sadly, coming from the world of Open Source, it is quite depressing to see the misunderstanding of Full Stack role. One may feel that having Full Stack is a competitive advantage. In fact, this is the opposite. Full Stack knowledge will become a commodity because most of Cloud Technologies offer templates with quick deployment methods that can be setup within hours. We shall see a decrease in this role as Cloud technologies mature. On the contrary, there will be a continued focus on SME and specialisation of domain knowledge. Let us not be sidetrack and go back to being a generalist just because it has a nice ring in “Full Stack”.

Jack of all trades, master of none

Quote

2 thoughts on “Debunking Full Stack Role

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s