When CHEAT SHEETS are allowed, all I want to do is celebrate!
I was half way through Unit 15 in the Artes Latinae Project, when I realized that there were a lot of frames that needed repetitive XML code. Rather than retyping everything over and over, I decided to make a cheat sheet! I opened my "Notes" on my Mac, and typed up a very nice and organized cheat sheet that contained all of the codes I needed for my project.
I was feeling pretty proud of myself until I tried to load my project. I kept getting error messages. I would do an XMLLINT on my file and the errors kept popping up. I could't figure out what the problem was so I finally had to ask Marco for help.
As usual, he came running to the rescue. The code where I was getting errors on "appeared" correct, but on further inspection by him, he found that my "quotation marks" looked slightly different. Apparently, when I typed the code in "Notes", it changed the quotations to curly instead of straight (like in my Sublime Text Editor for XML). Just that slight change caused error messages to appear all over the place.
I quickly learned the importance of making a cheat sheet IN my Sublime Text Editor (with XML selected) so that the code would not be altered. Here is what my new cheat sheet looked like once I made it in Sublime:
I was able to position this XML cheat sheet file next to my Sublime file that contained the XML code for my project; that way, I could copy and paste side by side. It made coding repetitive codes go fast.
The picture on the left is of the Artes Latinae Project, the picture on the right is my cheat sheet.
I guess there are times in life where cheat sheets are definitely encouraged!
Follow me as I learn to build my website bit by bit! IronTreeDev.com
Photo by Ben White on Unsplash
I was half way through Unit 15 in the Artes Latinae Project, when I realized that there were a lot of frames that needed repetitive XML code. Rather than retyping everything over and over, I decided to make a cheat sheet! I opened my "Notes" on my Mac, and typed up a very nice and organized cheat sheet that contained all of the codes I needed for my project.
I was feeling pretty proud of myself until I tried to load my project. I kept getting error messages. I would do an XMLLINT on my file and the errors kept popping up. I could't figure out what the problem was so I finally had to ask Marco for help.
As usual, he came running to the rescue. The code where I was getting errors on "appeared" correct, but on further inspection by him, he found that my "quotation marks" looked slightly different. Apparently, when I typed the code in "Notes", it changed the quotations to curly instead of straight (like in my Sublime Text Editor for XML). Just that slight change caused error messages to appear all over the place.
I quickly learned the importance of making a cheat sheet IN my Sublime Text Editor (with XML selected) so that the code would not be altered. Here is what my new cheat sheet looked like once I made it in Sublime:
I was able to position this XML cheat sheet file next to my Sublime file that contained the XML code for my project; that way, I could copy and paste side by side. It made coding repetitive codes go fast.
The picture on the left is of the Artes Latinae Project, the picture on the right is my cheat sheet.
I guess there are times in life where cheat sheets are definitely encouraged!
Follow me as I learn to build my website bit by bit! IronTreeDev.com
Photo by Ben White on Unsplash
Comments
Post a Comment