WEBVTT

00:02.120 --> 00:07.520
Let's continue adding features to this application by taking a look again at our requirements.

00:08.160 --> 00:12.280
So what we're going to see here is now we have a few things implemented.

00:13.640 --> 00:16.400
We have the basic functionality.

00:16.760 --> 00:22.880
I think also the column functionality is partially in place.

00:23.320 --> 00:24.600
We're going to check in a second.

00:25.000 --> 00:28.120
Pretty much what we need to do is implement this additional functionality.

00:28.120 --> 00:30.040
And we also have card editing.

00:30.320 --> 00:37.760
So there are a lot of things that we can still do step by step and ask lovable to build this particular

00:37.760 --> 00:38.640
functionality.

00:39.000 --> 00:43.480
It's also super important at this point in time to mention that the code that we have is getting more

00:43.480 --> 00:44.240
complex.

00:44.600 --> 00:52.040
It is very likely that at one point in time, lovable is going to ask you to refactor the code, but

00:52.040 --> 00:55.320
just as well, it's very likely that you.

00:55.320 --> 01:00.720
You'll also notice that maybe it's very difficult to add additional features.

01:00.960 --> 01:07.560
So if lovable is not prompting you to refactor a specific file because it has too many lines, it's

01:07.560 --> 01:14.560
also not a bad idea to directly prompt lovable and say, hey, we already built so many features.

01:14.560 --> 01:19.800
Take a look at the code, analyze it, see if there's anything that needs changing there.

01:20.200 --> 01:26.160
And even before you go directly into making changes, you can also use here this chat option so you

01:26.160 --> 01:33.800
can console yourself with lovable in terms of the state of your code base, and ask it to do a refactoring

01:33.800 --> 01:35.520
if that is something that's needed.

01:36.360 --> 01:39.000
You can also go ahead and inspect the code yourself.

01:39.440 --> 01:45.720
If you go here into dev mode, you have here under source you have components.

01:45.720 --> 01:47.560
For example, you have the board itself.

01:47.960 --> 01:52.480
You can already take a look and see how many lines of code are inside this particular file.

01:52.480 --> 01:58.120
So this one has almost 200 lines of code, this one only 75.

01:58.160 --> 02:02.360
So there are files that are longer and files that are a bit shorter.

02:03.000 --> 02:05.280
So that's always a good starting point.

02:05.360 --> 02:09.040
There are also many other things here that are relevant.

02:09.680 --> 02:15.880
So in a nutshell this is how you can continue developing this application step by step by referencing

02:15.880 --> 02:21.560
the Todo, taking a look at the changes that have been done, you need to do tests on your own to ensure

02:21.560 --> 02:27.320
that the application is working properly, refactoring from time to time, going to the next task,

02:27.520 --> 02:28.200
and so on.

02:28.520 --> 02:34.240
And if you think you need changes, always go back to the specification, add additional details there,

02:34.640 --> 02:40.640
because then everything that you have in terms of the application is managed from a single place, and

02:40.640 --> 02:44.120
you can simply take that and reuse it as needed.

02:45.080 --> 02:49.680
So now we have column management in place and I'm going to go ahead and test this.

02:50.000 --> 02:52.360
Just want to show you the main idea behind this.