AngularJS DC

Name: Scaling Angular as a Team
Start: 2014-06-18T23:00:00Z
Location: Learning Objects

Scaling Angular as a Team

Jun 18, 2014 · 7:00 PM
Learning Objects

Directions:

Learning Objects is located on top of the North Dupont Metro exit (Red Line); exit towards Q St.

There are a number of parking structures in the area. We recommend 11 Dupont Circle NW, underneath the Books-a-Million. Parking is $12/flat, open until 11pm, and a quick 3 minute walk to the entrance of our building.

Enter the building through the back door facing 20th street (Entrance through the PNC parking lot) then take the elevator to the second floor.

Building access is controlled, although the door will be propped in the back of the building; please plan to arrive no later than 7:45pm to minimize disruptions.

*********************************************************

Schedule:

6:30 - 7:00 Refreshments
7:00 - 7:15 Intro & Announcements

7:15 - 7:30 Special Presentation

7:30 - 8:15 Presentation by Mike Whitfield
“Scaling Angular as a Team”

8:15 - 9:00 Networking and fun!

*********************************************************

Bio:

Mike Whitfield recently moved back to DC from Austin, TX where he spent the last year working for Cisco among others. Mike began working on his own JavaScript library in 2012 called Ambassador. His goal was to translate the effective “hooks” system used in WordPress to the client. Luckily, the market was moving in the same direction. Mike has benefitted working in libraries like AngularJS since they “feel” more like developing with Flash. Mike lived a past life developing 3D military games like Insurgency.

*********************************************************

Talk Synopsis:

Scaling Angular as a Team

What do you do when your application has 50 views and you want to create a new view? How do you condense your HTTP calls for grabbing data when 12 views share the same data requirements? How do you memory manage a page and prevent it from holding 50x the DOM data needed to display what the user is currently looking at? What is the best way to approach authentication? How do you distribute workload and define roles in Angular? In this talk I’ll share an Angular implementation we architected at Cisco.

Join or login to comment.

Hit enter to add your reply

Vik S.

Oh my god !

0 · June 18, 2014
- View all 8 replies
- Vik S.
  
  I feel like I should elaborate further on my comment .. this talk was a trainwreck and we should evaluate speakers more closely before letting them present - I, for one, would volunteer to be part of the screening committee :)
  
  2 · June 20, 2014
- A former member
  
  Vik, you feedback is appreciated and you make a good point. This is a volunteer organization and the few of us who have taken on the responsibilities of organizing it have demanding full time jobs. Please connect with Christina Hall about your offer to volunteer. And remember, we are always looking for guest speakers and you are welcome to participate at any time.
  
  4 · June 20, 2014
- A former member
  
  I also don't know if there's an inside joke I'm missing. In case there isn't: Vik, the speaker volunteered his time to share his experience with the group. If you have constructive feedback about how he can do a better job next time, why don't you reach out to him privately? If you wish to help the organizers select speakers, that's kind of you and it sounds like they'd appreciate your help. But I think it's neither fair nor productive to criticize a volunteer publicly.
  
  7 · June 20, 2014
- Vik S.
  
  @Leigh - Understood, and me and my team will reach out to Christina and present once things have calmed down a bit - we'll be releasing a pretty cool Angular app in July/August and we can certainly talked about lessons learned along the way.
  
  1 · June 20, 2014
- Vik S.
  
  *talk
  
  0 · June 20, 2014
- Christian S.
  
  Mike, I think where the confusion lies is the synopsis above for the talk is about performance scaling an Angular application but the talk that was delivered, at least what I took away from it, was more around how to scale a team i.e. lots of devs and designers working on the same app.
  
  1 · June 20, 2014
- Jason M.
  
  Hey, Vik - Regardless how you felt about the talk, those comments are out of line. It wasn't what I was expecting either, but calling it a "train wreck" here discourages not only the original presenter, but also others who might be considering talks you'd like better.
  
  Speakers and presentations don't spring full-formed from the head of Zeus. There has to be room for devs to explore topics and improve their skills, with an expectation of being treated with respect. These speakers and organizers are volunteering their time. They take a risk putting themselves out there, and the only reward for investing time and ego in these risky endeavors is brief recognition; we have to keep the cost of 'failure' in proportion to that payoff. Most of all, if we want improvement, we have to define what 'improvement' is in a useful way. We know what it's like to get poor feedback; we should make a point to give better feedback ourselves.
  
  10 · June 20, 2014
- Vik S.
  
  @Jason@Mike - meant nothing personal - just did not want something like this to happen again - 150 people wasted an hour of their time because you were unprepared / thought it was a simple after-work presentation. I think expectations were higher than usual because of the title.
  
  1 · June 22, 2014
Mike G.

Hey, If there were slides to this presentation, could those be posted somewhere? I couldn't make it to this event but am really interested in the content of this talk.

1 · June 19, 2014
- Anu B.
  
  Same here, especially the memory management portion.
  
  0 · June 19, 2014
Mike D.

Can I get help getting in?

0 · June 18, 2014
A former member

At the front door, can someone let's us in

2 · June 18, 2014
- David H.
  
  Justasec...
  
  0 · June 18, 2014
- Chaz C.
  
  Try the back door
  
  0 · June 18, 2014