Podcasts about chrome developer tools

In this episode, James and Amy talk about the Chrome Developer Tools including familiar tabs like Elements, Console, Network, and a few you've probably never heard of! They also share some of their favorite tips and tricks along the way.SponsorsZEALZEAL is a computer software agency that delivers “the world's most zealous” and custom solutions. The company plans and develops web and mobile applications that consistently help clients draw in customers, foster engagement, scale technologies, and ensure delivery.ZEAL believes that a business is “only as strong as” its team and cares about culture, values, a transparent process, leveling up, giving back, and providing excellent equipment. The company has staffers distributed throughout the United States, and as it continues to grow, ZEAL looks for collaborative, object-oriented, and organized individuals to apply for open roles.For more information visit codingzeal.comVercelVercel combines the best developer experience with an obsessive focus on end-user performance. Their platform enables frontend teams to do their best work. It is the best place to deploy any frontend app. Start by deploying with zero configuration to their global edge network. Scale dynamically to millions of pages without breaking a sweat.For more information, visit Vercel.comDatoCMSDatoCMS is a complete and performant headless CMS built to offer the best developer experience and user-friendliness in the market. It features a rich, CDN-powered GraphQL API (with realtime updates!), a super-flexible way to handle dynamic layouts and structured content, and best-in-class image/video support, with progressive/LQIP image loading out-of-the-box."For more information, visit datocms.comShow Notes00:00:00 - Intro00:04:43 - Amy's Trip to Berlin for Prisma Days00:07:47 - What Are Chrome Developer Tools?00:12:18 - The Elements Tab00:16:00 - Sponsor: DatoCMS00:16:54 - Tweaking Styles in the Elements Tab00:19:06 - The Layout Tab, Event Listeners, Breakpoints, and Accessibility Tabs00:23:34 - The Console00:27:18 - Sponsor: Zeal00:28:12 - Performance Insights and Performance00:29:07 - Debugging and the Sources Tab00:31:22 - The Network Tab00:37:07 - Sponsor:  Vercel00:38:14 - The Application Tab - Local Storage, Cookies, and More00:41:30 - The Lighthouse Tab and Framework Specific Tabs00:44:52 - Grab Bag Questions00:50:02 - Picks and Plugs

In the last two episodes of Build we tackled why accessibility needs to be prioritized in product design and the three key tips that are critical and will make a big impact on your product's adoption. This week we’re going to answer two questions that inspired this series from one of our audience members: Jane. We chose these two because we figured they might also be on your mind! Jane wrote: Poornima, Thanks for tackling a wide variety of topics when it comes to building software products. One area that I'm curious about is accessibility. As a user experience designer, I know accessibility is important, but I've struggled when it comes to balancing out accessibility across devices and also making mobile apps interactive and fun without compromising on accessibility. How should I think about web versus mobile and balancing out fun and engaging interactions with accessibility in mobile apps? Sincerely, Jane                     Jane thank you for writing in! Laura Allen who is the Accessibility Program Manager at Google for Chrome and the Chrome operating system is back and together we are going to be answering Jane’s questions in today’s episode. As you listen to today’s episode you’ll learn: What are the similarities and differences when it comes to designing for accessibility on web versus mobile devices How to balance balance out fun and engaging interactions versus accessibility on mobile devices The various types of accessibility testing: manual versus automated and tradeoffs associated with both  Here are links to the resources Laura mentions in the video: Web Content Accessibility Guidelines Android Developers Site  iOS Human Interface Guidelines  Android Accessibility Scanner Lighthouse  -- Build is produced as a partnership between Femgineer and Pivotal Tracker. San Francisco video production by StartMotionMEDIA. -- ## How To Balance Accessibility And Interactivity Across Devices Transcript Poornima Vijayashanker:        In the previous two episodes of *Build*, we talked about the importance of accessibility and we shared three critical strategies that will help make a big impact when it comes to building and designing products. If you missed either of those episodes, I've included links to them below. In today's final episode on accessibility, we're going to talk about what accessibility means across devices for both web as well as mobile. Stay tuned.                     Welcome to *Build*, brought to you by Pivotal Tracker. I'm your host, Poornima Vijayashanker. In each episode, I invite innovators, and together we debunk a number of myths and misconceptions related to building products, companies, and your career in tech.                     We're continuing our conversation on accessibility with Laura Allen, who is the accessibility program manager at Google for Chrome and the Chrome operating system. Thanks again for joining us, Laura.   Laura Allen:        My pleasure. Thank you.   Poornima Vijayashanker:        One of the inspirations for this series on accessibility came from our audience member Jane, so I'm going to start off today's episode by reading the question that Jane posed. Jane wrote, "Poornima, thanks for tackling a wide variety of topics when it comes to building software products. One area that I'm curious about is accessibility. As a user experience designer, I know accessibility is important, but I've struggled when it comes to balancing out accessibility across devices and also making mobile apps interactive and fun without compromising on accessibility. How should I go about thinking about web versus mobile and balancing out fun and engaging interactions with accessibility in mobile apps? Sincerely, Jane."                     Jane, if you're tuning in to this episode, thank you for writing in. Laura, why don't we start by answering Jane's question to begin with. How do we balance out web versus mobile?   Laura Allen:        It's a really great question. When you think about it, a lot of these concepts that we were talking about in previous episodes are actually going to stand true no matter what platform you're actually designing for. Think back to the web content accessibility guidelines, WCAG. They talk about perceivable, operable, understandable, and robust, and those sorts of concepts and principles that go within each of those categories. Just taking one example, color contrast. Color contrast, having really solid contrast between text and its background, that's important no matter what device you're on. It's going to be the same sort of truth for if you're on a mobile phone or if you're on a desktop computer. A lot of these concepts are going to just span across platforms and be really relevant for you to consider.                     One thing that's obviously a little bit different on mobile is that it's clearly more touch oriented for most users. Things like touch targets and the size of your touch targets, that's important to consider. Some people might not have as precise motion or control as they're using their phone or tablet, but honestly, the lines are getting a little bit blurry anyway. Think about all the different devices that are out there now, like laptop computers that also have touch screens or convert and are then used in tablet mode. As designers, we're starting to think about, "How do we just make an app itself accessible on all these different platforms, or a site itself?"   Poornima Vijayashanker:        Let's tackle Jane's second question on how do we balance out fun and engaging interactions versus accessibility.   Laura Allen:        Yeah. That's another really great question. I think something that we should keep in mind when developing for mobile is sometimes we just rely a little bit too heavily on this idea of gestures and touch-based interfaces. I understand why, of course. It's typically being used by using touch. Some users aren't able to actually use touch to operate a phone. There's something called switch access, for example, which basically allows you to pair a one-button, or two-button, or multiple-button switch and control a phone just using those external buttons. That's just one example. Some people might be only using voice to control a device. Some people might be navigating with a screen reader, so as something flashes on the screen, they're not able to actually perceive that and then catch it in time to actually take action. Thinking about what are these things that we're assuming our users can do here, and then offering alternative ways to actually operate.                     For example, if you have an app that you're building where you have cards that you need to swipe away to take action, a swipe can work for some people, but for others, maybe that's not going to be possible. How do we think about things like, "OK. Can we add a hidden close button here so that a screen reader could actually access that and somebody could just simply double tap to activate?" Lots of different things like that. Just, again, removing assumptions about how our users are interacting and then just building to cater to different groups.   Poornima Vijayashanker:        I think your answers are going to be very helpful for Jane and the rest of our audience. Any final words of wisdom that you'd like to share when it comes to accessibility?   Laura Allen:        Sure, yeah, a couple things. First, just thinking again about mobile versus desktop and web and what not, I think it's also really helpful when designing for mobile to be thinking about the platform-specific guidelines. This is like guidelines for more so just the interaction models for that platform. I know there's the Android developers resources and site. iOS has the iOS human interface guidelines. These things obviously go well beyond just the concepts of accessibility, but they're really important to keep in mind because if you think about it. One example of what would be discussed is focus management. When you first open up an app, where is focus meant to go? What is the default? As you think about these concepts that are kind of illustrated through guidelines for each of these platforms, it's really helpful to keep that consistent so that when a user who happens to be using assistive technology interacts with this app, they get a similar experience to what they're used to. It's a similar model for them, and therefore it's an easier ramp-up curve to actually get introduced to your design. That would be one suggestion.                     Another thing to consider, which we haven't really discussed at this point: We talked a lot about auditing and integrating accessibility into your processes, and a lot of what we've talked about so far has been manual testing and the importance of really diving in, trying out the keyboard-only experience, or trying out a screen reader. Absolutely, I think that is so critical. I think honestly...I often get asked about manual versus automated testing, like what can we put in place to run automated tests. There are some great things to do, so there are automated tools, like, for example, there's a tool, there's an Android app called the Android Accessibility Scanner. It's free. It helps to run an audit of your app's accessibility and show you the results for things.   Poornima Vijayashanker:        Oh, great.   Laura Allen:        Yeah. For things like missing labels on a button or color contrast, things like that, which I would imagine to be kind of low-hanging fruit that you look at and hopefully fix rather quickly. There are similar things on the web and desktop. Lighthouse is a great tool, which integrates with the Chrome Developer Tools. There are lots of other types of tools out there that you can leverage to do some automated testing and audits, but in my opinion, automated can only go so far. That's where you use it to kind of see a baseline, track progress over time and your results, but manual is really critical. Again, whether it's you going through or having assistive technology users go through and give you feedback, that's where you're going to capture that more human interface experience. You're going to understand what is the usability of this product, whether on mobile or on desktop. It's just really critical to find that right balance of manual versus automated testing.   Poornima Vijayashanker:        This has been wonderful, Laura, and we'll be sure to include all the resources you mentioned below so that our audience can make sure to get access to them.   Laura Allen:        Great. Thank you so much for having me.   Poornima Vijayashanker:        Yeah, yeah. You're welcome. This has been great.                     That's it for this week's episode of *Build*. Be sure to subscribe to our YouTube channel to receive more episodes like this, and be sure to share this with your friends, your teammates, and your boss. A thank you to our sponsor, Pivotal Tracker, for their help in producing this episode. Ciao for now!                 This episode of *Build* is brought to you by our sponsor, Pivotal Tracker.                   

Today's guest, Patrick Stox, is the technical SEO for IBM and the organizer of the Raleigh SEO Meetup. He’s also a frequent writer for many search blogs and an accomplished speaker. You might not know the difference between HTTP, HTTPS, and HTTP2. But understanding the difference is more important than ever. Chrome users will soon be warned that sites using HTTP are no longer secure. How can you protect your site? You can make the switch to HTTPS. Join us to learn about SEO and development to keep your site running smoothly. Find Out More About Patrick Here: Patrick Stox@patrickstox on TwitterPatrick Stox on FacebookPatrick Stox on LinkedIn In This Episode: [02:32] - Patrick talks about the massive size of the IBM website. He then discusses some of the big issues in maintaining a site that big from an SEO perspective. [04:58] - We hear why one should use hreflang tags on their website. [07:05] - What are Patrick’s preferred tools for crawling? [07:44] - Stephan compares building a website without an SEO involved to building a house and then realizing you didn’t specify that you needed electrical wiring. [09:34] - What sorts of documents does Patrick use to get everyone on the same page? He and Stephan talk about the problems with having extensive documentation. [14:26] - Patrick talks about the potential issues with HTTP, and explains why seeing ads on a site that doesn’t normally have them is potentially really scary. [17:09] - What are the reasons you need to go from HTTP to HTTPS even on your personal blogs? [19:13] - HTTPS is a small ranking factor in SEO, Patrick explains, which is basically a tiebreaker between equal sites. He isn’t sure whether its importance as a ranking factor will be increased. [20:50] - What are some of the biggest mistakes that Patrick sees with HTTPS migrations? [23:43] - Patrick talks about what content delivery networks (CDNs) he comes across most frequently, and which are his favorites. [26:23] - Patrick defines service workers for marketers who are listening and may be unfamiliar with some of the geekier SEO terms. He then explains the benefits of minifying JavaScript. [28:49] - What are some of Patrick’s favorite features within the Chrome Developer Tools? [33:05] - Stephan talks about the painful procedure that was involved in removing an SEO CDN, and talks about his invention, GravityStream. [34:47] - Now that we’ve covered HTTPS, Patrick moves on to talking about HTTP2. Its main benefit is that it makes things a lot faster. [37:28] - Patrick and Stephan talk about server response headers, and Patrick offers some tips and tricks. [42:58] - We hear about Patrick’s use of Ryte. [44:04] - Patrick elaborates on frameworks in SEO, discussing specifically React and AngularJS. [46:57] - Stephan asks Patrick a question: what would be his SEO advice and best practice suggestions to a listener who is using infinite scrolling? [48:12] - Are there any other server response header or redirect tips that Patrick wants to share with listeners? [49:54] - Patrick and Stephan talk about Google’s SEO best practice document, and discuss whether H1 tags have an effect. [52:57] - Stephan explains that he is very outcome-focused rather than activity-focused like most other SEOs. [54:56] - What’s an example of one of the scripts and tools that Patrick uses to automate and scale across the 50 million pages at IBM? [57:25] - Patrick is pretty picky about side projects, but if you have a difficult problem that you can’t quite figure out, he may be able to help. He directs listeners on where to find him. Links and Resources: Patrick Stox @patrickstox on Twitter Patrick Stox on Facebook Patrick Stox on LinkedIn IBM Raleigh SEO Meetup Pubcon Hreflang tags Screaming Frog Botify React Meteor Bill Hunt on Marketing Speak Mike Moran “HTTP to HTTPS: An SEO’s guide to securing a website” by Patrick Stox on Search Engine Land “What is HTTP2 and How Will it Affect Your SEO?” by Patrick Stox on Search Engine Journal Akamai Cloudflare Fastly Service workers Chrome Developer Tools RankSense GravityStream Alex Bertram Jon Henshaw Rank Ranger Search Analytics for Sheets Google Data Studio Ryte Marcus Tandler on Marketing Speak React AngularJS Dan Sharp  

On this episode of Eat Sleep Code, guest Robert Boedigheimer discusses debugging HTTP with Fiddler and Chrome Dev Tools. Robert talks about Fiddler and how it's used to sniff out mixed https content and what are protocol-less URLs. Robert shares his tips on performance tuning by troubleshooting website images. Working with Location APIs, and mimicking slow network traffic are also discussed.

Over a year ago I wrote one our most popular posts on the WP-Tonic’s website about the importance of speed when it comes to your WordPress-powered website in regards to usability and how Google ranks your website in SEO (search engine optimization) terms.   https://www.wp-tonic.com/blog/11-the-key-steps-to-make-your-wordpress-site-load-faster/   In this episode, we talk about 11 things you can do to make your WordPress website faster. A lot of this is based on a 3500+ word article that Jonathan put together for the WP-Tonic, but we further extrapolate the ideas and techniques talked about there. https://www.wp-tonic.com/blog/11-the-key-steps-to-make-your-wordpress-site-load-faster/ Show Table of Contents: 0:00 Intros 2:06 Reviewing the 11 steps to making your WordPress site faster 2:59 Page speed testing tools 3:23 Google Page Speed Insights 3:48 Time to first byte is an SEO factor 4:05 Why large sites spend so much time on page speed 4:44 The waterfall view of browser resources 5:28 Chrome Developer Tools to see the waterfall view 5:50 How to find the time to first byte for your website 6:26 DNS and page speed performance 8:28 How hosting affects page speed 9:03 You will never have a fast website with shared hosting 10:29 Why managed WordPress hosting is superior to general hosting 11:52 The near-future: PHP7 and HTTP/2 12:23 What is better? nginx or Apache? 13:00 The biggest performance difference between general hosts and managed hosting 15:40 External calls and HTTP requests can affect page speed 17:20 How caching can reduce HTTP requests and improve page speed 117:52 Why you need to talk to a consultant before buying a base theme 18:35 The dirty secret about how 85% of web shops pick WordPress themes 20:40 Visual builders based on shortcodes are terrible for performance 21:38 Page speed affects your marketing efforts 23:25 You get what you pay for 24:28 The quality and number of plugins can affect page speed 28:20 How caching helps your page speed 31:04 Web fonts: how much does this affect page speed? 31:55 A short history of web fonts 33:21 The down side of using web fonts 36:07 Image optimization, and how easy it is to add tons of page weight without knowing it 37:21 A short history of web images 37:59 A huge problem with modern web design and website performance 40:35 Image compression tools like Kraken.io 41:50 CDNs: What are they, and how do they help page speed? 42:30 How CDNs work 45:40 General tips for learning more about improving page speed 47:45 Outros and some interesting news   =========================   WP-Tonic is not only a WordPress maintenance and support service, but we publish a twice weekly WordPress podcast where we talk with some of the brightest minds in WordPress development and online marketing.  

We're getting up to speed with the fascinating world of web frontend performance. Concatenation, compression, optimization and more delivered in one speedy package this week! Kenneth, Kevin & Len are joined by Mannuel Ferreira, a web designer and developer from Superbalist.com. Mannuel shares with us some practical experiences he's had at his current job making Superbalist fast, as well as the work he did at World Wide Creative on a recent relaunch of the IOL website. Mannuel has a lot to share with practical tips and tricks to help all of us make our websites performant. Follow Mannuel online: - http://themwebs.me - https://twitter.com/manidf - https://github.com/manidf Here are some resources mentioned during the show: * PageSpeed Insights - https://developers.google.com/speed/pagespeed/insights/ * Website Speed Test - http://tools.pingdom.com/fpt/ * SpeedCurve - https://speedcurve.com/ * Load Google Fonts asynchronously for page speed - http://bit.ly/1QTsiYh * Understanding the critical rendering path - http://bit.ly/22fjmnf * Quick guide to webfonts via @font-face - http://bit.ly/1nJJALE * Google Web Font Loader Events - http://bit.ly/1RhP6D7 * Font Face Observer - http://bit.ly/1TJywME * HTML5's async Script Attribute - http://bit.ly/1RhPhOR * Gulp - http://gulpjs.com/ * Bourbon - http://bourbon.io/ * Neat - http://neat.bourbon.io/ * How to optimize your site with GZIP compression - http://bit.ly/250Kplk * Grunt: The JavaScript task runner - http://gruntjs.com/ * webpack module bundler - https://webpack.github.io/ * broccoli.js - http://broccolijs.com/ * Working with quotas on mobile browsers - http://bit.ly/1pqd9DV * Mobile Browser Cache Limits, Revisited - http://bit.ly/1S0xwR6 * CSS Transitions - http://bit.ly/1pqdwhC * Add two variables using jQuery - http://bit.ly/1pHxe8D * fetch API - https://davidwalsh.name/fetch * A window.fetch polyfil from Github - https://github.com/github/fetch * Essential reading list for getting started with Service Workers - http://bit.ly/1Ln7MPJ * Offline First! - http://offlinefirst.org/ * Leverage Browser Caching - http://bit.ly/1U2dIkd * HTTP/2 - https://http2.github.io/ * HTTP/2 on CloudFlare - https://www.cloudflare.com/http2/ * HTTP/2 on Akamai - https://http2.akamai.com/ * HTTP/2 on nginx - http://bit.ly/1QSQicL * HTTP/2 on Apache httpd - http://bit.ly/1RhP3an * Forgo JS packaging? Not so fast - http://bit.ly/1pqdsyp * HTML5 picture element - http://mzl.la/1RiKzKs * Built-in Browser Support for Responsive Images - http://bit.ly/1P92DoY * Picturefill: a responsive image polyfill - https://scottjehl.github.io/picturefill/ * How to avoid duplicate downloads in responsive images - http://bit.ly/1Mj60tv * Modernizr - https://modernizr.com/ * Responsive logos with SVG - http://bit.ly/1RiKOoP * CSS Only Image Preloading - http://bit.ly/1SO01Uj * Prefetching, preloading, prebrowsing - http://bit.ly/1S0xMPS * HTML5 Link Prefetching - http://bit.ly/1RKeL1x * AngularJS Server Side Rendering - https://github.com/saymedia/angularjs-server * From AngularJS to React: The Isomorphic Way - http://bit.ly/1QSQcC1 * Ember FastBoot - https://github.com/tildeio/ember-cli-fastboot * AMP (Accelerated Mobile Pages) Project - https://www.ampproject.org/ * Designing for Performance - http://designingforperformance.com/ And finally our picks Kevin: - statsd - https://github.com/etsy/statsd - Chrome Developer Tools - https://developer.chrome.com/devtools Kenneth: - High Performance Browser Networking - http://chimera.labs.oreilly.com/books/1230000000545 Mannuel: - CSS Stats - http://cssstats.com/ - Big Rig - https://github.com/GoogleChrome/big-rig - SpeedCurve - https://speedcurve.com/pricing/ Thanks for listening! Stay in touch: * Socialize - https://twitter.com/zadevchat & http://facebook.com/ZADevChat/ * Suggestions and feedback - https://github.com/zadevchat/ping * Subscribe and rate in iTunes - https://itunes.apple.com/za/podcast/zadevchat-podcast/id1057372777

In which we talk about Chrome Developer Tools and how to get started.

01:35 - Katya Eames Introduction Twitter [YouTube] Katya Eames: How to Teach Angular to Your Kids 01:52 - Ben Nadel Introduction Twitter GitHub Blog Adventures in Angular Episode 029: Angular At Work with Ben Nadel InVision @InVisionApp 04:47 - Performance Basecamp Nested Pages 08:04 - User Experience 10:01 - Fixing Performance Problems as a Team Engineering Validation “Premature optimization is the root of all evil -- Donald Knuth” DOM Manipulation ngRepeat Screen Experience 23:28 - Finding Performance Issues Chrome Developer Tools Firefox Firebug Utilizing Chrome Dev Tools and Creating the Videos on Ben’s Blog “Imposter Syndrome” Addy Osmani Paul Irish 29:27 - “Just-in-Time View Construction” 34:43 - ngIf 37:16 - Angular 2 Opinions [YouTube] Dave Smith: Angular + React = Speed Unit Directional Data Flow & Functionality Victor Savkin: Change Detection in Angular 2 [Egghead.io] John Lindquist: Angular 2: Template Syntax ES5, ES6    AtScript, TypeScript traceur-compiler Babel 46:01 - Moving to 2.0 Picks BrowserSync (John) [Egghead.io] Angular 2: Template Syntax (Joe) Win an InVision App T-Shirt! (Lukas) Adventures in Angular (Lukas) WELCOME TO NIGHT VALE (Katya) Being and Time (Harper Perennial Modern Thought) by Martin Heidegger (Ward) Angular Grid (Ward) Steelheart (The Reckoners) by Brandon Sanderson (Chuck) StarTech.com MUHSMF2M 2m 4 Position TRRS Headset Extension Cable (Ben) Any Given Sunday (Ben) News ng-vegas: May 7th and 8th, 2015! AngularU in the Bay Area in June

01:35 - Katya Eames Introduction Twitter [YouTube] Katya Eames: How to Teach Angular to Your Kids 01:52 - Ben Nadel Introduction Twitter GitHub Blog Adventures in Angular Episode 029: Angular At Work with Ben Nadel InVision @InVisionApp 04:47 - Performance Basecamp Nested Pages 08:04 - User Experience 10:01 - Fixing Performance Problems as a Team Engineering Validation “Premature optimization is the root of all evil -- Donald Knuth” DOM Manipulation ngRepeat Screen Experience 23:28 - Finding Performance Issues Chrome Developer Tools Firefox Firebug Utilizing Chrome Dev Tools and Creating the Videos on Ben’s Blog “Imposter Syndrome” Addy Osmani Paul Irish 29:27 - “Just-in-Time View Construction” 34:43 - ngIf 37:16 - Angular 2 Opinions [YouTube] Dave Smith: Angular + React = Speed Unit Directional Data Flow & Functionality Victor Savkin: Change Detection in Angular 2 [Egghead.io] John Lindquist: Angular 2: Template Syntax ES5, ES6    AtScript, TypeScript traceur-compiler Babel 46:01 - Moving to 2.0 Picks BrowserSync (John) [Egghead.io] Angular 2: Template Syntax (Joe) Win an InVision App T-Shirt! (Lukas) Adventures in Angular (Lukas) WELCOME TO NIGHT VALE (Katya) Being and Time (Harper Perennial Modern Thought) by Martin Heidegger (Ward) Angular Grid (Ward) Steelheart (The Reckoners) by Brandon Sanderson (Chuck) StarTech.com MUHSMF2M 2m 4 Position TRRS Headset Extension Cable (Ben) Any Given Sunday (Ben) News ng-vegas: May 7th and 8th, 2015! AngularU in the Bay Area in June

01:35 - Katya Eames Introduction Twitter [YouTube] Katya Eames: How to Teach Angular to Your Kids 01:52 - Ben Nadel Introduction Twitter GitHub Blog Adventures in Angular Episode 029: Angular At Work with Ben Nadel InVision @InVisionApp 04:47 - Performance Basecamp Nested Pages 08:04 - User Experience 10:01 - Fixing Performance Problems as a Team Engineering Validation “Premature optimization is the root of all evil -- Donald Knuth” DOM Manipulation ngRepeat Screen Experience 23:28 - Finding Performance Issues Chrome Developer Tools Firefox Firebug Utilizing Chrome Dev Tools and Creating the Videos on Ben’s Blog “Imposter Syndrome” Addy Osmani Paul Irish 29:27 - “Just-in-Time View Construction” 34:43 - ngIf 37:16 - Angular 2 Opinions [YouTube] Dave Smith: Angular + React = Speed Unit Directional Data Flow & Functionality Victor Savkin: Change Detection in Angular 2 [Egghead.io] John Lindquist: Angular 2: Template Syntax ES5, ES6    AtScript, TypeScript traceur-compiler Babel 46:01 - Moving to 2.0 Picks BrowserSync (John) [Egghead.io] Angular 2: Template Syntax (Joe) Win an InVision App T-Shirt! (Lukas) Adventures in Angular (Lukas) WELCOME TO NIGHT VALE (Katya) Being and Time (Harper Perennial Modern Thought) by Martin Heidegger (Ward) Angular Grid (Ward) Steelheart (The Reckoners) by Brandon Sanderson (Chuck) StarTech.com MUHSMF2M 2m 4 Position TRRS Headset Extension Cable (Ben) Any Given Sunday (Ben) News ng-vegas: May 7th and 8th, 2015! AngularU in the Bay Area in June

While at NDC in London, Carl and Richard talk to Shay Friedman about the Chrome Developer Tools. The conversation starts out talking a bit about the state of web development, the jump in JavaScript performance, and the huge increase in the complexity of web applications - which naturally leads to the challenge of debugging said JavaScript-based applications. Enter the Chrome Developer Tools. Firefox was the original web developer browser, but Chrome has slid into that slot with more capabilities than ever. More than just element inspection, the Chrome Developer Tools let you look at your web application executing on the browser. Shay talks about tracking down memory leaks in complex Javascript code, where many variables are created, but few are destroyed. You need these tools in your kit!Support this podcast at — https://redcircle.com/net-rocks/donations

While at NDC in London, Carl and Richard talk to Shay Friedman about the Chrome Developer Tools. The conversation starts out talking a bit about the state of web development, the jump in JavaScript performance, and the huge increase in the complexity of web applications - which naturally leads to the challenge of debugging said JavaScript-based applications. Enter the Chrome Developer Tools. Firefox was the original web developer browser, but Chrome has slid into that slot with more capabilities than ever. More than just element inspection, the Chrome Developer Tools let you look at your web application executing on the browser. Shay talks about tracking down memory leaks in complex Javascript code, where many variables are created, but few are destroyed. You need these tools in your kit!Support this podcast at — https://redcircle.com/net-rocks/donations