📺 Develpreneur YouTube Episode

Video + transcript

Why Learn SQL?

2023-06-13 •Youtube

Detailed Notes

This is an introductory presentation to lead into one of our free classes. (https://school.develpreneur.com/p/free_courses). You can also check out our SQL series on YouTube here.

You can find out more through our online classes at https://school.develpreneur.com and register for free. Registration will add you to our email list and you will periodically receive coupons for courses as well as notifications of the latest releases.

Transcript Text
foreign
[Music]
welcome to another discussion about why
learn a specific language
we put together a little
sort of summary a few weeks back
about languages in general learning
languages how do you make that decision
and it really felt like we wanted some
specifics for some of the more common
types of questions and languages that
are out there
this time we want to talk about SQL or
SQL
and this is an interesting one because
it's a lot of people are going to say
why would you choose SQL isn't it really
just a database language and more or
less yes it is you're not going to use
SQL if you're not dealing with
a with querying that's what SQL stands
for it's structured query language so it
is a way to query against a database
now
the good news is it is used in some form
and most if not all databases I in all
of the languages all the databases I've
dealt with I have not come across one
that doesn't actually recognize SQL even
object-oriented databases that have
their own query script usually in their
own form
there is still a way to access the data
with SQL now it doesn't look the same
because the structure is very different
but there is a a rudimentary form of SQL
that is that is used even there now
that's not to say that all of them are
there may be some that don't but
it is really the common language for
working with data and by working with I
mean like it's selecting it and doing
inserts and updates and deletes and
things of that nature and
aggregations and things that are so it's
not just pulling the data but actually
doing manipulations of the data
now SQL is one of the more common
languages because data is everywhere
no matter what your application is
there's data there whether it's about
your users whether it's about your
products whether it's about your
services whether the data is the
application whether it is manipulating
data whether it is calculating against
data you're going to find data and it's
part of every application in some way
form or fashion
and that may be because you need some
reporting or you may need to relate data
back and forth so you need to search
through the data to find certain records
or you may need to combine or aggregate
the data the nice thing is with SQL it
does all of these things it is the
most sort of the common denominator of
those types of queries those types of
tasks with data
and it is
a solid
static kind of language it is not
changing a lot while there are
definitely extensions with various
databases if you look at the core SQL
things you're going to do
it's going to look the same everywhere
the naming you know the naming
convention is maybe a little different
things like that but if you do select
star from my table
where my value equals three
that's going to be almost identical in
every single database you look at
now you may have to adjust stuff a
little bit there may be things around
that but usually if you take that and
you run it
as long as those objects and things
exist you're going to get data back and
it's going to look basically the same
from database to database to database
so that makes it in itself something
that's nice to have because like another
language we've talked about JavaScript
when you have something that you learn
that is going to be used
regardless wherever you're at
you get to keep using it it's not going
to get rusty it's going to stay current
and it's something also probably because
you're going to use it maybe on a daily
basis
you're going to build your skills you're
going to build your confidence you're
going to master that sooner rather than
later because you're actually putting it
to use
now a thing about SQL that's interesting
these days is because there are a lot of
tools out there that allow you to
quickly browse and work within data
they essentially hide the complexity
though of the queries and they sort of
block you from more complex queries
but they do allow you to quickly go
browse data if you go to like a DB
visualizer or if you go out and use a DB
admin or PHP admin or whatever you know
PG admin whatever those
the varying types of those tools or toad
or something like that you can go in you
can quickly browse tables databases
schemas whatever it is store procedures
triggers look at source code write code
insert update records added them on the
Fly things like that
so those tools definitely have their
place
and they are useful and as a SQL
Developer you're probably going to want
to keep those tools and use those
however
they're not always going to be available
to an application and the queries you
can write are going to be far more
powerful than probably every tool
because those tools are going to be
solving for a general case where you can
write a
tuned specific query for whatever your
purposes are
and that sometimes is going to make the
difference in something being useful or
just sit on a Shelf
particularly these days as we get into
larger data sets
if you can't work with the query
language and help it
help itself basically so that you can
get answers back in a reasonable amount
of time
if you're dealing with you know
terabytes of data
that stuff can get out of hand quick
so you want to be able to use this
to
benefit your applications you also like
I said you're not going to be able to
use those those other tools within
applications sometimes there are there's
going to be Frameworks in libraries but
usually you're going to be better off if
you at least understand what's going on
underneath the the covers and also if
you can write your own like raw SQL
queries because then you can more
specifically solve the problems you need
to solve and not have a overly large use
of of resources or time or anything like
that
it also can allow you in some cases to
get things done faster because you're
not waiting for the quote database team
to get some work done you can actually
write the couple of pieces of code you
need and you move forward and you're off
and running
now as I mentioned SQL is used in many
many projects across many Industries and
platforms you're probably not going to
see
yeah I was gonna say you're probably not
going to see SQL as a primary job
request or position but you will see
database developer or database
administrator and there are in a not as
a career not as a salary employee but as
a project you will see projects that are
hey we've got problems database isn't
working right we need somebody to tune
or do a performance review of our SQL
queries of our queries of our database
and find ways to help us do what we're
doing better
so just knowing SQL is great but
actually
we'll say mastering it also has its
benefits and can open doors to projects
that
many people aren't going to touch
because
it is one of those things that while SQL
is very common a lot of people know how
to do it when you get into the
performance tuning side of it and really
writing tight specific queries
those skills are are less common you can
that's sort of a rarity
now the nice thing is it's popular it's
one of the best documented languages out
there probably every vendor every
database has got some some basic SQL
documentation sitting out on their site
somewhere
uh you're gonna have to watch out for
the vendor specific extensions and
tweaks however you're going to be able
to find examples you're going to be able
to find a lot of tutorials that are
generic and also vendor specific
so if you want content if you want a way
to help yourself learn
SQL is one of those language it's it has
got a plethora of options for you to
work with
now database knowledge in general and
SQL in particular is also for those of
you that are newer to the development
world they're often a way to separate
Junior from senior developers or even
you know mid-level level developers I
have seen data seen developers and
worked with developers that have limited
database skills a little bit limited or
just a little bit of SQL knowledge
and they really struggle to advance
Beyond about a mid-level you know
mid-tier developer job because by the
time you get to a senior expected to
understand data and how to work with it
how it works how it should work how to
access it
and not be Reliant entirely on a
framework or a library or a tool or a
database developer
so while it is
probably not a language you're going to
want as your first language it could be
I mean
you're gonna you're sort of
you're setting your path up for your
decree your career in a specific way if
you start with SQL it means you're going
to be database first probably for your
whole career it's going to be difficult
to get out of that however once you've
settled in on a couple of languages if
you don't have SQL
at least to a level where you're
comfortable with it I've again strongly
recommend take a look at it spend some
time
check some stuff out there look at some
of the documentation so that you do get
to a point where you're comfortable with
it
it is in general better to learn it
sooner rather than later
get in there spend a little bit of time
even if you're not mastering it just so
you understand the basic idea of what's
a select what's an insert what's an
update look like what does a where
Clause look like how do I order those
kinds of things and at least what is a
trigger what is a store procedure what
do those look like how do I call them
those are some of the things that I
think are going to be very valuable and
sooner rather than later you will find
that it allows you to to Really expand
the type of work you can do type of
problems you can solve and the
applications you can build because you
can't be full stack if you don't have
some sort of a database knowledge and
usually that's going to be SQL of some
sort
now the bonus is we do have some classes
out on this YouTube we've got some SQL a
whole series of learning SQL walk
through a bunch of examples do it with
mySQL which is free easily available
so you don't have to go far to spend a
little bit of time and these are they're
basically 10 to 15 minute
Snippets of stuff you could probably
spend an hour or two today
and in the day being moderately
comfortable with SQL enough that you
could get around and you know maybe
you're not going to be building a
database but at least you can get data
out of a database which you know that's
probably the important thing initially
because somebody else is you know if you
don't know it somebody else will have
built it for you
thanks a lot for your time I hope this
helped if you have any questions shoot
us an email at info developpanur.com and
go out there and have yourself a great
day
hello this is Rob with developmentor
also known as building better developers
wanting to announce that we have
school.developmentor.com feel free to
check it out if you like any of this
information any of the content that
we've sent and you would like to see
more you can come out you can enroll for
free we have free courses we've got
places for you to get better at just
learning a technology our how to's you
can work on your business skills we can
help you with becoming a better
developer as encoding and things like
that a lot of the stuff you've seen on
YouTube we also have out at
school.developing or we just have it a
little more of a educational format and
a way for you to track your progress as
you move forward becoming a better
developer
thank you
Transcript Segments
0.42

foreign

18.89

[Music]

27.66

welcome to another discussion about why

31.5

learn a specific language

33.6

we put together a little

36.6

sort of summary a few weeks back

41.34

about languages in general learning

44.34

languages how do you make that decision

46.02

and it really felt like we wanted some

48.539

specifics for some of the more common

51.36

types of questions and languages that

53.1

are out there

54.12

this time we want to talk about SQL or

57.12

SQL

58.68

and this is an interesting one because

60.48

it's a lot of people are going to say

61.8

why would you choose SQL isn't it really

64.32

just a database language and more or

68.64

less yes it is you're not going to use

70.86

SQL if you're not dealing with

73.32

a with querying that's what SQL stands

76.14

for it's structured query language so it

79.38

is a way to query against a database

82.32

now

83.82

the good news is it is used in some form

86.34

and most if not all databases I in all

90.479

of the languages all the databases I've

92.34

dealt with I have not come across one

94.32

that doesn't actually recognize SQL even

98.22

object-oriented databases that have

101.28

their own query script usually in their

103.38

own form

104.939

there is still a way to access the data

108.24

with SQL now it doesn't look the same

111.38

because the structure is very different

113.579

but there is a a rudimentary form of SQL

116.64

that is that is used even there now

118.14

that's not to say that all of them are

119.88

there may be some that don't but

123

it is really the common language for

125.64

working with data and by working with I

128.039

mean like it's selecting it and doing

130.56

inserts and updates and deletes and

132.36

things of that nature and

134.42

aggregations and things that are so it's

136.739

not just pulling the data but actually

138.3

doing manipulations of the data

142.26

now SQL is one of the more common

145.379

languages because data is everywhere

149.34

no matter what your application is

151.02

there's data there whether it's about

153.12

your users whether it's about your

154.44

products whether it's about your

155.459

services whether the data is the

158.52

application whether it is manipulating

161.099

data whether it is calculating against

163.8

data you're going to find data and it's

166.739

part of every application in some way

168.72

form or fashion

170.22

and that may be because you need some

172.319

reporting or you may need to relate data

175.2

back and forth so you need to search

176.76

through the data to find certain records

178.5

or you may need to combine or aggregate

180.959

the data the nice thing is with SQL it

184.56

does all of these things it is the

188.04

most sort of the common denominator of

191.459

those types of queries those types of

195.18

tasks with data

197.819

and it is

199.2

a solid

201.239

static kind of language it is not

203.58

changing a lot while there are

205.5

definitely extensions with various

207.12

databases if you look at the core SQL

210.68

things you're going to do

213.18

it's going to look the same everywhere

215.22

the naming you know the naming

216.9

convention is maybe a little different

217.98

things like that but if you do select

220.68

star from my table

222.68

where my value equals three

226.799

that's going to be almost identical in

229.739

every single database you look at

232.019

now you may have to adjust stuff a

233.879

little bit there may be things around

235.68

that but usually if you take that and

237.54

you run it

238.98

as long as those objects and things

240.84

exist you're going to get data back and

243.599

it's going to look basically the same

245.04

from database to database to database

247.62

so that makes it in itself something

249.9

that's nice to have because like another

252

language we've talked about JavaScript

253.5

when you have something that you learn

255.42

that is going to be used

258.06

regardless wherever you're at

260.88

you get to keep using it it's not going

263.58

to get rusty it's going to stay current

265.52

and it's something also probably because

268.139

you're going to use it maybe on a daily

270.06

basis

271.139

you're going to build your skills you're

272.699

going to build your confidence you're

274.62

going to master that sooner rather than

276.96

later because you're actually putting it

279.72

to use

282

now a thing about SQL that's interesting

285.06

these days is because there are a lot of

286.86

tools out there that allow you to

289.68

quickly browse and work within data

292.68

they essentially hide the complexity

295.56

though of the queries and they sort of

298.32

block you from more complex queries

300.9

but they do allow you to quickly go

303.18

browse data if you go to like a DB

306.36

visualizer or if you go out and use a DB

310.44

admin or PHP admin or whatever you know

312.72

PG admin whatever those

314.46

the varying types of those tools or toad

317.4

or something like that you can go in you

320.16

can quickly browse tables databases

322.139

schemas whatever it is store procedures

324.66

triggers look at source code write code

327.18

insert update records added them on the

329.58

Fly things like that

331.259

so those tools definitely have their

333.539

place

334.56

and they are useful and as a SQL

338.039

Developer you're probably going to want

339.12

to keep those tools and use those

340.56

however

342.66

they're not always going to be available

344.039

to an application and the queries you

347.639

can write are going to be far more

349.68

powerful than probably every tool

351.6

because those tools are going to be

353.52

solving for a general case where you can

355.5

write a

357.68

tuned specific query for whatever your

362.28

purposes are

363.66

and that sometimes is going to make the

366

difference in something being useful or

368.759

just sit on a Shelf

370.86

particularly these days as we get into

372.72

larger data sets

374.699

if you can't work with the query

377.46

language and help it

379.38

help itself basically so that you can

381.78

get answers back in a reasonable amount

383.46

of time

384.539

if you're dealing with you know

386.34

terabytes of data

388.44

that stuff can get out of hand quick

391.02

so you want to be able to use this

393.84

to

395.22

benefit your applications you also like

398.639

I said you're not going to be able to

400.139

use those those other tools within

403.139

applications sometimes there are there's

405.12

going to be Frameworks in libraries but

407.12

usually you're going to be better off if

409.62

you at least understand what's going on

411.3

underneath the the covers and also if

414.3

you can write your own like raw SQL

418.44

queries because then you can more

420.539

specifically solve the problems you need

422.28

to solve and not have a overly large use

425.94

of of resources or time or anything like

429.36

that

430.139

it also can allow you in some cases to

432.24

get things done faster because you're

433.86

not waiting for the quote database team

436.44

to get some work done you can actually

438.78

write the couple of pieces of code you

440.28

need and you move forward and you're off

442.259

and running

444.24

now as I mentioned SQL is used in many

446.699

many projects across many Industries and

448.68

platforms you're probably not going to

450.78

see

451.919

yeah I was gonna say you're probably not

454.5

going to see SQL as a primary job

457.38

request or position but you will see

461.34

database developer or database

463.5

administrator and there are in a not as

466.44

a career not as a salary employee but as

469.08

a project you will see projects that are

472.319

hey we've got problems database isn't

475.199

working right we need somebody to tune

478.16

or do a performance review of our SQL

481.8

queries of our queries of our database

484.5

and find ways to help us do what we're

487.56

doing better

489

so just knowing SQL is great but

491.699

actually

492.599

we'll say mastering it also has its

495.419

benefits and can open doors to projects

497.4

that

498.3

many people aren't going to touch

499.74

because

500.759

it is one of those things that while SQL

502.919

is very common a lot of people know how

504.3

to do it when you get into the

506.039

performance tuning side of it and really

508.62

writing tight specific queries

511.62

those skills are are less common you can

515.039

that's sort of a rarity

517.8

now the nice thing is it's popular it's

519.959

one of the best documented languages out

521.94

there probably every vendor every

523.26

database has got some some basic SQL

526.08

documentation sitting out on their site

527.7

somewhere

528.779

uh you're gonna have to watch out for

530.519

the vendor specific extensions and

533.22

tweaks however you're going to be able

536.1

to find examples you're going to be able

538.2

to find a lot of tutorials that are

540.48

generic and also vendor specific

543.42

so if you want content if you want a way

546.54

to help yourself learn

548.58

SQL is one of those language it's it has

550.86

got a plethora of options for you to

553.38

work with

555.6

now database knowledge in general and

559.38

SQL in particular is also for those of

562.62

you that are newer to the development

564.899

world they're often a way to separate

567.24

Junior from senior developers or even

569.04

you know mid-level level developers I

571.86

have seen data seen developers and

574.68

worked with developers that have limited

576.42

database skills a little bit limited or

579.66

just a little bit of SQL knowledge

582.959

and they really struggle to advance

585.48

Beyond about a mid-level you know

588.24

mid-tier developer job because by the

590.82

time you get to a senior expected to

593.22

understand data and how to work with it

595.08

how it works how it should work how to

597.839

access it

599.519

and not be Reliant entirely on a

602.94

framework or a library or a tool or a

606.36

database developer

608.58

so while it is

610.56

probably not a language you're going to

612

want as your first language it could be

613.92

I mean

615.18

you're gonna you're sort of

617.779

you're setting your path up for your

621.06

decree your career in a specific way if

623.64

you start with SQL it means you're going

625.68

to be database first probably for your

627.839

whole career it's going to be difficult

629.04

to get out of that however once you've

632.519

settled in on a couple of languages if

634.56

you don't have SQL

636.48

at least to a level where you're

638.16

comfortable with it I've again strongly

641.04

recommend take a look at it spend some

643.56

time

644.579

check some stuff out there look at some

646.38

of the documentation so that you do get

648.6

to a point where you're comfortable with

650.04

it

651.66

it is in general better to learn it

653.88

sooner rather than later

656.94

get in there spend a little bit of time

659.399

even if you're not mastering it just so

661.079

you understand the basic idea of what's

663.72

a select what's an insert what's an

665.7

update look like what does a where

667.44

Clause look like how do I order those

670.74

kinds of things and at least what is a

674.7

trigger what is a store procedure what

676.44

do those look like how do I call them

678.779

those are some of the things that I

681.24

think are going to be very valuable and

684

sooner rather than later you will find

685.8

that it allows you to to Really expand

688.56

the type of work you can do type of

691.079

problems you can solve and the

693.18

applications you can build because you

695.22

can't be full stack if you don't have

697.8

some sort of a database knowledge and

700.44

usually that's going to be SQL of some

702.779

sort

703.74

now the bonus is we do have some classes

707.579

out on this YouTube we've got some SQL a

711.18

whole series of learning SQL walk

713.88

through a bunch of examples do it with

715.8

mySQL which is free easily available

719.399

so you don't have to go far to spend a

722.94

little bit of time and these are they're

725.22

basically 10 to 15 minute

727.38

Snippets of stuff you could probably

729.66

spend an hour or two today

732.839

and in the day being moderately

735.72

comfortable with SQL enough that you

738.54

could get around and you know maybe

741.42

you're not going to be building a

742.38

database but at least you can get data

744

out of a database which you know that's

746.76

probably the important thing initially

748.26

because somebody else is you know if you

750.6

don't know it somebody else will have

752.1

built it for you

753.899

thanks a lot for your time I hope this

755.519

helped if you have any questions shoot

757.019

us an email at info developpanur.com and

760.2

go out there and have yourself a great

762.3

day

764.88

hello this is Rob with developmentor

767.22

also known as building better developers

769.26

wanting to announce that we have

771.68

school.developmentor.com feel free to

773.94

check it out if you like any of this

776.16

information any of the content that

778.139

we've sent and you would like to see

779.399

more you can come out you can enroll for

781.44

free we have free courses we've got

783.72

places for you to get better at just

786.36

learning a technology our how to's you

789

can work on your business skills we can

791.1

help you with becoming a better

792.54

developer as encoding and things like

794.94

that a lot of the stuff you've seen on

796.62

YouTube we also have out at

798.8

school.developing or we just have it a

801.06

little more of a educational format and

803.579

a way for you to track your progress as

806.04

you move forward becoming a better

808.2

developer

823.579

thank you