Top Job Applicants Never Stop Learning

From time to time, my job allows me to be a part of the hiring process for our technical positions. Unfortunately for some of the applicants, I repeatedly come away from these interviews amazed at the responses I get from pretty standard and basic technical questions related to Web Development.

Recently we were looking for a front-end web developer that was good at UX and design and proficient at HTML, CSS, and JavaScript. One of the things that we tend to ask everyone is to rate themselves on a scale of 1 to 10 as to how good they are with each technology. The majority of responses are in the 5-8 range with the corresponding answers to the questions about each techology falling about in the range you would expect. A couple of applicants were brave enough to rate themselves at a 9.5 out of 10 on HTML, CSS, and JavaScript, leading us to believe they were “exceptional applicants”.

Intrigued, we began to delve into the technical questions about each technology. One of the first questions centered on the applicant writing a snippet of CSS that made the text in a div blue. The typical applicant would attempt to write the appropriate CSS rule with a couple of slight syntax issues, but would successfully complete the task. It never failed that the “exceptional applicants” would look at the sample HTML for a couple seconds and then proclaim that they didn’t remember how to do it. A common excuse for not knowing how to begin to answer this simple CSS question was that they didn’t memorize anything since you can easily just go look it up on Google or Stack Exchange when working on a real project. I don’t know about you, but when I think of a non-entry-level front end developer, I am not envisioning an employee that has to look up on Google every line of JavaScript and CSS that they write.

This may make me sound old, but I’m willing to risk it. There are way too many people out there that believe that they don’t have to learn, or ‘memorize’ as they refer to it, anything as they can always go find it on the Internet. Unfortunately for people like these “exceptional applicants”, writing CSS, JavaScript, and HTML by hand is something that you should be able to do the vast majority of the time without consulting Google or Stack Exchange for the way to do it. If, however, you attempt to write the code by hand first, determine it doesn’t work the way you anticipated, and have exhausted things to try to make it work correctly, then it is time to look online for the answer.

A competent front end web developer should be able to perform their major job duties, which includes writing CSS, JavaScript, and HTML without the need for any internet or network connection on any of their various devices. Even without a connection, they should be able to create a mostly functional webpage that is ready for peer review and testing.

Since it seems too rare, the Never Stop Learning motto should become the motto of more professionals eager to climb the occupational ladder, lest we forget that there is more to learning than wrote memorization.

Related Posts

Mar 31, 2014
2 minutes

JavaScript Templating

Many times it becomes useful to be able to make an AJAX request for some data, insert it into some HTML that is already on the client, and then display it to the user. There are a few ways to implement this, each approach has its benefits and drawbacks.

String Concatenation

Possibly the simplest way to accomplish the templating in JavaScript is to use simple string concatenation with ‘+’. This is the approach that I see many newcomers to JavaScript use in their code, as it is the simplest to implement. However, it does have a major drawback in that this method has the worst performance of all, especially in older versions of Internet Explorer. This could be implemented as below:

Apr 29, 2014
2 minutes

Avoid jQuery.bind()

When chasing down performance issues, you never know what kind of problems you will find. I was looking for something that would cause jitter when scrolling on the page. After looking at the custom code that runs on every scroll event, I still had not found a reason for the jitter. Looking at the JavaScript CPU profile when scrolling in Chrome showed that there was an overwhelming majority of the time spent in a function in the Prototype JS library.

Jun 10, 2014
3 minutes

5 Ways to Do SCRUM Poorly

As a developer that frequently leads projects and operates in various leadership roles depending on the current project lineup, the Agile development methodology is a welcome change from the Waterfall and Software Development Life Cycle approaches to software development. SCRUM is the specific type of Agile development that I have participated in at a few different workplaces, and it seems to work well if implemented properly. However, there are several ways to make a SCRUM development team perform more poorly than it ought. The top 5 I have seen include: