HTML All The Things - Web Development, AI, and Developer Careers

HTML All The Things - Web Development, AI, and Developer Careers

By Matt Lawrence and Mike KaranNewsTechnologyEducationHow ToTech News
Download on the App Store

HTML All The Things - Web Development, AI, and Developer Careers episodes

  • Cross-Platform Web Development

    Matt's freshly back from vacation to discuss developing for multiple platforms using various tools such as Apache Cordova, React Native, and Ionic. Allowing developers to use what they're familiar with, and still make apps for a variety of platforms.

     

    Segment 1 - When to Use/Not Use Cross-Platform Development

    • Cross Platform Web Development allows you to build apps in Javascript that you can then use as native apps on iOS, Android and even Windows
  • This allows developers that are already familiar with JavaScript to great native experiences without having to learn new languages
  • In some cases, like with Apache Cordova a team can use one single code base with some hooks for different platforms to build their application for the web, android and ios
  • This allows for more agile development and smaller development teams as you don’t have resources tied up in native app development
  • This issues arise when needing to perform complex multimedia tasks like constantly playing audio and video
  • As we’ve experienced heavy media tasks can cause crashes in webviews where native code might perform just fine
  • Just beware when decided to go with cross platform development because you can never simulate the performance of a native application, so if buttery smooth animations and lightening quick load actions are important to you, the native way is prefered
  • For a small business though, like a bakery or restaurant, if they want an application that resembles their website then using a cross platform framework is ideal because it can save them money and give them the functionality they desire

    • Segment 2 - Cross-Platform Technologies

    • Apache Cordova
    • https://cordova.apache.org/
  • Its free and open source
  • A plugin that allows you to create native applications out of standard website code (HTML, JS, CSS)
  • Provides developers the opportunity to create only one main code base for all platform
  • Also the main advantages of cross platform technologies are they give you the ability to create a offline mode and access native api’s such as push notifications, file systems, etc
  • It is necessary to create hooks that change how the application loads depending on if it’s on the web or if it's packaged as a native application
  • React Native and Nativescript with Vue.js
    • https://facebook.github.io/react-native/
  • https://www.nativescript.org/vue
  • Both of these frameworks allow for development on both Android and iOS
  • They use a very similar structure to their corresponding technologies with some minor differences when it comes to views, as xml is used to construct layouts
  • Both use JS as their scripting language
  • These frameworks allow developers that a familiar with React or Vue to build Native applications that perform very close to their Obj C or Java counterparts
  • Ionic
    • https://ionicframework.com/
  • Allows you to make web apps into desktop applications for both MacOS and Windows

    • Segment 3 - Progressive Web Apps

    • These are websites or web applications that with minor adjustments give the user native functionality straight for the browser
  • This doesn’t require you to have to build the application and package it for a specific platform (i.e Android, iOS), the newest browsers, safari and chrome both can auto detect if you have a progressive web app in the browser and the prompt the user of the functionality
  • To create a PWA there are only a few steps required:
    • Site has to be HTTPS secured
  • Page need to be responsive for mobile devices
  • Page needs to use Service Workers to load URLS offline
    • A service work is a background script that can be created and tied to your webpage but which does not have access to your DOM elements
  • Through the service worker you can access the native API’s of you desired system like push notifications
  • They can also be used to process parallel tasks as service workers run on their own threads (cores)
  • A Web App Manifest file which allows you to put information and image data for adding your application right to the users home screen on their device (like a real application)
  • The site must be able to load ‘fast’ on a 3G connection
  • https://www.pwabuilder.com/
    • Really interesting utility that allows you put in your websites URL and gives you a list of steps plus helps you create the necessary changes to make it a PWA
  • PWA’s I’ve used
    • Twitter has a really good PWA, allowing you to not have to worry about installing another application
  • Telegram message application has a good PWA that work on both PC and Mobile

    • Web News - Strict Learning

    • Disclaimer: We are not education experts in any way, we discussed this and wrote the notes below based on our personal experiences.
  • Schools seem to want you to do it right the first time, or risk losing marks, time, or electronic components in the case of our college labs
  • Meanwhile actual learning is supposed to be filled with mistakes and experimenting so that you can figure out what works and what doesn’t
  • Example: In college, we would receive a new set of components for our labs that would be conducted throughout the semester, however, we would receive a limited set of components - sometimes with spares, sometimes we’d only have one of each
    • You could purchase more if they were in stock, but that’s expensive for a student
  • These components are generally cheap electronic components - yet we were expected not to break them, or have a bunch of DOA components
  • This discouraged messing around with circuits and caused a lot of checking over and over to ensure your circuit was correct before hooking it up to power
  • When we learn new web technologies we typically end up setting it up incorrectly a few times, and have plethora of errors throughout the process as we figure out how things should be working.
    • This type of learning I find personally the best for understanding what you’re doing and what you can/can’t do with a piece of technology, however, this could get you docked valuable marks in school
  • The counter argument is that you should make all your mistakes before the test, however, in college especially, those “in-between” marks can add up to 10% or more of your overall grade depending on the class.

    • You can find us on...

    Facebook | Twitter | Instagram

    RSS | Patreon | Spotify

    Medium | YouTube | GitHub 

    Reddit

    1 hr 24 min
  • Cross-Platform Web Development
    Matt's freshly back from vacation to discuss developing for multiple platforms using various tools such as Apache Cordova, React Native, and Ionic. Allowing developers to use what they're familiar with, and still make apps for a variety of platforms.
    1 hr 24 min
  • Front-End Developer Roadmap

    In this episode we dive into the the Front-End Developer Roadmap by Kamran Ahmed, going through all the technologies you need to learn from the basics, through the mastery phase of your career.

    Segment 1 - Roadmap Discussion

    • We discuss the 18-20 main points of the developer roadmap
  • Source: https://github.com/kamranahmedse/developer-roadmap

    • Segment 2 - Update on HTML All The Things

    • Authentication for admins was added to edit the site
  • Pagination with infinite scroll was added
  • Major code refactoring
    • Created components out of reusable code
  • Got rid of redundant variable setting
  • Deployed database and server authentication on our Digital Ocean docker setup
  • Messed around with nginx configuration files

    • Web News - Microsoft Office vs Google Docs

    • Microsoft Office has a premium paid-for desktop experience in the form of the Office Suite (main programs: Word, Excel, PowerPoint) they also have a free Office Online counterpart that work at a basic level for editing, and allow people to view documents online
    • This plugs into OneDrive (desktop app, web app, and mobile app)
  • Both versions talk and work with each other
  • Google Docs has a similar offering, however, it is free.
    • Google Docs, Sheets, and Slides are the main programs within this suite.
  • Integrate well with Google Drive and have collaboration features
  • They have desktop “apps” if you’re using Chrome, as well as Chromebook apps and smartphone apps.

    • You can find us on...

    Facebook | Twitter | Instagram  

    RSS | Spotify | Reddit

    Medium | YouTube | GitHub

    Patreon

    1 hr 41 min
  • Front-End Developer Roadmap
    In this episode we dive into the the Front-End Developer Roadmap by Kamran Ahmed, going through all the technologies you need to learn from the basics, through the mastery phase of your career.
    Segment 1 - Roadmap Discussion
    We discuss the 18-20 main points of the developer roadmap
    Source: https://github.com/kamranahmedse/developer-roadmap
    Segment 2 - Update on HTML All The Things
    Authentication for admins was added to edit the site
    Pagination with infinite scroll was added
    Major code refactoring
    Created components out of reusable code
    Got rid of redundant variable setting
    Deployed database and server authentication on our Digital Ocean docker setup
    Messed around with nginx configuration files
    Web News - Microsoft Office vs Google Docs
    Microsoft Office has a premium paid-for desktop experience in the form of the Office Suite (main programs: Word, Excel, PowerPoint) they also have a free Office Online counterpart that work at a basic level for editing, and allow people to view documents online
    This plugs into OneDrive (desktop app, web app, and mobile app)
    Both versions talk and work with each other
    Google Docs has a similar offering, however, it is free.
    Google Docs, Sheets, and Slides are the main programs within this suite.
    Integrate well with Google Drive and have collaboration features
    They have desktop “apps” if you’re using Chrome, as well as Chromebook apps and smartphone apps.
    You can find us on...
    Facebook | Twitter | Instagram  
    RSS | Spotify | Reddit
    Medium | YouTube | GitHub
    Patreon
    1 hr 41 min
  • Developing with Vue.js, Node.js, and MongoDB

    We've been hard at work, learning a new development stack on which the HTML All The Things website is built.

    Note: Matt is on vacation for 1.5 weeks, this episode has been pre-recorded before his departure, some things that were discussed may have a different status (hopefully complete) upon the release of the episode.

    Segment 1 - VueJS Frontend Development

    • Due to the nature of VueJS, we spun up an entirely new development environment
  • Switching from Notepad++ to Visual Studio Code w/ the Vetur plugin
  • Some of the most valuable/used parts of VueJS that we used include:
    • Components - are like small pieces that makeup the website, placed in separate files and used over and over again, can be imported into each other (component inside a component)
  • Scoped Stylesheets - limit the styles you're applying to the file you're writing them in, we limited many styles to specific components, allows you to use the same classnames and ids with completely different properties
  • Dynamic data was the most challenging part of using VueJS, not from a technical perspective, but more so from a procedural standpoint - not used to having them as apart of my workflow
  • Vuex, Vue Router, Axios
    • Vuex is a state management solution in vue that allows all components to share data between each other
  • We use it for storing our loggedIn status for our editing content
  • Vue router is used for handling any routes so that we can navigate around our site

    • Segment 2 - Nodejs and MongoDB Backend Development

    • Nodejs
    • Used as our server to serve webpage content from the Mongo Database and store content in the mongo database
  • The server has be handle many calls to it that request things like:
    • Get all content
  • Get content of a specific type
  • Add content of a specific type
  • Delete content
  • Authentication
  • These are standard server requests but still took some time to setup as we’ve never hooked in vue.js into Node, usually use the built in templating engines
  • MongoDB
    • A alternative to sql that stores objects in json blocks
  • Has great hookins into Nodejs using the Mongoose package
  • Used to store our content block data and  admin user account for editing the site
  • Had to implement mongo admin and database users so that even if our site is hacked they can’t delete or modify the entire mongo database

    • Segment 3 - Digital Ocean and Docker Deployment

    • Digital Ocean provides a vps with an already installed Docker instance.
  • Docker is a way to create small virualizable containers for each technology in your stack
  • In our case we used docker to create 3 containers:
    • Nginx - serve static files and proxy routes to Nodejs server
  • Nodejs - run our server infrastructure
  • MongoDB - runs our mondodb server that communicates with Nodejs
  • Had to learn how to create a docker compose file which is a configuration file for building your containers together and letting them know how to communicate
  • Everything is launched and built through a SSH into your digital ocean server. You have to be familiar with using a Command Line Interface (CLI)

    • Web News - Wrapping it Up

    In this Web News we had a discussion regarding our current status (at the time of recording) in the development of the HTML All The Things website, as well as what to complete for deployment.

    1 hr 11 min
  • Developing with Vue.js, Node.js, and MongoDB
    We've been hard at work, learning a new development stack on which the HTML All The Things website is built.
    Note: Matt is on vacation for 1.5 weeks, this episode has been pre-recorded before his departure, some things that were discussed may have a different status (hopefully complete) upon the release of the episode.
    Segment 1 - VueJS Frontend Development
    Due to the nature of VueJS, we spun up an entirely new development environment
    Switching from Notepad++ to Visual Studio Code w/ the Vetur plugin
    Some of the most valuable/used parts of VueJS that we used include:
    Components - are like small pieces that makeup the website, placed in separate files and used over and over again, can be imported into each other (component inside a component)
    Scoped Stylesheets - limit the styles you're applying to the file you're writing them in, we limited many styles to specific components, allows you to use the same classnames and ids with completely different properties
    Dynamic data was the most challenging part of using VueJS, not from a technical perspective, but more so from a procedural standpoint - not used to having them as apart of my workflow
    Vuex, Vue Router, Axios
    Vuex is a state management solution in vue that allows all components to share data between each other
    We use it for storing our loggedIn status for our editing content
    Vue router is used for handling any routes so that we can navigate around our site
    Segment 2 - Nodejs and MongoDB Backend Development
    Nodejs
    Used as our server to serve webpage content from the Mongo Database and store content in the mongo database
    The server has be handle many calls to it that request things like:
    Get all content
    Get content of a specific type
    Add content of a specific type
    Delete content
    Authentication
    These are standard server requests but still took some time to setup as we’ve never hooked in vue.js into Node, usually use the built in templating engines
    MongoDB
    A alternative to sql that stores objects in json blocks
    Has great hookins into Nodejs using the Mongoose package
    Used to store our content block data and  admin user account for editing the site
    Had to implement mongo admin and database users so that even if our site is hacked they can’t delete or modify the entire mongo database
    Segment 3 - Digital Ocean and Docker Deployment
    Digital Ocean provides a vps with an already installed Docker instance.
    Docker is a way to create small virualizable containers for each technology in your stack
    In our case we used docker to create 3 containers:
    Nginx - serve static files and proxy routes to Nodejs server
    Nodejs - run our server infrastructure
    MongoDB - runs our mondodb server that communicates with Nodejs
    Had to learn how to create a docker compose file which is a configuration file for building your containers together and letting them know how to communicate
    Everything is launched and built through a SSH into your digital ocean server. You have to be familiar with using a Command Line Interface (CLI)
    Web News - Wrapping it Up
    In this Web News we had a discussion regarding our current status (at the time of recording) in the development of the HTML All The Things website, as well as what to complete for deployment.
    1 hr 11 min
  • Gathering Project Scope & Requirements

    Getting details from your customers can be a challenging experience, but it is vital so that you can deliver a complete produce on time.

    Segment 1 - The Contact

    • There are a lot of way that customers can contact you
  • Some clients want to be hands-on, some want to hand over everything to you - the professional, and others get right to the point
  • Despite how many details these customers give you, every project has a unique spin on it, even if it seems run of the mill, this makes it vital that your communication is on point
  • Sometimes you need to resist customers requests/demands in order to deliver a complete and quality product (ie refusing to move forward on a project that hasn't had enough details communicated to begin accurately)

    • Segment 2 - Gather Project Requirements

    • Before sending the first quote we need to know what the client needs us to do
  • Ensure that you ask the right questions to get all the information you need, clients generally don't know how many details you need

    • When we work on a small business site some of the sample questions we might ask include:

    1. How do your current clients find you?
  • If you have a site currently, what are some things you like about it, what are the things you really don't like
  • What is the intention with the new site, generate leads? Just a digital business card/a way to for people to find your phone number?
  • Who are your biggest competitors? And which of their sites do you like the most?
  • Do you have a database of products you want displayed on the site?
  • Do you want to be able to edit the main components of the site yourself?
  • How important is the google rank to you?
  • Do you see your website expanding in some way? Becoming a web app? Or growing a lot? Having a team of editors?
    • Generally you should gather details over a personal meeting or screen share
  • After gathering the details you can start creating the basis of the project including details on time to completion and what will be required
  • This is a major component in your quote for a client

    • Segment 3 - Changing Project Requirements

    • Changes can suddenly happen, even in the middle of a project
  • They can be brought on by customer preferences, market conditions, or company-wide strategy changes of some sort
  • When a project requirement changes, especially when it drastically changes from the original vision, it often falls to you as the creator to make the appropriate changes
  • It’s important to have a layout of what you’re willing to do with a client before you begin any work and to have a similar layout for what you're willing to do about changes that arise

    • Web News - What do yo want from a phone/Android launcher?

     

    • We all have different needs and wants from our mobile devices, they’re an extension of us and the main way the people communicate with one another these days
  • With that being said, they’re still mobile computers and can be used for a wide variety of tasks from working on the go, taking photos, chatting with friends, and much more.
  • With different use cases comes a variety of user preferences in terms of hardware and software
  • Are you a fan of Android fragmentation, or is there too much variation?

    •  

    Apply to become our SubReddit Manager/Mod - [email protected]

    You can find us on...

    Facebook | Twitter | Instagram

    RSS | Patreon | Spotify

    Medium | YouTube | GitHub 

    Reddit

    1 hr 23 min
  • Gathering Project Scope & Requirements
    Getting details from your customers can be a challenging experience, but it is vital so that you can deliver a complete produce on time.
    Segment 1 - The Contact
    There are a lot of way that customers can contact you
    Some clients want to be hands-on, some want to hand over everything to you - the professional, and others get right to the point
    Despite how many details these customers give you, every project has a unique spin on it, even if it seems run of the mill, this makes it vital that your communication is on point
    Sometimes you need to resist customers requests/demands in order to deliver a complete and quality product (ie refusing to move forward on a project that hasn't had enough details communicated to begin accurately)
    Segment 2 - Gather Project Requirements
    Before sending the first quote we need to know what the client needs us to do
    Ensure that you ask the right questions to get all the information you need, clients generally don't know how many details you need
    When we work on a small business site some of the sample questions we might ask include:
    How do your current clients find you?
    If you have a site currently, what are some things you like about it, what are the things you really don't like
    What is the intention with the new site, generate leads? Just a digital business card/a way to for people to find your phone number?
    Who are your biggest competitors? And which of their sites do you like the most?
    Do you have a database of products you want displayed on the site?
    Do you want to be able to edit the main components of the site yourself?
    How important is the google rank to you?
    Do you see your website expanding in some way? Becoming a web app? Or growing a lot? Having a team of editors?
    Generally you should gather details over a personal meeting or screen share
    After gathering the details you can start creating the basis of the project including details on time to completion and what will be required
    This is a major component in your quote for a client
    Segment 3 - Changing Project Requirements
    Changes can suddenly happen, even in the middle of a project
    They can be brought on by customer preferences, market conditions, or company-wide strategy changes of some sort
    When a project requirement changes, especially when it drastically changes from the original vision, it often falls to you as the creator to make the appropriate changes
    It’s important to have a layout of what you’re willing to do with a client before you begin any work and to have a similar layout for what you're willing to do about changes that arise
    Web News - What do yo want from a phone/Android launcher?
     
    We all have different needs and wants from our mobile devices, they’re an extension of us and the main way the people communicate with one another these days
    With that being said, they’re still mobile computers and can be used for a wide variety of tasks from working on the go, taking photos, chatting with friends, and much more.
    With different use cases comes a variety of user preferences in terms of hardware and software
    Are you a fan of Android fragmentation, or is there too much variation?
     
    Apply to become our SubReddit Manager/Mod - [email protected]
    You can find us on...
    Facebook | Twitter | Instagram
    RSS | Patreon | Spotify
    Medium | YouTube | GitHub 
    Reddit
    1 hr 23 min
  • Responsive Design

    Responsive design has revolutionized how websites are developed, but static layouts still have their place. We explore these two different layout methods in this episode of the podcast.

    Reference from Treehouse: https://blog.teamtreehouse.com/which-page-layout

    Segment 1 - What is Responsive Design?

    • Responsive design responds to its environment, in the case of web design it’s specifically referring to how a website’s user interface responds to different window sizes and technologies available.
  • This gives us the ability to have a single design that changes and adapts to various devices from ultrawide PC displays, down to older smartphones.
  • It also allows users to make the most  of the screen real estate they have
  • Responsive design makes the use of a variety of tactics that are generally found in CSS including: media queries, relative positioning, relative length units, whitespace
    • Having two browsers snapped to each side of a 1080p display for more information, rather than always having a webpage open at full resolution
  • Responsive design makes the use of a variety of tactics that are generally found in CSS including: media queries, relative positioning, relative length units, whitespace

    • Segment 2 - How to Implement Responsive Design

    • CSS Responsive Tactics:
    • Media Queries
    • Offer breakpoints to a design, allowing developers to apply design changes at a specific breakpoint, such as a certain max-width (probably most popular breakpoint)
  • Relative Positioning
    • Position: relative;
  • Positioning absolute elements within a relative container and then controlling that relative container to automatically move the elements within the container
  • Relative Length Units
    • Units that allow your elements to be responsive. These units are dynamic and change based on their environment
  • Unlike exact, or absolute length units which are (cm, mm, px, etc.)
  • 3 examples:
    • rem - relative to the font-size of the root element
  • % - relative to the parent element
  • Vw - relative to 1% of the width of the viewport
  • Reference link: https://www.w3schools.com/cssref/css_units.asp
  • Whitespace
    • The space between elements (ie the space between columns)
  • It’s basically blank space on the web page
  • Responsive design uses this as a buffer zone to move elements around various elements
  • Filling a site up too much (minimal whitespace) requires space for elements to be displaced and the site will become too crowded on smaller screens (infinite scrolling, or a lot of pagination)
  • Main high-level CSS responsive tactics include: Flexbox, CSS Grid
  • Mobile or Large screen first design?
    • It seems currently it’s more popular to design for mobile first and then create media queries for larger displays
    • This is useful if you are also designing for older browsers and want to use newer technologies like Grid of even Flexbox
  • Older browsers will see a mobile design (one column) while any larger screen or new browser can utilize the newer technology for a more advanced/easier to set up layout
  • Traditionally we design for larger screen and adapted for mobile/smaller
    • This is still viable depending again on your audience, an older audience for example still prefers larger screens

    Segment 3 - When to use Static instead of Responsive Design

    • Static layouts/static design is when the page is laid out in a fixed way
  • The elements on the page do not adjust to the screen resolution, or window changing size, generally, overflow is used in order to scroll all around the page
  • Older sites, especially those that appear left aligned and not fullscreen are done in a static layout, as they’re typically 640px or 800px wide and remain left aligned, if the screen shrinks below this point, as with a phone screen, the user must scroll around the design
  • Elements are generally not optimized for all platforms, which results in very small buttons, and text on high definition and mobile phone screens
  • Modern Static Design or Static Layouts
    • We’ve experiences situations in which a single device, or a single type of monitor will be used, adding responsivity in any way would add additional development and testing time and obviously cost more money
  • With a single screen in mind you can use the space at your disposal more effectively, have content blocks that perfects fill any available whitespace (within reason) and take advantage of any unique characteristics (ie notch)
  • Industrial equipment is often like this, when they use a technology called PLCs to control them, generally an HMI (Human Machine Interface) is required to control it via a touch screen, with the web steadily expanding it’s not outrageous to assume that one day a browser version of an HMI may be used on these touch screens, which are all one specific size and don’t update like consumer products (remain the same for years, even decades)
  • When we first got into business we set out with the idea that we’d never make a static layout, all our websites were going to be mobile-friendly and responsive
    • Even a few years ago when we opened, there was a lot of production websites that had either a static layout, or had a separate mobile site
  • Today responsivity is the way to go and is generally cheaper and less clunky than an entire mobile website
  • We wouldn’t recommend making something with a static layout unless it has a very specific fixed set of parameters that need to be met, or if it will exclusively be used on a specific display for years to come

    • Web News - Early Access Software/Games

    • Potential Issues:
    • Developers don’t want the pressure of saying that it is version 1.0 because of the assumed amount of polish
  • The developer getting paid and receiving free bug testing while in early access/beta doesn’t seem fair to the user/customer that is buying it
  • The potential that you could pay for something but it never gets fully released
  • Even if something is free but in beta like flutter.io a cross platform framework for android and iOS. It could be abandoned, and your efforts can be for nothing in learning it and helping with its feature development/bug fixing
  • Potential Benefits: 
    • The user can feel part of the development and evolving process of the software and when/if it is released will be more attached to the product
  • Strapped for cash but talented developers have a chance to maybe release a MVP and work on it while receiving feedback and funding from the people using it
  • A longer update cycle for applications/games because of constant funding
  • User feedback can lead to new features and improvements as the system is not yet complete and it is easier to add/change something in this state

    • You can find us on...

    Facebook | Twitter | Instagram

    RSS | Patreon | Spotify

    Medium | YouTube | GitHub 

    Reddit

    1 hr 22 min
  • Responsive Design
    Responsive design has revolutionized how websites are developed, but static layouts still have their place. We explore these two different layout methods in this episode of the podcast.
    1 hr 22 min

About HTML All The Things - Web Development, AI, and Developer Careers

From the publisher's feed

HTML All The Things is a podcast for developers navigating the modern web industry.

More shows like HTML All The Things - Web Development, AI, and Developer Careers

The Joe Rogan Experience by Joe Rogan

The Joe Rogan Experience

227,535 Listeners

The Changelog: Software Development, Open Source by Changelog Media

The Changelog: Software Development, Open Source

286 Listeners

The Side Hustle Show by Nick Loper of Side Hustle Nation | YAP Media

The Side Hustle Show

1,582 Listeners

Software Engineering Daily by Software Engineering Daily

Software Engineering Daily

622 Listeners

JavaScript Jabber by Charles M Wood

JavaScript Jabber

234 Listeners

This Past Weekend w/ Theo Von by Theo Von

This Past Weekend w/ Theo Von

28,024 Listeners

JavaScript Jabber by Charles M Wood

JavaScript Jabber

62 Listeners

Syntax - Tasty Web Development Treats by Wes Bos & Scott Tolinski - Full Stack JavaScript Web Developers

Syntax - Tasty Web Development Treats

982 Listeners

The freeCodeCamp Podcast by freeCodeCamp.org

The freeCodeCamp Podcast

484 Listeners

PodRocket by LogRocket

PodRocket

59 Listeners

Whiskey Web and Whatnot by Skill Issue Studios

Whiskey Web and Whatnot

55 Listeners

Develop Yourself by Brian Jenney

Develop Yourself

7 Listeners

The Startup Ideas Podcast by Greg Isenberg

The Startup Ideas Podcast

211 Listeners

WEAPONIZED with Jeremy Corbell & George Knapp by Jeremy Corbell and George Knapp

WEAPONIZED with Jeremy Corbell & George Knapp

1,417 Listeners

Front-End Fire by TJ VanToll, Paige Niedringhaus, Jack Herrington

Front-End Fire

11 Listeners