Tag Archives: week3

JavaScript…ouch

1 Reply

This week, I appreciate that our work was broken down into a small increment that was more manageable for me to work through and digest between last week’s class and this week. That being said, I definitely struggled with keeping all of the concepts straight, and I definitely took comfort in the fact that my fellow classmates had difficulty with some parts of the lessons as well.

One thing that confused me, and that I think Codecademy did not do a good job explaining, was some of the small pieces of syntax that got overlooked. Most specifically I believe this case was demonstrated when the syntax switched from regular parentheses to square brackets when writing out arrays — something I didn’t catch initially but only noticed when I worked through the problem for long enough. Things like this are very minute, but obviously make a difference when writing code. I also thought that the amount of knowledge (most specifically lumping in jQuery and JavaScript together) was a lot to comprehend. Even though it makes a lot of sense to learn those two language together, it was very hard for me to digest JavaScript and then jump right into jQuery — a language I don’t think was explained all that well.

One question that I had was about the explanation in Codecademy about generating a random card by using the Math.random and Math.floor functions. I wasn’t sure why you would multiply that function by 4, and where exactly that number and matching “card” came into play. Hopefully Greg will be able to shed some light on this, or hopefully walk us through this example and explain where the multiplication comes into play.

Overall I am looking forward to working through a couple of examples, similar to how we walked through the photo gallery last week, so that the overall structure of some of the jQuery concepts can be explained, and how that integration process works.

Muddling Through JavaScript Madness

Leave a reply

I do have to say that I found this a little easier than the combined HTML and CSS lessons. Somehow this was less confusing. Much of my trouble came from Codecademy’s unclear instructions.

I also wonder if there was a glitch with the program. I have no idea if other students had the same problem but for some reason when I opened some of the lessons, the code was already complete. The solution was simple, I just refreshed the code. But when you are just starting out it is a little confusing.

I also struggled with the directions at points. The exercise would say to write JavaScript but not where. As I found out, the placement of certain elements is very important. I did not find the hints helpful with this, especially since they often gave the answer instead of gentle nudges in the right direction.

Thankfully many of the codes are very similar and build on each other. I struggled with divs and how to put them together and the way they interact with the elements on the HTML page. Variables and functions though, I picked up easily. It is strange because structurally they are kind of similar.

Overall I had significantly less trouble understanding this than I thought I would. Surprisingly enough I found myself enjoying learning this language. Maybe my fear came from the way it was described in class. Or seeing the completed code in another language while I was still struggling with the first two. I’m not sure really, but I like it now that I have tried it. Will I say the same thing later this week while trying to build a photo slideshow? Will I have the same level of clarity as I do today? Watch this space in a week for my answer.

Javascript Confusion

1 Reply

After reading everyone else’s post thus far, I feel a little better. This weeks CodeAcademy exercises were very frustrating and confusing. I felt really good at first that I was really understanding everything. That was all until logical operators and functions. The functions were easy at the start, and I was able to comprehend and write in comparison operators and if/else statements. However, I became very confused when logical operators and functions came into play. I think it might be because there wasn’t great visualization on the CodeAcademy exercises.

Later in the course, I thought that the Array was very easy to understand. I found this to be a simple concept and way of creating lists. However, I’m not exactly sure what those lists would mean when put onto my HTML website. I think I am having trouble deciphering HTML, CSS, and Javascript and what they all mean separate from each other, and added together. I am praying that one day this will be made into an easier process.

I am worried that I will have trouble with the rest of this class and am starting to get a little stressed. I spent about 3 hours trying to learn this language, and still have a low understanding. I think that it will help me in the future to have classes that really walk through the basics. Last class was lost on me as I am a visual learner and don’t think just talking through the different things JavaScript can do was of much help to my learning type. I really do like the CodeAcademy that it walks you through the basics, and think bringing it down to that level in class would be extremely helpful.

Overall, I think I still have much to learn when it comes to Javascript and hope to learn more in the next class!

Logic, or JavaScript?

1 Reply

I struggled mightily with this week’s Codecademy lessons. I knew that JavaScript relied heavy on logical values and statements to perform its functions, but I did not anticipate just how difficult these things would be to comprehend.

I worked on lessons one, two, and three prior to the June 7 class so that I could at least have a basic understanding of what our lecture that night was going to cover. I was able to make it through lessons one and two fairly easily and with few issues. Lesson three, however, proved to be a different beast. No matter how many times I re-read the descriptions and instructions, there were certain steps that I was unable to perform correctly and move past. For the first time this semester, I was forced to use the “get a hint” and “get the code” tools during this lesson module. I’m not happy about having to do that, to say the least, but it was a necessary step in order for me to proceed through the exercises. I went back through each lesson and looked at the correct code, which helped me to see where I went wrong when trying to complete the exercises.

Completing the first few lessons prior to class enabled me to follow Greg’s lecture more easily. As we looked at the JavaScript code of the slideshow sample, I was left wondering where exactly the console.log property comes into play. This is something that figured heavily into the Codecademy exercises, but I don’t recall seeing it come up during our in-class analysis of the example of JavaScript code. Is the console.log something that is specific only to Codecademy when printing the output to the screen, or does it have real-world applications?

I thought the lessons on JQuery were interesting, and I appreciate that there is an easier way to interact with elements in the DOM that does not require us to write such lengthy JavaScript code. I am dreading having to memorize the JQuery commands, as they are difficult to understand (I needed more hints during this lesson, too). I find it difficult to memorize and truly learn the concepts as I work through them on Codecademy, because referring back to an earlier concept requires hitting the back button and navigating away from your current page. I’ve started copying and pasting the entire lesson into a Google document so that I can refer to earlier parts of the lesson while working on the current module. My Google doc for the JavaScript and JQuery lessons 1-5 is 41 pages long.

I’m hoping that our June 14 class lecture will help me make more sense of the concepts I encountered in the Codecademy lessons. I look forward to applying these concepts through the slideshow exercise in the coming week.

The Struggles with JavaScript

Leave a reply

I now see why everyone had difficulties with JavaScript. Completing the exercises on CodeAcademy this week was brutal. I spent five straight hours trying to code for it.

The problems I have with it are that the code is fickle. In journalism and public relations, creativity is key. No one can copy your voice, your thoughts or your reporting. In coding, the answers are the answers. While there is a little creativity in how you create your code, knowing how to do it is straightforward. In other words, you cannot BS code.

What was challenging about the exercises was that you had to remember every little thing in order to do the next exercises. I kept having to do hints to help me remember how to code or what to press or what to do. I’m honestly scared of what comes next, but I just have to keep working hard in order to master this. Once I can do it, I’ll be so proud of myself.

As a feminist, it is so important for me to learn how to code. On Linkedin, I always see tech employers discuss how they get hundreds of applications for a tech job opening, and very few are from women. There are so many male coders, but not many female tech employees. There needs to be more representation of women in many industries, but especially in tech, considering some of the workplace drama that has been happening in startups and tech enterprises.

There were days this week when I was tired from work, extracurriculars and schoolwork. Still, I need to remind myself to keep striving, keep pushing and remember that anything worthwhile requires time, effort and patience. I’ll just have to keep practicing in order to get any better.

One thing I am excited about is working on our developer profile. One of the reasons I enrolled in the Journalism program is because I love interviewing and learning about people and why they decide to do what they do. I’m already researching some leads on Linkedin and cannot wait to get started.

JavaScript or jQuery, That is the Question

1 Reply

June 11, 2017
11:09 PM

I was an idiot and did almost all of next week’s jQuery exercises before realizing that I was in fact on the jQuery page and not this week’s JavaScript page. At least now I know why I was so confused. But, needless to say, a dastardly start to this week’s homework.

I learned the abstraction before I even knew I what I was abstracting. I am, however, happy to say that I am now adept at navigating the murky depths of the Codecademy Question Forums. I’m also grateful that now I will understand the “why’s” and “how’s” behind the “what’s” of my mediocre accomplishment. I had no idea how I was supposed to know how to write the beginning JavaScript. But! Now I can use functions. Sort of. So, that’s exciting. Out of frustration and sleepiness, I am going to bed. Thank god I have some time to tackle this tomorrow.

June 12, 2017
7:53 PM

Well. Now I have stuck my toe into the cold lake of JavaScript, and it is not as logical as it seems. I really do feel like I’m drinking out of a fire hose–mostly because I’m building concepts that are built on top of shaky concepts. I’m definitely going to need to review this and ask a bunch of questions on Wednesday. It makes me kind of concerned about going forward, but I also am gaining confidence in my ability to google stuff, which I’m trying to tell myself is all that matters.

The exercises make sense…mostly? But it feels like something finicky is going on with the Codecademy stuff, but I don’t know if it’s just me. For example, I’ll start an exercise and it will say I am wrong before I’ve even clicked anything. It’s frustrating, because then I just have to click through and I’m not exactly sure what I’m supposed to be learning.

I will say, I’m feeling some serious solidarity with my fellow classmates, and that’s encouraging.

I may need to stick to BASIC

2 Replies

I left this Codecademy lesson probably more confused than when I started. I found myself searching for whatever code would allow me to progress to the next page with very little to no grasp of what I actually did. No matter how many times I looked back on what I did, I could not figure out why or how I managed what it is I did.

My JavaScript experience in Codecademy was like night and day to how I felt when I had completed HTML. And yes, I do know that HTML and JavaScript should not be compared because we’re talking about two way different things, but it’s a pretty bad feeling to be sitting behind your computer for hours and still not feel that overwhelmingly short rush of victory once it is completed.

I would prefer the answers to be given to you at some point beyond just hints because at several points in this lesson, I found myself just completely off-track. I read one of Rob’s posts before and he made a good point that because there’s no such thing as really cheating, there is no reason why the answers could not be displayed somewhere. After hearing from our guest speakers, I understood that programmers often grab and add-on to other codes they find, so it’s not like it would take away from our learning if we had them as an option. By not having them, I found myself focusing more on how to complete this task on time, rather than really learning. Also, I’m curious if I’m just an extremely slow learner or if these assignments are taking everyone over 7 hours to figure this stuff out.

Now that I’ve complained this entire post, I will admit that I do understand why JavaScript is so necessary for a website to really catch and keep your attention. Even the most basic interactive websites use JavaScript and knowing that, I will continue to struggle but try as hard as possible to figure this out before the semester is over.

JavaUNscripted

1 Reply

It has by far been the most frustrating weeks of learning in the web development course.

JavaScript is not the easiest to comprehend, and yet it accomplishes some of the greatest tasks on the Internet.

The Codecademy lessons were somewhat informative, but also not easy.

Due to a work/vacation trip I had to work on the lessons before Tuesday’s class. Learning from a written lesson is not the best way of learning for me, and the errors on Codecademy don’t provide much assistance. I found myself in the forums a lot looking for key pieces of information, evaluating other coders who also had broken code and comparing them to mine. I finished the lessons before Tuesday class which I imagined would give me a leg up in class, but I was sorely mistaken. There were a lot of key terms and lessons that weren’t even a part of the Codecademy section.

I appreciated Emily coming into the class and diving deep into JavaScript and the console. I think I learned a good amount from it. I’m sure I forgot a lot of it during the trip, so we’ll see how much I retained.

The image gallery we built was by far the biggest frustration so far. After three cups of coffee, 4 hours of googling and repeated cursing, I finally figured it out and it was the simplest work around I could have imagined. Thankfully it works and I never have to look at that gallery again.

Week 3

1 Reply

General

I never thought web-development was going to be so complex. There are so many details, and different rules that you have to remember. It is a bit insane. So far I am enjoying learning the material, especially the stepping-stones: start with HTML (titles, body, and paragraphs), add some style to the verbiage which you create to make it lively through CSS (create ID’s, change fonts, change font-styles) and finally add some interaction to your HTML and CSS creations through JavaScript.

Codecademy

Codecademy is a great learning mechanism, it provides step-by-step instructions. The only functionality that is a somewhat disappointing is the hint feature. The feature seems to be hit or miss. Some of the exercise have very clear hints others are clear, but not at useful. I have truly learned to appreciate bloggers who have posted their Codecademy questions, especially the JavaScript paper, rock, scissor blogs. That exercise was pretty difficult in my book.

Questions

1. How long did it take you to learn how to code and what language did you start with?

2. What source can I look at to create a form? I want the webpage that I create for class to have a registration sheet which includes a name (first and last), address, phone number (required field), Date of birth, and a free text field which for medical history. Will we be learning about these features in class? Can these functions be written using HTML, JavaScript?

3. Is it possible to gather information from a registration page without a database? If yes, how? If no, which database option is the most effective?

4. What webpage do you recommend for leveraging tab features, specifically: home, about, contact us, testimonies

I am really excited about creating my own web-page, but at the same time am feeling overwhelmed, there is so much to learn.