# data[].attributes.headline
I like to implement the code on a daily basis and use it live, and do so among ourselves and change the general attitude.

# data[].attributes.subject
I like to implement the code on a daily basis and use it live, and do so among ourselves and change the general attitude.

# data[].attributes.body
It was good to delve deeper into various topics, as well as to be able to talk to the TL about the time needed for in-depth study in order to improve our learning and adaptability.

# data[].attributes.body
Better feedback on topics was achieved, allowing for much greater depth in exploring them.

# data[].attributes.headline
Although the topics are good, sometimes it is not possible to do them due to time constraints, but having a solid foundation should be the priority in this process.

# data[].attributes.subject
Although the topics are good, sometimes it is not possible to do them due to time constraints, but having a solid foundation should be the priority in this process.

# data[].attributes.body
I think that covering so many topics at the beginning was a bit overwhelming, as was the speed at which they were explained. There was also a lack of information to enable us to explore and understand the topics better.

# data[].attributes.body
The knowledge of how certain libraries work and how to use them within an MVC structure.

# data[].attributes.body
clear tasks and assignments :3

# data[].attributes.body
Some changes in the classes, the preparation of other classes, and the learning methodology.

# data[].attributes.body
I think we can improve independent study a little more. It would be good to share study links or do something more dynamic that isn't just theory and code, so that we can better digest all the information and learn more easily.

# data[].attributes.body
the learning methodology.

# data[].attributes.body
In my opinion, we had good communication as a group. When we didn't understand certain topics, a solution was found that improved things a little. In addition, the topics were understood very well.

# data[].attributes.body
For me it's important to note, that we are not perfect, this week we take the time to review the things we need to improve with our TL, we learn many concepts that provides us a lot of knowledge.

# data[].attributes.headline
I stayed consistent with my studies and managed my time better. I also felt more motivated during the week.

# data[].attributes.subject
I stayed consistent with my studies and managed my time better. I also felt more motivated during the week.

# data[].attributes.body
I think live coding is a gigant help for our learning and it was good the TL took his time to explain while he was doing code so we can follow the topic easier but I think in cors and ZOD was lack of explanation

# data[].attributes.body
It's good to know that we can follow TS, node and this topics in a way that everyone understand and give us the time of learning and develop our application

# data[].attributes.headline
Perhaps implementing the use of more focused cells and, in turn, creating individual projects for each class, adding to a more robust code for each cell while using the methodologies.

# data[].attributes.subject
Perhaps implementing the use of more focused cells and, in turn, creating individual projects for each class, adding to a more robust code for each cell while using the methodologies.

# data[].attributes.body
At first, the topics weren't easily absorbed, people were biased, etc.

# data[].attributes.body
The methodology has changed, and now it is easier to understand the topics with the right amount of time and the correct explanation.

# data[].attributes.body
We need to do it beetter with our 70% of independent study, and we can improve the learning methodology

# data[].attributes.body
Prepare a Readme file in advance that describes what we need to do, the criteria, and the technologies/libraries to be used. Like the userstory :b

# data[].attributes.body
This week I was able to understand better how cors, middlewares, cronjobs and nodemailer worked because of the explanations from other coders and further information provided by the TL and even though we were suposed to not use the index.ts for the routes that we used the last week, I use it and I undertood much better how it functions thanks to the TL support

# data[].attributes.body
We have improved the communication and it helped us to get better results when we was studying the topics again

# data[].attributes.body
Prepare classes better and better, conduct a weekly Kahoo-type survey to get an idea of how well the topics were understood, assign exercises, weekly challenges.

# data[].attributes.body
We did well to do live coding and go step by step, topic by topic, so that everything was clear. I liked that we first presented the concept and then moved on to the practical part. I liked the links to the documentation.

# data[].attributes.headline
More time for explaining code and reviewing the understanding 

# data[].attributes.subject
More time for explaining code and reviewing the understanding 

# data[].attributes.body
it felt good that due to repetition and the time spent on exercises this week my understanding overall the sbjects reviewed felt more in dept

# data[].attributes.headline
Sometimes I got distracted and couldn’t focus as much as I wanted. I also felt a bit tired on some days, mostly because of external things.

# data[].attributes.subject
Sometimes I got distracted and couldn’t focus as much as I wanted. I also felt a bit tired on some days, mostly because of external things.

# data[].attributes.headline
I think it's better to have a good guide

# data[].attributes.subject
I think it's better to have a good guide

# data[].attributes.body
As an experience I learn better with visual help so I know what to do and how to do it, otherwise I got lost and don't know how to implement the topic on my code

# data[].attributes.headline
We could have moved a bit more towards learning new concepts

# data[].attributes.subject
We could have moved a bit more towards learning new concepts

# data[].attributes.body
since thursday I felt we didn't do much with the time spent here and it could have been important to use the time to learn more

# data[].attributes.body
The class was very good in general, but I would like to do more dynamic activities.

# data[].attributes.body
I feel since we did not do much on the last 2 days, we could have spent the time by ourselves studying

# data[].attributes.body
trying to teach many topics at the same time and moving forward without being clear about the topic

# data[].attributes.body
We need to do it beeter with our 70% of independent study, and we can improve the learning methodology

# data[].attributes.body
There were delays due to a lack of clarity in some requirements.

# data[].attributes.body
Include more practical exercises, not just the basics.

# data[].attributes.body
I think it's a good idea to see how things are done first by TL and then try to do them ourselves, but with that starting point, which would be analogous to live code.

# data[].attributes.body
I think that is still not completely clear the projects or tasks that we have to be doing each class

# data[].attributes.body
I understand a lot when they give examples of usage when explaining a concept

# data[].attributes.body
for the theory try to implement a most dynamic way to learn, like more kahoots or other methods

# data[].attributes.body
We can start using tools like azure or Jira and we could also start making team projects using those tools with SCRUM methodology, and also I think that drawing things would help to understand some concepts

# data[].attributes.body
I think that from the beginning, the topics were not addressed very well. We went too fast, and the topics were not clear, nor was it clear how to implement them, or how much time to give to each class. In conclusion, I think that only at the beginning did we not have a good class methodology.

# data[].attributes.body
Monday was a fantastic day because the topic was covered and explained very well, but thursday was more difficult because we went back to the first day when we couldn't understood the topic very well and got lost when the TL make us implment it in our code, as well I think it's important that the TL explains the topics instead of someone else do it, because he have more experience and clarity on it, we, as students whose are leaning don't and sometimes we can explain it in a very good day. I think it's important to explain it in a good way that everyone understands and slowly.

# data[].attributes.body
We as a team have already improved, and we will continue to apply what we are doing, but I believe there is always some for improvement, such as practicing exercises on topics that have already been explained.

# data[].attributes.body
totally disagree with sharming