The FullStack Developer Story

The Unlikely Love Affair:
The FullStack Developer Story

Table of Contents
1
2
4
The Infatuation
The Comparison
The Unlikely Affair
5
6
8
New Relationships
Chink in The Armor
Introduction of
Relationship
Councilor
10
12
13
Unlikely Councilor –
The Simulator
Solution
The Perfect One
The Wedding
Invitation
Hello
There.

TABLE OF CONTENT
The
Infatuation
It seems as though everyone in the IT realm today is
infatuated with the full-stack developer dream and there are
valid reasons to it as well. Many IT departments are still
operating with platforms that are cobbled together, loosely
connected, open-source components on the path of
apocalypse.
The long-term viability of these “Frankenstacks” will
need to be addressed in the new year, says Bill Bodin,
CTO of Kony, an enterprise mobility solution provider.
Otherwise, like the monster they’re named after,
these creations will eventually turn on their masters
with disastrous consequences.
Which CTO would ignore these facts? Rightly so, they have
started to get into action. But in this era of AI, Big Data, AR
etcetera, can you find the superhero who can deal with all of
this at the same time? Let’s read on to find out more.
1

TABLE OF CONTENT
FullStack may have been possible in the Web 2.0 era, but a new generation of
space-age organizations is evolving, pushing the limits of virtually every field of
software. From machine learning to predictive push computing to data analytics to
wearable tech and more, it’s becoming virtually impossible for a single developer to
program across the modern full stack. Period.
The
Comparison
Two Sides of the Same Coin
On the contrary, come 2017 and it has become imperative for organizations to get
efficient and turn to a pre-integrated, full-stack mobile development platform that can
take the drudgery and risk of maintaining a mobile back end off their hands. Thereby,
encouraging free thoughts and product evolution across the board.
So there you go, the love story between an organization and the FullStack developer
comes up to dreadful and heartbreaking twist. Read on to find out how this love gets
to the go-live status.
First Rendezvous
During the good old days, a FullStack developer in the pre-mobile, pre-web late
1970s/early 1980s, a single person typically writing a complete software program
end-to-end, and there weren’t many other layers of software between the programmer
and the hardware. Simple love stories did exist. Using assembly language was the
norm for coders trying to squeeze more performance and space out of machines with
8-bit processors and 64-bit RAMs.
2

TABLE OF CONTENT
Second Date
Come 1980s, programming applications quickly evolved into a
team sport with the advent of client/server computing in the
late 1980s and early 1990s, and the wave of Internet
computing in the late 1990s and early 2000s. Long distance
relationships gained popularity. Each new turn of technology
seemed to be so complex that a specialist was often required,
sometimes one for different tiers (e.g. front-ends, databases,
application servers, etc.).
The Rift
Managing websites started to become a skill that included
operating network equipment, cyber security, tweaking Java
virtual machines, and using various database models. Need for
an end-to-end back-end manager was increasing, and the love
story was fading away. The distance started growing and the
need for closure was eminent.
The Break-Up
By the mid-2000s, creating anything on the web-o-sphere -
from simple websites to next-generation SaaS services -
became prohibitively expensive and extremely tedious. The
rising expense was directly correlated to the overhead of
numerous individuals from the various tiers communicating
(and often miscommunicating) with each other.
Bridges were burnt, and hate emails were exchanged, as the
mistake got amplified after every level it advanced to.
As Marc Andreessen pointed out in a recent tweet
storm about burn rates, “More people multiplies
communication overhead exponentially, slows
everything down.”
3

TABLE OF CONTENT
On the other hand, technologies used to create the new
generation of Web 2.0 sites started to become
increasingly straightforward and simplified. Coders
switched from using the complex enterprise Java stack
to the more straightforward LAMP stack (Linux,
Apache, MySQL, PHP/Python/Perl).
New kids on the block
New languages and frameworks such as Django and
Ruby on Rails automated the layer between the website
and the database. Front-end frameworks such as jQuery
helped to pull down boundaries between different
service provider portals.
The Unlikely
Affair
The Perfect Combinations
By the late 2000s, it had become possible for coders to
deliver a website or SaaS application end-to-end,
including a dynamic web server client, server-side
business applet, a scalable database algorithm
implementation, field deployment, and operational
support.
4

TABLE OF CONTENT
This new pedigree of FullStack programmers became the
perfect substitutes, replacing the hordes of coders, analyst to
perform one task end-to-end.
New
Relationships
When projects started to scale up, adding newcomers to the
profile allowed one individual to inculcate that new feature
onto all levels of the application, which ultimately resulted in
better efficiency and faster adaptability of new features across
the board.
The combinations were perfect. CTOs got what they needed
while the FullStack love was not diminishing anytime soon. A
match made in heaven.
5

TABLE OF CONTENT
Chink in The Armor
Come 2017, and technologies on the upcoming horizons were
aplomb and assorted. There was trouble in the affair,
expectations were high albeit rarely met. The perfect
combination started to look bleak and there were issues in the
paradise.
The Break-Up
Dredging on, CTO/CIOs started to seek the sweet spot
between all the skills needed for their business in one person.
Incorporating the perfect combination of
Skillset
Decision Making
Testing
Deployment
Network Security
Leadership
Started to become the point of discord, dissatisfaction &
diversification. The love affair was in peril again and neither
parties were happy about it.
6

TABLE OF CONTENT
Full Stack Developers Then
Full Stack Developers Now
B/E
B/E
UX
SQL
UX
SQL
CSS
JS
CSS
JS
HTML
HTML
7

TABLE OF CONTENT
Introduction of
Relationship
Councilor
Both the parties needed a change, one in their
expectations and one in their deliverables. But the
major threat posed itself imminently. The perfect
FullStack developer was nowhere to be seen. The
news was grim, and no solitude was in tow.
There came along the savior in shining armor.
Simulators The knight in shining armor
In 2017, IT firms are in the midst of a rapid shift to
more complicated technologies that, as in days
gone by, require experts at each level to execute
perfectly. Developing the perfect integration from
Web, to Android iOS and to other platforms is
seen to be the executive task for any and every
organization.
8

TABLE OF CONTENT
Operationally, tending to new object databases such
as MongoDB requires constant attention and
tweaking. Running an application on cloud services
such as Amazon requires knowing the ins-and-outs
of its various services and expertise on how to
failover across regions. Even the venerable web
front-end has evolved into CSS4, JSON and
JavaScript MVC frameworks, such as Angular.js and
Backbone.js.
The relationship councilor proposed a simple framework.
The problem statement
The relationship between CTO/CIOs and developers needs
that one person who can successfully integrate composite
parts of the problem statement at various levels of the
application. Of course, an expert related to the field would be
needed for the Go-Live status but at least the leg work would
be covered.
The Solution
In a way, these level-connecting, bridge-building software
creators, who are likely experts in only one or a couple of
levels of the application, are less full stack developer and
much more full stack disruptor.
The lines are set and the directions are in sight. The
relationship needs mending and it needs the solution now. So
what do you do?
Relax, the Relationship Councilor got you covered.
9

TABLE OF CONTENT
Unlikely Councilor
The Simulator
Solution
As the relationship councilor to host of problems,
remember we suggested Simulators? Yes, an unlikely
problem solver to a humongous list of problems. Here
are some of the key points that encompasses all the
solution in one go.
The Key Learner
The one constant in technology has been change, and
2017 has seen that a lot!
Just as Fullstack's curriculum is constantly being
updated, your organizational need to be able to learn
new technologies throughout your workforce’s
lifecycle will keep changing as well. The key in making
the perfect FullStack developer is to understand where
programming languages are going and how to react,
learn and utilize them effectively.
10

TABLE OF CONTENT
The Charge Taker
As CTOs need FullStack developers to align themselves according to the business
objectives, in turn the developers need teams to implement what they envisage.
This needs leadership, and that is why your organization needs to seek that
simulator which makes this magic happen.
Compounding Knowledge Areas
Great coders understand the context in which they're coding, and this is the one
thing which CTOs should capitalize on the most. Once your workforce is integrated
as a developer, they will be part of a larger organization that has important
priorities like design, product, business strategy, and more. The simulator to look
would be integrating all of this in one package, so that your upcoming workforce
can integrate quickly into new teams and understand how they fit into the product
creation process and their company's overall business model.
11

TABLE OF CONTENT
As a CTO, now you know what to do, how to do it and when to do it. But
which councilor to select to take this relationship forward. Relax, we got
you covered here as well, we won’t leave you high and dry.
As a counselor to all your CTO woes, take Mettl’s simulator suite for
example. Offering time-intensive, efficient solutions to train your workforce
as you need it and when you need it.
Delving in deeper, a FullStack Developer team nowadays is all about
collaboration between developers and operating teams. With this massive
cultural shift, it is important to have shared goals and metrics across the
organization. But what makes this real, day in and day out is when teams
become more productive, more agile and deliver great performance.
The Perfect One
One of the best ways to ensure that every developer, tester, system
engineer is a high performer is to make sure they get early and instant
gratification to their skillset. But ideal situations aside, the go-live status
take ages to operate.
This is exactly where Simulators help.
12

TABLE OF CONTENT
Technology start-ups and heavy-weights alike, need full stack
developers for their versatility! However, as an organization
matures, it needs more and more focused skills.
So we have given it all, and trust us this was a lot of work.
The ultimate decision lies upon you. We can obviously help.
The Wedding
Invitation
GodSpeed.
Save your
FullStack affair.
13

What is Mettl?
Mettl is a Saas based assessment platform that enables
organizations to create customized assessments for use across the
entire employee lifecycle, beginning with pre-hiring screening and
candidate skills assessment, training and development programs for
employees/students, certification exams, contests and more.
TRY FOR FREE
+91-9555114444
contact@mettl.com
Plot 97, Sector 44, Gurgaon,
Haryana, India - 122003
TRUSTED BY