VDubinator Coder

Ever since my first job as a web developer, I've loved the language of JavaScript. The freedom, the flexibility, the power. With JavaScript, you can have it all! But, JavaScript had some weird parts to it. Well, they're not really that weird, but they're just different enough from C or Java that it throws a lot of people through a loop. However, once you learn more about the language, you can easily handle even it's strangest pieces. Because of my love for JavaScript, I decided to take Pluralsight's IQ assessment for JavaScript to see how I stacked up. I ended up getting a score of 219 which is good for an"expert" level. To be honest, I was a little disappointed with the result. I thought I knew it better than that! So here's a look at what I missed and what the correct answers are and why. Missed Questions Missed Question 1 This one I was just going to quickly on and fell for a similar answer. Suffice it to say, there is no eval() method

To lead, or not to lead, that is the question: Whether 'tis nobler in the mind to write code That may change the very world as we know it, Or to seek for positions of leadership And by managing guide them. To lead--to code, No more; and by "to lead" to say we end The heart-ache and the changing requirements That Scrum is heir to: 'tis a Lean-Agile dream Devoutly to be wish'd. To lead--to code; To lead, perchance to dream--ay, there's the rub: For in that leadership what dreams may come, When we have shuffled off this legacy code, Must give us pause--there's the respect That makes the coding of so long life. For who would bear the scrum master's bold whips, The sales pressure, the program's fickle heart, The pangs of quality, the changing dates, The insolence of process, and the spurns That patient merit of th'unworthy takes, When he himself might his own tests make With a blank keyboard? Who would fardels bear, To grunt and

"Wow! I didn't know there was creativity in software engineering!" Such was the reaction I received recently when I explained what I did for a living. And it's completely understandable. For most people, when they hear "computer programmer" or something similar, something like this comes to mind: We often picture dark rooms, stale pizza, and poor hygiene. Or we picture mind-numbing hours spent telling the computer what to do and finding small errors like a misplaced semi-colon. But the stereotypical views on programming are hardly the reality of it. While there are times when some of these stereotypes may be true, that's definitely not the norm. At least not in my experience. The reality is that software engineering generally goes best when engineers are allowed to be creative. That may not be the case for everyone every time, but it holds up in the general case. When engineers are allowed to be creative, they're often more engaged in t