►
From YouTube: Humans of DataHub: Mike Linthe
Description
Maggie Hays and Elizabeth Cohen sit down with Mike Linthe, Managing Director of Contiamo.
Mike shares his journey with DataHub, how Contiamo is leveraging DataHub for successful client outcomes, his favorite features, and more! This is a conversation you don't want to miss.
A
Hey
folks,
I'm
maggie,
we
are
back
with
another
round
of
humans
of
data
hub
today
we
are
joined
with
our
community
member
named
mike
mike
welcome,
give
us
a
little
bit
of
an
introduction
who
you
are
where
you
work.
What
you
do
we'd
love
to
hear
about
it.
B
Great
thanks
a
lot
for
having
me:
hey,
maggie,
hey
community,
I'm
mike
I'm
33
years
old,
based
in
berlin
in
germany,
so
on
the
european
side
of
the
data,
and
I
am
been
working
consulting
for
the
last
decade,
mainly
in
like
tech,
heavy
projects
started
off.
As
a
software
engineer,
working
with
like
these
typical,
very
boring,
big
enterprise
applications,
then
I
made
a
little
transition
worked
for
pwc
as
a
manager
and
then
built
up
some
rpa
business
in
germany
and
now
I'm
the
managing
director
of
conchamo
and
maybe
to
briefly
introduce
kanchama.
B
What
are
we
doing?
We
are
a
data
consultancy.
We
are
specialized
in
building
data,
heavy
applications,
but
also
implementing
data
governments
and
leveraging
data
science.
So
these
are
the
three
main
pillars
we
do
and
yeah
we
used
to
be
a
classical
startup
and
because
we
built
it
our
build
our
own
data
catalog
with
an
integrated
data,
virtualization
layer.
So
I
have
a
long
history
with
data
catalogs,
so
fell
in
love
with
them
very
early,
but
yeah
due
to
the
development
in
the
space.
B
If
you
look
at
it,
so
many
new
truths
coming
up
and
also
awesome
shoots
like
the
data
we
we
are
now
talking
about.
We
figured
out
that
the
success
in
this
consulting
space
and
the
consulting
business
was
a
better
adventure
to
take
on.
So
we
now
do
only
individual
data
consultancy
projects
and
we
work
with
global
companies.
Probably
most
of
you
know:
mercedes-benz
or
cbie.
A
That's
awesome,
so
I'm
curious.
So
I
remember
I
remember
us
talking
about
this
when
we
first
met
that
you
had
kind
of
gone
through
the
process
of
building
your
own
data
catalog,
and
you
knew
kind
of
you
know
how
much
of
an
undertaking
that
really
was
how
how
did
you
stumble
upon
data
hub
like
yeah?
How
did
you
end
up
in
the
community.
B
I
made
an
analysis
on
looking
at
like
the
classical
enterprise
data
catalog
products,
but
also
looked
in
open
source,
because
open
source
was
always
something
we
as
a
company,
valued,
very
highly
so,
and
we
have
a
lot
of
people
that
are
top
contributors
at
open
source
projects
and
basically,
all
the
projects
we
do.
Everything
is
open
source
based.
So
I
also
looked
at
that
and
like
two
years
ago,
I
I
stumbled
across
it
had
a
look
set
up,
my
own
a
little
data
hub
played
around
a
little
bit
and
fought
like
okay.
B
So-
and
it
was,
it
was
very
interesting
also
to
see
another
product
when
you
build
it
on
your
own
is
similar
right
because
you
see
wow,
they
solved
this
challenge
so
good
and
we
are
like
okay.
We
we
really
cracked
at
this
for
a
long
time.
B
So
basically,
we
had
a
look
at
all
of
the
source
catalogs
as
well,
and
when
we
decided
to
make
the
switch
to
consulting
only
we
more
or
less
let
loose
of
our
own
product
and
then
decided
on.
What
do
we
think
is
the
best
data
catalog
product
out
there
and
yeah.
We
stick
with
data
hub,
so
I
joined
the
community,
maybe
a
little
bit
over
a
year
ago
and
yeah
from
that
moment
onwards.
B
I
think
it
was
more
or
less
love
at
second
site,
because
the
first
thing
was
the
look
in
the
product
itself
and
yeah,
but
the
community.
I
guess
we
will
talk
a
little
bit
about
it
as
well,
but
for
me
it
was
regain
game
changer.
I
think.
A
B
A
B
So
I
think
the
the
most
important
thing
for
me
is
it's
remarkable.
How
quick
and
helpful
the
community
is.
So
basically,
whenever
I
write
something
down
it's
like
I
know,
so
we
have
this
time
difference.
I
think
a
lot
of
people
are
also
based
in
the
u.s
and
but
no
matter
when
I
post
something
someone
will
come
back
at
maximum.
I
would
say
six
hours
and
I
think
that's
that's
incredible.
B
Like
imagine,
you
have
a
corporate
tool
and
whatever
question
you
have,
someone
will
come
back
to
you
with
a
really
good
answer
in
sex
out
six
hours.
Companies
would
pay
a
lot
of
money
for
that
stuff.
So
really
that
that's
amazing,
I
think
it's
very
open-minded
and
very
very
welcoming
everyone
is
trying
to
show
what
you
can
do
and
how
we
can
progress
together,
and
so
I'm
not
a
software
engineer
anymore,
so
I
used
to
be.
But
that
means
I
program
very
rarely
so.
B
For
me,
it's
sometimes
even
harder
to
really
follow
like
everything
that's
happening
there,
but
I
feel
everyone
is
really
making
an
effort
to
explain
it
properly
and
give
helpful
advice,
and
so
for
me
it
was
also
very
easy
to
get
on
board
in
the
community,
although
I'm
not
like
the
perfect
tech,
expert
and
yeah.
So
it
was
just
a
lot
of
fun
and
trying
around
and
yeah.
There
is
really
a
lot
of
cool
stuff
around
with
the
community.
Also
documentation
is
really
good.
C
A
Yeah,
that's
cool
and
I
I
noticed
mike
that
I
see
you
jump
in
every
once
in
a
while
with
kind
of
like
you
know,
more
thought,
provoking
questions
or
conversations,
and
so
I
love
I'm
personally
really
excited
to
see
the
trajectory
of
the
community
move
beyond.
You
know
just
kind
of
like
the
troubleshooting
support,
which
of
course
is
critical,
and
we
will
continue
to
do
that,
but
I
think
there's
just
a
lot
of
really
great
opportunities
for
us
to
have
more
of
these
kind
of,
like
you
know,
meta
conversations
around.
A
B
B
Contribute
from
from
our
company
they
contribute
with
like
coding
and
sharing
better
connectors
whatever,
but
for
me
also,
I
think
I
try
to
to
give
some,
maybe
a
little
helper.
So
for
some
projects,
for
example,
I
today
just
posted
something
like
a
script
to
just
build
your
own
json
file,
so
you
can
just
metadata
very
easily
and
quickly.
That's
awesome!
A
B
A
We'll
see,
I
don't
know
about
that,
so
I'm
curious,
like
with
the
with
the
implementation
of
data
hub,
that
your
team
has
done
what
are
kind
of
the
main
use
cases.
So,
when
you're
working
with
your
clients-
and
of
course
you
know
share,
only
one
is
reasonable.
I
don't
expect
you
to
you,
know
air
dirty
laundry
or
anything,
but
you
know
what
why
are
these
or
like?
Why
are
you
using
data
hub?
What
problems
are
you
hoping
that
data
hub
will
kind.
B
B
B
Yeah,
because
I
mean
we
are
an
engineering
company
and
our
engineers
were
like
hey.
First
of
all,
we
want
to
show
clients
the
product
we
should
use
it
ourselves
and
second,
it's
really
nice
for
doing
the
stuff.
We
do
so
like
the
first
real
use
case
is
really
for
ourselves
to
to
get
hold
of
all
the
data
assets
we
have
and
the
infrastructure
we
run
for
clients.
So
we
have
to
we
sometimes
build
pipelines
for
the
clients
and
monitor
them
and
make
them.
C
B
And
yeah
it
was
really
nice
and
it's
really
nice
for
us
to
like
manage
document
stuff
and
knowing
okay.
These
are
the
kubernetes
clusters
we
have
here.
Are
the
people
responsible
for
this
and
this
client
things
like
that,
so
we
definitely
and
also
for
the
machine
learning
model,
so
something
we
use
it
to
document
stuff.
That's
also
why
I
asked
some
questions,
sometimes
in
the
in
the
slack
and
yeah.
The
second
thing,
obviously,
is
the
data
implementation
projects
with
clients,
and,
I
think,
like
I
have
some
some
most
valuable
features.
B
Love
it
when
you
have
a
modern
data,
stick
which
is
certainly
not
too
common
in
germany
yet
so
I
think
us
is
probably
two
years
ahead
of
that,
but
now
more
and
more
clients
they
adapt.
Maybe
the
cloud
data
wares
like
snowflake,
bigquery,
redshift
and
also
dbt
is
really
taking
off.
We
are
also
a
partner
with
dbt,
and
I
think
this
is
really
some
great
great
technology
also
coming
out
of
the
open
source
community,
obviously
yeah
yeah-
and
I
love
that
lineage
feature
of
of
data
hub.
B
It's
so
helpful
in
a
lot
of
ways,
also
with
the
test
et
cetera.
The
integration
got
way
way
better
over
time.
Also,
so
that's
definitely
something.
We
see
a
lot
of
value
at
client
side,
and
I
mean
the
main
use
case
is
efficiency.
I'd
say
for
this
lineage
feature
in
data
engineering
teams,
so
share
the
information
about
the
pipelines,
also
seeing
the
impact
of
changes
in
your
data
pipeline.
B
Definitely
a
big
use
case.
We
also
have
seen
a
lot
of
times
at
clients
and
I
think
the
second
one
is
the
ownership
aspect
of
saying:
okay,
who
is
responsible
for
what
and
also
the
overview
of
what
assets
do
I
have
so.
B
What
I
really
really
love
is
the
openness
of
the
tool,
so
you
can
ingest
pretty
much
everything,
although
maybe
there's
no
real
connector
for
it
yet,
but
you
can
still
ingest
that
stuff
through
the
data
model,
and
so
we
we
built
a
lot
of
like
more
or
less
crazy
stuff
with,
for
example,
kpi
tracking
and
oh,
you
can
do
a
lot
of
things.
I
think.
B
Maybe
you
remember
that
we
also
had
a
discussion,
I
think
about
kpis
yeah
like
a
couple
of
months
ago,
and
so
you
can
really
easily
do
this
individually
and
showcase
it
to
clients
and
build
it
inside
a
data
model,
and
so
I
think,
there's
a
lot
about
this
data
discovery.
Part
and
also
this
data
governance
part
you
can
do
with
the
data
and
so
therefore
it's
it's
a
very
flexible
tool,
it's
very
open
and
yeah.
I
think
this.
This
is
the
main
advantage
of
it
also
in
terms
of
looking
at
the
competitor.
C
B
Yeah
yeah
I'd
say,
and
so
the
lineage
is
my
favorite
in
terms
of
because,
because
I
think
that's
mainly
because
we
try
to
build
it
on
our
own
and
it's
really
hard.
So
this
is
definitely
something
something.
I
appreciate
the
effort
that
has
been
done
there
and
the
smartness
in.
How
will
you
build
this
and
it's
also
pretty
flexible
in
terms
of
that
you
can
connect
whatever
you
want
and
yeah.
B
We
have
something
planned:
oh
that's,
great
yeah,
but
the
data
data
profiling
really
helpful
feature,
I
think,
also
to
understand
the
data
and
it's
really
a
game
changer
in
terms
of
for
the
from
the
user
perspective,
especially
in
germany
and
europe,
we
have
a
lot
of
regulations
pretty.
I
think,
a
lot
more
than
the
us
yeah.
B
Is
happening
is
in
terms
of
data
protection,
you
probably
heard
about
gdpr
and
yeah
whatever
there
is-
and
this
is
super
helpful
feature
for
data
scientists
and
data
engineers
to
understand
okay.
How
is
this
data
looking
and
give
me
some
samples
that
are
like
non-critical,
so
I
do
not
violate
anything
yeah,
so
I
I
really
love
it
and
we
personally
use
it
a
lot
also
at
the
concert,
but
also
internally,
for
some
of
the
data
we
have.
So
it's
really
good.
B
It's
really
for
us,
it's
really
the
number
one
go-to
tool
and
yeah.
I
also
so
now
we
did
a
couple
of
implementation
projects
or
like
as
an
implementation
partner
in
germany.
Now
and
german
companies
usually
are
pretty
conservative.
I
need
to
say,
and
still
we
we
and
open
source
is
also
not
really
a
big
thing
in
germany.
Yet
so
it's
getting
better
and
better.
But
if
you
look
at
the
application
landscape
we
have.
B
We
have
sap
as
the
main
application
provider
here
and
it's
a
very
isolated,
very
like
log
in
log-in
application,
so
you
can
get
out
of
it
and
it's
also
it's
not
very
open
in
terms
of
hey.
Can
I
give
your
data
exchange
manager
whatever,
so
people
are
more
or
less
like?
B
Let
me
have
my
standard
infrastructure
system
with
sap
and
I'm
fine,
but
we
now
did
a
couple
of
projects
and
bringing
data
up
in
and
due
to
the
flexibility
of
the
product
and
also
like
the
overall
feeling
and
how
you
can
work
with
it.
We
really
convinced
a
couple
of
clients
with
the
project
itself
that
they're
like
wow.
That's
amazing.
I
didn't
even
know
that
it
was
possible
and
to
work.
C
B
This
in
an
enterprise
environment,
so
it's
it's
definitely
a
great
tool
and
I
don't,
I
think,
it's
way
ahead
in
terms
of
what
other
open
source
tools
can
do
there,
and
it
can
definitely
compete
with
also
the
enterprise
tools.
So.
C
B
Actually
had
a
project
where
we
benchmarked
datahub,
so
we
implemented
data
and
they
hired
another
agency
that
implemented
colibra
for
them
and
the
same
use
case,
which
was
like
very
fair,
like
just
do
it.
B
And
the
feedback
was
that
the
the
client
actually
liked
data
hub
more
than
colibra.
So
this
well-
and
I
think
so.
A
I
guess
that's
so
exciting,
that's
so
cool,
so
I'm
curious
kind
of
thinking
about
the
community
and
your
experience,
you
know
getting
familiar
with
the
tool
or
the
project.
I
know
you're
not
as
kind
of
hands-on
with
development
anymore,
which
I'm
sure
you
you
miss
a
little
bit,
but
that's
you
know
we
all
we
all
move
on.
I
miss
it
too,
but
I'm
curious
for
folks
like
if
you
met
someone
tomorrow
who
was
joining
the
data
hub
community
or
starting
with
data
hub.
A
What
advice
would
you
give
them
to
help
them
be
successful?.
C
B
Like
there,
first
of
all,
no
dumb
questions
and
second
of
all,
people
will
help
you
in
in
so
many
ways.
C
B
Go
to
slack
sign
up
like
or
go
go
to
the
slack
channel
and
start
introducing
yourself.
That's
also
one
of
my
favorites,
like
channels
introduce
yourself
channel
yeah,
because
I'm
a
curious
person-
and
I
love
seeing
like
oh
so
many
people
from
different
sides
of
the
world
are
connecting
in
this
community.
Yes,
so
just
just
ask
and
also
have
a
look
at
youtube.
I
think
the
youtube
videos
are
actually
really
helpful,
also
some
of
the
features
so,
for
example,
the
youtube
video
about
the
ui
extension
you
there's
a
firebase
ui
extension.
B
Super
useful
to
understand
this
is
how
it's
supposed
to
work,
etc
and
there's
so
many
good
resources.
So
I
think
people
should
first
so
go
to
slack,
go
to
youtube
and
go
to
github.
Have
a
look
at
the
github
example.
So
my
favorite
place
is
the
bootstrap
data
file
because
it
gives
a
nice
overview
on
all
the
assets
you
can
put
in
and
for
me
as
a
like
semi-technical
person
that
can
at
least
ingest
json
files.
B
This
is
super
helpful
because
my
engine
is
usually
like:
hey,
let's
just
build
this
in
python
and
make
an
api
call,
and
I
said
I
don't
need
it.
I
just
copy
paste
that
stuff
in
this
dress,
yeah
so
and
sometimes
I'm
quicker
than
I'd,
say:
yeah.
That's
awesome,
yeah!
So
really
a
lot
of
very
useful
information
on
the
github
and
slack
and
youtube
and,
and
then
the
documentation
is
also
nice
on
the
homepage.
So
I
think
these
are
the
four
main
pillars
of
getting
ready
with
datahub
and
just
try
it.
B
It's
super
quick.
It's
really
also
for
people
that
are
not
100
technical,
the
whole
community
and
the
team
they
made
the
product
so
easy
to
use
that
it's
just
perfect.
C
B
So,
first
of
all
obviously
adoption
because
I
think
the
bigger
the
community,
the
better
for
all
of
us-
and
you
see
it
already.
I
mean
the
speed
of
of
implementation
is
crazy,
which
also
sometimes
is
a
challenge
for
big
companies.
I
see
because
so
we
are
going
anywhere
like
yeah
by
the
way
in
three
three
weeks
there
will
be
a
new
release
and
it
will
have
awesome
features,
so
you
should
get
it
and
they
are
like.
Usually
we
do
half
yearly
releases.
B
Okay,
so
yeah
I'm
it's
it's
really
quick
and
I'm
looking
forward
to
fine-grained
lineage,
so
like
column-based
spinach,
I
think
this
is
if
this
is
implemented.
Well,
this
is
really
a
great
feature
to
get
like
more
detailed
information
and
also
to
provide
more
value
to
use
cases
to
different
use
case,
especially
on
the
engineering
side,
but
also
on
the
side
of
like
impact
analysis.
So
there's
a
lot
of
value
in
there
yeah.
A
B
Yeah,
I
think,
maybe
for
the
community,
I
would
hope
to
have
more
people
from
europe,
because
I
think
it's
also
good
when
you
have
a
lot
of
people
in
all
the
different
time
zones
to
help
each
other
yeah
and
sometimes
so.
Basically,
for
example.
Now,
if
I
look
at
it,
we
are
pretty
much
the
first
ones
really
doing
a
lot
of
work
with
sap.
Although.
C
B
Is
the
main
system
a
lot
of
people
have
here,
so
I
see
that
we
need
to
get
more
people
on
board
to
be
quicker
and
provide
more
value
and
discuss,
use
cases
things
like
that,
and
so
that's
what
I'm
looking
for,
but
I
feel
you
guys
are
doing
an
awesome
job
and
extending
the
community
and
making
it
a
good
place
to
be
around.
So
I'm
confident
that
this
will
really
work
out.
B
Some
more
flexibility
in
the
ui
I
need,
so
I
think
the
ui
is
very
good,
very
nice
to
the
point
of
what
you
need.
The
only
thing
I'm
missing
sometimes
is
some
some
more
and
possibilities
to
adjust
a
little
bit
in
terms
of,
for
example,
you
have
a
schema
and
add
more
metadata
than
the
glossary
and
tags,
so
some
people
are
already
clients,
cameras
and
said,
like
look,
I
want
to
to
add
to
this
column
ownership
in
a
column-based
ownership.
Oh.
B
It's
possible
with
with
data,
but
it's
not
like
so
easy
to
change
to
ui
in
a
way
that
it
shouldn't
fit
neat.
But
I
also
I,
as
I
mentioned
earlier,
the
the
file
based
approach
is
already
really
nice,
so
you
do
not
have.
B
Anything
about
it
and
but
I
think
there
are
some
some
potential
improvements
there
as
well,
but
nevertheless
I
love
it
yeah.
A
I'm
going
to
follow
up
with
you
on
that
the
the
column
level
ownership
is
very,
very
interesting
and
also
exciting.
I
mean
just
from
a
timing
perspective.
We
have
some
of
the
team
working
on
calm
level,
lineage
specifically
impact
analysis,
basically
extending
that
impact
analysis
to
the
calm
level,
so
really
really
exciting
stuff.
Coming
up
there,
cool.
C
A
Mike,
it's
just
been
such
a
pleasure
to
speak
with
you,
thanks
for
sharing
your
experience
with
us
and
your
time
and
yeah.
We,
we
really
love
having
you
in
the
community
with
us.
B
Yeah,
I'm
I'm
also
very
grateful
to
be
here
and
thanks
for
the
opportunity.
Also,
a
shout
out
to
all
the
people
in
the
community
continue
doing
the
great
work
and
if
someone
needs
any
help,
just
contact
me
on
slack.
I'm
always
happy
to
provide
some
insights
in
what
we
did
and
how
we
probably
solved
some
of
the
things
you
you
are
struggling
with,
so
yeah
just
reach
out
and
thanks
a
lot
for
having
me.