Skip to content

Instantly share code, notes, and snippets.

@eads

eads/a-baseline-for-frontend-developers.md

Created April 24, 2012 02:42
Show Gist options
  • Save eads/2475700 to your computer and use it in GitHub Desktop.
Save eads/2475700 to your computer and use it in GitHub Desktop.
Download ZIP
R Murphey post outline
Raw
a-baseline-for-frontend-developers.md

Rebecca Murphey's "A baseline for frontend developers" http://rmurphey.com/blog/2012/04/12/a-baseline-for-front-end-developers/ in tweet form:

  1. Learn Javascript, then jQuery. Learn from the best.
  2. Use Git. Get a Github account.
  3. Use build tools and dependency management.
  4. Use in-browser development tools and learn debugging skills.
  5. Develop strong command line skills: ssh, scp, grep, ack, find, package managers and tools for OS and platform.
  6. Use client side (Javascript) templating for structured data.
  7. Write CSS using preprocessors like LESS and SASS.
  8. Test first, test often using tools like Grunt and Jasmine.
  9. Dot your i's, cross your t's, and use tools like JSLint to clean up your code.
  10. Use automation to make your life easier.
  11. There's no manual, but Mozilla Developer Network is very handy.

Editorializing:

  1. A get-it-working sysadmin ethos helps a lot. Search and add to Stack Exchange sites as a gateway to open source participation.
  2. MDN is one of the best reasons to donate to Mozilla.
  3. In-browser dev tools: Start with Chrome or Firefox, then Opera and IE or mobile simulators as situation demands.
  4. Pick open source projects based on how willing you are to contribute.
  5. Use whatever form of lightweight task + project management fits your purposes: meetings, scrums, issue trackers, white boards, et al.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment