Every course from every provider we track, with the same filters over all of them: level, length, price, certificate and who stands behind it.
212 courses for “Master Python Plotly in 1.5 Hours: From Basics to Advanced Data Visualizations”
12 hours
A 12-hour generative AI course from Noble Desktop, taught live in New York or online.
6 hours
A six-hour advanced Figma class from Noble Desktop, taught in New York or live online, covering variables, modes and conditional prototyping.
New courses, a couple of emails a month. One click unsubscribes.
28 lessons, about 15 hours
A paid certification from GrowthHackers University: prompting, working with PDFs, images, video and data as inputs, and producing landing pages, video, audio and animation as outputs. The provider states 15 hours across 28 lessons.
27 hours
25 lessons, 1592 minutes in all, from YouTube.
41 minutes
Connected & Software-Defined Vehicles
8 lessons, 41 minutes in all, from YouTube.
12 minutes
2 lessons, 12 minutes in all, from YouTube.
15 hours
Automotive Testing & Validation
26 lessons, 917 minutes in all, from YouTube.
1 hour
15 lessons, 66 minutes in all, from YouTube.
47 minutes
A 47-minute video from Advanced Thermal Solutions, Inc..
6 minutes
A 6-minute video from DigiKey.
3 minutes
A 3-minute video from The Learning Studio.
5 hours
Five hours on MLOps: getting a model out of a notebook and keeping it running.
12 hours
Twelve hours of Python, taught by building rather than by explaining.
12 hours
Twelve hours of Python for beginners, taken slowly enough to follow along.
4 hours
Four and a half hours of Python from nothing, the course most people start with.
45 minutes
Forty-five minutes of scikit-learn, from fitting a model to scoring it.
55 minutes
Building a working e-commerce data pipeline, start to finish, with Snowflake and dbt.
3 hours
Nearly three hours on time series: the components, the models, and the forecasts built from them.
2 hours
An hour and a half of forecasting in Python, for somebody who has not done it before.
2 hours
Two and a half hours on decision trees — how one is built, and how it is read.
