0:00:25
welcome back guys um another day another
0:00:28
break and fix we had a pretty good
0:00:32
um episode yesterday when the principal
0:00:35
developer from seek
0:00:37
andre get joined us for a live q a where
0:00:42
guys join in as well we had a pretty
0:00:44
good response and a lot of people
0:00:47
appreciated it otherwise after the
0:00:51
we are pretty uh positive after that and
0:00:54
we are looking forward to
0:00:56
the next guests as well so
0:00:59
before that we were working on our
0:01:01
middleware as well
0:01:03
and they as i can recall we are pretty
0:01:07
getting it done um though it's been a
0:01:10
while we've been working on that
0:01:12
um probably more than a week but
0:01:15
hopefully we can get that done today
0:01:17
or else we need to get it done offline
0:01:21
by tomorrow um that's something which
0:01:24
um in this project um
0:01:28
so yeah today we will focus on that then
0:01:30
what do you have to say
0:01:32
that was brilliant um yeah i just
0:01:36
wanted to give you and the viewers a bit
0:01:40
um i kept it to announce it
0:01:47
no no it's more internet better than
0:01:49
that it's better than that
0:01:51
new internet it's even better than that
0:01:54
new laptop nowhere
0:01:56
it's even better than that new zen
0:02:04
good as that oh do you got aws creds
0:02:13
new guest no damn it
0:02:20
gave up i mean i can keep going
0:02:24
oh you you got it working oh yeah
0:02:28
uh well not me uh not me so
0:02:32
the original persons whose issue this
0:02:35
was and we were just
0:02:36
helping him um he he finally got it
0:02:41
so yeah which was pretty amazing because
0:02:46
got to know it this evening as well
0:02:50
um so of he has already committed
0:02:54
the code on here repo so we're gonna
0:02:57
be analyzing what he did that we
0:03:04
learned from that code oh
0:03:13
yeah okay so um i'll just
0:03:16
i'll just do the test first to
0:03:20
show you and then we can carry on as in
0:03:25
did you pull the code already yes
0:03:28
nice already done um
0:03:34
so this one is there
0:03:50
all right um testing board
0:04:00
that goes to the board so if i
0:04:12
and go to tables and then
0:04:17
when you load go to the
0:04:28
there you go nice that's pretty cool
0:04:36
this is working but it still causes
0:04:39
issues on the spaces but that we can get
0:04:43
rid of but that's not really the main
0:04:46
main thing was that it wasn't coming
0:04:49
from the front end but
0:04:50
now that is coming coming yeah
0:04:58
by the way have you have you got water
0:05:01
or not no it's there you go
0:05:05
give me a second help
0:05:26
okay guys let's check
0:05:34
as in what the person whose original
0:05:38
this was fixed there and we
0:05:41
missed out on that code so let's check
0:05:47
um so this i'm gonna actually what i'm
0:05:50
is i'm going to compare it to the
0:05:55
right in that way we can keep track of
0:05:58
what was changed and what was not all
0:06:14
so what changed was yeah this is the
0:06:18
middleware that we're working on so this
0:06:22
all right yeah function go this one
0:06:26
was the same as well so right
0:06:34
okay so hey just calling it which
0:06:37
we don't really have to at the moment uh
0:06:41
but oh so he's calling it
0:06:45
in the girl function cool
0:06:48
and wait for me wait for me what
0:06:53
huh wait for me i want to analyze it as
0:06:58
yeah i was just um bringing it as it on
0:07:03
yeah the screens so we can
0:07:06
compare form code and to
0:07:10
code right deal all right so i'll just
0:07:17
make your biggest so you can see as well
0:07:20
are you able to now all right
0:07:28
go function looks the same no it doesn't
0:07:34
oh it's calling all right
0:07:37
that makes more sense yeah yeah
0:07:40
that makes a lot of sense instead of
0:07:44
uh giving in that other jobs
0:07:48
file two functions we are just calling
0:07:50
one and in that one
0:07:52
the board post name is being called
0:07:56
which is fair enough yeah
0:07:59
i'd agree with that and then we made
0:08:02
our asynchronous function which is
0:08:10
and then he was passing the board name
0:08:16
okay and and then what i did was
0:08:24
made it await okay we missed that
0:08:28
um you're right that so he's passing
0:08:33
interesting do you know how that looks
0:08:36
apparently yeah mean remember when we
0:08:40
tried doing chords it worked
0:08:41
it's just uh yeah yeah this control
0:08:43
allow region should be
0:08:47
this little line stops here
0:08:52
if we don't have that then we get the
0:08:56
cause arrow okay and then he's basically
0:08:59
stringifying the board name here
0:09:13
and then his oh okay so
0:09:16
on the result so he's doing everything
0:09:21
here but then on the result
0:09:25
yep he's going to the next page
0:09:28
in in industrial html right
0:09:37
and then go into the industrial html and
0:09:44
yeah yeah this was forest
0:09:48
yeah right this is what we did yeah
0:09:52
yeah he just basically
0:09:55
added the missing bits on top of our
0:10:00
and then he also did uh uncommented the
0:10:05
get boards function as well right yeah
0:10:08
that's basically it huh
0:10:11
he changed to get bored a bit because
0:10:14
now it's good that it's returning
0:10:16
jason first he was just returning a
0:10:23
no no no no it's the same yes
0:10:26
he just made it to come on more lines
0:10:30
yeah i didn't see the jason thingy cool
0:10:34
it's pretty cool that's fantastic
0:10:38
i wouldn't be more excited but this is
0:10:41
actually pretty cool
0:10:52
and hello mate how are you doing
0:10:56
welcome and pranav uh welcome man
0:11:00
you're already feeling sleepy huh
0:11:07
these are my friends oh okay cool
0:11:12
oh my boy okay what i'll do is i'll
0:11:15
um pull this i guess
0:11:18
yeah well this one but it's in
0:11:22
a different branch so
0:11:25
i'm gonna uh it's in the branch
0:11:28
called um a little something
0:11:31
i know i know that middleware
0:11:35
i mean at the end it's possible uh
0:11:39
post board oh wait
0:11:48
oh i just realized something bad never
0:11:53
no nothing very important
0:11:56
middleware implementation
0:11:59
uh no is this the one called padding
0:12:03
working post board name try seeing my
0:12:06
screen i can't find it
0:12:12
driver see my screen i can't find it
0:12:29
what middle branch
0:12:35
do they intact entire command again
0:12:44
and stuff don't do minus a
0:12:49
all right you just ask me for an
0:12:56
why are you only seeing
0:13:02
i think it might be
0:13:08
but if you do get branch you're only
0:13:10
seeing two branches
0:13:12
main and middleware implementation yeah
0:13:15
isn't that what's supposed to happen
0:13:16
when it shows the main and the current
0:13:22
it should show you all the branches
0:13:35
okay because if i um
0:13:40
in which branch are you at the moment
0:13:43
middleware implementation
0:13:46
okay so go to main branch
0:14:09
okay now that's weird oh
0:14:12
because i haven't pulled the other
0:14:14
branches oh here we go then
0:14:20
hang on a minute try to switch
0:14:25
try to switch to well
0:14:40
so i can do that but i can't oh my
0:14:49
no no i meant um okay i meant get
0:14:52
get check out middleware underscore
0:14:57
underscore board underscore uh
0:15:00
no no no middleware underscore
0:15:04
post underscore board
0:15:24
i i just told you the wrong name my bad
0:15:27
is middleweight underscore
0:15:30
underscore post on the scoreboard
0:15:36
yeah it's a bit of a big name
0:15:52
spelling is right okay nope
0:15:57
i'll just pull it i mean i have to put
0:16:02
fetching egg on right to set a sip
0:16:33
that must have been the case
0:16:36
don't check out just switch to f
0:17:21
oh my my quizzes open
0:17:24
oh and movie rejects
0:17:30
all right let's do this console
0:17:46
okay yeah let's open the end point
0:17:55
right yeah all right
0:17:59
here we go are we gonna get rid of these
0:18:05
uh yeah i don't really want to
0:18:08
focus on these tiny bits
0:18:12
yeah because these things are gonna like
0:18:14
pretty sure there are other ways you can
0:18:16
um kind of put in stuff in dynamodb
0:18:19
which is not string friendly so
0:18:21
yeah you'll have to spread out any words
0:18:24
cool um if you can go to jira now and
0:18:28
we need to update the issues
0:18:31
over there we haven't really been doing
0:18:35
as in for the past few yeah
0:18:43
oh and my internet is slow today
0:19:07
we've done the don't don't yeah yeah
0:19:11
i did it okay fine
0:19:17
okay make the backhand talk to the front
0:19:21
so that's working um
0:19:24
yeah this is the best one so can you
0:19:28
yeah done perfect okay post a
0:19:32
note from the front end to the back end
0:19:35
cool but we don't want
0:19:47
or do you want to do i think i'll
0:19:50
let's finish the board operations first
0:19:54
from the front end and then we can
0:19:59
then we can move on to the notes one as
0:20:07
right now we need to get the specific
0:20:10
from the front end to the uh
0:20:13
from the back end to the front and i'm
0:20:17
thinking how will this work first we'll
0:20:21
function get full name i guess
0:20:26
no no no hang on hang on okay okay this
0:20:30
this is know how it works in real world
0:20:34
come on you're not writing the function
0:20:37
you're really excited
0:20:42
to move on i can tell okay um
0:20:45
so how it would work that first four
0:20:48
we we kind of have to make a
0:20:54
design and then an approach so
0:20:58
the design that's coming on top of my
0:21:06
so i guess like literally the board name
0:21:10
which the person passed
0:21:11
his hair we take that and get it from
0:21:14
the board because you're
0:21:16
only going to display one board at a
0:21:20
that's just like there's this board and
0:21:23
we get it we don't have to get multiple
0:21:25
so if the person like we'll have a
0:21:29
place where the person will enter like
0:21:32
but that's for afterwards so for now uh
0:21:35
we can just get the board name from here
0:21:39
yeah we'll change content afterwards and
0:21:40
we'll just change the text field that's
0:21:43
um we get the board name from here go to
0:21:47
table like a query thing which we
0:21:49
already have in the get board name
0:21:52
but the only interesting thing is that
0:21:55
in our api we do it um through the
0:22:00
what do you call it the url
0:22:04
you know what i mean yeah yeah
0:22:16
yeah so do we still want to do it with
0:22:20
we do it with board id you know what i
0:22:23
if you have to get let's say um this
0:22:28
with our current api design um we go
0:22:32
oh wait a minute yeah and we do this
0:22:38
that's right right and can we get the
0:22:42
yeah that's right but instead of that i
0:22:46
we would have to pass in the board
0:22:49
name yes so that's
0:22:53
i feel like we need to add another
0:22:56
function in the api
0:22:58
sorry controller which takes in
0:23:02
uh so when you mean the api
0:23:06
are you talking about the backhand or or
0:23:09
express button it's a backhand
0:23:22
contrary um we can
0:23:26
get the board with the board name from
0:23:33
but then we'll have to go ahead and add
0:23:36
it to the url every time
0:23:42
no no no i don't think that would be a
0:23:46
idea what we might do is you know
0:23:50
how we are already getting the board
0:23:53
only getting a specific board
0:23:57
what we might do is we
0:24:02
will um you know how when we pass in
0:24:07
the name of the board that we want to
0:24:11
yeah we will pass it to the
0:24:14
api and then when it searches
0:24:18
the database it would actually search
0:24:23
board name and then wherever the
0:24:28
id of that object is
0:24:31
which is the board id it will
0:24:35
take that into consideration
0:24:38
so essentially the user will be
0:24:42
with the board name but the db
0:24:46
will be inter um but the api will be
0:24:49
interacted with the board id
0:24:52
so it will be the programming part
0:24:56
again okay so all right so you know how
0:25:01
um we would have to pass a board
0:25:04
name from the front end to get a
0:25:09
yes um what i'm thinking that
0:25:12
when we pass the board name to the
0:25:17
api okay then it will go
0:25:24
okay and then it would oh we would have
0:25:29
create another method in the api
0:25:36
corresponding boards id only
0:25:40
and then we can take that id and pass it
0:25:45
get a bow specific method
0:25:53
but we still need to change that method
0:25:56
that method takes it from the url but we
0:26:00
put like a big um board id in the url
0:26:03
you know what i mean
0:26:04
like this yeah yeah so it's
0:26:08
essentially what this board id
0:26:11
will be as a um it won't appear in the
0:26:24
okay so when so this is kind of what we
0:26:28
i'm thinking what you're saying could be
0:26:31
like in the code way that we make two
0:26:41
so when i say make an additional
0:26:45
function i mean to say
0:26:48
make an additional function in the
0:26:52
yes but to access those functions as
0:26:55
you need to create yeah you fetch
0:26:58
functions one will be get board id
0:27:00
which will match the board name with the
0:27:04
like you pass the board name and the
0:27:06
express will give you sorry
0:27:09
yeah you pass the board name to the back
0:27:12
and that func that will return the board
0:27:15
then that function will go back to the
0:27:18
original function which is get board
0:27:20
sorry which is get bored um yeah
0:27:23
yeah and that will pass the board id to
0:27:27
and the function which is already there
0:27:31
we'll just change up a bit of that
0:27:34
not take it from the url but take it in
0:27:38
correct correct and then we will return
0:27:42
back yeah so i guess first we need to
0:27:43
work on the back end and only we can
0:27:46
the middleware okay um so
0:27:49
first thing is first let's go back to
0:27:53
jira because i want to actually break
0:27:58
down into the specific steps that
0:28:02
we have just discussed
0:28:05
so it's a lot easier for us to keep
0:28:08
track yeah i'll do relates to because i
0:28:11
can't create child tasks
0:29:21
um can you just uh add a little bit more
0:29:27
update guest specific port function in
0:29:30
back end to take the info
0:29:34
from uh from the body which one
0:29:37
which one you want to update it the
0:29:41
specific board function yeah that one
0:29:45
just add a bit more description because
0:29:49
yeah it's a lot easier to
0:29:52
try to when it's him when it's
0:30:15
will be passed from our new function
0:30:39
when you're from the program and we need
0:30:42
the board id from our new function
0:30:50
so our new function will
0:30:54
take in the borden board name
0:30:57
from the front end and then it will
0:31:01
return us that corresponding board's id
0:31:05
and then when he returns us there we're
0:31:08
going to use that board id in this
0:31:11
function um so for the same
0:31:16
i'm thinking we do that in the fetch not
0:31:23
like how do we do that in the fetch
0:31:27
um so you know how there's a
0:31:30
so you're thinking that the we'll pass
0:31:33
information in the back end
0:31:38
id will pass information to get bored is
0:31:42
that what you're saying
0:31:46
say that again please i gotta be
0:31:49
yeah so you know how there's a function
0:31:52
get bored id in the back end and there's
0:31:54
a function called get bored
0:31:55
in the back end get bored id and get
0:32:00
there will be get bored id let's see
0:32:03
yeah uh there will be gap board name
0:32:07
function no no sorry
0:32:15
so what this is what i'm thinking what
0:32:18
you're trying to say that
0:32:19
from the middle where we'll only call
0:32:21
back get board name
0:32:23
and from get board name we'll call get
0:32:28
is that what you're saying
0:32:37
so i'm thinking i just
0:32:40
so well i just understood that
0:32:43
according to you what we're gonna do
0:32:47
is we will create i i'm thinking that
0:32:50
you are saying this
0:32:51
i have something else in mind
0:32:54
okay so if my understanding is
0:32:59
right um for you understand from what i
0:33:03
said is that yeah um
0:33:08
we'll create one function
0:33:11
in the fetch api that will be
0:33:14
get board name all right
0:33:18
and then the and then another function
0:33:25
back end which would be get board id
0:33:30
and then we will pass in the value from
0:33:34
get board name in the fetch api to
0:33:38
get board id in the express app
0:33:42
yeah and then when we have the board id
0:33:46
from the express apps new function then
0:33:49
we will use that board id in our
0:33:53
which is already get both
0:33:57
taking the board id
0:34:00
yes so this is what um
0:34:05
i'm thinking is that to do that you need
0:34:09
functions in the fetch one
0:34:12
would be correlating to getting the
0:34:15
um id so when you got the board id you
0:34:18
can internally call
0:34:20
the get board name function like um this
0:34:24
uh he called the postport name from
0:34:29
so that your back end is possible
0:34:32
can you repeat the first part as in the
0:34:36
exactly first part you just said
0:34:39
yes okay let's do this the properly
0:34:46
i mean it's not that hard though um no
0:34:50
i i i wanted to doing this
0:34:54
as well but then i don't have the
0:34:57
as in free license of this raw
0:35:03
like okay we might as well do this
0:35:07
but seems to have it so which is
0:35:38
okay i know what to do i'll just create
0:35:41
probably a flowchart it's easier
0:36:20
i'm just making a rough diagram
0:36:23
yeah that's that's um expected
0:36:33
backhand middleware
0:36:53
left and back on the right
0:36:56
well what difference does it make it
0:37:00
well like no normally
0:37:04
the sequence goes from left to right
0:37:09
that's why okay that makes sense
0:37:13
middleware has a good board that's fine
0:37:52
oh i know how to make last time
0:38:03
all right so i'm still making
0:38:14
viewers you continue don't don't worry
0:38:18
yeah so what we're doing at the moment
0:38:22
um we want to start on a new piece of
0:38:26
which is ex exciting times and
0:38:31
he instead of uh jumping right in the
0:38:35
curve they're doing a bit of planning
0:38:42
we have already written down um
0:38:46
as in we have already broken a big
0:38:50
task into subtasking jira which we
0:38:54
will be showing um after
0:38:58
this one just as a recap but um here
0:39:02
kothik is doing is um he's
0:39:05
making a kind of a visual
0:39:08
architectural diagram um
0:39:11
to represent how being
0:39:15
gonna implement the new feature
0:39:18
and also how will the data
0:39:22
flow between the functions
0:39:27
and how with the middleweight and
0:39:30
uh say in terms of talking to
0:39:33
each other that's all so
0:39:37
yeah if you've got any questions as in
0:39:41
you know show us something in
0:39:45
in general sense feel free to
0:39:48
comment and we'll try our best to answer
0:39:52
all your questions
0:39:56
all right so that's looking
0:39:59
pretty good okay just
0:40:03
almost finishing it that's all right
0:40:09
it's important that we take more time
0:40:13
right then take less
0:40:17
time and do a bad job yeah
0:41:56
it's really fascinating when you um
0:41:59
as in bring all your thoughts onto paper
0:42:03
and then let's just be amazed
0:42:07
how much sense does it make and how much
0:42:10
clear idea yeah for sure
0:42:20
so this is what i think yeah
0:42:24
it's gonna happen this is the middleware
0:42:28
um we go to the get board id function
0:42:31
the get borrowed function yeah
0:42:36
so i just if you can also
0:42:40
elaborate that if that particular
0:42:44
would be a new function or always
0:42:48
functions so this function is
0:42:51
already existing i'll mark it
0:42:54
but i think that's pretty obvious at
0:42:58
this function is the only function which
0:43:03
um yeah that's one
0:43:11
i yeah max needs some juice
0:43:17
give it a high quality juice so it
0:43:21
as a high quality i mean high
0:43:25
yeah well i don't want to spill sp
0:43:29
salting or red bull on no no
0:43:32
no you don't want to i can do it
0:43:42
these are all new functions uh we'll go
0:43:44
ahead and create them
0:43:45
um in the middleware
0:43:49
um there's this function called get
0:43:51
board id which is gonna
0:43:53
go to the back end and get the board id
0:43:57
this is a new function as well she's
0:43:59
gonna go through the table
0:44:11
um just to make sure this board name is
0:44:14
going through the body
0:44:17
but i'm pretty sure that's pretty clear
0:44:18
because it's in the back end it's not
0:44:20
going as an option
0:44:22
um yeah this function is going to just
0:44:25
match the board name in the um
0:44:28
database and it's going to return with
0:44:33
when this function has a board id it's
0:44:37
and in the middleware only um it's gonna
0:44:41
get bored like you know how we have done
0:44:48
then we'll go to get bored with the
0:44:52
um then hang on so
0:44:55
from which part is this is
0:44:58
starting is it the gap board id from the
0:45:06
what do you mean sorry so
0:45:09
there to get bored i
0:45:12
no no no hang on i mean you'll obviously
0:45:14
start from the middle of it right like
0:45:16
you can't start from the back
0:45:20
of course but yeah
0:45:30
fine because i think how we named
0:45:36
just confusing me a bit but yeah i've
0:45:41
slight hang of it i
0:45:44
i named them because of like consistency
0:45:48
um right here also like the function
0:45:52
literally same like get get and post
0:45:55
but we can change the function names
0:46:02
that's fine no problem at all right
0:46:06
from here when you get the board id
0:46:09
um in the get board function you
0:46:12
send it to this get bored function
0:46:16
which is obviously going to get the
0:46:18
board id but in the body
0:46:23
it'll go through the database fine
0:46:26
for that particular board id and return
0:46:29
the whole board in adjacent format
0:46:33
let me clarify that this is gonna be
0:46:39
make it small like this bigger
0:46:44
that didn't make any difference anyway
0:46:48
so this is gonna return that in a json
0:46:54
and we will live happily ever after
0:47:00
what do you say right okay
0:47:04
so how i'm understanding it that pretty
0:47:08
makes sense but i just want to confirm
0:47:11
understandings so we both are on the
0:47:16
um from the get board
0:47:20
id when we get the get bored
0:47:26
from uh when we get the
0:47:29
jet board name from the front end to the
0:47:33
it will go into get board
0:47:36
id which doesn't accept any parameters
0:47:41
and then it will go into
0:47:44
the back end to get the
0:47:48
board id by passing in the board and
0:47:52
right yeah and then
0:47:58
back to the middleware why would it
0:48:02
go back to the middleware i mean the
0:48:04
function is already in the middle when
0:48:06
it has to return something right we're
0:48:08
looking for the board id
0:48:13
to be honest i don't think we need to go
0:48:16
middle because when we
0:48:25
when we get the board id
0:48:28
in the back end from the board name
0:48:37
jetboard function which accepts a board
0:48:43
in the background so you're gonna like
0:48:46
that that's what i'm saying like you're
0:48:48
gonna call an internal function from the
0:48:50
back end is that what you're trying to
0:48:56
what do you mean an internal function
0:48:59
this function we'll call this function
0:49:03
yeah okay right so essentially
0:49:15
that's exactly what i mean that
0:49:18
the function on the top of the back end
0:49:22
call the function on the bottom of the
0:49:33
and then once it's got the board
0:49:37
id from that existing
0:49:40
function which is on the top then we can
0:49:44
pass that directly to the middleware
0:49:48
um so heading out that's there's a
0:49:50
reason i kind of designed it to it
0:49:53
this way um you heard about the terms
0:49:56
um like uh what do you call that thing
0:50:00
cohesion and uh oh my god
0:50:04
low coupling uh when it comes down to
0:50:11
so when you do when you
0:50:14
go and call these two functions from a
0:50:17
board id function so let's say you have
0:50:21
to use get board id somewhere else as
0:50:24
architecture your this function is kind
0:50:27
of wasted just for
0:50:29
like not wasted but like it's doing
0:50:32
like it's handling two functions in the
0:50:35
but rather it could handle one function
0:50:37
this could handle one function
0:50:39
which breaks it down that means that if
0:50:41
you need to use get board id once more
0:50:44
it will not go ahead and do this
0:50:46
particular functionality
0:50:48
rather it'll just get the board id and
0:50:51
then you can go ahead and like get bored
0:50:54
you know what i mean but rather what
0:50:56
you're trying to say right now is that
0:50:57
if you do get bored id
0:50:59
it will get bored id and then inside
0:51:01
that you'll get the board as well like
0:51:02
even if we rename it get bored but like
0:51:06
it'll not be low coupled like if one of
0:51:09
these functions break
0:51:10
the whole program will stop but rather
0:51:12
in this architecture
0:51:14
if let's say uh get bored isn't working
0:51:18
get bored id will still work
0:51:19
because these two aren't um
0:51:22
communicating with each other
0:51:28
so basically in that in that sense
0:51:32
you don't mind hitting the database two
0:51:36
yeah yeah until then
0:51:39
independent yeah but
0:51:44
the more we hit the database the more
0:51:47
it causes on the performance which is
0:51:50
but not really aren't we hearing the
0:51:52
database exactly the same number of
0:51:55
getting the board um id first
0:51:58
and then getting the board doing that in
0:52:01
two separate functions
0:52:02
still hitting the database twice
0:52:08
even if we do it um that way it's
0:52:11
it's still gonna go find the board id
0:52:14
then it's gonna go again
0:52:15
get the board no so
0:52:19
what i'm actually trying to say
0:52:22
is that save visualize
0:52:26
and anti-clockwise circ
0:52:37
yeah from what i'm understanding
0:52:41
yours saying that we go to
0:52:46
the board id in the middleware
0:52:49
and the at the bottom then go
0:52:52
to the back end uh board id board
0:52:57
board name and then come back and then
0:53:00
go to the board id in the middleware
0:53:04
and then again hit the back end
0:53:08
why are we going in that
0:53:19
this this and then with this
0:53:27
okay i mean i'm just not
0:53:32
sure oh right right so
0:53:38
and then that way okay and then
0:53:41
coming back and then coming back again
0:53:46
why can't we do it as
0:53:50
this this and then this
0:53:53
so instead of creating a
0:54:02
right okay um if yeah i mean it says
0:54:05
yeah sure if it's going to affect
0:54:09
surely we should do that um because
0:54:13
if you if you go back to your screen
0:54:18
i just don't see at any point baby
0:54:23
going in the back end once
0:54:26
okay and then and then
0:54:29
coming out of the back end
0:54:33
going to the middleway and then going
0:54:36
to the back and why not do everything in
0:54:40
one trip in the back end and then
0:54:44
have all the information that we need
0:54:48
come to the middle i guess that's
0:54:51
where uh keeping the function
0:54:54
independent comes in play as well
0:54:56
um why do we have two functions then for
0:54:58
doing the same stuff
0:55:01
like we have two functions right and
0:55:04
here as well we we anyway would some at
0:55:07
some point we'll create a get board id
0:55:10
yeah so it's gonna come there um even if
0:55:13
we don't create it now
0:55:15
so i was just thinking that if we split
0:55:18
things up so that these things get lowly
0:55:21
coupled so that even if
0:55:23
one of these functions break um
0:55:26
it doesn't kind of affect the other get
0:55:28
bored id and other functionalities
0:55:36
what do you think i mean it's pretty
0:55:39
much the same stuff though it's it's not
0:55:42
um do you think it's making a huge
0:55:47
i i mean i'm happy to do it the way
0:55:49
you're saying though like
0:55:51
it's it's pretty much the same
0:55:54
no no um so what i'm actually
0:55:58
trying to indicate that
0:56:05
let me put put it this way
0:56:14
kfc okay and then you also
0:56:17
run again mcdonald's right okay
0:56:21
so you go from your home
0:56:30
come back home drop the kfc
0:56:35
go back again to mcdonald's and then
0:56:38
come back home again is that efficient
0:56:41
or if you go from your home
0:56:45
get kfc get mcdonald's and then
0:56:49
and then come back home straight um
0:56:52
all right so you're doing this getting
0:56:57
but if you meet an accident on the way
0:57:01
um while like let's say kfc was burning
0:57:06
then yeah we don't even get mcdonald's
0:57:10
it comes down to which type of design we
0:57:13
do we want to um lowly couple it in the
0:57:19
why wouldn't we be able to get
0:57:23
the mcdonald's if caps
0:57:27
are broken down because the program will
0:57:29
stop if kfc is broken down
0:57:31
it's not that it's gonna skip the code
0:57:40
so you're saying that if we connect
0:57:48
travel between the kfc and
0:57:52
mcdonald's mcdonald's
0:57:58
okay let's um take something else
0:58:02
because i just don't see the point
0:58:06
of um i feel like it's pretty much the
0:58:10
if you if you strongly feel that we
0:58:12
should do it love it then
0:58:13
um i i mean like i'm really happy to do
0:58:18
i mean it's not gonna make any
0:58:19
difference though like we are anyway
0:58:21
gonna create a get board id
0:58:22
in at some point in the future so if you
0:58:25
wanna if you think that that's a way
0:58:27
better option then
0:58:28
uh i don't have in like i am just 5149
0:58:32
so we should go ahead and do what you
0:58:42
okay if you if you if you
0:58:45
if you go back to the to the
0:58:51
so in your thoughts um
0:58:55
the only reason why you've got that
0:59:00
one line from get board id to
0:59:04
get board id board id in them
0:59:09
in the middle way is because if one of
0:59:13
broke down then you uh
0:59:18
the application is still running is it
0:59:21
yeah and also because you know how
0:59:24
uh at some point in this code
0:59:28
we're gonna create a get board id
0:59:29
function in the middleware separately
0:59:32
like this is gonna come yeah even if not
0:59:36
so that means even if we are doing a get
0:59:39
we are having a redundant code that
0:59:42
this function is doing the same thing
0:59:45
which is being done
0:59:46
here you know what i mean if you just
0:59:50
exclude all of this like this is kind of
0:59:52
what you're saying right like
0:59:54
um if we just work with these two but
0:59:57
even if this is going here and doing
1:00:01
here there is a piece of code which is
1:00:04
getting the board id
1:00:05
which can rather be done with this which
1:00:07
is gonna come up eventually in this code
1:00:10
so it's just causing a bit of redundancy
1:00:14
i know where the problem
1:00:17
is and i'm i might have not been able to
1:00:23
properly i'll rephrase it so
1:00:26
you know how you've got um the board
1:00:30
id in the in the middle where
1:00:34
that's taking nothing
1:00:38
good yeah yeah no that's been called
1:00:40
from the front end
1:00:44
yes so that's in the front end isn't it
1:00:48
that's like being called from the front
1:00:52
yeah so that's in the
1:00:56
but hey it's in the middleware
1:00:59
i mean like front end is gonna like on
1:01:01
click this is gonna be cool or something
1:01:04
okay yeah yeah that's that's
1:01:10
i feel like it's fine then i think we
1:01:12
should just go ahead and um
1:01:14
um kind of change this diagram to what
1:01:18
because it's i know why i'm mean is is
1:01:22
about me or you it's about doing the
1:01:26
right thing and i'm just trying to
1:01:30
understand where you're coming from as
1:01:33
right no i was just thinking about um
1:01:36
code redundancy and independence but
1:01:38
um i feel like i also feel like
1:01:40
performance is more important um
1:01:42
when it comes to um high-level apps so
1:01:45
i was thinking more i'm thinking more
1:01:47
because i do java right so
1:01:49
when we do java these things come a lot
1:01:51
in play like um local
1:01:53
like um low coupling high cohesion stuff
1:01:57
but i think when we are dealing with
1:02:00
a bit of middleware the we can have a
1:02:03
bit of redundant code rather than um
1:02:06
visiting the database twice so
1:02:09
i i i do get your point though uh
1:02:12
and it's probably i think i get your
1:02:15
as well i'm just actually trying to
1:02:19
that as in what am i not understanding
1:02:24
understanding because that might be more
1:02:28
in terms of performance as well and
1:02:31
low low low coupling
1:02:36
that's where i'm at
1:02:39
right um it's just about um
1:02:44
i guess like you know how we're gonna go
1:02:49
like even if we delete this
1:02:54
um right even if we have these two
1:02:58
functions we're gonna go to get bored
1:03:01
yeah and we're gonna have a piece of
1:03:06
which is gonna go to the database and
1:03:09
board uh with the id
1:03:22
i think we can just um have
1:03:26
these two methods okay okay and
1:03:30
why i'm saying is because you know how
1:03:34
we are putting in the
1:03:47
front end and then we can return
1:03:51
from that function we can return the
1:03:55
and pass it to the back end
1:04:00
and bought the back end board and
1:04:04
do you get what i mean we'll have them
1:04:08
and you want to get the board id right
1:04:13
yes so in the front end we can
1:04:23
takes in the board name
1:04:27
right and returns a board id
1:04:34
okay but the board id is in the database
1:04:41
that's for my next thing was that we can
1:05:04
that's literally what we are trying to
1:05:07
and get the board name and then do stuff
1:05:13
is that what you're saying or is it
1:05:17
hang on a minute oh
1:05:29
now if you change the function
1:05:44
of the middleware uh
1:05:48
the bottom one [Â __Â ] it says
1:05:51
get bored i no no no sorry my bad
1:05:55
i'm i think i'm i'm confused
1:06:10
yeah oh okay yeah i was
1:06:13
confusing as both i just let's leave it
1:06:18
and we can we can take you from there
1:06:21
yeah i mean good design is really
1:06:23
important as well um
1:06:25
and i guess this was a good discussion
1:06:28
i mean both of our things were pretty
1:06:33
it's just uh um yeah what do we want to
1:06:36
do in the long term or like
1:06:37
which one is more efficient it's sec
1:06:42
clay and you will make some valid points
1:06:46
valid points as well i had some
1:06:49
valid points too yeah i think it's just
1:06:52
a matter of a little bit more
1:06:54
discussion and it will reach to our
1:06:58
because i really want to be satisfied
1:07:02
with what you're thinking and you have
1:07:06
successful on my mind so it's a mutual
1:07:10
for sure yeah yeah yeah all right
1:07:14
cool um it was a good day um
1:07:18
we got to know that we finished the
1:07:21
i mean at least we got the post working
1:07:24
tomorrow we're just gonna um start
1:07:26
working on this and probably
1:07:28
now we know how fetch apis work so
1:07:30
probably maybe finish one function
1:07:32
yeah and make it work as well so cool
1:07:35
see you guys tomorrow you have to
1:07:38
sounds good now it's been a great
1:07:43
we will hopefully start the
1:07:46
implementation of the new feature
1:07:57
oh he's just going to um like
1:08:00
we'll see you tomorrow night same time
1:08:05
same place same place same place
1:08:09
and a different task
1:08:14
cheers all right guys have a good night
