You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: activities/book-of-the-week.md
+22-12Lines changed: 22 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,38 +9,44 @@ parent: Activities
9
9
10
10
Each week we invite a book author to DataTalks.Club to answer questions about their book and the topic it covers.
11
11
12
-
We don't regularly host this event at the moment. If you know a book author and want to ask them questions, reach out to Alexey Grigorev - we can invite them.
12
+
We don't regularly host this event at the moment. If you know a book author and want to ask them questions, reach out to the DataTalks.Club team. We can invite them.
13
13
14
14
Archive of past book discussions: [datatalks.club/books.html](https://datatalks.club/books.html)
15
15
16
16
## How it works
17
17
18
+
To take part:
19
+
18
20
- Join the [`#book-of-the-week`](https://app.slack.com/client/T01ATQK62F8/C01H403LKG8) channel in Slack
19
21
- Ask as many questions as you'd like
20
22
- The book authors answer questions from Monday till Thursday
21
23
- On Friday, the authors decide who wins free copies of their book
22
24
23
25
## Information for authors
24
26
25
-
Book of the week is an AMA-like event where the community asks authors questions about their books and the topics the books cover.
27
+
Book of the week is an AMA-like event. The community asks authors questions about their books and the topics the books cover.
26
28
27
29
It's not a live event. The interaction happens asynchronously in Slack, so you can answer questions at a time that is convenient for you.
28
30
29
-
If you'd like to take part, email Alexey at [alexey@datatalks.club](mailto:alexey@datatalks.club) or find Alexey Grigorev in the [DataTalks.Club Slack](https://datatalks.club/slack.html).
31
+
If you'd like to take part, email [alexey@datatalks.club](mailto:alexey@datatalks.club) or contact the DataTalks.Club team in [Slack](https://datatalks.club/slack.html).
32
+
33
+
## Community support
30
34
31
-
### What we do
35
+
DataTalks.Club helps with:
32
36
33
37
- Promote the event in the DataTalks.Club newsletter
34
38
- Announce the event internally in Slack
35
39
- Give the community a place to ask questions during the week
36
40
- Help select giveaway winners randomly if you prefer not to choose them yourself
37
41
- Send a calendar invite to remind you to answer questions
38
42
39
-
DataTalks.Club has a mailing list with 120k subscribers and an average open rate of 30%, so more than 36,000 people can see the book announcement. The Slack community has 90,000 registered members, and more than 3,000 people are in the `#book-of-the-week` channel.
43
+
DataTalks.Club has a mailing list with 120k subscribers and an average open rate of 30%. More than 36,000 people can see the book announcement. The Slack community has 90,000 registered members. More than 3,000 people are in the `#book-of-the-week` channel.
40
44
41
45
On average, authors get 10-20 questions per week.
42
46
43
-
### What authors do
47
+
## Author responsibilities
48
+
49
+
Authors usually:
44
50
45
51
- Join Slack at least once per day from Monday to Thursday and answer questions from the community
46
52
- Reply in Slack threads so the discussion stays organized
@@ -52,31 +58,35 @@ If you don't want to answer some questions, that's fine.
52
58
53
59
Winners can be selected randomly or based on the most interesting questions. If you want random selection, we can take care of it.
54
60
55
-
Ebooks are preferred because printed books can be difficult to ship. We already have agreements with Manning, O'Reilly, and Packt, so if your book is with one of these publishers, you don't need to arrange anything separately. If your book is with another publisher, we'll be happy to talk to their marketing team.
61
+
Ebooks are preferred because printed books can be difficult to ship. We already have agreements with Manning, O'Reilly, and Packt. If your book is with one of these publishers, you don't need to arrange anything separately. If your book is with another publisher, we'll be happy to talk to their marketing team.
56
62
57
-
### What we need from you
63
+
## Materials we need
64
+
65
+
Please send:
58
66
59
67
- Your bio and a picture, or a link to a website where we can take them
60
68
- Optionally, social media accounts such as Twitter, LinkedIn, GitHub, and your personal website
61
69
- The book cover image and description, or a link to a website where we can take them
62
70
- Optionally, links to the publisher's page, book landing page, GitHub repository, or other supplemental materials
63
71
64
-
###Publishing answers
72
+
## Publishing answers
65
73
66
74
Your Slack answers will be published on the DataTalks.Club website, so people can read them without logging in to Slack.
67
75
68
-
If you don't want to publish your answers, or you'd like to remove or edit some of them, let us know.
76
+
If you don't want to publish your answers, let us know. We can also remove or edit specific answers.
69
77
70
78
You can look at previous discussions in the [book archive](https://datatalks.club/books.html).
71
79
72
-
### Typical schedule
80
+
## Typical schedule
81
+
82
+
The usual weekly schedule:
73
83
74
84
- After the announcement, people start asking questions in Slack
75
85
- From Monday to Thursday, come to Slack every day and answer questions
76
86
- On Thursday, we'll ask whether you want to select the winners yourself or use random selection
77
87
- On Friday, we'll announce the winners
78
88
79
-
###Feedback from authors
89
+
## Feedback from authors
80
90
81
91
> Hi Alexey. We're only part of the way through the week but I wanted to thank you for inviting me to be part of the DataTalks.Club book of the week. The questions in Slack have been super high quality and I've been getting a lot of positive feedback via LinkedIn as well. I would highly recommend this format to any author. Thanks!
We also run free online courses (zoomcamps) on data engineering, machine learning, MLOps, LLMs, and more. See the [courses section]({{ '/courses/' | relative_url }}) for details, or read our [guide to free online courses](https://datatalks.club/blog/guide-to-free-online-courses-at-datatalks-club.html).
26
+
We also run free online courses called zoomcamps that cover data engineering, machine learning, MLOps, and LLMs. See the [courses section]({{ '/courses/' | relative_url }}) for details. You can also read our [guide to free online courses](https://datatalks.club/blog/guide-to-free-online-courses-at-datatalks-club.html).
25
27
26
28
## Other activities
27
29
28
-
-[Book of the Week]({{ '/activities/book-of-the-week/' | relative_url }}) - book authors answer community questions (currently not very active)
30
+
Other formats:
31
+
32
+
-[Book of the Week]({{ '/activities/book-of-the-week/' | relative_url }}) - book authors answer community questions (currently not active)
29
33
-[Open-Source Spotlight]({{ '/activities/open-source-spotlight/' | relative_url }}) - short demos of open-source tools by their authors
30
34
-[Project of the Week]({{ '/activities/project-of-the-week/' | relative_url }}) - learn-by-doing study groups (currently inactive)
If you'd like to showcase your open-source project, reach out to Alexey Grigorev.
14
+
If you'd like to show your open-source project, reach out to the DataTalks.Club team.
15
15
16
16
## Notes for guests
17
17
18
18
Please don't prepare slides - it's best when we jump into a demo directly.
19
19
20
-
### Plan
20
+
## Plan
21
+
22
+
The usual structure:
21
23
22
24
- Intro, some info about you and about the tool (1-2 minutes)
23
-
- "Welcome to Open-Source Spotlight. We invite open-source authors and ask them to show the tools they're working on. Today we have NAME. Hi NAME, tell us a few words about yourself and about the tool you want to show us."
24
25
- The demo
25
26
- Questions (3-4 minutes):
26
27
- How many people are working on it?
@@ -35,19 +36,19 @@ After the video, please send me:
35
36
- Link to your GitHub repo and documentation
36
37
- Everything else you'd like to add to the description
37
38
38
-
###Preparation tips
39
+
## Preparation tips
39
40
40
41
Make sure the font size is large enough (the default size is always too small).
41
42
42
-
- Prepare your browser, the terminal and your IDE - and other things you want to share
43
-
-Good rule of thumb: the text should be visible on YouTube on 13" laptop screens without people having to go full-screen
43
+
- Prepare your browser, terminal, IDE, and anything else you want to share.
44
+
-Make the text visible on YouTube on 13" laptop screens without people having to go fullscreen.
Copy file name to clipboardExpand all lines: activities/podcast.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ parent: Activities
9
9
10
10
Live events where we invite data science practitioners, ML engineers, and AI researchers to share their experience. No slides - just a conversation between the guest and the host.
11
11
12
-
Everyone who joins the live broadcast can ask questions, and we cover them as we go. After the live event, the recording is published as a podcast episode on audio platforms like Spotify and Apple Podcasts. Transcripts and show notes are available on our website.
12
+
Everyone who joins the live broadcast can ask questions, and we cover them as we go. After the live event, the recording is published as a podcast episode. It is available on Spotify, Apple Podcasts, and other audio platforms. Transcripts and show notes are available on our website.
13
13
14
14
-[YouTube playlist](https://www.youtube.com/playlist?list=PL3MmuxUbc_hK60wsCyvrEK2RjQsUi4Oa_) - video recordings
15
15
-[All episodes](https://datatalks.club/podcast.html) - transcripts and show notes
Copy file name to clipboardExpand all lines: activities/project-of-the-week.md
+29-41Lines changed: 29 additions & 41 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,11 +9,13 @@ parent: Activities
9
9
10
10
Project of the week is a study group with focus on building things and learning by doing. Every day we have a set of tasks. We finish them together and hold each other accountable.
11
11
12
-
This activity is currently not active. If you'd like to organize a project of the week, reach out to Alexey Grigorev.
12
+
This activity is currently not active. If you'd like to organize a project of the week, reach out to the DataTalks.Club team.
> Welcome to project of the week! This week we will learn about recommender systems
56
-
>
57
-
> You can find more details here: <link>
58
-
>
59
-
> Plan for today:
60
-
>
61
-
> - Come up with a project idea.
62
-
> - Select the dataset for your project.
63
-
> - Create a GitHub project.
64
-
> - Share your progress on Slack and in social media.
65
-
66
-
### Template for other days
67
-
68
-
> Hi everyone :wave:
69
-
>
70
-
> Welcome to second day of project of the week.
71
-
>
72
-
> Today we will start learning about <topic>.
73
-
>
74
-
> Hope you all have selected the dataset to use.
75
-
>
76
-
> Plan for today:
77
-
>
78
-
> - Point 1
79
-
> - Point 2
80
-
> - ...
81
-
>
82
-
> Suggested materials:
83
-
>
84
-
> - thing 1
85
-
> - thing 2
86
-
>
87
-
> You will find all the details here: <link>
55
+
## First message template
56
+
57
+
Include:
58
+
59
+
- Greeting
60
+
- Topic for the week
61
+
- Link with details
62
+
- Plan for the day
63
+
64
+
For the first day, the plan usually asks participants to choose a project idea and select a dataset. It also asks them to create a GitHub project and share progress.
Copy file name to clipboardExpand all lines: activities/webinars.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ parent: Activities
7
7
8
8
# Webinars
9
9
10
-
Talks with slides on topics like data engineering, machine learning, MLOps, AI tools, and more. The main part is the presentation, followed by Q&A. Webinars are typically 60 minutes.
10
+
Talks with slides cover data engineering, machine learning, MLOps, and AI tools. The main part is the presentation, followed by Q&A. Webinars are typically 60 minutes.
Copy file name to clipboardExpand all lines: activities/workshops.md
+20-18Lines changed: 20 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,52 +7,54 @@ parent: Activities
7
7
8
8
# Workshops
9
9
10
-
Hands-on sessions with minimal slides and maximum practice. We pick a specific problem and solve it together throughout the session. Workshops are typically 90 minutes - longer than other events - so people walk away having learned something new by doing it themselves.
10
+
Hands-on sessions have minimal slides and maximum practice. We pick a specific problem and solve it together throughout the session. Workshops are typically 90 minutes, so people learn by doing.
-[Upcoming and past workshops](https://datatalks.club/events.html)
14
14
15
15
## Notes for instructors
16
16
17
-
### How it works
17
+
##Format
18
18
19
19
We use Zoom for workshops.
20
20
21
21
- We have a Zoom call and broadcast it to our YouTube channel.
22
22
- Viewers join on YouTube. They do not join Zoom.
23
-
- The Zoom call is only for Alexey and the workshop instructor or instructors.
23
+
- The Zoom call is only for the host and workshop instructor or instructors.
24
24
- We typically start 5 minutes before to check that everything works fine.
25
-
-In Zoom, Alexey starts streaming to YouTube.
25
+
-The host starts streaming to YouTube from Zoom.
26
26
- We only get the YouTube link after the stream starts.
27
-
- After that, Alexey shares the YouTube link via Luma, Meetup, and other channels.
28
-
-Alexey keeps an eye on questions from YouTube and brings them up during the session.
29
-
- If a question fits what we are talking about right now, Alexey can bring it up right away.
30
-
- Otherwise, Alexey brings it up at the next logical point or at the end of the session.
27
+
- After that, the host shares the YouTube link via Luma, Meetup, and other channels.
28
+
-The host watches questions from YouTube and brings them up during the session.
29
+
- If a question fits the current topic, the host can bring it up right away.
30
+
- Otherwise, the host brings it up at the next logical point or at the end of the session.
31
31
32
-
###Examples
32
+
## Examples
33
33
34
-
Typically, you prepare the workshop yourself. In some cases, Alexey can prepare it too.
34
+
Typically, you prepare the workshop yourself. In some cases, the DataTalks.Club team can prepare it too.
35
35
36
36
-[How to Evaluate MCP-powered AI Agents Beyond Accuracy using Agent GPA - Josh Reini](https://www.youtube.com/watch?v=oMmJvlNuDZE)
37
37
-[From APIs to Warehouses: AI-Assisted Data Ingestion with dlt - Aashish Nair](https://www.youtube.com/watch?v=5eMytPBgmVs)
38
-
-[Build a Production-Ready YouTube AI Agent with Temporal - Step-by-Step Tutorial](https://www.youtube.com/watch?v=N1gaI3Qz6vw) - example where Alexey prepared the workshop
38
+
-[Build a Production-Ready YouTube AI Agent with Temporal - Step-by-Step Tutorial](https://www.youtube.com/watch?v=N1gaI3Qz6vw) - example prepared by the DataTalks.Club team
39
39
40
-
### Preparation
40
+
## Preparation
41
+
42
+
Before the workshop:
41
43
42
44
- Download Zoom for your operating system before the workshop.
43
-
- Test Zoom in advance by starting a meeting by yourself and checking that audio and video work.
45
+
- Test Zoom in advance. Start a meeting by yourself, then check audio and video.
44
46
- If this is your first time using Zoom, test screen sharing too.
45
47
- On macOS, Zoom may ask for permissions when you share your screen, so it is better to resolve them before the workshop.
46
48
- Make sure the font size is large enough. The default size is always too small.
47
49
- Prepare your browser, terminal, IDE, and anything else you want to share.
48
-
-Good rule of thumb: the text should be visible on YouTube on a 13" laptop screen without people having to go full screen.
50
+
-Make the text visible on YouTube on a 13" laptop screen without people having to go full screen.
Copy file name to clipboardExpand all lines: courses/course-management-platform/contributing.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,13 @@ The course management platform is open source. Contributions are welcome from th
12
12
13
13
## GitHub Repository
14
14
15
+
The platform code is public:
16
+
15
17
-[Course Management Platform on GitHub](https://github.com/DataTalksClub/course-management-platform)
16
18
17
-
## How to Contribute
19
+
## Contributing
18
20
19
-
###Reporting Issues
21
+
## Reporting Issues
20
22
21
23
If you find a bug or have a suggestion:
22
24
@@ -27,7 +29,9 @@ If you find a bug or have a suggestion:
27
29
- Expected behavior
28
30
- Screenshots if applicable
29
31
30
-
### Areas to Contribute
32
+
## Areas to Contribute
33
+
34
+
Useful contribution areas include:
31
35
32
36
- Bug fixes
33
37
- Feature suggestions
@@ -41,4 +45,3 @@ For questions about contributing:
41
45
42
46
- Join the [`#course-management-platform`](https://app.slack.com/client/T01ATQK62F8/C06EKF95CQ3) channel on Slack (see [Slack guide]({{ '/general/slack/' | relative_url }}))
0 commit comments