Podcast appearances and mentions of jake archibald

Igalia's Brian Kardell and Eric Meyer chat with Jake Archibald and Surma about their new show and browser politics.

In this episode, we talk to Jake Archibald, programs engineer and developer advocate working on Chrome, about web page transitions introduced at this year's Google I/O conference. We talk about the issues with creating web page transitions and what Chrome is doing to bring easy-to-use transitions to the web. Links https://twitter.com/jaffathecake Bringing page transitions to the web. (https://www.youtube.com/watch?v=JCJUPJ_zDQ4) https://github.com/jakearchibald/navigation-transitions Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket combines frontend monitoring, product analytics, and session replay to help software teams deliver the ideal product experience. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Jake Archibald.

Yoav Ganbar joins the Jabber crew to discuss Dev FOMO. He leads the panel through a discussion about adopting technologies and knowing about new niches. The panel discusses how to stay on top of the movements in our ecosystem and when we should prioritize other things. Panel Aimee KnightAJ O'NealCharles Max WoodDan ShappirSteve Edwards Guest Yoav Ganbar Sponsors Shortcut (formerly Clubhouse.io)Top End DevsCoaching | Top End Devs Links GitHub: Yoav Ganbar ( hamatoyogi )LinkedIn: Yoav GanbarTwitter: Yoav Ganbar ( @HamatoYogi ) Picks Aimee- What is SSH Tunneling, SSH Reverse Tunneling and SSH Port Forwarding? | TeleportAimee- Why Does Quantitative Easing Benefit the Rich?AJ- GitHub - ulid/spec: The canonical spec for ulidAJ- Jake Archibald on TwitterAJ- GitHub - Creeds of CraftsmanshipCharles- The Search for Planet XCharles- Author | Top End DevsDan- Core Web Vitals Technology ReportDan- The Kite Runner by Khaled HosseiniSteve- The wholly pun bible | InstagramSteve- The wholly pun bible | InstagramYoav- Zack JacksonYoav- Next.js Conf 2021Yoav- daily.dev Special Guest: Yoav Ganbar.

Yoav Ganbar joins the Jabber crew to discuss Dev FOMO. He leads the panel through a discussion about adopting technologies and knowing about new niches. The panel discusses how to stay on top of the movements in our ecosystem and when we should prioritize other things. Panel Aimee KnightAJ O'NealCharles Max WoodDan ShappirSteve Edwards Guest Yoav Ganbar Sponsors Shortcut (formerly Clubhouse.io)Top End DevsCoaching | Top End Devs Links GitHub: Yoav Ganbar ( hamatoyogi )LinkedIn: Yoav GanbarTwitter: Yoav Ganbar ( @HamatoYogi ) Picks Aimee- What is SSH Tunneling, SSH Reverse Tunneling and SSH Port Forwarding? | TeleportAimee- Why Does Quantitative Easing Benefit the Rich?AJ- GitHub - ulid/spec: The canonical spec for ulidAJ- Jake Archibald on TwitterAJ- GitHub - Creeds of CraftsmanshipCharles- The Search for Planet XCharles- Author | Top End DevsDan- Core Web Vitals Technology ReportDan- The Kite Runner by Khaled HosseiniSteve- The wholly pun bible | InstagramSteve- The wholly pun bible | InstagramYoav- Zack JacksonYoav- Next.js Conf 2021Yoav- daily.dev Special Guest: Yoav Ganbar.

Caching is the hardest problem in building software, and having the browser cache is not any different. In this video, I'll discuss Jake Archibald's article https://jakearchibald.com/2016/caching-best-practices/ 0:00 Intro 2:00 Pattern 1: Immutable content + long max-age 5:40 Pattern 2: Mutable content, always server-revalidated 8:00 max-age on mutable content is often the wrong choice 12:20 CDN and Caching Article https://jakearchibald.com/2016/caching-best-practices/ https://twitter.com/jaffathecake --- Send in a voice message: https://anchor.fm/hnasr/message

The infamous Jake Archibald, member of the Chrome Team, an author of the Service Worker spec, and host of the HTTP 203 Podcast takes us on a whirlwind tour of recent and upcoming browser standards including Portals, iframes, App Cache, Service Workers, HTML, Browser History and more - why they are the way they are, why we can't have nice things, and how we might get nice things anyway in the future. Lots of good back and forth and only a little name calling… jaffa… Panel Aimee Knight AJ O'Neal Dan Shappir Steve Edwards Guest Jake Archibald Sponsors Dexecure Raygun | Click here to get started on your free 14-day trial JavaScript Error and Performance Monitoring | Sentry Links Portals GitHub streaming vs SPA Newline delimited JSON AVIF compression article HTTP 203 The old 300ms tap delay Session history is confusing  Spectre & Meltdown COOP & COEP  App history API proposal Application cache is a douchebag Extensible web manifesto IDB promise library Twitter: Jake Archibald ( @jaffathecake ) Picks Aimee- On The Experience of Being Poor-ish, For People Who Aren't AJ- HTTP 203 | YouTube AJ- Mac OS X Lion CSS3 by Alessio Atzeni AJ- Worms WMD AJ- Deku Deals AJ- Final Fantasy IX (English) | playasia AJ- RTMP setup in Nimble Streamer Dan- The Sopranos  Jake- It's a Sin  Steve- An Interactive Guide to CSS Transitions Steve- Monty Python Spanish Inquisition Part 1 Steve- Monty Python Spanish Inquisition Part 2

The infamous Jake Archibald, member of the Chrome Team, an author of the Service Worker spec, and host of the HTTP 203 Podcast takes us on a whirlwind tour of recent and upcoming browser standards including Portals, iframes, App Cache, Service Workers, HTML, Browser History and more - why they are the way they are, why we can't have nice things, and how we might get nice things anyway in the future. Lots of good back and forth and only a little name calling… jaffa… Panel Aimee Knight AJ O'Neal Dan Shappir Steve Edwards Guest Jake Archibald Sponsors Dexecure Raygun | Click here to get started on your free 14-day trial JavaScript Error and Performance Monitoring | Sentry Links Portals GitHub streaming vs SPA Newline delimited JSON AVIF compression article HTTP 203 The old 300ms tap delay Session history is confusing  Spectre & Meltdown COOP & COEP  App history API proposal Application cache is a douchebag Extensible web manifesto IDB promise library Twitter: Jake Archibald ( @jaffathecake ) Picks Aimee- On The Experience of Being Poor-ish, For People Who Aren't AJ- HTTP 203 | YouTube AJ- Mac OS X Lion CSS3 by Alessio Atzeni AJ- Worms WMD AJ- Deku Deals AJ- Final Fantasy IX (English) | playasia AJ- RTMP setup in Nimble Streamer Dan- The Sopranos  Jake- It's a Sin  Steve- An Interactive Guide to CSS Transitions Steve- Monty Python Spanish Inquisition Part 1 Steve- Monty Python Spanish Inquisition Part 2

The infamous Jake Archibald, member of the Chrome Team, an author of the Service Worker spec, and host of the HTTP 203 Podcast takes us on a whirlwind tour of recent and upcoming browser standards including Portals, iframes, App Cache, Service Workers, HTML, Browser History and more - why they are the way they are, why we can't have nice things, and how we might get nice things anyway in the future. Lots of good back and forth and only a little name calling… jaffa… Panel Aimee Knight AJ O'Neal Dan Shappir Steve Edwards Guest Jake Archibald Sponsors Dexecure Raygun | Click here to get started on your free 14-day trial JavaScript Error and Performance Monitoring | Sentry Links Portals GitHub streaming vs SPA Newline delimited JSON AVIF compression article HTTP 203 The old 300ms tap delay Session history is confusing  Spectre & Meltdown COOP & COEP  App history API proposal Application cache is a douchebag Extensible web manifesto IDB promise library Twitter: Jake Archibald ( @jaffathecake ) Picks Aimee- On The Experience of Being Poor-ish, For People Who Aren't AJ- HTTP 203 | YouTube AJ- Mac OS X Lion CSS3 by Alessio Atzeni AJ- Worms WMD AJ- Deku Deals AJ- Final Fantasy IX (English) | playasia AJ- RTMP setup in Nimble Streamer Dan- The Sopranos  Jake- It's a Sin  Steve- An Interactive Guide to CSS Transitions Steve- Monty Python Spanish Inquisition Part 1 Steve- Monty Python Spanish Inquisition Part 2

Quick show notes Our Guest: Phil Hawksworth What he'd like for you to see: JAMstack_conf San Francisco: October 16-18 | JAMstack.org/slack His JAMstack Jams: 11ty | Serverless Functions His musical Jam: Toto | Free Code Camp's Radio | Gaz Coombes Phil's post about dynamic 404 pages with Serverless functions Other Tech mentioned Jekyll Netlify Hugo Cloudinary Auth0 Transcript Bryan Robinson 0:03 Hello everyone, welcome to another episode of that's my JAMstack podcast where we are profile amazing people working in this awesome JAMstack community. In this podcast we ask the age old question, what's your jam in the JAMstack? I'm your host Bryan Robinson and today I'm joined by the ever amazing Phil Hawksworth. Phil is a member of the absolutely incredible developer experience team at a little JAMstack company called Netlify. Bryan Robinson 0:37 Hey, Phil, thanks for joining us on today's episode. Phil Hawksworth 0:40 Well, thanks for having me. It's, it's nice to be here. Bryan Robinson 0:43 Yeah, no problem. And I guess let's let's start. Hopefully, a lot of our audience knows who Phil Hawksworth is at this point. But I give us a little introduction. Tell us you know, what you do for work what you do for fun, that sort of thing? Phil Hawksworth 0:53 Yeah, of course. So say as you say, My name is Phil and I work at Netlify. So I'm kind of fairly well as a right in the middle of the the JAMstack kind of world really, I guess, been working in there for a little while. So I work as part of the developer experience team at Netlify. And I've been there for almost two years, I'm I don't quite know where the time has gone. But yeah, I've been there a little while now. But I've I've kind of been working on figuring out how to use Netlify as part of the JAMstack, finding out what people need from it, trying to find interesting ways to use it. And I've been, I've been interested in JAMstack and building kind of static sites, I'm careful of using the phrase static sites, it's so it's a dangerous thing to say. But I've been dabbling in that world for quite a long time, I used to work at an agency. So I did lots of work for doing architectures for different projects and clients there. And I kept on coming back to this approach that I now know to be called the JAMstack. Bryan Robinson 1:49 Cool. So you kind of already partially answered the next question. But your answer your point to the JAMstack was in this agency world? Phil Hawksworth 1:56 Yeah, I think really, anyone who's been doing anything like technical architectures in an agency, where the client often dictates the the kind of platform and the architecture you might use, irrespective of what the problem is you're trying to solve, I was in that world for quite a few years. And more and more often, I'd be thinking, we can simplify this, there's an easier way to build these things out. You know, often a project would have an aggressive lead time, but that didn't always marry perfectly with the lead time for the infrastructure you have to build on. So for quite a long time I was I was really curious about how we might simplify things, how we might pre render things, and then serve them from a much simpler hosting infrastructure. And to be honest, it was things like Jekyll and GitHub Pages that got me into this. I think that's probably an entry point for lots of people over the years. Phil Hawksworth 2:45 I think Jekyll was one of the first static site generators that made things really approachable, and was you know, felt mature and felt like it was well documented and had a nice on ramp, if you could get over one of the two of the wrinkles to do with Ruby. I'm not a Ruby guy. So that usually where I came unstuck, but once you got past that, I found that that was the that was the way in for me. And I got really excited about how easy it could be to generate a site and deploy it onto something like GitHub Pages at the time, which I think was pretty much at the forefront of automating kind of hosting a static site. So that's, that was my route in. Bryan Robinson 3:21 Okay, and how the clients feel about that. Like you said, like, they tend to dictate technology, irrespective of what they're doing. Phil Hawksworth 3:28 Yeah. And it, it really depended on the client. Some, some clients were much more open to it than others. But I found that the bigger the brand, and the big, like the more established they were in the market, the more likely they would be to say, Oh, no, no, that's not for us, we need an expensive thing. irrespective of how complicated the thing is you're making. Phil Hawksworth 3:50 So actually, that that became quite a difficult challenge, I found to to actually persuade people that they didn't need to spend a fortune on complex infrastructure and something simpler could could actually serve the purpose. And that that kind of played into the conversations I started having with Matt and Chris, the founders of Netlify back in the day, as, as they were trying to coin this term JAMstack, because they were having the same problem, you know, I was talking about static site architectures, and they were doing the same thing. And I think it's such a loaded term, the word static, that, you know, that's where the phrase jumpstart was kind of born from this, this, this desire to get beyond the kind of baggage that comes with the term static, which makes people think simple. Phil Hawksworth 4:37 And I think as the the ecosystem, and all of the vendors and tools have matured around this, that's what's takes JAMstack sites to something beyond static, you know, it's beyond what you might think of traditionally a static so that's, that's where that kind of term I think, was was born from, and that was my entry point into as well trying to find ways to convince clients, some of whom would be okay with it, some of whom would need some convincing the they could spend less and go faster, which seems like a sweet spot for me. Bryan Robinson 5:04 Well, yeah. And it's funny, because like, clients assume that the more you pay, the better the service is. And that's not necessarily true. In fact, it rarely, is. Phil Hawksworth 5:13 Yeah, there's, I think there's always this kind of feeling of finding something which is reassuringly expensive. I've definitely been in that world a lot where, by default, particularly the larger brands, who might go to a large, you know, big global agency, which is the kind of place I was working at, they, I think there's an assumption that they, they need the best in class thing, which has the biggest price tag. And often those are the things that are designed to do a wide variety of things for a wide variety of people. And that makes it hard for them to do the right, you know, the one thing that you need well, and so it's, yeah, it's definitely not like a perfect kind of marriage of what you pay more, you get something which is better. Phil Hawksworth 5:59 This is a great example, I think JAMstack's a great example of simplifying and focusing down on the on really what you need to do, and then building that out, rather than trying to use a product which can do everything for everybody, which, as we all know, is hard to do. Well. Bryan Robinson 6:15 Cool. So obviously, you are working at one of the bigger JAMstack companies in the world, but how are you using the JAMstack professionally? How are you using it in your personal life, that sort of thing? Phil Hawksworth 6:26 Well, I certainly am still using it very much in my personal life. You know, any sites that I that I make, either from my own blog, or any of my kind of side projects, what have you, I've got a handful of those. And I'm, I'm very promiscuous, when it comes to the static site generator, I use that I think we all kind of have our have our darlings that we like, over over and those kind of evolve over time. You know, I already mentioned Jekyll as the one that I started with him for a while I was also using Hugo a lot really got into Hugo. Phil Hawksworth 7:00 More recently, I've been using 11ty it on my own site and various kind of hobby sites of mine and kind of sites of side projects. But at Netlify I we also use all of the all of those as well, you know, we use our .com site is built on Hugo has been for quite some time. But we also use things like React Static, which is which I think is an excellent framework for things like headless cms.org, that's with react static and also static gen. Phil Hawksworth 7:35 So those, those are both websites that that Netlify put together so we use those static site generators. Aa bunch of templates and example sites, I use a 11ty on, which is there's all sorts all over the place. And and the only reason I feel kind of safe in doing that is one of these core properties of JAMstack sites in the you know, I don't need maintain that platform, once it's deployed. You know, if I've deployed something in one framework, one static site generator, I know that that's going to just keep working, as long as I don't, you know, I don't need to go back and keep maintaining it, I know that will be be fine. So I feel reasonably comfortable with, you know, trying out different static site generators, here or there. And knowing that once something's deployed, is just going to stay deployed. Phil Hawksworth 8:22 And that's one of the kind of nice attributes of this stack. And the the overhead really is in remembering how to maintain it. And if you want to make changes, remembering the different templates, and syntax is and those kind of things. But that's one of the hazards of being someone like me, who's kind of dabbling with lots of different static site generators and, and trying lots of different things out at the same time. But and I don't know, that's kind of that's kind of fun, it keeps it fresh as well. Bryan Robinson 8:46 So you're experimenting with a lot. So what what is your current jam, right? Like, what what are you really enjoying using at the moment, or, you know, in the coming, you know, few months? Phil Hawksworth 8:58 I feel like a lot of my colleagues, gonna make fun of me, because I'm always going on about 11ty. And I really enjoy it very much. And it feels, it feels to me a lot like Jekyll, in so much of as it's a it's kind of approach and the logic that sits down within it. But it doesn't have that Ruby speed bump that I mentioned. So it's very, very portable, in terms of both the output that it creates, like all JAMstack sites, but also the build environment is very, very quick and easy to get bootstrapped with it. Phil Hawksworth 9:29 So I've been having just a ton of fun with that, especially as the project's been evolving a little bit. And it started to add things like support for JavaScript in the data files. So that's a fairly kind of common convention, I think, for static site generators to have a folder full of data files that you can use in your templates. And I really like the fact that it will let you write those files with JavaScript, which could go off and make a request and return data. So it makes it very easy to pull data in from different points that build time. It just makes it loads of fun. So yeah, I've been having, I've been having a lot of fun with that recently. Phil Hawksworth 10:08 And the other thing I'd maybe call out is some I've been dabbling more and more with serverless functions, which I know kind of aren't necessarily kind of, from a purist point of view, part of the JAMstack, but they're, they're best friends, I think, you know, they complement each other really, really well. And so I've been having a bit of fun playing with things like using serverless functions as a fallback as a 404. Sso for any routes on my page on my sites that don't, that don't resolve to a pre generated page, sending those off to serverless functions instead, which can then dynamically render on the fly, something that's maybe hitting a data source or something like that. So it's an interesting kind of model. I'll publish some some examples of that. Hopefully, they'll be out by the time this is this is this is published as well. Bryan Robinson 10:55 I'm very, very interested in that. That's, that's a concept that I hadn't even thought about. Phil Hawksworth 10:59 Yeah, it's a really, it's really interesting, because I think there's this temptation sometimes to say, well, we could use serverless function to, to render things on the fly. So we're still kind of, you know, not having a web server. And you know, we don't you know, so we've still, we still got that kind of simplicity in terms of the infrastructure, but you're not pre generating them. So I'm always cautious. I like to try and pregenerate as much as possible. So if something fails, it fails in my house, not in the user's house. But it's interesting thinking of serverless functions as a fallback for 404s, particularly if you're hitting something like a database, when you're generating the pages, you know, what if you're adding content to the database, and while the site is regenerating, and maybe creating other pages, your 404s could hit that database directly. And then return pages is an interesting kind of model just to extend the reach of JAMstack. So yeah, I've been having a lot of fun playing with that recently, Bryan Robinson 11:54 And so so where do you you mentioned pre rendering, and how, you know, that's kind of your philosophy on it? Where do you lie when it comes to like pre render, and then taking over that render with JavaScript on the fly on the front end? Phil Hawksworth 12:08 I'm, I mean, I think that was great. I think it's, it's one of those things that, you know, it's all down to progressive enhancement, right? And treating things as, as a progressive enhancement, and deciding where your baseline is, what are you enhancing from, because you could very easily argue that a JAMstack approaches to render an empty body tag with a div with an ID in it, and then everything comes down the wire is JavaScript, and you do everything in the client. That's perfectly valid. And I think you know, it, there's this word again, it depends, right? Phil Hawksworth 12:42 You know, if you're building an application, maybe that would be fine. But I love to try and get as much pre rendered as possible. So that while you're going off and making the request for JavaScript, the user has something to see. And while your JavaScript being interpreted particularly on things like mobile devices, which we know not everyone's got a powerful iPhone in their pocket, there are lots of like, less powerful devices, even if the connectivity is good, the power that's required to pause and execute and do all this stuff with JavaScript can make things a bit slow. Even if we're doing you know, what feels like a performant thing. We're relying on JavaScript a lot, we need to be careful. So I like to pregenerate as much as humanly possible. And you end up in this position where there's a balancing act, isn't there? Phil Hawksworth 13:28 I mean, you've got to think about what's, what's reasonable, and what starts to add complexity for the sake of being a purist, and way that balance up. But yeah, I like pregenerating as much as possible. And then really thinking about progressive enhancement. And I'll always stand by progressive enhancement. I know, I know, there's some debates around that at the moment. But I think that's the right way to go. Bryan Robinson 13:49 So you've been professionally in this like, full on JAMstack world for a couple years now at Netlify. You were dabbling in it at the agency. Other than obvious being gainfully employed in a JAMstack company, what's going to keep you in the JAMstack going forward. What makes you just kind of deep down? know that that's kind of the future? Phil Hawksworth 14:08 Well, I think, I think a big part of it is seeing the, the JAMstack ecosystem. Gah, that sounds like a terrible, like salesy phrase, isn't it but there are so many tools and vendors now, really supporting this and being a part of it, whether that's the explosion in the different types of headless CMSs or things like image services from people like Cloudinary, or Authentication Service services from people like Auth0, there's so many things coming along people doing ecommerce, there's, there's so much. So I think seeing the advancement in each one of those areas, that's keeping it very interesting for me. Phil Hawksworth 14:48 And it's a I think it's a real validation that the approach is starting to reach critical mass, the fact that businesses are being formed and, and funded and you know, established based on these kind of models. And I think that's really exciting. There are so many people looking at different avenues now, here that we can all make use of that keeps it far from dull, and I love playing with all of the new services as they as they, they surface. It's nice. Bryan Robinson 15:18 So I think you might be uniquely situated to answer this question, which I haven't had a chance to ask before, which is, what are kind of the impediments to JAMstack flourishing in the future? Is it going to keep exploding? Are there any things we need to worry about in terms of hurdles? Phil Hawksworth 15:33 Oh, that's a good question. I mean, it, I always, I'm always surprised about how the boundary seems to seem to get put getting pushed back further and further away. Because you know, the more you look at it, the more you think of think of the model as kind of static first and, you know, approach the approach the architecture, as I'm going to assume things are going to be static, unless I reach something that I just can't make static, and then look at the alternatives, as opposed to doing the other way around, where we might traditionally have thought, Okay, well, I need, I'll have a dynamic back-end, but there might be some opportunities to do things that are cached or make static and what have you. And, and I think that's, that's the harder way to approach it, I much prefer doing it the other way and assuming static first. Phil Hawksworth 16:17 So the roadblocks seem to get pushed further and further away. Um, I think the, probably the ceiling that's hard to get through at the moment is sites that have many, many URLs, many, many pages. So I'm talking many hundreds of thousands or millions of pages, that's really tough to do from a pre generated standpoint. And static site generators are getting faster and smarter about that. And, you know, and I know lots of people are working on trying to get beyond the, this kind of hurdle of can be selectively generate different parts of the site. And it's a fairly complex problem, because the dependency graph of you know, all of your templates and pages isn't very nice, isn't necessarily very easy to visualize, or easy to understand. So that's an interesting challenge. But once we, once we get further down that line, and the site generators get faster and faster, I think that opens the doors to bigger and different types of sites as well that maybe have millions of millions of URLs, which at the moment is, is probably a bit of a ceiling for us. Bryan Robinson 17:20 Well, and really, I'm trying, I'm trying to think of what those sites would be other than, like big news organizations. That's about the only thing I can think of don't have millions of your eyes. Phil Hawksworth 17:31 Yeah, I think typically, that's that's the classic example, you know, news, news organizations, or publications that have, you know, many hundreds of thousands of pages. Yeah. And the other one, of course, is sites that have lots of targeted, personalized content, that can be challenging as well. But again, that starts to become one of those points of how you architect it and what you're what what you value. So for instance, Netlify the app itself and Neltify, you know, where you go and configure your sites and all of those things, that has hundreds of thousands of users using it. And they're all using content, which is specific to them, you know, it's the data which is specific to their sites. But it's a JAMstack site. It's a, it's a staticly served React app, which then talks to dynamic API's. And you, that seems like a good model, you aren't giving up the pre generated nature of every page that might then be cruel, callable by search, search engines and what have you. But that's fine. But in that kind of environment, you know, I don't want the admin view of my website, you know, admin console being crawled by Google. So it's, there's a balancing act, and it's trying to figure out what's, what's appropriate and what you actually want. But yeah, so serving personalized content to people and then having that crucibles because you needed regenerated. That's another challenge. But I don't always know if it's actually required. Bryan Robinson 19:02 And on top of that, like most of those personalized things, you don't want crawlable anyway. So you probably right, as long as as long as you are connected in a way that the user gets the content properly, then you're probably pretty good to go. Phil Hawksworth 19:13 Yeah, I think so. Yeah. So it's always a balancing act. And then I'm very cautious about describing anything as a silver bullet. And there are so many different ways that we can approach these architectures with the, with the tools that we've got in the jam stack. ecosystem, there's that word again. There's so many tools and approaches that we can take that we can kind of cut the cloth to suit what we need, I think, Bryan Robinson 19:34 So obviously, I try to keep these relatively short. So I'm gonna go ahead and move into the next question, which is, what are you actually jamming to right now? What what's your musical jam? Phil Hawksworth 19:43 Oh, this is a great question. Well, obviously, Toto is never far from the top of my history. It's amazing how often I fall back to having some Toto being played is particularly good on a Friday afternoon, I think, when I need a little bit of a spring in my step. Phil Hawksworth 20:04 But I one of the things I actually often find myself writing code to is the, the, the code radio that Free Code Camp provided. And if you've encountered that, it's just, it's just a YouTube link. And it's like this 24/7 music that's good to code by radio. And it's kind of nice as well, because you tuned in there, and you can see how many other people are listening as well. So even though you're not interacting in any way at all, you've got this kind of solidarity, which is kind of nice. Phil Hawksworth 20:34 So those two things, but the only other thing I'd probably mentioned his Gaz Coombes, who he used to be the lead singer of super grass going back way, way back. But he's, he's got some albums out at the moment that I really, really like, and kind of keep me keep me interested as I'm kind of writing things and and building code. So yeah, definitely recommend Gaz Coombes, I think called Matador that I've been listening to a lot. It's good stuff. Bryan Robinson 21:03 I'll find that and tuck that in the show notes. So anything that you're you're looking to promote, obviously, you're identified, but anything specific, you want to talk about Phil Hawksworth 21:11 the so there's probably just just two things. And depending on the timing of this, we've got JAMstack conference coming up in San Francisco, on the 16th, 17th, and 18th of October. So who knows, maybe this will squeak out into the world in time. Hopefully it's coming up very quickly. So that's, that's coming up. Phil Hawksworth 21:30 And the only other thing I'd call out is there's now a nice slack community growing for the JAMstack community. And there are already a couple of good places to talk like TheNewDynamic Slack is a brilliant place that I'd recommend to people. But also for people who are maybe going to JAMstack conferences and meetups jamstack.org/slack will get you into a good place for for talking about all things JAMstack, we, we foolishly didn't call it JAMslack, which I think Jake Archibald kind of mentioned was a huge missed opportunity but so be it will have to that's just that's just a mess that will have to live with Bryan Robinson 22:11 and I might be a little too kitschy for some people though. Phil Hawksworth 22:16 Yeah, we've we've stuck with just jamstack.org/slack Bryan Robinson 22:22 Alright. Well, I want to thank you for for taking the time and talking with us today. And and I want to say I appreciate all the all the different content that you put out. Phil Hawksworth 22:30 Oh, that's very kind. Well, thanks for this. It's, it's nice to get to talk. And yeah, I've really enjoyed listening to everyone you've had on so we're looking forward to whoeverTranscribed by https://otter.aiIntro/outtro music by bensound.com

My guest on today’s show is a Developer Advocate at Google working with the Chrome team to develop and promote web standards and developer tools.  Prior to Google he worked at Lanyrd on their mobile website and for the BBC on JavaScript libraries and standards. He says that he wants the web to do what native does best, and fast. EPISODE DESCRIPTION: Phil’s guest on today’s show is Jake Archibald. He is a Developer Advocate at Google. Currently, he is working with the Chrome team developing and promoting innovative tools like squoosh.app. He is there to promote web standards and developer tools to all who will listen. Before beginning his career at Google he worked for the BBC developing their web services and JavaScript library and standards. Later he moved to Lanyrd. Today, he is a well-known conference speaker. Jake has delivered talks at JSConf.Asia, LDNWebPerf and SmashingConf London, to name a few. KEY TAKEAWAYS: (00.49) –Could you give us an understanding of what your current role with Google as a developer advocate is like? Jake starts out by explaining that it is a really varied role that changes from day to day. Last year, he was working on Squoosh.app, an image compression tool for the web. It uses codecs from C and Rust to compress images in the browser. Other times he works on web standards. He is also involved in fixing Chrome bugs. He sees is role as promoting the web rather than just Google services. When other browsers get things right they praise and promote them too. His aim is to help everyone to get more out of the web and working for Google has not constrained him at all he has been given the freedom to speak freely, which helps things to move forward faster. (3.50) Phil asks him to tell the audience about his work with the BBC, which was also all about web standards. Initially, Jake made web pages for TV shows. He then moved on to work on the BBC’s JavaScript library, which they use on pretty much every one of their pages. One of the biggest challenges he faced then, was keeping everything backward compatible. BBC policy meant that everything they produced had to be accessible using free tools, even older versions. Because, at the time, the newest version of Safari was a paid for tool, everything they built had to be compatible with the older version because it was still free. (5.41) – Can you please share a unique career tip with the I.T. career audience? The thing that made Jake successful was being in the right place at the right time. He feels there is an element of luck involved in everything. When he started out he knew very little about the web. But, within 2 years he had learned most of CSS, HTML, and JavaScript. So, when the web exploded he was able to exploit that knowledge to the full. This was despite the fact that there were, and still are, gaps in his knowledge. Not knowing everything will not stop you from progressing in your IT career. So, don’t get hung up about it. Just maximize what you do with your current skills and keep on learning to succeed. (8.00) – Can you tell us about your worst career moment? That happened early in his career. He was working for a large corporation looking after their site and intranet. One day the HR department asked him to take some of the job postings and install them on their intranet. It sounded easy but was far from it. The way their site worked with cookies made it very tricky to scrape the information, so it could be added to the intranet. At the time, he knew nothing about Perl. But, it was really the only solution. So, he had no choice but to work out how to do it. After a bit, he managed it and the team he was working with were really pleased. But, he realized they had zero understanding of what it had taken to achieve that result. At that point, he realized he had not found his dream job. In fact, it was going to be quite limiting, so he had no choice but to move on. That felt pretty bad. He was pretty disappointed. The other worst moment was when he broke the BBC’s iPlayer, their streaming service. He had not uploaded something properly. An error which, after two weeks, broke the corporation’s streaming service when a rarely used server was pulled into use. Only then did the error become apparent. He was blamed, despite the fact that it was a weakness in the deployment system that ultimately caused the issue. (13.58) – What was your best career moment? For Jake, being able to contribute to the HTML spec was a huge moment. The web will outlive him, so it feels good to be leaving a legacy, something which others will continue to benefit from. (15.45) – What excites you about the future of the IT industry and careers? For Jake, the fact that the web and JavaScript are still growing is exciting. In 10 years it is going to look very different than it does now. We are going to be able to do so much more with it. (17.55) – What drew you to a career in IT? When Jake was given his first computer at about the age of 7, he was hooked. He loved programming stuff that resulted in immediate visual feedback. So, he fell in love with the web the moment he was introduced to it. (19.00) – What is the best career advice you have ever received? One of Jake’s first jobs was working for a UK retail chain called GAME. Weirdly, his then boss told him to “get out of retail as soon as possible.” He pointed out that the pay was awful and the job was rarely enjoyable. At the time, the job fitted in well with his studies, so he stayed. But, he took the advice to heart and was careful to make sure he did not follow a career path that led to him working in retail. (20.55) - Conversely, what is the worst career advice you've ever received? Interestingly, that came from a deputy manager at GAME. He wanted him to go into retail management. Fortunately, his direct boss had already pointed out to him the pitfalls of that career path. So, Jake did not make the mistake of staying in retail. (21.19) – If you were to begin your IT career again, right now, what would you do? Jake would make sure that he got a grounding in the basics. His career path meant he skipped a lot of the simpler stuff. Now, he is struggling a bit because of this. He wishes he had done more of a computer science based course. Instead of the multimedia orientated one he actually completed. (22.38) – What are you currently focusing on in your career? Jake’s primary objective is not to get promoted into misery. It is something that he has seen happen to others. It is all too easy to get taken further away from what you enjoy doing every time you get promoted. Plus, of course, every time you move up the ladder you end up with more responsibility. He would rather take a sideways move than end up doing something he does not enjoy. Right now, his focus is web performance. He thinks that a lot of the bundling tools have got things wrong. So, that is very much a focus. (24.07) – What is the number one non-technical skill that has helped you the most in your IT career? Becoming a confident speaker has made a huge difference to Jake’s career. One conference talk led to another until he started to become well know. When that happened, finding work became really easy. The thing he enjoys most about conferences is speaking to people after he has given his talk. Jake finds that he learns so much from those conversations. (27.00) - What do you do to keep your own IT career energized? Jake says that he embraces procrastination. The most important work he has done has happened when he has meandered away a bit from what he should have been doing. Giving yourself a little time to explore is a great way to get the creative process going and come up with something really different. It is a great way to break the cycle of boredom and re-energize yourself so you can get some of the more tedious stuff done. (29.13) - What do you do in your spare time away from technology? Jake walks a lot, especially in the countryside. He finds it to be a good way to get away from things, take a bit of exercise, re-set and re-energize. (31.00) – Phil asks Jake to share a final piece of career advice with the audience. While at school his art teacher said to him “you get better with every painting that you paint.” Now, he realizes that is true of coding too. You need to practice to get good at it. If you are not developing the skills you want on the job. Take on small projects outside of the workplace to help you to do so. BEST MOMENTS: (2.35) JAKE – “I’m paid by Google to promote all things web." (5.50) JAKE – "Learn to be in the right place at the right time." (14.11) JAKE – "Contributing to the HTML spec was a huge moment for me." (16.36) JAKE – "In 10 years, we're going to look at the web now and think that looks so ancient." (22.40) JAKE – "Don’t get promoted into misery." (27.00) JAKE – "Embrace procrastination, as much as time allows." CONTACT JAKE: Twitter: https://twitter.com/jaffathecake GitHub: https://github.com/jakearchibald/ Website: https://jakearchibald.com/

The other day I got to watch a few talks from JSConf Asia 2018 on Youtube. There are 39 of them in the playlist, so I picked a random one. And I got so lucky I just had to make this episode about it! The talk was "In the Loop" by Jake Archibald. Jake is developer advocate for Google Chrome. He's one of the editors of the service worker spec, so he's into offline-first, push messaging and web performance. - https://www.youtube.com/playlist?list=PL37ZVnwpeshFqN5dcZ704lxI3F5iHDYkl - JSConf.Asia 2018 - https://youtu.be/cCOL7MC4Pl0 - Jake Archibald: In The Loop - https://youtu.be/rLgBqT_e6Yo - Feross Aboukhadijeh: JavaScript Pranks 5 minutes of React - podcast about React hot topics and JavaScript ecosystem. https://5minreact.audio

A lot of folks have been looking into the CSS keylogging demo that Max Chehab has put out. On the heels of that, Jake Archibald has written up a nice look on why it’s a...

In this Modern Web Podcast Tracy Lee (@ladyleet) and Ben Lesh (@benlesh) speak with guests Jake Archibald (@jaffathecake) and Jay Phelps (@_jayphelps) to talk about upcoming proposals in TC39 and WHATWG.   Proposals discussed:EventTarget Observable Proposal in WHATWGObservable Proposal in TC39 https://github.com/tc39/proposal-observable BigInt Proposal in TC39https://github.com/tc39/proposal-bigint Structure Cloning in WHATWGhttps://github.com/whatwg/html/issues/793 Pipeline operator in TC39https://github.com/tc39/proposal-pipeline-operator Other topics:How to get involved if you care about a proposalWhat Ben looks like with yogurt on his noseTracy’s BF said “let’s git committed!"   To learn more visit www.thisdot.co   Follow us on Twitter @moderndotweb http://moderndotweb.com

Panel: Charles Max Wood Guest: Houssein Djirdeh This week on My Angular Story, Charles speaks with Houssein Djirdeh. Houssein works at Rangle currently and first got into programming during an intro to programming course in college and he initially hated it. A few years later he found out that he really was interested in programming when he wanted to build a website. From there he discovered JavaScript and Angular and has never looked back. He is most proud of his work on multiple Open Source projects and his blog posts. In particular, We dive pretty deep on:  Progressive applications How did you first get into programming? Studies mechanical engineering C programming, Basic, and Sequel Building a website How did you get into JavaScript? What have you done with JavaScript that you are proud of? Open Source projects and blog posts Node Rangle Works most on front end programming He focuses on both content as well as coding in his day to day life What are you working on now? GitPoint app React, View, and Angular How do you decide what to learn next? And much, much more! Links:  Linode Rangle GitPoint app FreshBooks @HDjirdeh Houssein.me   Picks: Charles React Roundup and Views on View Podcasts Houssein Ivy In the Loop by Jake Archibald Dark

Panel: Charles Max Wood Guest: Houssein Djirdeh This week on My Angular Story, Charles speaks with Houssein Djirdeh. Houssein works at Rangle currently and first got into programming during an intro to programming course in college and he initially hated it. A few years later he found out that he really was interested in programming when he wanted to build a website. From there he discovered JavaScript and Angular and has never looked back. He is most proud of his work on multiple Open Source projects and his blog posts. In particular, We dive pretty deep on:  Progressive applications How did you first get into programming? Studies mechanical engineering C programming, Basic, and Sequel Building a website How did you get into JavaScript? What have you done with JavaScript that you are proud of? Open Source projects and blog posts Node Rangle Works most on front end programming He focuses on both content as well as coding in his day to day life What are you working on now? GitPoint app React, View, and Angular How do you decide what to learn next? And much, much more! Links:  Linode Rangle GitPoint app FreshBooks @HDjirdeh Houssein.me   Picks: Charles React Roundup and Views on View Podcasts Houssein Ivy In the Loop by Jake Archibald Dark

Panel: Charles Max Wood Guest: Houssein Djirdeh This week on My Angular Story, Charles speaks with Houssein Djirdeh. Houssein works at Rangle currently and first got into programming during an intro to programming course in college and he initially hated it. A few years later he found out that he really was interested in programming when he wanted to build a website. From there he discovered JavaScript and Angular and has never looked back. He is most proud of his work on multiple Open Source projects and his blog posts. In particular, We dive pretty deep on:  Progressive applications How did you first get into programming? Studies mechanical engineering C programming, Basic, and Sequel Building a website How did you get into JavaScript? What have you done with JavaScript that you are proud of? Open Source projects and blog posts Node Rangle Works most on front end programming He focuses on both content as well as coding in his day to day life What are you working on now? GitPoint app React, View, and Angular How do you decide what to learn next? And much, much more! Links:  Linode Rangle GitPoint app FreshBooks @HDjirdeh Houssein.me   Picks: Charles React Roundup and Views on View Podcasts Houssein Ivy In the Loop by Jake Archibald Dark

Jake is a developer advocate for Google Chrome where he speaks regularly about Service Worker, application performance, and offline-first apps. Before joining the team at Google, Jake worked at Lanyrd honing his performance skills, and before that worked at the BBC creating an inclusive experience for users with disabilities.

Descripcion del programa José Manuel es ingeniero de software, trabaja como desarrollador web en Estocolmo para Spotify. Especializado en web performance optimization, SEO y accesibilidad. Con él nos adentraremos en el mundo de las Progressive Web Apps, y veremos como gracias al nuevo Catálogo de Apis podemos realizar acciones tales como notificaciones push, almacenamiento local y ejecución offline entre muchas otras. ¡Esperamos que os guste el episodio y como siempre nos vemos al final! ¿Queréis participar? ¿Queréis participar y ayudarnos a decidir que grabar en WeCodeSign y proponer invitad@s? Aquí podéis participar en WeCodeSign. Recomendaciones Preguntas rápidas: José Manuel Quién me ha inspirado: Alberto Quién me ha inspirado: Davide Mendolia Quién me ha inspirado: Felipe Ribeiro Quién me ha inspirado: Steve Souders Quién me ha inspirado: Nicholas C. Zakas Quién me ha inspirado: Addy Osmani Quién me ha inspirado: Dan Abramov Quién me ha inspirado: Stoyan Stefanov Recomiéndanos un recurso: Frontend Focus Recomiéndanos un recurso: JavaScript Weekly Recomiéndanos un recurso: Chrome and Web at Google I/O 2017 Recomiéndanos un recurso: JS Conf Recomiéndanos un recurso: CSS-Tricks Recomiéndanos un recurso: Smashing Magazine Recomiéndanos un recurso: High Performance Browser Networking Recomiéndanos a un invitado o invitada: Jaume Sanchez Elias ¿Qué tema te gustaría que tratásemos?: Web Performance Contacta con: José Manuel Twitter de José Manuel Web de José Manuel Links del programa Hilo sobre cómo aparecieron las PWA, por Alex Russell Progressive Web Apps: Great Experiences Everywhere (Google I/O '17) Production Progressive Web Apps With JavaScript Frameworks (Google I/O '17) PWA Directory Progressive Web Apps La guía sin conexión by Jake Archibald The Service Worker Cookbook Service Worker Tools Service Worker Pre Cache Tu primera Progressive Web App by Pete LaPage Building Progressive Web Apps A big list of progressive web app tips and tricks The State of Progressive Web Apps Production Progressive Web Apps with JavaScript Frameworks Qué son las Aplicaciones Web Progresivas o "Progressive Web Apps" Progressive web apps PWA: Para Webs Asombrosas Recomendaciones de Ignacio Progressive Web App questions Progressive Web App Checklist The PWA Resource list Lighthouse Patrocinadores Fictizia.com Contacta con Ignacio Web de WeCodeSign Twitter de WeCodeSign eMail de WeCodeSign Web de Ignacio Villanueva Twitter de Ignacio Villanueva

AiA 146: 10 Ways to Lose a Developer with Bonnie Brennan and Keith Stewart On today's episode of Adventures in Angular, we have panelists Ward Bell, Alyssa Nicoll, Joe Eames, and Charles Max Wood. We have special guests, Bonnie Brennan of ngHouston and Keith Stewart of CollabNet. The discussion ranges from the Most Common Reason for People to Leave to Mandatory Happy Hour that companies have! Stay tuned! [00:01:05] Introduction to Bonnie Brennan and Keith Stewart Bonnie is an Angular architect at Houston, Texas. She is the founder of ngHouston. She also runs Code Bridge Texas with her daughter. They do free programming workshops for girls. She’s going to be at a couple of conferences coming up. They’re going to AngularMix and FrontEnd Connect with Alyssa. Keith, on the other hand, works for a company called CollabNet as a UI Tech Lead. He is working mostly on UI’s for DevOps-related products. He is also a frequent panelist on the ngHouston Meet up broadcast that Bonnie runs and a curator on ngDoc.io with Alyssa and Joe. [00:03:20] – Most common reason for people to leave If Bonnie has to narrow down, she thinks it’s the tech stack. Some companies have a lot of legacy code that needs to be maintained but at the same time, when you are a developer who spends a lot of time on emerging technologies, you want to be working on this new stuff that you’re learning. While working on this course on how to find a better dev job, Charles surveyed people on Skype or the phone. They feel stuck and not moving ahead. [00:10:50] – In the culture, if you’re not a performer, then, you’re not trying hard enough? Joe thinks that we have this problem in this industry that if you are not going to be blogging and speaking at conferences, then, you just don’t belong. Ward also thinks that you don’t have to be a performer to contribute to a great development environment. But for Bonnie, being a performer is not exactly about getting up on stage. It really is about caring enough. Alyssa tells about the gradient of the type of person. There’s a person like, “Okay, this is just a job for me but I still take pride in my work.” But if you’re in the mindset of “Hey, I have kids or I have a wife outside of this. But I’m still giving it my all while I’m here.” Then, it’s perfectly reasonable. Keith also tells about the two different types of people. The generalists, the folks who are on the bleeding-edge, they don’t necessarily master one of those, and the other folks who get really good at one particular thing that they’re working on. Ward cites an instance where you’re in an enterprise and you have a lot of very important legacy systems that need a person who cares about the legacy stuff. You can’t have a company that has all people who have to be on the bleeding-edge all the time. [00:18:55] – Type of developers that companies want and how to keep them Ward mentions how professional growth is important. The opportunities for people to work on the leading technologies is not always something that every company can offer but they can sprinkle these opportunities here and there. It can be done but if it’s not, there are things that you can do with some of the legacy applications to make them more palatable to work on. Charles suggests to companies to show the developers that you care, you are listening. It’s on the roadmap and you’re going to get there. [00:22:55] – Is boss on your list of Ways to Lose a Developer? Bonnie can’t think of the time that she has left because of her boss. But the company culture is an important thing because however, the upper management feels about culture, that’s going to trickle down. One issue about Charles’ boss is that he is very controlling. Another issue is he was specifying the requirements for the application and he wasn’t very good at staying consistent with it. They wind up building one thing but gets angry with them because they hadn’t built what he wanted, even though it was exactly what he specified. Bonnie also had a situation similar to Charles where the project requirements kept changing while she was writing the code. If you feel like you’re going to work to be frustrated again, it doesn’t matter what technology you’re using, it doesn’t matter how you like the rest of your co-workers, eventually, you’re going to burn out. [00:27:00] – Not being paid enough When you’re not making a whole lot of money, Bonnie thinks it can be a big deal but it’s not the biggest issue. For Keith, if he would be weighing two companies, he’ll also choose the company with the good tech stack instead of the company which pays a little higher. But Ward thinks that it is a privilege to be in an industry where even in the low-end of the salary rank, you tend to be pretty comfortable. [00:29:55] – Effective ways to show your appreciation to a developer Bonnie refers to an instance when the boss gives credit for a developer in a meeting on how he did a great job on a feature. And on the flipside, the worst kind of boss is the boss that says, “Look what I did.” But Keith finds it a difficult question because it might be different for other people. Some people like to be called out in a meeting and say, “You did a good job.” But some folks would like that to be a little more behind the scenes. Or some folks might be looking for a bonus instead. So you might be able to read your people. For Alyssa, she likes the boss who regularly checks in even if it’s not a pat on the back because it just shows that they care about the process. Ward speaks of the boss who asks your opinion on an important decision, technical or otherwise. [00:37:40] – Recruitment Keith never likes the recruitment process of companies which bring a lot of people in and give them coding exercises on a whiteboard. So they built a small application that’s similar to the application that the folks will actually be doing. [00:41:05] – Remote vs. working in an office Alyssa loves being remote. She mentions she has ADHD so she was distracted in an office setting. It’s important for her to set up her environment to be more productive. Bonnie also has been working remote for 3 years now. It used to be difficult to communicate but now, we can just use video call. But Keith finds people more engaged in a meeting when it’s in person. An office space can add a lot of value to a team. Ward points out that you can also be distracted as well by working remote. In Google, they all work in the office. Even though they have open office plans, sitting right next to each other, they trust the people that they can do well in that environment. People put on headphones when they’re really focusing on something. [00:53:20] – Mandatory happy hour Companies which have a snack room, ping pong table, foosball can contribute to company culture and make it a much more attractive place for developers. But Alyssa gets scared a little bit when programmers go overboard and sometimes you’re not into it as much as they are. Picks Ward Bell Progressive Web Apps (PWA) Jake Archibald on PWA Joe Eames Shimmer Lake Keith Stewart Charles Angular Dev Summit Camelbak Eddy water bottle JAM XT Bluetooth speaker Bonnie Brennan Pluralsight course on Angular Reactive Forms by Deborah Kurata Todd Motto’s Ultimate Angular JS Twitter @bonnster75 Youtube ngHouston Angular Meetup Keith Stewart Adam Laycock’s blog post: Building maintainable Angular 2 applications Rogue One Twitter @TheKeithStewart

AiA 146: 10 Ways to Lose a Developer with Bonnie Brennan and Keith Stewart On today's episode of Adventures in Angular, we have panelists Ward Bell, Alyssa Nicoll, Joe Eames, and Charles Max Wood. We have special guests, Bonnie Brennan of ngHouston and Keith Stewart of CollabNet. The discussion ranges from the Most Common Reason for People to Leave to Mandatory Happy Hour that companies have! Stay tuned! [00:01:05] Introduction to Bonnie Brennan and Keith Stewart Bonnie is an Angular architect at Houston, Texas. She is the founder of ngHouston. She also runs Code Bridge Texas with her daughter. They do free programming workshops for girls. She’s going to be at a couple of conferences coming up. They’re going to AngularMix and FrontEnd Connect with Alyssa. Keith, on the other hand, works for a company called CollabNet as a UI Tech Lead. He is working mostly on UI’s for DevOps-related products. He is also a frequent panelist on the ngHouston Meet up broadcast that Bonnie runs and a curator on ngDoc.io with Alyssa and Joe. [00:03:20] – Most common reason for people to leave If Bonnie has to narrow down, she thinks it’s the tech stack. Some companies have a lot of legacy code that needs to be maintained but at the same time, when you are a developer who spends a lot of time on emerging technologies, you want to be working on this new stuff that you’re learning. While working on this course on how to find a better dev job, Charles surveyed people on Skype or the phone. They feel stuck and not moving ahead. [00:10:50] – In the culture, if you’re not a performer, then, you’re not trying hard enough? Joe thinks that we have this problem in this industry that if you are not going to be blogging and speaking at conferences, then, you just don’t belong. Ward also thinks that you don’t have to be a performer to contribute to a great development environment. But for Bonnie, being a performer is not exactly about getting up on stage. It really is about caring enough. Alyssa tells about the gradient of the type of person. There’s a person like, “Okay, this is just a job for me but I still take pride in my work.” But if you’re in the mindset of “Hey, I have kids or I have a wife outside of this. But I’m still giving it my all while I’m here.” Then, it’s perfectly reasonable. Keith also tells about the two different types of people. The generalists, the folks who are on the bleeding-edge, they don’t necessarily master one of those, and the other folks who get really good at one particular thing that they’re working on. Ward cites an instance where you’re in an enterprise and you have a lot of very important legacy systems that need a person who cares about the legacy stuff. You can’t have a company that has all people who have to be on the bleeding-edge all the time. [00:18:55] – Type of developers that companies want and how to keep them Ward mentions how professional growth is important. The opportunities for people to work on the leading technologies is not always something that every company can offer but they can sprinkle these opportunities here and there. It can be done but if it’s not, there are things that you can do with some of the legacy applications to make them more palatable to work on. Charles suggests to companies to show the developers that you care, you are listening. It’s on the roadmap and you’re going to get there. [00:22:55] – Is boss on your list of Ways to Lose a Developer? Bonnie can’t think of the time that she has left because of her boss. But the company culture is an important thing because however, the upper management feels about culture, that’s going to trickle down. One issue about Charles’ boss is that he is very controlling. Another issue is he was specifying the requirements for the application and he wasn’t very good at staying consistent with it. They wind up building one thing but gets angry with them because they hadn’t built what he wanted, even though it was exactly what he specified. Bonnie also had a situation similar to Charles where the project requirements kept changing while she was writing the code. If you feel like you’re going to work to be frustrated again, it doesn’t matter what technology you’re using, it doesn’t matter how you like the rest of your co-workers, eventually, you’re going to burn out. [00:27:00] – Not being paid enough When you’re not making a whole lot of money, Bonnie thinks it can be a big deal but it’s not the biggest issue. For Keith, if he would be weighing two companies, he’ll also choose the company with the good tech stack instead of the company which pays a little higher. But Ward thinks that it is a privilege to be in an industry where even in the low-end of the salary rank, you tend to be pretty comfortable. [00:29:55] – Effective ways to show your appreciation to a developer Bonnie refers to an instance when the boss gives credit for a developer in a meeting on how he did a great job on a feature. And on the flipside, the worst kind of boss is the boss that says, “Look what I did.” But Keith finds it a difficult question because it might be different for other people. Some people like to be called out in a meeting and say, “You did a good job.” But some folks would like that to be a little more behind the scenes. Or some folks might be looking for a bonus instead. So you might be able to read your people. For Alyssa, she likes the boss who regularly checks in even if it’s not a pat on the back because it just shows that they care about the process. Ward speaks of the boss who asks your opinion on an important decision, technical or otherwise. [00:37:40] – Recruitment Keith never likes the recruitment process of companies which bring a lot of people in and give them coding exercises on a whiteboard. So they built a small application that’s similar to the application that the folks will actually be doing. [00:41:05] – Remote vs. working in an office Alyssa loves being remote. She mentions she has ADHD so she was distracted in an office setting. It’s important for her to set up her environment to be more productive. Bonnie also has been working remote for 3 years now. It used to be difficult to communicate but now, we can just use video call. But Keith finds people more engaged in a meeting when it’s in person. An office space can add a lot of value to a team. Ward points out that you can also be distracted as well by working remote. In Google, they all work in the office. Even though they have open office plans, sitting right next to each other, they trust the people that they can do well in that environment. People put on headphones when they’re really focusing on something. [00:53:20] – Mandatory happy hour Companies which have a snack room, ping pong table, foosball can contribute to company culture and make it a much more attractive place for developers. But Alyssa gets scared a little bit when programmers go overboard and sometimes you’re not into it as much as they are. Picks Ward Bell Progressive Web Apps (PWA) Jake Archibald on PWA Joe Eames Shimmer Lake Keith Stewart Charles Angular Dev Summit Camelbak Eddy water bottle JAM XT Bluetooth speaker Bonnie Brennan Pluralsight course on Angular Reactive Forms by Deborah Kurata Todd Motto’s Ultimate Angular JS Twitter @bonnster75 Youtube ngHouston Angular Meetup Keith Stewart Adam Laycock’s blog post: Building maintainable Angular 2 applications Rogue One Twitter @TheKeithStewart

AiA 146: 10 Ways to Lose a Developer with Bonnie Brennan and Keith Stewart On today's episode of Adventures in Angular, we have panelists Ward Bell, Alyssa Nicoll, Joe Eames, and Charles Max Wood. We have special guests, Bonnie Brennan of ngHouston and Keith Stewart of CollabNet. The discussion ranges from the Most Common Reason for People to Leave to Mandatory Happy Hour that companies have! Stay tuned! [00:01:05] Introduction to Bonnie Brennan and Keith Stewart Bonnie is an Angular architect at Houston, Texas. She is the founder of ngHouston. She also runs Code Bridge Texas with her daughter. They do free programming workshops for girls. She’s going to be at a couple of conferences coming up. They’re going to AngularMix and FrontEnd Connect with Alyssa. Keith, on the other hand, works for a company called CollabNet as a UI Tech Lead. He is working mostly on UI’s for DevOps-related products. He is also a frequent panelist on the ngHouston Meet up broadcast that Bonnie runs and a curator on ngDoc.io with Alyssa and Joe. [00:03:20] – Most common reason for people to leave If Bonnie has to narrow down, she thinks it’s the tech stack. Some companies have a lot of legacy code that needs to be maintained but at the same time, when you are a developer who spends a lot of time on emerging technologies, you want to be working on this new stuff that you’re learning. While working on this course on how to find a better dev job, Charles surveyed people on Skype or the phone. They feel stuck and not moving ahead. [00:10:50] – In the culture, if you’re not a performer, then, you’re not trying hard enough? Joe thinks that we have this problem in this industry that if you are not going to be blogging and speaking at conferences, then, you just don’t belong. Ward also thinks that you don’t have to be a performer to contribute to a great development environment. But for Bonnie, being a performer is not exactly about getting up on stage. It really is about caring enough. Alyssa tells about the gradient of the type of person. There’s a person like, “Okay, this is just a job for me but I still take pride in my work.” But if you’re in the mindset of “Hey, I have kids or I have a wife outside of this. But I’m still giving it my all while I’m here.” Then, it’s perfectly reasonable. Keith also tells about the two different types of people. The generalists, the folks who are on the bleeding-edge, they don’t necessarily master one of those, and the other folks who get really good at one particular thing that they’re working on. Ward cites an instance where you’re in an enterprise and you have a lot of very important legacy systems that need a person who cares about the legacy stuff. You can’t have a company that has all people who have to be on the bleeding-edge all the time. [00:18:55] – Type of developers that companies want and how to keep them Ward mentions how professional growth is important. The opportunities for people to work on the leading technologies is not always something that every company can offer but they can sprinkle these opportunities here and there. It can be done but if it’s not, there are things that you can do with some of the legacy applications to make them more palatable to work on. Charles suggests to companies to show the developers that you care, you are listening. It’s on the roadmap and you’re going to get there. [00:22:55] – Is boss on your list of Ways to Lose a Developer? Bonnie can’t think of the time that she has left because of her boss. But the company culture is an important thing because however, the upper management feels about culture, that’s going to trickle down. One issue about Charles’ boss is that he is very controlling. Another issue is he was specifying the requirements for the application and he wasn’t very good at staying consistent with it. They wind up building one thing but gets angry with them because they hadn’t built what he wanted, even though it was exactly what he specified. Bonnie also had a situation similar to Charles where the project requirements kept changing while she was writing the code. If you feel like you’re going to work to be frustrated again, it doesn’t matter what technology you’re using, it doesn’t matter how you like the rest of your co-workers, eventually, you’re going to burn out. [00:27:00] – Not being paid enough When you’re not making a whole lot of money, Bonnie thinks it can be a big deal but it’s not the biggest issue. For Keith, if he would be weighing two companies, he’ll also choose the company with the good tech stack instead of the company which pays a little higher. But Ward thinks that it is a privilege to be in an industry where even in the low-end of the salary rank, you tend to be pretty comfortable. [00:29:55] – Effective ways to show your appreciation to a developer Bonnie refers to an instance when the boss gives credit for a developer in a meeting on how he did a great job on a feature. And on the flipside, the worst kind of boss is the boss that says, “Look what I did.” But Keith finds it a difficult question because it might be different for other people. Some people like to be called out in a meeting and say, “You did a good job.” But some folks would like that to be a little more behind the scenes. Or some folks might be looking for a bonus instead. So you might be able to read your people. For Alyssa, she likes the boss who regularly checks in even if it’s not a pat on the back because it just shows that they care about the process. Ward speaks of the boss who asks your opinion on an important decision, technical or otherwise. [00:37:40] – Recruitment Keith never likes the recruitment process of companies which bring a lot of people in and give them coding exercises on a whiteboard. So they built a small application that’s similar to the application that the folks will actually be doing. [00:41:05] – Remote vs. working in an office Alyssa loves being remote. She mentions she has ADHD so she was distracted in an office setting. It’s important for her to set up her environment to be more productive. Bonnie also has been working remote for 3 years now. It used to be difficult to communicate but now, we can just use video call. But Keith finds people more engaged in a meeting when it’s in person. An office space can add a lot of value to a team. Ward points out that you can also be distracted as well by working remote. In Google, they all work in the office. Even though they have open office plans, sitting right next to each other, they trust the people that they can do well in that environment. People put on headphones when they’re really focusing on something. [00:53:20] – Mandatory happy hour Companies which have a snack room, ping pong table, foosball can contribute to company culture and make it a much more attractive place for developers. But Alyssa gets scared a little bit when programmers go overboard and sometimes you’re not into it as much as they are. Picks Ward Bell Progressive Web Apps (PWA) Jake Archibald on PWA Joe Eames Shimmer Lake Keith Stewart Charles Angular Dev Summit Camelbak Eddy water bottle JAM XT Bluetooth speaker Bonnie Brennan Pluralsight course on Angular Reactive Forms by Deborah Kurata Todd Motto’s Ultimate Angular JS Twitter @bonnster75 Youtube ngHouston Angular Meetup Keith Stewart Adam Laycock’s blog post: Building maintainable Angular 2 applications Rogue One Twitter @TheKeithStewart

This week we speak to Jake Archibald about communication.

Just because it requires JavaScript, doesn't make it wrong, but we often use JavaScript to engineer-away the parts of the web that are already better than native. Let's take a look at some real-world JavaScript-heavy applications, and how they can regain the performance of the web without losing features. Then, let's tackle the area progressive enhancement has largely ignored: Connectivity. More info at: https://fronteers.nl/congres/2015/sessions/modern-progressive-enhancement-jake-archibald

Just because it requires JavaScript, doesn't make it wrong, but we often use JavaScript to engineer-away the parts of the web that are already better than native. Let's take a look at some real-world JavaScript-heavy applications, and how they can regain the performance of the web without losing features. Then, let's tackle the area progressive enhancement has largely ignored: Connectivity. More info at: https://fronteers.nl/congres/2015/sessions/modern-progressive-enhancement-jake-archibald

Turning their oscillating online outing into a decidedly destructive down-to-earth diatribe - for one night only - in the blue corner: it's Peter-Paul "The Wall" Koch, QuirksMode's quaestor, and in the red corner, it's Young Jaffa, the boy bashful, the Web's wondrous wizard: Jake "The Cake" Archibald. Presented and moderated like no other, in the Amsterdam 2015 Fronteers Jam Session Arena, by that inimitable imperator, Opera's own Ozymandias, Fronteers's MC, Mr: Bruce "The Law" Lawson. More info at: https://fronteers.nl/congres/2015/jam-session

Turning their oscillating online outing into a decidedly destructive down-to-earth diatribe - for one night only - in the blue corner: it's Peter-Paul "The Wall" Koch, QuirksMode's quaestor, and in the red corner, it's Young Jaffa, the boy bashful, the Web's wondrous wizard: Jake "The Cake" Archibald. Presented and moderated like no other, in the Amsterdam 2015 Fronteers Jam Session Arena, by that inimitable imperator, Opera's own Ozymandias, Fronteers's MC, Mr: Bruce "The Law" Lawson. More info at: https://fronteers.nl/congres/2015/jam-session

Summary The Offline First Heroes, Jan Lehnardt (@janl), John Kleinschmidt (@jkleinsc), Alex Russell (@slightlylate), and Jake Archibald (@jaffathecake) join forces to chat on why web developers should be designing and building with offline capabilities in mind from the beginning. From emerging standards like ServiceWorker to well thought out web frameworks like Hood.ie & UpUp, there are many differnt approaches and reasons why we would develop with an offline first mentality. There are so many gotchas and so many pro tips that have come out of the lessons learned by these offline web evangelists. For better or worse the technical marvels of development in this engineering arena are hard to visualize demo much like the features of good security or performance. Offline is vital and integral to the web just as security and performance are vand it should not be an afterthought in our designs.   Resources Offline First - http://offlinefirst.org/ The Original Offline First Article: http://hood.ie/blog/say-hello-to-offline-first.html Hood.ie - http://hood.ie/ Offline First on IBM Cloudant - https://www.youtube.com/watch?v=PEHGSiC9_ck Beyond Offline - https://medium.com/@slsoftworks/beyond-offline-bf5c013ec8e7 Building Offline mobile apps - http://www.mobilitytechzone.com/topics/4g-wirelessevolution/articles/2015/07/06/406205-how-build-an-offline-ready-mobile-app-why.htm A List Apart article - http://alistapart.com/article/offline-first UpUp - https://www.talater.com/upup/ Application Cache - http://www.html5rocks.com/en/tutorials/appcache/beginner/ ServiceWorker Spec - https://github.com/slightlyoff/ServiceWorker ServiceWorker Explainer Document - https://github.com/slightlyoff/ServiceWorker/blob/master/explainer.md Is ServiceWorker Ready Yet? - https://jakearchibald.github.io/isserviceworkerready/ ServiceWorker W3C Spec - http://www.w3.org/TR/service-workers/ Service Worker Explained on MDN - https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API ServiceWorker News - https://twitter.com/service_workers Service Worker Platinum Polymer Elements - https://github.com/PolymerElements/platinum-sw Offline Cookbook - https://jakearchibald.com/2014/offline-cookbook/ Safari is the new IE - http://nolanlawson.com/2015/06/30/safari-is-the-new-ie/ Service Worker Toolbox - https://github.com/GoogleChrome/sw-toolbox ServiceWorkerWare - https://github.com/gaia-components/serviceworkerware Capability Reporting with ServiceWorker - https://www.igvita.com/2014/12/15/capability-reporting-with-service-worker/ HospitalRun - http://hospitalrun.io/ Angular Remote Conf Do you want to attend a conference with top level Angular speakers but can afford the cost and inconvenience in travelling? Angular Remote Conf is an online conference Sept. 24th through the 25th with live interactions, a dedicated forum, respected leaders in Angular, and best of all you never have to leave the comfort of your own home to attend.   The Web Platform Podcast listeners receive a 20% discount for https://angularremoteconf.com/. All you have to do is use "webplatform" as the coupon code at checkout to  get your 20% off. This works for group tickets, standard tickets, and early bird as well. Head over to angularremoteconf.com and sign up ASAP to get the maximum savings DevFestDC 2015 The Web Platform Podcast is a proud media sponsor of DevFest 2015. DevFest is a conference  with Great Sessions and Code Labs on Android, Wearables, Polymer, AngularJS, Google Cloud Platform, Meteor and many others.   Show hosts Danny Blue & Erik Isaksen will be speakers and the event will be held at AOL Headquarters in Dulles VA Friday Sept 11th 2015 & Saturday Sept 12th 2015. For event registration details check out devfestdc.org and click on the eventbrite link. www.eventbrite.com/e/devfestdc-2015-google-developer-group-dc-tickets-17538373748 now! Panelists Erik Isaksen (@eisaksen) - Front End Development Lead at Deloitte Digital & Google Developer Expert in Web Technologies Justin Ribeiro (@justinribeiro)  - Wearables & HTML5 Google Developer Expert & Partner at Stickman Ventures James Duvall (@JamesDuvall) - Director of Technology at Stickman Ventures

In this episode, Brenda Storer stands in for the vacationing Reda. Brenda and Kyle talk about Brenda's recent talk on SVG's. The in's and out's of her process of learning about them and talking about them. They also talk about giving talks. This episode of The Bike Shed is sponsored by: Code School: Entertaining online learning for existing and aspiring developers. Leave a review on our iTunes page to be entered to win a free month of Code School. Links and Show Notes Slides from the talk Brenda's codepen account with a bunch of simple examples of SVGs to play with SVGO Sara Soueidan's 2014 CSSConf talk Jacob Jenkov's SVG Book online Chris Coyier's technique for using symbols as icons in svgs Jake Archibald's article on animating a stroke Iconic Icon Responsive Icons ManhattanJS website with animated clouds Brenda on Twitter

Diesmal widmen Hans, Rodney und Schepp sich einzig und allein einem Thema, und zwar… Schaunotizen [00:00:22] Progressive Enhancement Angeregt durch eine Diskussion auf Twitter zwischen Jake Archibald und Jeremy Keith, und aufgrund des Artikels von Jeremy, sprachen wir darüber, inwieweit wir das Thema „Progressive Enhancement“ in unsere Projekte implementieren.. Rodney erwähnte dabei Aaron Gustafsons Konzept […]

Vamos para a segunda parte da entrevista? VAMOS! Conversamos bastante sobre gráficos, web workers e as tendências pra esse ano relacionadas ao desenvolvimento. Como no último episódio, com Addy Osmani, Jake Archibald and Paul Lewis

A GENTE É CHIQUE! Fala ingrêis e tudo mais. Nas férias, o Daniel Filho viajou mas não largou o podcast. Nesse episódio ele conversou com Addy Osmani, Jake Archibald and Paul Lewis sobre Web Components, Performance, Progressive Enhancement, Service Workers e mais um monte de coisas.

Anselm, Hans, Peter und Stefan versammelten sich in vorösterlicher Stimmung um in Eintracht mal wieder festzustellen, wie kaputt doch alles ist. Schaunotizen [00:00:12] That’s so fetch! Jake Archibald verteidigt die unter Beschuss geratene Fetch-API. Fetch soll als Ersatz für das alterwürdige XHR dienen, wird aber unter anderem kritisert, weil man laufende Requests (noch) nicht abbrechen […]

Panel Jake Archibald (twitter github blog) Jamison Dance (twitter github blog) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:14 - Jake Archibald Introduction Works on Developer Relations on the Google Chrome Team 01:57 - The Application Cache Eric Bidelman: A Beginner's Guide to Using the Application Cache - HTML5 Rocks Down Fall 07:12 - Working with Single Page Apps 08:40 - Detecting Connectivity Express.js Yehuda Katz: Extend the Web Forward 15:42 - Running Offline 19:55 - Generating Manifest Files Grunt Task for App Cache Manifests 26:34 - NavigationController 28:49 - Progressive Enhancement Jake Archibald: Progressive enhancement is still Important 059 JSJ jQuery Mobile with Todd Parker 058 JSJ Building Accessible Websites with Brian Hogan Feature Detection Modernizr SEO Picks Arduino (Jamison) Draft (Jamison) RoboRally (Chuck) Adobe Audition CS6 (Chuck) Blue Microphones Yeti USB Microphone - Silver Edition (Chuck) async-generators (Jake) Rick Byers: DevTools just got a cool new feature in Chrome canary (Jake) johnny-five (Jamison) Next Week Book Club: JavaScript Allongé with Reginald Braithwaite Transcript CHUCK:  Maybe we’ll just talk about your general smarty-pants-ness. [Hosting and bandwidth provided by the Blue Box Group. Check them out at Bluebox.net.]  [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]  [This podcast is sponsored by JetBrains, makers of WebStorm. Whether you’re working with Node.js or building the front end of your web application, WebStorm is the tool for you. It has great code quality and code exploration tools and works with HTML5, Node, TypeScript, CoffeeScript, Harmony, LESS, Sass, Jade, JSLint, JSHint, and the Google Closure Compiler. Check it out at JetBrains.com/WebStorm.] CHUCK:  Hey everybody and welcome to Episode 69 the JavaScript Jabber Show. This week on our panel we have Jamison Dance. JAMISON:  Hello friends. CHUCK:  I’m Charles Max Wood from DevChat.TV. And we have a special guest and that is Jake Archibald. JAKE:  Hello. CHUCK:  Jake, do you want to introduce yourself for the folks who haven’t heard of you before? JAKE:  Sure thing. I work on the Google Chrome team as part of DevRel. What I’m doing there is a combination of speaking at conferences about particular stuff. I got to do a lot in performance at the moment, but I also do a lot of standards work where I’ve done a lot with an alternative to application cache, which we’ll be talking about, but also looking at things like script loading and some of the resource priority stuff. CHUCK:  Cool. So it sounds like you’re smart on a number of levels then. JAKE:  Or dumb at all. [Chuckles] I can only see what I work on. I don’t know if I’m any good at it. [Chuckles] CHUCK:  So we brought you on to talk about the application cache. I’m not completely sure I know what is totally involved there. Is it just the cache like you clear the browser cache cache or is it something else? JAKE:  Well. the aim for the application cache was to let you make a site that works offline. So we’ve got the http cache and that works, in a manner of speaking. But if you have, say a website where you’ve cached your JavaScript, you’ve cached your CSS. You’ve cached your html page and some images. That’s great, but the user will visit another website and the browser will go and delete the CSS file from your site from the cache just to make room for the stuff from this other site. That means that if we were just going to use the http cache for making things work offline, people go to your site, your html’s there, your images are there, your JavaScript’s there, but your CSS is not and that’s going to break your site.

Panel Jake Archibald (twitter github blog) Jamison Dance (twitter github blog) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:14 - Jake Archibald Introduction Works on Developer Relations on the Google Chrome Team 01:57 - The Application Cache Eric Bidelman: A Beginner's Guide to Using the Application Cache - HTML5 Rocks Down Fall 07:12 - Working with Single Page Apps 08:40 - Detecting Connectivity Express.js Yehuda Katz: Extend the Web Forward 15:42 - Running Offline 19:55 - Generating Manifest Files Grunt Task for App Cache Manifests 26:34 - NavigationController 28:49 - Progressive Enhancement Jake Archibald: Progressive enhancement is still Important 059 JSJ jQuery Mobile with Todd Parker 058 JSJ Building Accessible Websites with Brian Hogan Feature Detection Modernizr SEO Picks Arduino (Jamison) Draft (Jamison) RoboRally (Chuck) Adobe Audition CS6 (Chuck) Blue Microphones Yeti USB Microphone - Silver Edition (Chuck) async-generators (Jake) Rick Byers: DevTools just got a cool new feature in Chrome canary (Jake) johnny-five (Jamison) Next Week Book Club: JavaScript Allongé with Reginald Braithwaite Transcript CHUCK:  Maybe we’ll just talk about your general smarty-pants-ness. [Hosting and bandwidth provided by the Blue Box Group. Check them out at Bluebox.net.]  [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]  [This podcast is sponsored by JetBrains, makers of WebStorm. Whether you’re working with Node.js or building the front end of your web application, WebStorm is the tool for you. It has great code quality and code exploration tools and works with HTML5, Node, TypeScript, CoffeeScript, Harmony, LESS, Sass, Jade, JSLint, JSHint, and the Google Closure Compiler. Check it out at JetBrains.com/WebStorm.] CHUCK:  Hey everybody and welcome to Episode 69 the JavaScript Jabber Show. This week on our panel we have Jamison Dance. JAMISON:  Hello friends. CHUCK:  I’m Charles Max Wood from DevChat.TV. And we have a special guest and that is Jake Archibald. JAKE:  Hello. CHUCK:  Jake, do you want to introduce yourself for the folks who haven’t heard of you before? JAKE:  Sure thing. I work on the Google Chrome team as part of DevRel. What I’m doing there is a combination of speaking at conferences about particular stuff. I got to do a lot in performance at the moment, but I also do a lot of standards work where I’ve done a lot with an alternative to application cache, which we’ll be talking about, but also looking at things like script loading and some of the resource priority stuff. CHUCK:  Cool. So it sounds like you’re smart on a number of levels then. JAKE:  Or dumb at all. [Chuckles] I can only see what I work on. I don’t know if I’m any good at it. [Chuckles] CHUCK:  So we brought you on to talk about the application cache. I’m not completely sure I know what is totally involved there. Is it just the cache like you clear the browser cache cache or is it something else? JAKE:  Well. the aim for the application cache was to let you make a site that works offline. So we’ve got the http cache and that works, in a manner of speaking. But if you have, say a website where you’ve cached your JavaScript, you’ve cached your CSS. You’ve cached your html page and some images. That’s great, but the user will visit another website and the browser will go and delete the CSS file from your site from the cache just to make room for the stuff from this other site. That means that if we were just going to use the http cache for making things work offline, people go to your site, your html’s there, your images are there, your JavaScript’s there, but your CSS is not and that’s going to break your site.

Panel Jake Archibald (twitter github blog) Jamison Dance (twitter github blog) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:14 - Jake Archibald Introduction Works on Developer Relations on the Google Chrome Team 01:57 - The Application Cache Eric Bidelman: A Beginner's Guide to Using the Application Cache - HTML5 Rocks Down Fall 07:12 - Working with Single Page Apps 08:40 - Detecting Connectivity Express.js Yehuda Katz: Extend the Web Forward 15:42 - Running Offline 19:55 - Generating Manifest Files Grunt Task for App Cache Manifests 26:34 - NavigationController 28:49 - Progressive Enhancement Jake Archibald: Progressive enhancement is still Important 059 JSJ jQuery Mobile with Todd Parker 058 JSJ Building Accessible Websites with Brian Hogan Feature Detection Modernizr SEO Picks Arduino (Jamison) Draft (Jamison) RoboRally (Chuck) Adobe Audition CS6 (Chuck) Blue Microphones Yeti USB Microphone - Silver Edition (Chuck) async-generators (Jake) Rick Byers: DevTools just got a cool new feature in Chrome canary (Jake) johnny-five (Jamison) Next Week Book Club: JavaScript Allongé with Reginald Braithwaite Transcript CHUCK:  Maybe we’ll just talk about your general smarty-pants-ness. [Hosting and bandwidth provided by the Blue Box Group. Check them out at Bluebox.net.]  [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]  [This podcast is sponsored by JetBrains, makers of WebStorm. Whether you’re working with Node.js or building the front end of your web application, WebStorm is the tool for you. It has great code quality and code exploration tools and works with HTML5, Node, TypeScript, CoffeeScript, Harmony, LESS, Sass, Jade, JSLint, JSHint, and the Google Closure Compiler. Check it out at JetBrains.com/WebStorm.] CHUCK:  Hey everybody and welcome to Episode 69 the JavaScript Jabber Show. This week on our panel we have Jamison Dance. JAMISON:  Hello friends. CHUCK:  I’m Charles Max Wood from DevChat.TV. And we have a special guest and that is Jake Archibald. JAKE:  Hello. CHUCK:  Jake, do you want to introduce yourself for the folks who haven’t heard of you before? JAKE:  Sure thing. I work on the Google Chrome team as part of DevRel. What I’m doing there is a combination of speaking at conferences about particular stuff. I got to do a lot in performance at the moment, but I also do a lot of standards work where I’ve done a lot with an alternative to application cache, which we’ll be talking about, but also looking at things like script loading and some of the resource priority stuff. CHUCK:  Cool. So it sounds like you’re smart on a number of levels then. JAKE:  Or dumb at all. [Chuckles] I can only see what I work on. I don’t know if I’m any good at it. [Chuckles] CHUCK:  So we brought you on to talk about the application cache. I’m not completely sure I know what is totally involved there. Is it just the cache like you clear the browser cache cache or is it something else? JAKE:  Well. the aim for the application cache was to let you make a site that works offline. So we’ve got the http cache and that works, in a manner of speaking. But if you have, say a website where you’ve cached your JavaScript, you’ve cached your CSS. You’ve cached your html page and some images. That’s great, but the user will visit another website and the browser will go and delete the CSS file from your site from the cache just to make room for the stuff from this other site. That means that if we were just going to use the http cache for making things work offline, people go to your site, your html’s there, your images are there, your JavaScript’s there, but your CSS is not and that’s going to break your site.

Jeffrey Zeldman interviews Jake Archibald of Google Chrome about upcoming web caching standards, how the network connection is merely a layer of progressive enhancement and why you should build your app offline, communicating with non-developers, accessibility standards at BBC and The Guardian, the forking of Webkit, native versus web part 99, and why the much-linked article "Why Mobile Web Apps are Slow" proves no such thing.

Jeffrey Zeldman interviews Jake Archibald of Google Chrome about upcoming web caching standards, how the network connection is merely a layer of progressive enhancement and why you should build your app offline, communicating with non-developers, accessibility standards at BBC and The Guardian, the forking of Webkit, native versus web part 99, and why the much-linked article "Why Mobile Web Apps are Slow" proves no such thing. Links for this episode:http://jakearchibald.comhttps://twitter.com/jaffathecakehttps://github.com/jakearchibaldhttps://plus.google.com/116237864387312784020/postshttp://aneventapart.com/speakers/jake-archibaldhttp://sealedabstract.com/rants/why-mobile-web-apps-are-slowhttp://webplatformdaily.orghttp://cloud.feedly.com/#welcomehttp://dailynerd.nlhttps://github.com/gnarf/jquery-requestAnimationFramehttps://github.com/slightlyoff/navigationcontrollerhttp://alistapart.com/article/application-cache-is-a-douchebagThis episode is sponsored by Lynda.com.

Ex tempore -jakso, jossa haetaan omaa näkökulmaa erilaisiin aiheisiin. Tapaamista ei edellisen jakson jälkeen järjestetty, joten luvassa on luovaa kaaosta aiheiden osalta. Uutisia Selainmaailman muutokset Opera vaihtaa WebKitiin Jonka jälkeen Google forkkaa WebKitin (nimeltä Blink) Blink rendering engine for chromium Chromium.org/blink VentureBeat: Google forks Webkit to give the Chrome browser its own rendering engine Engadget: Google’s Blink engine (gently) hints at a more streamlined future for Chrome Ja Opera seuraa perässä Paul Irish: WebKit for Developers Webshaped-tapahtuma Helsingissä lähestyy Webshaped.fi Puhujat Jake Archibald, Google Chrome Jonathan Smiley, ZURB Vitaly Friedman, Smashing Magazine Darrell Stephenson, Soundcloud Holger Bartel , uforepublic Yves Peters, FontFeed Andrew Nesbitt, Forward Pari videota Brad Frost : Death to Bullshit Brad Frost käskee keskittymään sisältöön. Unohtakaa hälinä (mainokset, QR-koodit ym) ja keskittykää sisältöön. Mike Monteiro : Fuck you. Pay me Asiallinen ja kärkevä “puhe” Mike Monteirolta mm. asianajajien tärkeydestä, sopimusasiakirjoista ja muista vaikeista asioista. Erityisen hyvä webbiyrittäjille. Breaking the 1000ms Time to Glass Mobile Barrier Todella mielenkiintoinen pureutuminen siihe, miten webbisivu saadaan nopeaksi. Ei vain mobiilissa vaan ihan yleensä. Läpi käydään mm. se kuinka paljon aikaa menee pelkkään verkkoneuvotteluun puhelimen ja maston välillä. Creative JavaScript in advertising Muita aiheita Media Queries are a Hack by Ian Storm Taylor Ovatko media queryt liian laajoja RWD sivujen tekoon? Tarvitaanko element queryjä? Responsive Nav Viljami Salmisen js-kirjastoriippumaton responsiivinen valikkoplugari Advanced cross-browser flexbox Edellisen podcastin flexbox käytännössä. Saavutettuja etuja (myös demossa) mm. media query -vapaa layout. Haasteena on kolme erilaista syntaksia (ns. vanha, hybridi ja speksin mukainen) Can I Use Frontend Friday Meillä on webbisivut osoitteessa ouluweb.github.io Seuraava miitti on sovittu tiistaille 30.4. Paikkana Business Kitchen, Torikatu 23 (4. krs.), 90100 Oulu Podcastia voi kommentoida Branchissa Sähköpostitse voi lähestyä ouluweb@gmail.com Miitti-ideoita otetaan vastaan Podcast-aiheita ja ideoita otetaan vastaan

We finally have the ability to serve custom fonts to all popular browsers. However, like everything in our profession, there’s a minefield of gotchas and peculiarities between browsers, devices and operating systems. More info at: https://fronteers.nl/congres/2011/sessions/in-your-font-face-jake-archibald

We finally have the ability to serve custom fonts to all popular browsers. However, like everything in our profession, there’s a minefield of gotchas and peculiarities between browsers, devices and operating systems. More info at: https://fronteers.nl/congres/2011/sessions/in-your-font-face-jake-archibald

What sets reusable JavaScript apart from other JavaScript? How can we make our code developer-friendly, fast, robust & compatible? More info at: https://fronteers.nl/congres/2010/sessions/reusable-code-for-good-or-for-awesome-jake-archibald

What sets reusable JavaScript apart from other JavaScript? How can we make our code developer-friendly, fast, robust & compatible? More info at: https://fronteers.nl/congres/2010/sessions/reusable-code-for-good-or-for-awesome-jake-archibald