rmurphey3
Joined 16 years ago
Karma
377
Submissions
48
Member since
Jun 19
Recent submissions
Comment · 10 years ago
Comment · 14 years ago
Comments like this make me so excited to write more posts. Thanks.
Comment · 14 years ago
Thanks for the suggestion. Look for it in a future version!
Comment · 14 years ago
I won't address the rest of your comments, but please note that I said "tools like UglifyJS or Closure Compiler" -- if the RoR asset pipeline is taking care of this for you, then good! The point is that good front-end devs should be aware of the need for tools that address the various high-level topics I listed -- I just mentioned some tools that fill those needs for me.
Comment · 14 years ago
My fear with doing that is that if the functions file is separated from the tests file, then it becomes difficult to see at a glance what the function needs to do in order to make the test pass. That said, I agree that what you're supposed to do could be more clear -- would you care to open an issue so we can discuss it on the repo?
Comment · 14 years ago
I definitely want to add more tests to the set -- if you have ideas for other tests, please open an issue or a pull request on the repo!
Comment · 14 years ago
Thanks for the great feedback -- it occurred to me that people could simply hard-code the "right" answers into their function. However, if I am using this to assess a candidate, I plan to actually read the code that they write :) And if a person is using this to assess their own skills, I trust that they know that an answer like the one above hasn't taught them anything.
Your guess about why I chose something that involves a little bit of setup is right on target, too. Being able to follow the instructions in a readme and get a simple project like this set up is a key skill to have, too.
Comment · 14 years ago
The exact set of skills that one needs in order to do one's job will of course vary from person to person. What I have tried to point out in this post is that these topics are ones that anyone who calls themselves a front-end developer will need to be familiar with; if they are not familiar with them, then they risk being unable to keep up with the new information that is being shared about the front-end dev profession. This is based on my observations as much as my beliefs -- the set of things that you're expected to know in order to actively participate in the open-source front-end dev community is growing and changing, and this is my attempt to catalog those things in a way that I wish someone had done for me in the past.
Comment · 14 years ago
I hope I gave due credit to the possibility that part of what's changed is me when I said in the next sentence: "Maybe it’s the result of people starting to take front-end dev seriously, maybe it’s browser vendors mostly getting their shit together, or maybe it’s front-end devs – again, myself included – coming to see some well-established light about the process of software development."
I do think the profession of "front-end development" has grown up a whole lot in the last couple of years. There have been front-end pros since long before I was even in the business, but I think the profession as a whole is being taken more seriously, and a set of baseline expectations for people in the profession is solidifying.
Comment · 14 years ago
You are right, all of this can be done via makefile ... assuming you know how to set up a makefile and take the time to do so. Part of the goal of grunt, as I understand it, is to make it so developers have fewer excuses for not doing this -- setting up a project of a certain type becomes a one-liner. To me, that feels a whole lot simpler than suggesting that developers create the makefile you propose. More often than not, such suggestions result in projects that have no makefile at all -- and thus no tests, no minification, no linting, etc. If grunt helps developers integrate those best practices more easily, that feels like a good thing to me.
Comment · 14 years ago
Much love for Alex Russell and for efforts to move the web forward as a serious development platform, but this was among the more content-free stories I've read in a long time. If you'd like to actually learn about "model-driven views," the component system the article mentions, head over to http://code.google.com/p/mdv/.
Comment · 14 years ago
Yes, the point of the post was that it had a lot more to do with being a kid with a computer than with being male or female. The point of the title was that it was a story of ... a girl and her computers :)
Join a small, talented team that’s focused on radically changing how we approach front-end application development at Indeed. As an early team member, you’ll have significant input and influence on projects like a shared component library for UI development; tooling to make it easy for engineers to spin up and build new client-side applications; common systems for measuring and monitoring application performance; and more. You’ll evangelize front-end best practices to teams around the world, help them incorporate those practices into their development workflow, and take your learnings back to the front-end systems team to develop new tools. You’ll also help identify and mentor individual developers throughout the organization who will be the ultimate source of the front-end systems team’s success. Your work will increase the velocity of every developer who touches client-side code; it will impact hundreds of millions of job seekers around the world; it will — quite literally — change the face of Indeed.
---
The interview process will include a screening exercise and, for successful candidates, a day of on-site interviews. The process will focus specifically on identifying candidates with the required technical and communication skills necessary for the role; expect to talk about vanilla JS, maintainable CSS, client-side performance, testing client-side applications, designing and developing front-end systems to be used across projects, and communicating effectively with technical and non-technical audiences.
---
More information: http://www.indeed.jobs/career/JobDetail/Front-End-Engineer-S...