►
From YouTube: Jakarta Tech Talk - The five skills you must master to be outstanding as a software engineer
Description
An area of technology has been growing exponentially and bringing with it several opportunities and specializations. Among these thousands of options, we have software engineering and architecture. However, with so much content and easy access to happiness, how would be the best way to reach the goal that will achieve the desired satisfaction? In this debate, we will significantly address the area of expertise in software engineering, in other words, career approaches such as "techniques." Let's share five engineering skills for you, the professional software technician.
---
Jakarta EE gives developers a comprehensive set of vendor-neutral, open specifications that are used for developing modern, cloud native Java applications from the ground up. With Jakarta EE, technology developers and consumers can be confident they have the best technologies for developing cloud native, mission-critical applications. And they can build on decades of Java developer expertise to move existing workloads to the cloud.
Learn more: https://bit.ly/3IPrxOq
Follow us on Twitter: https://twitter.com/home
Follow us on LinkedIn: https://www.linkedin.com/showcase/jakartaee/
Like us on Facebook: https://www.facebook.com/JakartaEE/
A
Hello,
everyone
and
welcome
to
another
jakarta
tech
talk.
My
name
is
serena
and
joining
us
today
is
karina
varela,
with
solid
experience
and
architecting,
and
delivering
software
currently
works
at
red
hat
and
has
special
interest
in
business,
automation
and
business
dev.
Ops
also
with
us
today
is
octavio.
Santana
who's,
passionate
software
engineer
focused
on
cloud
and
java
technologies.
A
C
C
Yes,
exactly
so,
let
me
first
get
started
by
introducing
our
amazing
speaker:
who's
otago
santana.
He
is
not
only
a
java
champion,
but
he
has
also
several
other
awards
out
there,
like
the
dukes
champion
and
many
others.
He
also
contributes
directly
to
the
evolution
of
java,
so
he's
a
leader,
an
expert
leader
of
several
working
groups
in
the
specification
in
different
specifications.
C
Also
the
creator
actually
the
most
the
top
contributor
and
the
creator
of
jakarta
nosql
specification,
also
he's
an
apache
committer
eclipse,
committer
he's
part
of
the
eclipsey
he's
a
project
leader
at
the
eclipse
foundation
and
he
likes
to
use
his
free
time
to
not
only
read
but
also
write
and
share
his
knowledge
through
several
books.
You
can
see
it
in
his
site
in
his
at
his
website
and
also
in
blogs
around
the
different
options
over
there
like
this
one
and
if
info
cube
and
many
others.
B
B
No,
the
pleasure
is
totally
mine,
especially
because
I
will
talk
with
carina
varela,
who
is
principal
technical
market
marketing
manager,
the
biggest
open
source
company
in
the
world.
Yes,
exactly
talk
about
red
hat,
she
has
over
10
years
of
experience.
She
drives
several
communities,
such
as
so
java
and
knowledge
is
everything
key.
She
is
also
instructor.
She
writes
book
and
article
especially,
and
mainly
about
automation,
cloud
java,
texture
and
yeah.
We
have
a
huge
pleasure
to
write
a
book
together,
but
today's
not
to
talk
about
us
karina
right.
Indeed,.
C
Today
is
to
share
some
of
the
secrets
that
we
learned
over
this
several
years
of
experience
that
we
have
together
and
share
with
the
audience
here.
So
tell
me:
what
is
the
secret
to
succeed
in
a
night
technical
career?
Some
might
say
it
is
to
have
excellent
knowledge
on
technical
skills.
Let's
say
I
need
to
know
a
lot
about
cloud.
I
need
to
know
a
lot
about
programming,
some
others
might
say
yeah,
it's
that's
only.
That
is
not
enough.
You
also
need
soft
skills.
B
C
B
C
B
B
B
C
So
there
are
two
types
of
skills:
we
are
just
getting
started
with
the
basics.
Okay,
so
there
are
two
types
of
skills:
there
are
the
hard
skills
and
they're
the
soft
skills
and
I've
known
several
consultants
that
were
pretty
pretty
pretty
good,
like
really
good
in
what
in
what
they
did.
They
had
several
certifications.
C
They
had
several
courses,
they
could
do
like
an
exceptional
job,
technically
speaking,
but
he
they
these
type
of
people-
and
I
personally
know
a
couple
of
them.
They
always
had
complaints
when
they
were
at
customers
because
of
the
lack
of
soft
skills.
So
when
we
are
talking
about
hard
skills
we
are
talking
about,
can
you
actually
do
like
get
your
hands
dirty
and
implement
that
either
if
it
is
on
programming
or
infrastructure
or
in
any
level
middleware
management?
C
C
B
Yeah,
especially
because
we
also
talk
about
communication,
if
you
think
about
language
and
a
language
might
be
about
here,
for
example,
we
are
from
brazil
and
a
lot
of
people.
There
are
a
lot
of
people
who
do
not
speak
english
and
now
so
mandela.
You
usually
said
that
if
you
want
to
take
people
minds,
you
are
able
to
speak
english
because
right
right
now
is
the
most
popular
language
around
the
world.
B
C
Yeah-
and
we
will
get
deeper
on
this
topic
I
think
later
on,
but
that
was
just
an
introduction
because
only
understanding
your
own
native
language
and
might
not
be
enough.
That's
one
of
the
things
in
the
communication
there's
also
if
you
can
communicate
to
upper
management
or
people
that
are
that
is
under
the
hierarchy.
So
there's
many
many
skills
that
you
can
have
there,
including
problem
solving
conflict
resolution.
So
there's
several.
C
If
we
could
highlight
five,
we
would
say
that
the
five
top
soft
skills
that
you
should
prioritize
if
you
need
to
work
on
on
those,
would
be
knowledge,
sharing
knowledge,
acquirement.
So
learning
how
to
study
study
by
yourself
not
having
to
go
through
several
courses
in
order
to
get
there
where
you
actually
need
and
actually
getting
your
hands
dirty,
might
be
a
good
thing,
also
ability
to
have
focus
to
communicate,
handle
your
time,
that's
critical
and
know
how
to
set
your
objectives.
B
B
Yes,
and
especially
because,
for
example,
okay,
I
want
to
go
deep
and
cold,
so
even
the
developers
you
you
might
go
to
do
operation
sites,
so
you
can
become
a
platform
engineer
or
sre
use
the
devops
future
or
something
like
that
or
we
want
to
go
to
principal
engineer
in
the
architecture,
design
style
or
you
can
go
deep
in
just
one
language
or
one
framework.
So
even
the
technical
area,
there
are
couple
ways
where
you
are
able
to
go
so:
database,
sequel,
sequel,
new
sequel
cash
distributed
cash
data
grid.
B
C
B
Yes,
I
mean
in
the
past-
yes,
it's
true,
I
mean
usually
the
manager
received
more
money
than
the
engineer.
However,
right
now
the
software
engineer
become
more
complex.
There
is
a
huge
complexity
in
the
area
and
also
that
is
the
white
car
here,
where
you
can
go
through
technical
area,
because
in
the
past,
okay,
you
become
senior
there's
another
there's
no
another
way.
You
must
go
through
engineer
manager,
however,
right
now
no
you're
able
to
go
to
staff
engineer.
B
C
Get
started,
but
we
just
wanted
to
settle
that.
There
are
different
skills
and
that
not
necessarily
because
you're
going
to
one
career
or
the
other,
that
you
will
get
more
or
less
money,
I
mean
let's,
let's
get
started
octavio,
so
the
first
thing
you
need
to
know
as
a
technical
person
is
that
everything
has
a
trade-off.
C
B
Oh,
it's
hard
to
understand
right,
especially
because
at
this
moment
every
I
guess
a
lot
of
people
who
is
taking
from
answer
is
crying,
but
unfortunately
the
truth
is
everything
has
a
trade-off.
So
yes,
microservice
is
wonderful.
However,
microservice
are
is
not
to
everybody
or
it's
not
you
all
the
time,
there's
something
happening
with
kubernetes
and
so
on.
So
that
is
these
amazing
books
by
mike
richard
and
eufort,
and
it
has
these
amazing
codes
that
explains
about
this
soft
architecture
right
now
and
basically
the
idea
is
there's
no
right
answers.
B
We
need
to
understand
further
context
and
then
the
trade-off
mainly
right
now,
when
you
want
to
become
a
staff
principal
and
distinguish,
we
need
to
understand
that
is
no
right
answer.
You
need
to
understand.
The
trade-off
need
to
measure
the
trade-off
to
create
companies,
components
to
integrate
this
to
us.
C
Exactly
so
a
way
to
think
in
order
to
like
you
shouldn't
what
what
do
we
want
to
to?
What
do
we
mean
with
this?
So
you
shouldn't
always
go
with
this,
because
maybe
this
thing
that
you
hold
hold
on
to
is
not
always
the
right
answer,
so
always
kubernetes
always
microservice,
always
even
driven
always
whatever
you
have
in
your
head.
That
might
not
be
the
case,
so
be
pragmatic
and
incremental.
C
Exactly
so,
I
a
good
way
to
represent
this,
and
everybody
knows
about
this
because
it's
been
a
while
I've
been
around
for
a
while.
Now
is
that
people
at
first
everybody
was
microservice
microservice
and
now
they
say
well,
if
you're
gonna
get
started,
maybe
you
should
start
with
a
monolith
and
then
break
it
down
so
that
that's
one
of
the
practical
examples
out
there.
B
C
There
are
three
main
things
when
we
are
talking
about
software,
we
need
to
know
like
why
we
are
doing
it,
how
we
are
going
to
do
it
and
what
are
we
going
to
use
when
doing
it?
So
I'm
bringing
this
from
the
synax
golden
circle.
This
is
used
a
lot
for
selling
and
marketing
of
big
organizations
when
he
says
that
the
core
thing
that
we
need
to
know
is
the:
why
not
the
what
I
don't
care
if
you're
gonna
use
java
to
implement
your
software
first?
Why
are
you
doing
that
feature
like?
C
C
Maybe
what
they
are
asking
in
the
end
of
the
day
or
what's
been
written
down
and
passed
over
to
you
isn't
the
actual
thing
that
needs
to
be
delivered.
You
see
so
depending
on
why
you
are
creating
that
you
might
think
better
on
the
how
you
are
going
to
design
it
and
architect
it,
and
only
then
you
can
think
about
the
what.
In
other
words,
what
are
you
going
to
use
like
what
what
the
graspable
things
right,
the
technical
stuff
so
which
technologies
and
which
architecture
designs
you're
going
to
use
there.
B
It's
not
mandatory
to
use
kubernetes
in
everything,
and
probably
you
know:
sun
neiman,
who
wrote
several
books
mainly
about
microservice,
especially
those
two,
the
most
popular
one,
and
he
wrote
an
article
about.
Should
I
use
microservice
at
beginning
and
as
he
said,
you
need
to
understand
first
the
why
and
then
go
to
the
hall.
Okay,
especially
because
there
they
highlight
the
commentation
to
him
is
okay.
If
I
will
start
a
startup,
it
doesn't
make
sense
to
release
mvp
call.
C
Exactly-
and
that
applies
also
to
digital
transformation
in
the
cloud
journey.
For
example,
many
people
look
at
the
journey
that
other
companies
has
taken
and
they
might
target
a
similar
place
and
not
understand
that.
Maybe
that's
not
the
next
step
to
be
taken
into
their
corporation,
so
in
hello
francesca
so,
and
guys
we're
following
up
the
chest:
the
chat.
Okay.
So
if
you
have
anything,
you
want
to
comment
just
feel
free
to
to
drop
it
down
and
so
that
yeah
and
when
we
are
talking
about
these
adoptions,
we
need
to
understand
that.
C
Okay,
I
know
that
I
want
to
get
there.
Let's
say
I
want
to
be
the
best
I
have.
I
want
to
have
the
best
architecture,
my
business
teams,
my
ceos.
They
are
all
aligned
with
this,
but
how
can
I
get
there
right
in
order
to
know
how
to
get
there?
You
need
to
understand
where
you
are
and
where
you
are,
doesn't
only
mean
that
you
will
map
the
technology
landscape.
C
It
will
also.
It
also
means
that
you
need
to
to
map
the
skill
set
in
your
teams
that
will
handle
that
across
the
corporation.
So
you
might
even
need
to
do
a
rework
in
and
break
your
team
into
smaller
groups,
depending
on
the
goals
that
you
have
or
get
them
together.
We
don't
know,
maybe
change
the
way
your
project
managers
lead
and
manage
their
projects,
so
all
of
these
might
require
big
changes,
so
it's
not
only
about
adopting
a
new
technology.
C
B
C
B
B
C
Yeah,
so
the
there's
a
an
interesting
thing
that
I
learned
from
my
own
experience,
actually
that,
coincidentally-
and
luckily
I
started
learning
things
through
the
specification-
things
that
were
based
on
specification,
so
I
had
a
long
path
in
my
career
working
with
java
server
applications,
and
I
learned
the
concepts
there.
Okay,
so
I
I
could
learn
exactly
which
were
the
concepts.
So
what
are
the
data
sources,
how
you
can
configure
them?
What
does
it?
What
does
a
java
application
have
to
have
has
to
have
in
order
to
interact
with
those
things?
C
One
day
I
had
to
start
working
with
another
one
and
then
do
a
migration
with
another
one
and
guess
what
I
already
knew,
how
to
work
with
all
of
those,
because
all
the
concepts
were
the
same.
It
didn't
matter
which
application
server.
I
was
working
with,
because
all
the
concepts
were
the
same,
so
I
I
only
had
to
change
the
way
you
interact
with
it,
but
in
the
end
of
the
day
you
already
know
what's
going
on
right.
The
same
is
valid
for
applica
for
programming.
B
C
B
B
B
B
B
C
Yeah
so
max
asks
asked
the
question
like
so:
is
it
better
to
choose
the
specification
over
the
framework
library
product?
I
think
that
the
point
here
that
we
are
trying
to
bring
is
that
it's
better
for
you
and
your
career
if
you
learn
the
fundamentals
and
the
concepts
behind
the
framework,
so
a
great
example
is
for
people
who
start
learning
how
to
persist
in
databases
using
hibernate,
for
example,
but
they
never
had.
C
They
never
actually
tried
to
open
a
connection
like
in
it
like
manually
and
see
how
things
work,
so
they
will
never
be
able
to
actually
understand
when
they
have
a
connection
leak,
for
example,
when
they
are
having
zlo
databases,
slow
queries
that
are
be
because
of
auto
generated
queries.
So
there
are
several
several
things
that
if
you
understand
the
core
concepts
that
will
be
better.
So
that's
that's
what
we
are
trying
to
highlight.
On
the
other
hand,
now
regarding
the
question,
would
you
like
to
share
your
thoughts
on
this
otavio?
C
B
B
B
B
So
if
better,
if
you
choose
specification,
it
depends
of
the
context
right
because
there's
no
right
and
wrong
answers,
but
if
you
shouldn't
stand
the
specification,
especially
the
computer
science
and
the
software
engineer
behind
that.
Yes,
if
you
want
to
become
a
principal
engineer,
distinguished
in
the
fellow
engineer
staff
engineer
whatever,
yes,
you
need
to
understand.
What's
going
on
behind
so,
for
example,
what
happened
with
java
because
safe
memory,
it
would
be
cool
if
you
understand
that
that
is
a
garbage
collector
inside
doing
something
it
would
be
cool.
B
C
C
Do
you
know
what's
extra
there,
so
this
is
the
kind
of
thing
that
differentiates
the
more
senior
people
who
are
able
to
make
decisions
from
those
who
are
only
using
this
stuff
without
knowing
what's
going
on
there
see
so
another
example
also
is
when
you
are
choosing
frameworks
for
persistence,
and
you
see
several
options
out
there,
including
panashi.
Oh,
my
gosh
panashi
is
great.
You
don't
need
to
you.
Don't
need
to
do
anything.
You
just
put
some
annotations
here
and
bam.
Okay,
do
you
know
what
is
the
active
record?
C
B
B
Where
you
are
able
with
a
single
api,
you
can
go
through
several
implementations
and
that's
amazing
right,
because
I
can
use
payatta,
I
can
use
apache
tummy.
I
can
use
wide
fly
quakus
just
using
a
single
annotations,
so
the
same
annotation,
I'm
able
to
use
the
exact
sum
once
so.
It's
amazing
to
use
specification.
I
recommend
you,
if
you
at
least
understand
and
every
time
that
I
had.
I
had
a
discussion
about.
Okay,
should
I
use
spring
or
jakarta
e?
Oh.
B
C
Like
I
told
you
like,
if
you
know
the
basics
like,
if
you
go
to
the
actual
example
like
auto
wired
and
inject
we're
talking
about
cdi,
do
you
know
cdi?
Do
you
know
what
you
can
do
with
cdi?
So
how
can
you
do
it
pure
jacardi?
How
can
you
do
it
with
spring,
for
example?
So
that's
that's
kind
of
how
you
look
at
things
right.
So
that's
why
we're
telling
you
do
not
try
to
be
experts
only
on
the
specific
framework,
but
try
to
know
what's
behind
it.
B
C
B
C
C
They
have
some
sort
of
documentation
from
the
engineer
who
actually
coded
it,
but
they
need
to
explain
the
architecture
how
to
use
it,
so
they
have
to
kind
of
understand
what's
going
on
there
too,
so
even
on
the
documentation
team
and
now
the
truth
talked
about
documentation,
guess
what
documentation
needs
software,
don't
I
know
I
know
many
of
you
are
like
rolling
your
eyes
now.
Oh
my
gosh
documentation
yeah!
C
C
C
Why,
like
everything,
I
need
to
remember
I'll
forget
so
whenever
I
have
to
do
something,
I
can
just
go
there
and
copy
and
paste
oh,
but
I
have
my
private
notes
here
in
the
like
for
the
windows
users,
I
have
my
my
notepad
with
full
of
notes
here
on
my
evernote,
whatever
you
use,
so
why
not
share?
Let's
talk
about
this
in
a
second,
so
first.
A
B
B
This
kind
of
thing
happened
the
old
days,
so
so
you
need
to
have
at
least
a
good
documentation,
otherwise
default.
Tolerance
on
your
organization
is
not
software,
but
people.
So,
okay,
this
guy,
is
leaving
it
trust
me.
It
happened.
I
saw
this
happen
a
couple
of
times.
This
person
is
leaving
it
just
this
person
knows
how
to
handle
that
technology,
a
sun
dispenser
lived
and
on
friday,
because
chaos
started
on
monday
because
nobody
knew
that
software
component.
This
does
exist,
and
you
know
the
huge
headache
around
the
organization.
C
I've
seen
an
example
like
this,
but
it
was
on
public
sector
and
this
consultant
was
not
available
anymore
and
they
was
like
they
had.
The
production
stopped
for
three
weeks
until
they
could
get
the
guy
for
like
paying
price
of
gold
so
that
he
could
fix
the
problem.
So
if
they
had
the
proper
documentation,
they
might
not
have
gone
through
this
right.
So
also.
Another
thing
is
that
documentation
shows
people
shows
people
how
we
got
to
the
stage
where
we
are,
especially
if
you're.
C
C
B
C
B
Usually,
people
use
this
paragraph
out
of
the
context
right.
So
yes,
if
you
just
look,
if
you
go
to
the
book,
you
look
just
one
paragraph
you're
right,
but
usually
it's
it's
not
the
right
way
to
do
right.
So
you
need
to
read
the
entire
book
to
understand
what's
going
on
inside
and
yes,
if
you
try
to
compensate
the
complexity
of
your
code,
put
com
com
comments,
it's
not
good.
B
However,
it
doesn't
mean
that
you
should
not
write
code
so
or
write
comments
in
your
code.
Documentation
read
me
any
kind
of
information,
so
please
forget
about
that.
Like
the
means
black
set
right.
So
the
the
clean
code
is
an
excellent
book
is
awesome
book
that
has
several
advice
for
you
to
write
a
decent
code
closer
to
the
business.
But
if
you
look
just
one
paragraph
you're,
probably
reading
the
book
wrongly.
C
C
B
Yes
and
then
put
a
comment:
okay,
why
am
writing
just
me?
And
god
knows
the
code,
but
after
that,
just
god
knows,
and
so
you
need
to
write
a
decent
code
and
also
write
a
decent
documentation
because
documentation,
as
you
said
before,
belongs
to
the
code.
So,
okay,
don't
put
a
comment
inside
this
code,
but
self-documented
code
does
not
exist.
So,
yes,
you
should
write
unless
and
code
decent
code,
ddd
dsl
clean
code
ambiguous,
I
usually
say
it's
right
ubiquitous.
Thank
you
karina
is
important,
but
you
should
not
forget
about
documentation
right
karina.
C
So
as
you've
seen
so
far,
there
are
different
types
of
documentation.
Okay,
so
there
are
there's
the
software
documentation
where
you
can
have
the
code
for
the
users,
so
the
user's
guide.
How
will
they
use
their
software?
Your
software?
Maybe
that's
not
part
of
your
job.
Okay,
that's
fine,
but
there
are
some
others
that
are
definitely
part
of
our
jobs,
for
example
creating
a
proper
readme.
C
So
people
can
know
what
this
software
is
for,
especially
when
talking
about
open
source.
That's
the
first
place.
I
go
to
be
honest.
When
I'm
learning
about
a
project,
I
hardly
go
to
the
web
page.
I
definitely
go
to
the
github
page
and
I
go
to
the
readme
and
when
I
want
to
contribute
to
an
open
source
software,
I
need
to
know
how
to
contribute.
C
What
are
the
guidelines
there?
What
is
the
process
that
this
these
folks
usually
follow?
Who
requests
do
it?
Does
it
have
a
specific
name
pattern?
Does
it
have
to
have
a
gear,
a
gyro
associated
with
it
somewhere,
because
there
are
a
software?
There
are
some
specific
projects
that
they
have
open
project
management.
Let's
put
it
like
that.
We
have
the
issues,
we
know
the
features
that
are
coming
and
that
are
being
worked
on
and
it's
open
for
the
public
and
many
of
these
times.
These
have
to
be
linked
with
the
software.
C
So
all
of
this
stuff
needs
to
be
documented,
also,
for
example,
in
a
contributor
guideline,
if
you
are
creating
open
source
software.
Now,
if
you
are
creating,
let's
say
you,
I
don't
work
with
open
source.
I
only
have
my
internal
stuff,
it's
private
still.
You
need
to
have
developer
guides
like
what
are
the
frameworks
available
for
our
developers.
In
case
you
have
a
a
let's
say:
you
have
a
strict
line
to
follow
on
that
specific
group.
What
what
is
there
to
use
how
they
should
use
it
and
what
should
they
not
do
there?
C
B
Basically,
you
are
able
to
import
using
open
api
to
any
language
that
you
are
using,
so
exactly
like
soap
did
in
the
past,
so
it's
a
different
way.
We
also
able
to
integrate
that
with
swagger,
where
it
will.
You
have
the
option
to
put
several
documentation
service
styles,
this
kind
of
thing.
So
yes,
the
open
api
is
awesome
way
is
also
on
standards
where
several
companies
are
implementing.
C
Yeah,
especially
when
we're
talking
about
a
more
complex
architecture
when
you
start
having
several
versions
of
apis,
so
that
might
be
really
critical
on
distributed
systems
and
before
we
move
ahead.
Just
one
last
example
is
that
even
this
software
document,
the
the
documentation
of
a
software
has
its
own
documentation.
C
C
B
Yes,
especially
because,
oh
it's
a
boring
code,
nobody
we
are
able
to
see,
but
it's
important
to
know
us
to
understand
how
the
organization
works
and,
for
example,
this
is
the
c4
model
is
really
really
important
to
us,
especially
because
is
the
organizational
way
to
integrate
everything.
So
the
best
way
to
think
about
c4
model
is
with
this
map.
So
the
best
analogy
that
I
have
on
my
mind
right
now,
is
the
google
maps
where
I
start
with
the
planet.
C
C
Arrows
users
did
like
all
sorts
of
different
stuff
and
if
you're
just
drawing
boxes,
drawing
boxes
to
describe
your
architecture,
you
might
be
falling
into
a
a
trap
because
you
know
what's
there,
but
maybe
other
people
doesn't
but
other
people
don't.
So
that's
why
adopting
models,
well-established
models
models
like
the
c4
is
something
good.
So
there
are
docu,
there
is
a
documentation
out
there.
There's
videos
teaching
how
to
use
it,
and
I've
used
it
personally
to
explain
complex
architectures
of
red
hat
software,
for
high-level
people,
high-level
users
and
also
for
more
deep
technical
people.
B
The
idea
is
to
the
of
the
decorator
is
exactly:
is
you
exactly
map
the
technology
that
you
are
using
or
your
organization
is
using
right
now
so
you're
able
to
see
the
one?
It
is
core,
the
one
it
is
not
core
the
one
that
we
are
starting
to
looking
at.
It
is
kind
of
thing
right,
so
basically,
the
organization,
the
the
tech
radar
one,
is
basically
to
know
exactly
what
technology
we
are
using
as
an
organization
and
that's
a
nice
way.
C
B
And
it
has
a
huge
value,
especially
because,
right
now
everybody
knows
what
tools
the
whole
organization
is
using.
For
example,
I
want
to
use
a
message
queue
right
now.
I
have
the
option
to
check
if
there
is
a
message
queue
available,
that
somebody
else
is
my
using,
and
that
is
good
right.
So
right
now,
for
example,
if
everybody
is
using,
I
don't
know
apache
kafka.
B
B
B
Yes,
because
you
you
documented,
the
whole
decision
is
more
the
strategic
one,
so,
okay,
I
will
use
this
because
of
that.
I
will
use
that
because
of
this
and
move
on
the
whole
idea
of
a
tattoo
decision
record
is
okay.
I'm
gonna
use
you
don't
need
to
put
the
small
details
like
okay,
I'm
gonna
use,
hibernate
version,
one
dot,
oh
stuff,
like
that.
Okay,
I'm
gonna
use
relational
database
in
java,
and
then
you
explain
why
you
are
doing
that
and
then
move.
C
Forward
for
complex
decisions
right,
there
are
more
complexity,
decisions
like.
Why
are
you
using
operators
to
deliver
your
software
instead
of
helm,
charts,
for
example?
So
there
are
some
complex
stuff
that
actually,
that
really
needs
to
be
documented,
so
that
you
have
the
history
there
and
you
can
learn
from
the
mistakes
and
not
repeat
them
again.
C
So
our
last
topic
of
tavio,
oh,
my
gosh,
do
people
think
that
when
they
join
this
career
they
only
need
to
hit
to
deal
with
computers.
So
I
only
handle
my
black
screen
black
and
green
screen.
That's
it!
I
don't
need
to
handle
people
well,
if
you're
targeting
a
more
a
higher
position,
you
will
have
to
that's
not
an
option,
because
in
the
end
of
the
day,
technology
is
just
the
means
to
an
end,
which
is.
B
C
B
B
On
the
idea,
but
we
general
yes,
the
technology
is
a
mean
to
you
to
our
end
right,
for
example,
internet
banking.
The
java
is
just
I
mean
it's
not
nobody's.
Gonna
use
data
banking
because
it
has
java
that
you
use
to
facilitate
or
make
their
life
easier
in
operation
because
they
don't
need
to
to
go
to
a
line
stuff
like
that
they're
going
to
use
netflix
to
write,
watch
movies.
If
not
go
to
the
black
boxers.
C
Youtube
crossing
a
recent
change
in
brazil's
banking
transactions,
where
they
added
a
new
way
of
a
form
of
transaction,
and
the
technology
was
just
the
means
like
if
they
are
using
event
driven
or
kafka.
It's
just
the
means.
What
was
the
goal?
The
end
goal
was
just
to
have
the
same
same
way
for
people
to
do
free
transactions
and
that
it's
instant
and
then
you
can
roll
back
and
whatever
all
the
requirements
there.
C
B
B
C
C
Everybody
is
like
any
enemies,
so
programmers
are
not
in
peace
with
anyone.
So
we
need
to
break
down
the
silos
and
put
together
all
the
things
that
we've
learned
throughout
the
conferences,
all
the
stuff
about
agile,
ddd
and
devops.
All
the
culture,
cultural
changes,
all
the
methodology,
the
way
to
apply
that
is
to
break
down
the
silos.
C
Didn't
this
might
sound
cliche,
but
that's
really
a
a
practice
that
is
required
and
we
are
going
through
something
similar
inside
red
hat
right
now,
so
that
we
I'm
living
that
on
the
past
through
the
past
year,
and
we
are
going
through
several
changes
internally,
because
we
are
breaking
down
the
silos
so
that
we
can
actually
deliver
what
we
want.
So
I'm
seeing
that
in
a
large
scale
now
and
I
actually
see
that
it
works
and
it's
definitely
required.
Definitely
a
must.
B
Yes-
and
I
love
this
one
here-
because
it
has
this
the
the
flow
to
cloud
or
cloud
era
right,
because
you
want
to
deliver
it
more
faster,
it
doesn't
mean
to
deliver
fast.
That
means
you're
going
to
deliver
everything
at
some
single
time.
You
need
to
decrease
the
complexity.
Do
small
step.
Do
continuous
integrations,
pull
your
code
closer
to
the
business
they
choose.
C
No
yeah,
you
said,
pull
the
code
closer
to
the
business.
There
are
several
ways
to
do
that,
just
to
add
to
that
topic,
so
you
can,
for
example,
not
only
use
ddd
to
have
a
same
language
pattern
across
the
the
communication
with
with
the
business
folks,
you
can
even
include
different
standards
like
bpmn
or
cmmn
or
dmn
into
your
software,
so
that
you
can
create
executable
decisions
or
processes
or
workflows
whatever
it
is.
C
That
is
actually
represented
in
a
graphical
way
that
they
can
see
it
and
change
it
and
maintain
it
and
validate
it,
and
that
is
sincerely
that
it
is
executable
it
can
run
as
code.
So
there
are
several
ways
to
bring
the
business
people
closer,
including
into,
for
example,
the
develop
the
delivery
pipeline.
The
delivery
cycle
they
might
want
to
be
part
of
the
any
approval
processes
if
there
are
any
and
how
can
they
do
that
if
they
don't
understand
anything,
that's
in
there
like
w
s,
a
p
p
dot
war.
What
is
that?
C
C
B
C
A
Thank
you
for
that
excellent
presentation.
Today,
karina
and
otavio.
It's
just
a
great
reminder.
If
anyone
in
the
audience
has
any
final
questions,
please
feel
free
to
ask
in
the
chat
and
or
use
the
ask
the
questions,
tab
and
I'll
give
you
a
few
moments
to
do
that.
But
while
I
wrap
up
the
next
jakarta
tech
talk
happens
on
march
30th,
the
piranha
cloud
and
uee
mp
runtime
in
progress,
you
can
register
for
that
session
using
the
link
I
just
posted
in
the
chat.
A
Let
me
just
click
on
there
get
that
in
there,
for
you
guys
and
then
we're
also
looking
to
book
some
more
jakarta
tech
talks
throughout
2022,
so
if
you're
interested
in
presenting
feel
free
to
fill
out
the
form
which
I
will
also
link
in
the
chat
and
finally,
if
you
have
any
feedback
on
the
tech
talk
program,
we
would
love
to
hear
from
you.
So
just
click
the
green
button
that
popped
up
and
let
us
know
how
you
enjoyed
the
talk.