220 JSJ Teaching JavaScript with Kyle Simpson

Possibly related…

  1. Gatsby with Kyle Mathews and Sam Bhagwat - Software Engineering Daily

    Frontend software development has become as complex as backend development. There was a time when frontend web development was simple. There was a small number of JavaScript frameworks and templating systems. Your CSS was simple configuration for the colors on your webpage. Today, there is a giant ecosystem of frontend tools, APIs, and middleware delivering


    —Huffduffed by leivajd

  2. MJS 101: Chris Ferdinandi

    In this episode of My JavaScript Story, Charles Max Wood hosts Chris Ferdinandi, a Senior Front-End Engineer at Mashery. Chris is also a panelist on the podcast JavaScript Jabber and runs Go Make Things. Chris started out his career as in Human Resources, decided he wanted to go into development after he was asked to work on a coding project by his manager and he really enjoyed it. He got his first coding job as an entry level developer after attending a web development conference. Chris authors Vanilla JavaScript Pocket Guides which are short, focused e-books and video courses made for beginners.


    —Huffduffed by adactio

  3. Keep Betting on JavaScript by Kyle Simpson · JSCamp Barcelona 2018

    💻Slides: https://speakerdeck.com/getify/keep-betting-on-js

    🔗More information: https://jscamp.tech/speakers/kyle-simpson/

    Ⓒ Licence: CC BY-ND https://creativecommons.org/licenses/by-nd/4.0/legalcode #JSCampBCN #JavaScript

    Original video: https://www.youtube.com/watch?v=lDLQA6lQSFg
    Downloaded by http://huffduff-video.snarfed.org/ on Mon, 03 Sep 2018 00:50:34 GMT Available for 30 days after download

    —Huffduffed by jrsinclair

  4. JSJ 375: Are You Hurting the Web?

    Today the panel discusses the effect of current development practices, such as the heavy reliance JavaScript, on the web. Chris explains why he believes that current development practices are ruining the web. The panelists discuss different situations where they see complications on the web. They discuss the advantages and disadvantages of using an enterprise scale platform like React. The panel discusses Twitter’s move away from their legacy code base to CSS and JavaScript.

    The panelists agree that the way things are built, since it’s so JavaScript heavy, is alienating to people who work with other languages, and in turn other areas like UI are undervalued. They talk about possible reasons things ended up this way and some of the historical perception of a frontend as not a place for ‘real’ development. Because the web is now a serious platform, things associated with the backend has been thrown at the frontend where it doesn’t belong. They talk about changes in the ways programming is viewed now versus the past.

    There is a discussion about how market demands that have influenced the web and if the market value CSS as highly as other languages. They mention some of the Innovations in CSS. Chris shares his solutions for the problems they’ve been discussing, namely using less JavaScript, leaning more heavily on what the browser gives you out of the box, and avoiding dependency where possible. They talk about ways to get involved if you want to take a leaner approach to the web. Ultimately, it is important to embrace things about the past that worked, but sprinkle in new technology when it makes sense.


    —Huffduffed by adactio

  5. CodeNewbie: What is vanilla JS and how can it help you with Chris Ferdinandi

    In this episode, we talk about about vanilla JavaScript with Chris Ferdinandi, author of the Vanilla JS Pocket Guide series, and creator of the Vanilla JS Academy training program. Chris talks about how he went from HR professional to JavaScript expert, the pros of getting rid of all that tooling and learning good old fashion vanilla JS, and why this is relevant, not only from a personal perspective, but from a public safety perspective as well.


    —Huffduffed by adactio

  6. 85. The New Definition of Frontend Development - Podcasts | Heroku

    Charlie Gleason is a designer and frontend developer at Heroku and Salesforce. He’s invited Ben Vinegar, an experienced frontend developer and now manager at Sentry, to share his opinions on what frontend development means today. Way back in 2010, Ben understood that JavaScript, which wasn’t taken all that seriously, had the potential to take a more significant part of the web development experience. At the time, Firebug had just been introduced, exposing developers to a debugging experience in the browser. From there, more JavaScript tools and frameworks began to proliferate. Just as Rails popularized the idea of an MVC, so too did Backbone, as well as introduce the concept of single page apps, leading to Angular, Ember, and eventually, React. For many people involved in (and observing) the JavaScript community, the pace of change induced a certain amount of uncertainty as to which framework developers should be learning. Ben empathizes with this frustration, but cautions that software development really hasn’t changed in the last twenty years. Every time a brand new language or tool comes out that promises to revolutionize the industry, it’s better to wait it out a year before even considering putting it into production. Better still, take a step back and ask how this new tool will make your app better for your users. When you approach software development as a way to solve people’s problems, you become more pragmatic in your choices, and can work to solve real problems, rather than overoptimize or get distracted. Ben concludes by observing how designers have become much more technical over the last few years, with tools like Abstract introducing the concept of branches to design files, or the relationship between Figma and Sketch to actual code. Teams are no longer making mock-ups and handing them over to "real programmers" but actually building the components themselves, in reusable and shareable ways. Ultimately, he sees programming drifting more towards the full stack approach: in order to be able to build a good product, you need to understand how to implement features on a server, design it in a user friendly way, and apply JavaScript effectively to communicate with the backend and the browser.


    —Huffduffed by nsmsn

  7. 10 Business Tips When Launching Your First App | The Laracasts Snippet

    So you’re a developer planning to launch your first SaaS or subscription site? The business side of things get really complicated… really fast, right? In this episode, I rattle off ten tips and notes to be aware of, as you prepare for launch.


    —Huffduffed by pauld