# data[].attributes.body
Organization is key!! Trial and error is the name of the game and it is unwise to write long sections of code at once. It is good to take long breaks when you can't figure something out and come back with fresh eyes. Most of the time you can figure out what was going wrong!

# data[].attributes.body
After going to class and hearing Mr. Bakker talk about the assignment I decided to go in and give things a second shot. I went slowly and decided to focus on fixing the margin-pamphlet look I had tried to go for previously. After a lot of trial and error on the w3bshools website I found my error was in using improper brackets. I finalized the website and it ended up looking exactly like I wanted.

# data[].attributes.body
It is important to organize code in a way that will allow you to go back in an make edits. My code ended up being incredibly unorganized and hard to edit. I called an end to the project and decided I would hand in a pretty plain assignment.

# data[].attributes.body
I was forced to meticulously go back through my code and try everything one by one. I only fixed things to the bare minimum requirements. I tried to do complicated things--like change the margins and create a pamphlet-like design--but I couldn't figure it out. I gave up and called it quits on the assigment.

# data[].attributes.body
I was very discouraged. I though everything should be working correctly and I had already spent multiple hours writing the code and my poem. I was ready to give up.

# data[].attributes.body
I learned that it is not smart to add a lot of parts of code at a once. It is better to go step by step so you know--if something goes wrong--where the error lies.

# data[].attributes.body
I grouped the poem into three sections which I thought had some sense of a logical theme; although, the poem was largely a stream-of-consciousness piece. I added each place to the template of code and tested it as a whole. The first time, nothing showed up on the web page the way I wanted. I was left unsure of what went wrong in a sea of unorganized code.

# data[].attributes.body
This was pretty straightforward. I wasn't trying out any of the code I had written. This felt proportionally easier than actually writing the poem.

# data[].attributes.body
I began by writing out a very basic template of code. I tried to enter as many of the required features as I could; that was my only focus.

# data[].attributes.body
I was frustrated because I felt like I was taking too long to write the poem, and I felt that the quality of what I was producing didn't correlate with the amount of time I was putting in.

# data[].attributes.body
Taking inventory of myself was difficult. I struggled to talk about myself. I preferred to talk about what I did instead of who I really was.

# data[].attributes.body
I began by writing my "I am from poem" independently from the code. I reflected deeply on who I was, what I did, my past. my future, and the present. I considered both who do I want to be? and who am I? I tried to answer both of those questions in my poem.