►
Description
This is the first update from the low-code/no-code incubation engineering group.
Link to the issue: https://gitlab.com/gitlab-org/incubation-engineering/no-code-low-code/meta/-/issues/22
0:00 Overview
0:30 Self intro
1:49 Guiding principles
2:29 Assumptions
4:47 The double diamond process
6:15 Progress - Plan stage
8:47 Progress - Verify stage
9:51 Progress - Create stage
12:02 Appsmith demo
A
A
A
And
these
updates
summarize
on
myself
so
far
since
this
is
my
first
video,
let
me
perhaps
introduce
myself
to
begin
with.
My
name
is
Cal
I'm
based
in
Melbourne
Australia,
so
throughout
my
career,
I
had
the
opportunity
to
wear.
A
number
of
hats
have
been
a
freelance
developer,
while
starting
at
Uni
and
later
on,
did
some
research
on
machine
learning.
A
I
then
joined
the
industry,
and
it's
been
a
couple
of
years
as
an
analyst
programmer
in
the
insurance
industry,
building
waiting
engines,
I
didn't
fall
in
love
with
open
source
community
and
started
building
web
apps,
mostly
on
moving
on
Rails
I
co-founded.
Some
startups
mostly
failed,
but
one
day
survived
and
after
over
10
years,
and
that's
how
this
is
for
sale
Polo.
A
So,
first
I'd
like
to
begin
my
exploration
and
a
couple
of
guiding
principles,
and
hopefully
this
principle
not
only
can
Inspire
myself,
but
also
can
help
others
to
relate
to
besides.
I
also
believe
keeping
the
North
Star
in
mind
can
prevent
myself
from
falling
off
the
cliff
while
navigating
through
the
product
development
jungle.
So
the
two
guiding
principles
is
number
one.
A
The
kid
Labs
mission,
that
is
to
empower
everyone
to
contribute
number
two
I,
think,
is
also
important
that
the
products
built
back
your
lab
should
really
embrace
the
company's
value,
which
is
credit
with
the
help
of
the
principles,
and,
let's
maybe
talk
about
the
assumption
that
we
made
so
far,
I
call
them
three
pillar
assumptions
number
one
being
the
alignment
toward
the
other
company's
mission.
That
I
just
mentioned.
A
I
I,
might
just
quote
a
really
well
articulated
statement
from
the
the
the
local
local
Direction
page
that
owned
by
the
the
create
group
that
is
well.
It's
important
that
gitlab
is
able
to
serve
all
application
development
teams,
as
well
as
citizen
developers,
as
this
trend
continued
to
grow
and
as
such,
we
need
to
be
full
thinking
about
how
to
provide
a
good
experience
for
local
and
no
code
developers
inside
the
of
the
GitHub.
A
So,
secondly,
like
if
you're
talking
about
aligning
with
lab's
core
value,
I
believe
that
the
local
and
no
code
can
really
help
our
customers
to
reduce
the
technical
overhead,
improve
efficiency
in
almost
all
the
devops
lifecycle
stages.
In
addition
to
create,
for
example,
a
no-code
workflow
Builder
can
help
scrum
Master
to
customize
their
plan
and
delivery
process
by
introducing
rules
to
automatic
labeling,
State
transition
notification
and
other
parts
of
the
day-to-day
product
management.
A
A
Lastly,
why
don't
we
leverage
kill
that
strings?
The
number
of
challenging
the
current
state
of
the
the
local
offering,
for
example,
Version
Control
and
the
related
collaborations,
the
verification
which
is
about
the
automated
testing
security
and
compliance?
On
the
other
hand,
gitlab
has
a
great
feature
that
well
a
set
of
great
features
that
deal
exactly
those
challenges
in
the
depth
of
life
cycle.
So
this
is
obviously
an
alternative
for
GitHub
to
address
some
of
those
local
local
pinpoints
and
become
a
prominent
contender
in
the
in
this
new
market.
A
Now
that
we
have
to
talk
about
the
guiding
principle
and
the
early
assumptions,
let's
plan
our
journey
to
bring
local
and
local
together
when
I
say
it's
a
journey,
it's
actually
more
of
Adventure
than
for
the
follow-up
challenges
and
very
easy
to
get
lost
along
the
way
to
make
it
that
and
maximize
the
return
of
the
investment.
We
are
using
a
Double
Diamond
design
process
for
those
who
are
not
super
familiar
with
the
concept.
The
Double
Diamond
model
breaks
down
the
design
process
into
two
parts
that
focus
on
the
problem
and
solution
space
separately.
A
In
addition,
for
each
stage,
the
diamond
shape
incurred
the
Divergence
thinking
to
begin
the
discovery
and
then
a
convergent
thinking
to
take
Focus
action.
But
if
you
squint
your
eyes
and
turn
your
head
upside
down,
you
might
realize
something
interesting
that
I
also
discovered
so
far
enough.
My
very
first
task
is
actually
reverse
engineer
via
the
Double
Diamond
by
taking
the
local
no
code
as
a
solution
to
begin
with.
A
I
really
need
to
find
a
problem
that
makes
most
sense
to
give
up
customer
that
feel
like
casmas.
That
can
be
their
ways
by
local.
No
code
then
narrow
it
down
from
there.
Also
I
gotta
say
like
any
other
methodology,
and
Double
Diamond
has
its
limitation,
especially
in
its
waterfall
of
linear
nature.
However,
I
believe
the
unique
setup
of
the
SCT
group
here
at
the
lab
has
a
potential
fix
for
that
and
I'll
get
to
that
shortly.
A
So
that's
how
well
progress.
There
are
a
number
of
opportunities
that
I've
started
exploring
and
let
me
walk
you
through
them
stage
by
stage
the
way
it
comes
to
the
plan
stage.
We
know
that
I
get
lab
teams,
rely
on
the
issues
and
imrs
to
facilitate
async
collaboration
and
the
workflow
that
built
around
the
issue:
status,
labels
and
transitions
between
them.
There
is
also
a
work
stream
that
is
developing
the
this
generalized
work
item
model
to
provide
more
flexibility
to
our
customers.
A
I
will
say:
that's
all
well
and
good.
Until
complexity,
crimson
and
the
menu
intervention
becomes
repetitive
and
start
to
take
a
toll
in
the
current
local
landscape.
There
is
a
wildly
popular
category
of
publication
that
does
this
so
well,
so
you
may
have
heard
about
zap
here:
Mercado
Trail
I
have
TTT.
A
If
you
have
used
them
and
they
actually
evolved,
Way
Beyond
just
not
taking
tools,
they
become
the
central
hubs
for
distributed
teams
to
organize
wikius
and
collaborate
on
product
management
and
okrs,
and
basically
many
other
kind
of
documents-centric
use
cases
that
are
kind
of
applicable
and
fits
well
with
this.
With
these
two
apps
I've
only
been
scratching
the
surface
on
this
direction
so
far,
but
I
do
wish
to
invest
be
more
time
in
the
coming
weeks.
A
Instead
of
crafting
the
Yama
by
hand,
we
also
have
a
tab
to
visualize
the
complete
pipelines,
I'm
aware
that
the
verified
team
is
working
on
a
a
new
project
that
called
pipeline
components
that
basically
encapsulate
the
reusable
functionality
and
and
with
that,
we
can
also
encourage
Community
contribution
similar
to
the
previous
Dimension
workflow
automation.
I
personally
think
there
is
a
there's,
a
good
opportunity
to
consolidate
effort
into
a
generic
State
machine
construct
that
is
able
to
unify
the
automated
workflows
for
both
plan
and
verify.
A
A
So,
finally,
when
it
comes
to
the
create
stage,
think
we
we
have
alternative
here
to
perhaps
integrate
with
some
of
the
open
source,
low
code,
development
platforms.
This
is
closely
aligned
with
the
original
Direction
set
by
Sarah
Warner.
The
group
here
from
create
and
from
her
I
learned
that
Ghana
predicts
by
2024,
a
75
of
the
software
solution
will
be
delivered
with
some
help
of
the
local
twos.
While
developers
appreciate
the
efficiency
gain.
There
are
also
some
concerns.
A
I
remember
earlier
that
I
mentioned
the
rigid
linear
process
in
Double
Diamond.
That
has
a
lot
of
focus
on
The,
Upfront
analysis
and
the
press,
the
SCT
group,
with
this
new
unique
setup.
It
has
opportunity
to
tackle
that
problem
and
well
as
engineer
we're
unloading.
The
information
through
Reading
and
chatting
I
reckon
I
can
also
invest
some
time
to
experiment
some
of
the
ideas
just
to
to
fast
iterate
and
get
some
value
feedbacks.
A
So
I
spent
a
couple
of
days
to
get
an
open
source
local
platforms
called
appsmith
integrated,
whiskey
lab.
The
idea
is
to
allow
gitlab
users
to
bootstrap
a
self-managed
local
Dev
environment
within
a
couple
clicks.
It's
not
quite
a
couple
of
clicks
yet
but
close
enough
for
a
demo
so
to
bootstrap
a
self-match
local
platform
from
within
gilab.
One
of
the
entry
point
could
be
the
the
project
template.
A
A
A
So
what
it's
doing
behind
this
thing
is
that
gitlab
agent
is
is
installed
on
the
class
from
the
command,
and
it
has
the
token
it
knows
which
version
of
the
agent
to
install
and
use
a
token
to
authenticate
back
to
the
applicable
app
server,
and
it
also
knows
which
product
that
is
responsible
for
and
able
to
read
the
product.
Configuration
and
I'll
show
you
it's
basically
a
set
of.
A
A
The
click
on
this
workload
and
here
is
the
exposed
the
service
ID.
There's
a
public
IP
address
on
that,
and
that
takes
me
to
the
a
brand
new
instance.
That's
running
on
your
kubernet
cluster.
So,
instead
of
building
from
scratch,
let
me
perhaps
quickly
show
you
a
demo
app
that
folks
from
their
templates.
Hopefully
that
gives
you
a
rough
idea
of
what
kind
of
app
can
be
built
by
such
a
local
platform.
A
A
A
A
You
can
see
they
support
a
lot
of
widgets
I,
think
it's
like
40
of
them,
so
I,
unfortunately,
I
wouldn't
have
enough
time
to
go
through
all
the
all
the
bells
and
whistles
on
this
app,
but
I
think
for
the
for
the
given
time,
I
will
just
wrap
up
my
update
today,
I've
mentioned
a
few
directions.
I
would
really
like
to
explore
a
little
bit
more,
hopefully
conduct
some
field
research
with
customers,
while
waiting
for
the
feedbacks.
Thank
you
very
much
for
your
time.