Latest Podcast

Services

Full Stack Javascript
Development Tools, Frameworks, and Services Related To Full Stack Javascript
Development Workflows
Development Workflows Related to Full Stack Javascript
Git for Developers
Git Distributed Version Control For Developers
Git For Non-Developers
Git Distributed Version Control For Non-Developers
The Command Line Interface
Getting To Know Your Computer Better via The Command Line Interface (CLI) aka Terminal Program on OSX

1 of 5

Chattrbox app
application uses: nodejs, npm, websockets, socket.io, expressjs, js, jquery, geolocation, sass, google maps url api
learn more
Speech to Text app
application uses: code refactoring, workflow refactoring, react, webpack 4+, babel 7, scss, mini css extract plugin, js, npm, localstorage to file download, react-fontawesome, jest, eslint config react, service worker, asset manifest, precache manifest, workbox webpack plugin, webpack visualizer plugin, speech recognition, voice commands, session storage
learn more
Node Drawing app
application uses: nodejs, serve favicon, socket.io, websockets, expressjs, node canvas, collaboration
learn more

Outdated Content And Google Custom Search
Yesterday I pretty much completed this site ... But there was still one very important thing I hadn't addressed ...
tagged in: google search, google custom search, outdated content, seo
categorized under: outdated content
Why Your Local Machine (Computer) May Not be Pointing to Your Newly Propagated Site
The other day I moved my business site, interglobalmedianetwork.com, from Github gh-pages to Netlify, where this site resides as well ...
tagged in: dns, local hosts file, ip address, site propagation, dns information groping
categorized under: web hosting, changing web hosts

Tip of the Day #1
GatsbyJS Devs: Don't use the state prop (props.location.state). It may pass a Lighthouse audit. It may seem like a really cool "shortcut" to creating pages, but it will kill you in Search.
Tip of the Day #2
If you are offering a course, make sure that it is updated to the latest of whatever. Don't just create it and then forget about it while still offering it (for a hefty price).
Tip of the Day #3
Gatsby Devs: don't use @emotion/core and @emotion/styled 10+ with GatsbyJs 2. Too many breaking changes that only complicate matters and also incompatible out of the box. Use styled-components instead.
Tip of the Day #4
Gatsby Devs: don't use the iframe tag in your dangerouslySetInnerHTML with GatsbyJS. It won't work, and probably a bad idea anyway. Use it in your component.

1 of 4