Let's continue adding features to this application by taking a look again at our requirements.
So what we're going to see here is now we have a few things implemented.
We have the basic functionality.
I think also the column functionality is partially in place.
We're going to check in a second.
Pretty much what we need to do is implement this additional functionality.
And we also have card editing.
So there are a lot of things that we can still do step by step and ask lovable to build this particular
functionality.
It's also super important at this point in time to mention that the code that we have is getting more
complex.
It is very likely that at one point in time, lovable is going to ask you to refactor the code, but
just as well, it's very likely that you.
You'll also notice that maybe it's very difficult to add additional features.
So if lovable is not prompting you to refactor a specific file because it has too many lines, it's
also not a bad idea to directly prompt lovable and say, hey, we already built so many features.
Take a look at the code, analyze it, see if there's anything that needs changing there.
And even before you go directly into making changes, you can also use here this chat option so you
can console yourself with lovable in terms of the state of your code base, and ask it to do a refactoring
if that is something that's needed.
You can also go ahead and inspect the code yourself.
If you go here into dev mode, you have here under source you have components.
For example, you have the board itself.
You can already take a look and see how many lines of code are inside this particular file.
So this one has almost 200 lines of code, this one only 75.
So there are files that are longer and files that are a bit shorter.
So that's always a good starting point.
There are also many other things here that are relevant.
So in a nutshell this is how you can continue developing this application step by step by referencing
the Todo, taking a look at the changes that have been done, you need to do tests on your own to ensure
that the application is working properly, refactoring from time to time, going to the next task,
and so on.
And if you think you need changes, always go back to the specification, add additional details there,
because then everything that you have in terms of the application is managed from a single place, and
you can simply take that and reuse it as needed.
So now we have column management in place and I'm going to go ahead and test this.
Just want to show you the main idea behind this.