Our latest venture into the programming world has been working with event listeners in JavaScript, and learning how to “code” in markdown.
My had a few first impressions of event listeners. A few of them were “holy crap, there’s a lot to this,” and “oh my God, I’m drowning in new material.” Just like anything else with JS that we’ve learned so far, event listeners have been complicated. However, I think it’s probably the most fun I’ve had with JS so far, since now there’s a certain level of interactivity on the web page. I also get the feeling that it’s going to be similar when we learn jQuery: frustrating and stress-inducing at first, but fun once I get the hang of it.
When it came down to working on solo exercises where we implemented what we’ve learned about event listeners, I still needed a bit of nudge in the right direction. But after I got that initial push, it was much easier to handle the rest of the steps in the coding exercise. I’ve come to realize that, more than likely, every week there’s going to be moments where I freak out because I don’t know what’s going on, followed by a bit of crying, followed by assistance from a friend, and wrapped up with a general understanding of what’s going on. And I think I’m ok with this.
We’ve also learned about markdown, which is a way to “code” inside your README.md file. There really isn’t much that I have to say about markdown, aside from being excited to discover that the syntax is relatively painless to learn. It can almost be compared to learning about the formatting rules that Microsoft Word implements.
Other than those two things, there’s not much else to report. I shall speak with you next week after I have my next mental breakdown!