►
From YouTube: Analog Workgroup Meeting May 3, 2022
Description
AWG Meeting with presentation of programmatic analog design by Marko Kusunen and Mirjana Videnovic-Misic
A
A
B
A
A
F
F
D
D
F
I
A
D
D
A
I
think
I
think
you're
getting
to
that
point
and,
like
you
know,
like
I
said
I
was
surprised,
pleasantly
surprised.
You
know
at
the
interest
that
I
got
on
linkedin.
You
know
which
thanks
marco
for
suggesting
you
know
trying
to
get
some
additional
socialization
for
this.
So
I
think
that
I
think
that's
great.
A
A
You
know,
including
including
different
collaboration,
project
ideas
and
also
looking
at
improving
automation
in
the
analog
space,
which
of
course,
is
always
a
challenging
arena,
and
today
we're
gonna
have
an
update
on
programmatic,
analog,
ic
design
that
marco
cassinin
and
mariana
is
gonna
update
us
a
lot
of
most
is
gonna
update
us
on
today
and
the
work
that
they
have
been
championing
and
helped
to
try
to
move
the
community
forward
on
that
area.
So
with
that,
why
don't
I
turn
over
to
you,
marco
and
mariana.
D
G
G
G
There
is
one
main
project
under
this
group,
which
is
called
virtual,
so
template,
and
there
is
also
automatic,
continuous
integration,
build
of
a
documentation
of
this
project
containing
online
documentation
of
all
the
sub
modules
or
the
main
sub
modules
in
it,
and
I
briefly
show
you
the
documentation.
This
is
automatically
built
every
time
we
push
to
the
latest
development
branch,
so
it
has
certain
some
introduction
introductory
test
text
and
describes
all
the
modules
what
we
have
there.
G
So
as
this
is
open
source
project,
what
we
decided
with
miriana
at
quite
early
phase
is
that
we
should
have
a
kind
of
well-structured
development
plan
or
release
schedule
for
this.
So
I
wrote
a
brief
developer's
guide
for
this
environment
and
we
decided
that
we
have
do
two
release
dates
per
year,
fourth
or
fourth
and
tenth
of
10th.
They
are
easy
to
remember
and
then
some
instructions
about
branching
and
how
to
do
merge,
requests
for
for
these
releases
and
so
forth.
But
I
think
this
is
kind
of
the
backbone
of
the
development.
G
So
if
anyone
of
you
tries
the
environment,
find
something
that
needs
to
be
improved,
feel
free
to
file
in
a
merge
request,
and
we
or
someone
will
check
that
out
and
and
if
it's
okay,
we
will
merge
it.
If,
if
there
are
some
feedback,
then
we
will
provide
the
feedback
and
eventually
we
will
converse
to
the
better
environment.
G
G
G
The
aim
of
this
template
is
that
we
provide
provide
a
set
of
shell
scripts
that
you
can
easily
use
to
take
this
environment
into
use.
We
have
pip
installation
script
for
to
install
all
the
python
dependencies.
You
need
to
run
this
this
environment.
We
have
idiot
sub
modules
that
initializes
all
the
github
modules
in
this
project.
So
you
don't
need
to
worry
about
what
to
initialize
and
how
it
it
will
do
it
for
you.
G
We
have
readme
file,
of
course,
licensing,
and
then
we
have
two
source
me
scripts.
One
is
for
c
shell
and
derivatives,
and
one
is
for
bash,
and
basically
this
source
will
script.
Miriana
will
later
on,
show
you
how
it
works,
but
it
forces
you
to
set
things
up
correctly.
So
basically
you
start
in
all
of
it.
G
Let's
just
briefly
show
what
it
has.
So
it
has
a
configure
script.
You
run
dodge
class
configure
and
make
gen,
and
it
will
generate
the
layout
and
schematic
of
this
inverter
for
you.
So
it's
a
really
a
minimum
minimum
working
example
that
just
shows
that
your
environment
has
been
set
up
correctly
and
it
works,
and
you
can
start
extending
this
inverted
generator
or
you
can
generate.
G
A
G
G
G
G
G
If
you,
if
you
need
to
get
updates
for
those
those
setting
files,
then
we
have
back
to
framework
that
I
said
already,
it's
just
a
fork
from
using
berkeley
back
to
back
to
templates.
This
is
basically
a
sub
module
that
contains
analog
base
and
certain
examples,
also
from
ford
from
a
music
virtual
github
site
and
back
to
technology
template.
This
is
new
production.
G
It's
a
collection
of
virtual
sorry,
abstract,
abstract,
python
classes.
That
tells
you
all
the
properties
that
are
needed
to
define
pros
as
parameters
for
this
environment.
So
let
me
go
back
to
this
release
candidate,
so
I
can
show
you
the
latest
version
of
this.
So
if
I
go
through
this
back
to
technology
templates,
it
contains.
G
Okay,
if
I
go
back
first
so
basically,
this
template
is
something
that
you
can
fork
and
start
building
your
technology
definition
on
this
template.
There
are
instructions
how
to
do
this,
so
if
I
show
you
the
main
class,
it
tells
you
that
okay,
to
use
this
as
a
back
technology
definition
class
comment
the
following
lines
and
then
uncomment
the
following
lines
and
so
forth.
So
you
can
convert
that
this
from
actual
template
to
actual
definition
and
then
what
you
then
need
to
do.
G
You
need
to
figure
out
the
process
parameters
and
those
are
collected
mainly
these
sub
modules,
layer
parameters
in
most
parameters,
resistant
parameters
and
via
parameters,
and
these
are
just
abstract
properties
that
define
the
properties
that
we
use
in
the
technology.
So,
as
these
are
now
properties,
instead
of
like
entries
in
a
yaml
file,
we
can
use
dog
strings
to
document
the
purpose
of
these
properties,
which
is
relatively
handy.
Unfortunately,
for
many
of
these
parameters,
we
actually
don't
know
their
actual
function
or
what
how
they
really
affect
your
layout.
Some
of
them
are
clear.
G
G
So
you
can
also
use
that
as
a
example.
How
how
to
set
is
to
set
this
up.
But
the
reason
why
we
use
this
is
that
when
we
intron
you
introduce
a
new
parameter,
we
can
introduce
it
as
an
abstract
property
and
then
your
actual
technology
definition
inherits
this
class,
this
template
class
and
because
this
abstract
method,
it
forces
you
to
redefine
this.
So
in
your
process,
definition,
which
I
show
next,
you
must
define
values
for
these
parameters,
and
so
I
hope
that
the
idea
of
this
technology
template
is
now
kind
of
clear,
clear.
G
G
It
has
a
property
process
config
that
has
all
these
process
process
variables
or
process
parameters
store
stored.
Indeed,
and
values
of
those
parameters
are
defined,
for
example,
in
this
layer
parameters,
the
pi
which
inherits
the
layer
parameters
template.
So
this
template
tells
what
you
need
to
define,
and
here
we
have
defined
all
the
parameters
that
we
must
overload
in
this
class.
So,
for
example,
this
says
that
the
name
of
the
technology
library
is
sirius
ffmpt
layout
units
are
one
micron
layout
resolution
is
one
thousandth
of
micron,
meaning
one
nanometer
somewhere
yeah,
okay,.
A
A
Understanding
required
here,
of
course,
is
being
able.
You
know,
basically
understanding
how
to
do
abstract
based
programming
or
you
know,
in
other
words,
class-based
programming
like
you
know
what
was
originally
seen
in
c,
plus
plus
or
an
objective
c.
You
know
years
back.
I
just
was
curious
relative
to
what
are
you
guys,
thoughts
in
terms
of
you
know,
layout
or
circuit
design,
engineers,
understanding
this
and
taking
it
forward?
A
G
G
I
would
say
that
if
you
think
of
larger
bigger
organization
where
your
server
designers
remain
as
certain
designers,
they
still
need
to
know
the
basics
of
object-oriented
programming
configuring.
This
framework,
configuring
these
processes
in
a
larger
organization.
I
would
leave
those
for
like
technology,
bdk
supper
personal
personnel,
which
should
be
relatively
fluent
with
python,
but
it's.
B
G
It's
it's
possible
to
write
the
generators
without
advanced
knowledge
in
programming.
It's
also
possible
to
maintain
these
processes
without
any,
but
very
special
information
about
programming.
Just
basic
concepts
are
enough,
but
if
you
are
strictly
in
analog
design
strictly
schematic
entry
strictly
in
manual
layout,
there
is
certain
learning
curve
ahead.
J
Okay,
yeah,
may
I
comment
here
somewhat.
Yes,
what
I've
seen
is
that
young
design
engineers
circuit
designers,
they
are
open
for
doing
this,
not
all
of
them,
but
but
many
or
some
of
them.
What
is
more,
tricky
is
to
convince
layout
people
because
they
like
to
do
graphic,
use,
graphic
user
interfaces,
and
it's
it's
obvious
that
doing
layout.
This
is
a
very
graphical
thing,
so
these
people
are
are
more
reluctant
to
switch
and
there's
a
good
reason.
D
J
D
And
you
know
where
automation,
reuse
goes
hand
in
hand
with
ic
design,
and
there
is
no
question
about
it.
So
how
can
we
do
it
only
by
you
know
putting
something
to
get
and
making
this
onboarding
process
for
people
who
wants
to
join,
and
you
know
for
the
new
curriculum
etc,
making
it
easier
and,
like
kristoff
said.
D
I
also
seen
you
know
in
our
organization
very
experienced
designers,
they're,
very
reluctant.
That
is
like
mild
way
to
say,
but
I
believe
that
you
know
the
young
students
just
went
from
the
university.
They
are
much
more
kind
of
susceptible
to
new
methods
and
and
basically
they
should
be
at
this
stage.
Maybe
our
target
group
yeah
thanks.
A
I
appreciate
both
of
the
comments
now
I
agree
with
that.
I
was
just.
I
was
not
trying
to
start
an
insurrection
here.
I
guess
with
my
question,
but
mostly
just
you
know,
basically
just
based
on
my
own
experience.
I
worked
with
analog
folks
over
the
years
and
you
know
I
think,
in
terms
of
you
know
as
boris,
and
I
have
chatted
many
and
I've
chatted.
A
You
know
chatting
with
borah
as
well
and
others
right
that
we
certainly
need
to
look
at
improving
the
overall
productivity
and
reproducibility
of
results,
and
automation
certainly
helps
doing
that
and
also
aids
in
terms
of
technology.
Migration
as
well-
and
I
think
embracing
more
modern
concepts
in
terms
of
how
we
can
do
things
in
design
is,
is
important
and
it
also
will
help
help
us
attract
newer
students
right
and
enabling
different
ways
of
thinking.
So
thank
you.
D
F
G
Yes,
this
is
based
on
back
two,
which
is
like
pre-predecessor
of
factory,
and
the
reason
we're
using
this
is
that
with
both
me
and
miriam,
we
have
experience
on
using
back
too,
but
more
experience
of
using
back
too,
and
I
to
my
understanding
battery
is
actually
not
as
open
as
this
is
so
I
would
say
that
yeah.
This
is
it's
easier
to
in
the
future.
If
seem
feasible,
it's
easier
to
migrate
from
this
to
back
three
but
start
developing
the
needed
needed
skills
and
start
cleaning
up
this
environment
with
back
too.
D
So
I
think
then
you
can
correct
me,
but
you
know
when
I
was
comparing.
I
never
worked
with
back
three.
There
are
like
a
couple
differences.
The
major
is
that
back
three
does
not
use,
let's
say
skill
and,
like
let's
say
skill
procedures,
to
execute
something
you
know
in
vertozo,
but
does
it
directly
under
the
hood,
with
c
plus,
plus,
okay
and.
F
F
D
And
so
that,
and
that
exactly
part
cannot
be
because
of
this.
Si2
limitations
cannot
be,
let's
say,
open
source
source
cannot
be
shared,
and
I
think
you
know
that
is
the
major
obstacle
of
spreading.
You
know
back
three
in
performance
but
boris,
saying
like
it's
10
times,
you
know
fasting
simulation,
which
is
expected
and
execution
which
is
also
expected
and-
and
you
know,
and
they
kind
of
figured
out
that
back
to
has
a
limitation
when
they
have
been
designing
bigger
socs.
But
you
know,
maybe
then
you
can
add
something.
K
My
audio
is
not
working.
Can
you
guys
hear
me
now?
Yes,
yeah
what
I
said
it
is
more
or
less
right,
the
at
least
as
far
as
why
you
wouldn't
want
to
make
that
upgrade.
Is
it
primarily
jumps
from
python
code
that
manipulates
virtuoso
to
python
code
that
manipulates,
open
access
and
spectre
directly
I'd,
say
that's
half
of
like
the
major
goals
of
the
change.
K
The
other
half
is
kind
of
production
of
all
of
the
other
stuff
that
goes
with
the
analog
ip,
so
production
of
verilog
models,
production
of
timing
models
and
the
like-
and
I
would
say
much
of
the
work-
went
into
that
and
yeah
a
lot
of
the
shifts
to
directly
using
that
oa
c
plus
plus
api
was
based
on
having
you
know
sufficiently
large
generators
that
going
through
that
python.
This
skill
loop
really
did
turn
into
like
many
hour
or
even
many
day
run
times.
D
Yeah,
if
I
may
add
just
one
more
thing,
you
know,
for
instance,
in
back
two
we
use
analog
base
and
there
is
digital
base,
which
is
kind
of
you
know
additional
methods
a
bit.
You
know
more
flexibility,
but
if
I
remember
correctly,
baxley
uses
mass
space,
so
it
was
like
iteration
and
and
change
you
know,
and
they
in
my
opinion
they
figure
it
out
and
as
they
go,
they
change.
K
K
K
I
think
it
really
does
boil
down
to
just
what
is
the
mental
model
and
what
is
kind
of
the
interface?
What
are
the
ideas
that
the
library
injects
to
help
someone?
You
know
program
one
of
these
layouts
and
there
are
a
lot
of
the
opposite.
How
detailed
there
are
they
are
versus
how
accessible
they
are,
and
I
think
this
has
generally
drawn
a
very
detailed
line
that
you
know
it's
had.
A
pretty
niche
set
of
people
be
able
to
latch
on
to.
G
G
We
have
kept
simulations
and
even
drc
and
lvs
checking
out
of
the
scope
at
the
moment.
So
we
know
that
in
every
organization
you
want
to
do
it
in
your
own
way.
So
what
we
provide
is
the
way
to
programmatically
control,
your
schematics
and
layouts.
If
you
want
to
simulate
them,
you
can
generate,
of
course,
the
netlist
and
positive
simulation
environment,
but
it's
kind
of
up
to
you
how
you
want
to
do
it.
For
example,
in
other
universities,
we
use
something
that
is
called
the
sidekick,
which
is
a
python
interface
for
various
analog
simulations.
G
G
G
So
the
idea
is
that
every
generator
is
a
git
sub
module
inside
this
project.
This
is
just
a
project
template,
but
if
you
fork
this
and
push
it
to
the
other
repository
pocket
becomes
your
project
and
you
can
add
generators
as
a
git
sub
module,
so
they
will
believe
they
will
live
here.
In
parallel
with
this
university
and
in
this
main
project
we
have
a
configure
file.
G
G
If
I
want
to
run
only
one
generator,
I
can
give
make
gen
inverted
gen
and
it
will
run
the
generator
also
for
only
for
inverted
j,
so
this
is
kind
of
a
top
level
control
of
generators.
I
don't
take
at
this
point
any
any
stand
on
how
you
pass
the
parameters
to
those
generators
you
can
down
that
in.
You
can
do
that
in
various
ways.
G
G
When
you
run
the
configure,
it
will
create
a
make
file
and
then,
from
that
make
file,
you
can
write,
run,
make
gen
and
it
will
run
the
generator,
and
this
idea
of
using
the
same
structure
over
and
over
is
copied
from
from
kind
of
linux
environments.
Everyone
who
has
installed
linux
programs
from
source.
You
can
do
that
without
reading,
even
the
readme,
because,
most
often
it
goes
that
you
write
configure
it,
make
it
make
install
and
it
will
install
the
software
for
you.
G
If
that
doesn't
work,
then
you
need
to
read
actually
the
readme.
So
if
you
keep
the
structure
constant
for
all
certain
policy,
you
don't
need
to
document
it.
There
is
no
variation
if
the
generator
runs
in
the
same
way
and
also
the
structure
of
the
generator
all
of
the
generator
is
to
say
we
have
templates.
G
So
the
name
of
this
circuit
that
we
are
generating
is
inverter.
The
name
of
this
generator
is
inverted
gen
and
it
has
a
directory
with
the
same
name.
So
all
the
python
leads
here
and
the
templates
schematic
templates
for
this
inverter
they
live
here
called
inverted
templates.
If
you
have
op
amp,
this
would
be
op
amp
templates.
G
G
You
can,
if
you
want,
create
a
method
so
that
you
can
pass
these
properties,
for
example,
from
the
yaml
file,
or
you
can
use
this
inverter
inside
another
generator
and
pass
these
parameters
from
the
higher
level
or
higher
level
of
your
design
to
the
lower
level.
So
you
can
automate
this
parameter
fast
as
you
wish.
This
is
just
python.
G
We
can,
of
course,
in
the
further
development,
also
figure
out
ways
how
to
automate
this
parameter
provocation
throughout
the
hierarchy,
but
what
we
wanted
is
an
environment
where
you
can
use
doc
strings
to
document
your
actual
parameters
and
what
they
do
and
in
every
generator.
You
have
this
main
guard
which
actually
defines
what
you
do
so
the
generation
process
has
now
been
condensed
to
the
three
lines
of
god.
G
So
basically,
we
created
a
class
called
back
design
and
it
has
a
init
method
on
certain
methods
that
are
executed
when
you
actually
instantiate
this
generator
and
basically
what
it
does.
It
imports
the
schematic
from
the
schematic
templates
to
virtue,
also
and
back
then
imports
certain
python
definition
of
your
schematic
to
certain
locations.
So
it
replaces
that
important,
empty
file
with
your
actual
schematic
generator
so
that
you
can
run
it
from
your
generated
location,
but
this
is
kind
of
a
mess
under
the
hood.
G
G
D
G
Questions,
I
also
I
I
may
apologize
that
I
know
that
it's
not
the
most
interesting
thing
to
go
through
a
hierarchy
of
a
project
that
has
git
sub
modules,
but
anyway,
I
think
this
is
the
easiest
way
to
explain
what
is
there
and
how
they
are
organized
and
how
what
is
their
relations
and
so
forth.
So
then,
the
next
step,
if
you
want
to
try
this,
is
just
to
pull
on
pull
and
try
to
run
it
in
your
organization's
environment.
A
G
C
F
G
This
is
a
good
question.
What
I
did
in
our
university.
I've
tested
this
with
two
different
process
configurations
and
you
pull
in
this
template.
You
do
the
trick
for
the
source
me
file
so
that
it
takes
your
virtual
environment
into
use.
That's
of
course,
what
organizes
specific,
and
then
you
replace
this
back
technology
definition
with
the
back
technology
definition
that
you
want
to
use
and
the
generator
runs
without
any
problems.
So.
F
G
That
is
a
good
question.
Currently
you
need
to
define
all
these
parameters
manually
or
let's
say
I
don't.
I
don't
have
any
way
to
instruct
you
how
to
figure
out
this
number.
I
can
just
tell
you
what
it
means
because
of
the
like
mds
of
the
processes.
If
you
want
to
set
this
up,
let's
say
tsmc28,
I
probably
have
the
setup
for
the
process.
I
can't
give
it
to
you
got
it.
I
can't.
I
can't
tell
you
any
detail
about
that
process.
F
Okay,
so
another
question,
so
let's
say:
let's
assume
I
have
a
platform
where
I
have
all
these
setup
files
for
different
technologies.
So
then,
if
I
port
an
inverter,
it's
gonna
follow
up
the
the
same
rules
or
like.
Is
it
gonna,
have
a
standard,
sl
dimension
or
is
it
just
gonna
be
an
inverter
functionality.
G
It
will
it
will
follow
the
rules
given
in
these
technology
definition
files,
all
the
dimensions
given
in
the
in
the
inverted
gen
generator.
They
are
relative,
so
basically
we
we
give
them
as
multiples
of
routing
reach,
which
is
process
dependent
or
multiples
of
minimum
channel
length,
which
is
also
like
just.
D
D
Okay,
so
start
from
this
return
template,
I
don't
have,
let's
say,
a
flexible
working
environment.
So
basically
my
it
provided
me
something
like
you
know
this
terminal
where
I
can
just
clone.
You
know.
So.
Basically,
what
am
I
I'm
gonna
do?
Is
you
know?
I'm
just
gonna
get
this
return
template
and
then
you
know
pop
it
in.
I
I
D
D
I
D
D
D
D
G
I
G
D
D
I
E
F
F
I
D
I
D
D
I
I
E
A
D
So
basically,
you
know
before
me
executing
this
before
yeah,
it's
ending,
finished,
implemented
schematic.
So
before
me
executing
all
this
yeah,
you
just
had
inverted
templates,
and
that
is
basically
what
marco
said
it
is
in
this
specific.
When
you
see
you
know
you
have
these
inverter
templates,
but
basically
the
the
core
of
the
generator,
which
means
layout
description
in
python
and
schematic
description
in
python
and
sizing.
D
D
I
D
What
dummies
I
mean
very
typical
and
same
as
for
for
back
and
symbol,
also
which
you
can
see
here
so
at
this
point
you
know
you
can
clearly
see
we
demonstrated
the
basic
functionality
of
bag.
Like
marco
said,
we
didn't
want
to
go
into
drc
lbs,
because
every
every
let's
say
institution
has
its
own
customization.
D
D
So
marco
already
explained
so
the
idea
you
know
the
next
idea
will
be,
let's
say,
layer,
parameters.
What
we
give
to
mosaic
group
members
is
basically
kind
of
a
homework
so
that
they
clone,
execute
and
come
up.
You
know
with
the
problems,
but
also
to
check
these
specific
parameters
and
say
that
you
know
if
they
have
something
you
have
some
better
description
and
mark.
We
should
be
telling
them
to
do
that
into
and
back
to.
I
think
technology
definite
technology
templates,
because
the
documentation
is
generated
from
these
specific.
D
Let's
say
this
is
specific
files,
so
that
is
one
thing
that
I
believe
we
need
to
do
kind
of
to
make
if
we
cannot
share,
share
the
information
technology,
information
specific
and
protect
it,
what
we
can
share
is
description
such
that
people
can
easier,
find
and
debug.
You
know
find
information
in
the
technology
that
are
using.
There
is
also
a
silicon,
austria
labs.
We
have
some
work
going
on
about
generic
technology,
where
these
data
should
be
in
future
kind
of
semi-automa,
semiautomatic
or
optimized.
D
You
know
the
input
will
be
optimized,
but
that
is
not
the
current
status.
What
I
wanted
to
mention
here
also
is
at
the
moment,
if
you
see
here,
we
just
have
let's
say
vertegen,
and
it
is
basically
just
one
of
hopefully
many
generators
that
we
will
have
so
at
the
moment
excel.
I'm
I'm
finishing.
Basically,
I
cleaned
these
templates
and
adapted
for
tsmc
28
nanometer
technology.
D
My
goal
is
basically
to
change
the
project,
adapt
the
project,
basically
more
or
less
everything
is
set.
I
need
to
change
us
back
to
technology
definition
and
then
I
will
share
it
with
people.
Institutions
that
we
have
nda
with
bwc
is
one
of
them
effica
and
feel
like
it's
one
of
them
and
athenian
is
also
one
of
them.
After
that,
my
plan
is
because
we
had
a
tape
out.
D
F
D
D
D
F
A
D
A
D
D
You
know
some
people,
you
might
also
know-
or
you
know
they-
they
are,
let's
say
they're
here
as
a
more
as
a
guest
to
observe
the
situation,
but
what
I'm
also
planning
from
our
sides?
We,
for
instance
yesterday
we
have
two
new
members
that
next
to
joining
next
month,
to
use
basically
this
vertozo
template
as
as
as
the
ground
where
we
can.
Basically,
you
know
as
the
initial
steps
initial,
where
many
people
who
go
in
this
arena
can
make
initial
steps
together,
because
it
is,
you
can
see,
plug
and
play.
D
If
you
don't
miss
the
branch.
It
is
very
easy
to
execute
sorry,
it
is
very
easy
to
execute
and
it's
self-explanatory.
It
has
quite
good
documentation.
The
technology
information
will
be.
You
know
much
much
clearer
that
this
the
current
situation
will
back
to
and
it
will
have
more
available
generators.
D
You
know
to
plug
it
with,
and
it
will
give
this
like.
You
know
the
strategy,
how
to
do
hierarchical
approach,
so
what
I'm
seeing
is
basic
things
definitely
will
be
solved
and
in
july
we're
we're
putting
one
more
colleague,
one
of
these
two
that
I
mentioned
he
will
be
working
on
the
small
layout
generators
because,
in
my
opinion,
it
is
extremely
important
to
raise
the
level
of
abstraction
in
layout.
You
know,
without
that
people
will
be
very
much
reluctant
to
script.