Info triangle 7c7c507fbda756270577cb1ffd57354dfced4fa55409809b69987ed2d9983efa Request Info
Required
Request Information

By clicking next, you consent to receive autodialed informational or marketing calls or texts from NYCDA at the phone number you provided. Consent is not required to purchase goods or services. You can always call us at 844-322-CODE.

Ready to apply now?

Back to Blog

Meet an AngularJS Contributor: Ryan Schmukler

Written by Maddy Lau on August 18, 2016 in AngularJS 102, Class, Evening, Learn to Code, Technology

AAEAAQAAAAAAAANCAAAAJDY1MjViMDFiLTBiYjItNDk0NS1iNjMyLTk0YTQwYzM0NTBjMA

We were very lucky to have Ryan Schmukler stop by NYCDA to chat with us about his thoughts on Angular. Ryan is a self-taught programmer who transitioned from web development to big data/machine learning and has been an active contributor to the Angular framework, specifically, Angular Material.

He has worked on all elements of Material but most notably on the theming engine, which is a mobile-targeted framework that gives you a lot of theme possibilities that are really small on the wire. Basically what the theming engine does is generate CSS templates through permutations with JavaScript.

Ryan has dabbled in Backbone and React but likes that Angular has a low boilerplate, is semi-feature complete, libraries for routing and easy to get under the hood with—you can envision how to write all the built-in directives.

If you’re aspiring to become an Angular developer, you should know these 3 things:

Understand directives and what they enable you to do

Be able to make a web component

Encapsulate code correctly

So much of Angular is compositional development on behavior patterns so for example, if you know how to utilize attributes for a behavior like drag and drop, that’s incredibly powerful. If you want to take a class that goes over all of this, learn more about it here.

For those who struggle on finding the right framework to use, you ultimately need to find your pain points and see which framework addresses it. So write your app in a language you’re comfortable in, read extensively on it, reason with it and have it be close to what you would have done yourself.

 

Back to Blog