I noticed the addition of the data engineering path in this commit: 95fc081
This is huge! I think it will be a big offering. That being said I noticed you removed the S3/CDN course that is on the current Go backend path. While that course is a bit focused on things like streaming video and what not, knowing how to work with object storage and CDNs is crucial for data engineering. Data lakes are entirely S3/object storage based these days. I see the addition of DuckDB and it does handle scanning of the parquets from S3 itself, but a good data engineer cannot escape working S3 directly.
@wagslane would it make sense to still include the current Go S3 course on the new track or will a new S3/object storage course be added for DE path?
I noticed the addition of the data engineering path in this commit: 95fc081
This is huge! I think it will be a big offering. That being said I noticed you removed the S3/CDN course that is on the current Go backend path. While that course is a bit focused on things like streaming video and what not, knowing how to work with object storage and CDNs is crucial for data engineering. Data lakes are entirely S3/object storage based these days. I see the addition of DuckDB and it does handle scanning of the parquets from S3 itself, but a good data engineer cannot escape working S3 directly.
@wagslane would it make sense to still include the current Go S3 course on the new track or will a new S3/object storage course be added for DE path?