4.9 • 1.1K Ratings
🗓️ 13 August 2018
⏱️ 32 minutes
🔗️ Recording | iTunes | RSS
🧾️ Download transcript
In this Hasty Treat, Scott and Wes discuss how they create courses, design and build curriculum, as well as insights and best practices for content creation.
If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code “tastytreat”.
4:32 - Wes’ process
16:25 - Scott’s process
28:25 - How to get started
Click on a timestamp to play from that location
0:00.0 | Monday, Monday, Monday, |
0:02.0 | Open wide Dev fans. |
0:04.0 | Get ready to stuff your face |
0:06.0 | with JavaScript, CSS, node modules, barbecue tips, |
0:09.0 | get workflows, |
0:10.0 | break dancing, soft skills, web development, |
0:12.0 | the hastiest, the craziest, the craziest development the hastiest the craziest the tastiest web development treats coming in hot here is |
0:18.1 | Wes Barracuda bars and Scott El Tauru loco Tolinsky |
0:26.0 | Oh welcome to syntax |
0:29.0 | This is the podcast with the Hello. This is a Monday edition of syntax also known as a hasty treat. |
0:47.0 | So let's get ready for this hasty treat in which we're going to be talking about course |
0:51.2 | curriculums. A lot of people ask us how we develop our |
0:54.1 | courses, which they can range from short courses to long courses to monthly reoccurring courses to |
1:01.2 | all sorts of stuff. So we're going to talk all about how we make our |
1:05.1 | courses and some of the insights and how we develop our content. |
1:08.8 | So this episode is sponsored by Century which does error tracking for pretty much actually any language. |
1:14.9 | I'm going to specifically use it myself for JavaScript React applications on the front |
1:19.1 | end. I also run it on my node server. And what happens is that any time there's an error in your user's |
1:24.4 | browser or on your your server side what it does is it collects all of those |
1:28.6 | errors and provides it to you in a really smart backend that will allow you to peer into why those |
1:36.6 | errors happened what happened to the errors when are they happening on what |
1:39.8 | kinds of browsers where in the world are they they happening? You can attach specific data to a user. |
... |
Please login to see the full transcript.
Disclaimer: The podcast and artwork embedded on this page are from Wes Bos, and are the property of its owner and not affiliated with or endorsed by Tapesearch.
Generated transcripts are the property of Wes Bos and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.
Copyright © Tapesearch 2025.