I am an experienced software engineer, and have built things with JS. I have used jQuery quite alot, and written OO jQuery modules; but I can also write from raw JS. As a full stack in JS, I tend to:

  • All my code is “use strict”. Due to writing in other languages before JS, I rarely hoist;
  • I would like to use ES6 but don't think that there is enough support in browsers (this is improving 1). I am es5-shim-ing for older versions of MSIE;
  • I have some recent commercial experience in Node. In a particular project, I am extending it, the first version was built with Mongoose and Express. Koa would be a better framework, IMO;
  • I prefer to write in objects, it makes testing easier and cheaper;
    • I am flexible, but think improved ObjectLiteral is the best form of objects in JS;
  • I unit test, historically using qunit, as it is a really small dependency. This wouldn't scale for CI style use;
    • For full front end, Jasmine would be more relevant; I have used Mocha abit;
  • I do functional testing, historically with Selenuim;
  • I use closures;
    • My libraries tidily don't pollute the symbolspace anymore than is necessary. I know what the self executing function declarations are;
  • I use JS in a statefull fashion, in reverse chronological order, using localStorage, using AJAJ in preference to AJAH, failing over to a hash on the window object if needed;
  • I have done some demo code with websockets, but as fundamentally its a TCP socket, this is no different to normal POSIX programming. I have written alot of normal TCP and UDP based programming;
  • I currently don't use any JS specific design patterns, other than jQuery patterns; but as an OO engineer, I use the following.
  • Historically I have tested my code for DOM memory leaks; this is necessary for long running JS on MSIE. There are specialised tools for the older versions of MSIE that count references. My scripts are generally quite efficient as I know how computers work;
  • When I need to demonstrate snippets (for stack overflow mostly), I use jsfiddle. I am solving UX problems on my site and publishing this at github, I will push a batch over to jQuery.com when I have completed my shopping list;
  • Focussing on reports, I really like jQuery-ui datepicker; its removes two days off any isolated platform development;
  • I have built SPA, I have engineered partial-page support into most of the web page frameworks that I have built;
    • Specifically ECBM is a publically visible example;
  • General consensus is that data manipulation should be on the server, so its not manipulatable. I can do data manipulation in JS, but historically don't;
  • I have worked in high volume sites, but the server language isn't JS;
  • I have some personal testing scripts that use SpiderMonkey for verifying strictness. Limited use when your code is attached to the DOM;
  • With regards to UI, I target HTML5, mobile and RWD. I use CSS frameworks where practical. My site is targeting desktop mostly, due to the volume of words; but there is CSS for mobile;
  • The following are JS heavy projects:

Fullstack with JS

RSS. Share: Share this resource on your twitter account. Share this resource on your linked-in account. G+

Fullstack with JS

RSS. Share: Share this resource on your linked-in account. Share this resource on your twitter account. G+ ­ Follow edited