TRANSCRIPT 🔗
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 6/12/2024 4:55:02 AM
Duration: 3560.158
Channels: 1
1
00:00:02.720 --> 00:00:07.140
Hello, friends. We are back with episode 168 of the R Weekly Highlights podcast.
2
00:00:07.555 --> 00:00:22.320
We're so glad you're here listening from wherever you are around the world. And this is the show if you are new to this podcast. This is the show where we talk about the terrific resources that have been highlighted in this week's our weekly issue, all available at rweekly.org.
3
00:00:23.855 --> 00:00:30.435
My name is Eric Nantz. As always, I'm delighted that you've joined us wherever you are. We have a lot of fun things to talk about, but
4
00:00:31.140 --> 00:00:40.025
this is a team effort after all. And I got my partner in our related crime here, so to speak. Mike Thomas is here. Join me at the hip. How are you doing today, Mike?
5
00:00:40.345 --> 00:01:02.795
Doing pretty well, Eric. Not to violate any HIPAA laws and knock on wood. I am currently trying to dodge pink eye in our household so far. So good, but, I've I've heard that it's it's not fun. This is our first go around with it. So please pray for me. But We, we we have you in our thoughts for sure as somebody who's had a whole smorgasbord of
6
00:01:03.255 --> 00:01:04.475
illnesses, viruses,
7
00:01:05.015 --> 00:01:06.475
things, and that
8
00:01:06.810 --> 00:01:07.630
and the kiddos,
9
00:01:08.010 --> 00:01:09.530
daycare days. Yeah. You,
10
00:01:10.330 --> 00:01:14.110
keep strong, my friend. Thank you very much. But, Eric, how was your weekend?
11
00:01:14.545 --> 00:01:20.485
Yeah. You know what? It's been a while since we did this. We're gonna dust off a segment I used to do in my in my live streams.
12
00:01:21.185 --> 00:01:23.740
Who's ready for story time with our
13
00:01:24.700 --> 00:01:25.200
podcast?
14
00:01:25.979 --> 00:01:26.479
Beybey.
15
00:01:30.220 --> 00:01:35.555
So it's story time with Eric now. So let's, buckle up for a few minutes here. So
16
00:01:36.175 --> 00:01:47.460
Friday night, I get a little opportunity to do a little, you know, open source development work on some of this podcasting database stuff. I've been pitching in with a podcasting 2 point o project. And recently,
17
00:01:48.240 --> 00:01:52.515
Dave Jones, who helps spearheads a lot of that effort, gave me access to some more
18
00:01:52.895 --> 00:01:56.594
lower level JSON files and object storage to help
19
00:01:56.975 --> 00:02:08.555
analyze some of the the data that's going into their database as kind of a more real time access of it. And these are these are actually massive JSON files. In fact, one of them is over 200 gigs worth. So
20
00:02:09.015 --> 00:02:15.275
I figured, okay. You know what? To help, you know, minimize the bandwidth cost just for once, I'm gonna download
21
00:02:15.640 --> 00:02:17.420
a snapshot of those locally
22
00:02:18.040 --> 00:02:20.620
on my, you know, somewhat beefy
23
00:02:21.079 --> 00:02:27.265
network storage down in the basement where I have, like, a group of 4 hard drives networked together, and that's where I do
24
00:02:27.565 --> 00:02:37.400
all my backup. So I figured, you know what? I'm just gonna throw it on there. That way, I can, you know, work with them in a prototyping way like any good citizen would do with bandwidth and everything like that.
25
00:02:38.020 --> 00:02:45.935
So that was like, earlier in the week, and then Friday night rolls around. I'm gonna do a little hacking on it again, just kinda get to know those files a bit.
26
00:02:46.379 --> 00:02:47.739
Go to the path.
27
00:02:48.459 --> 00:03:01.105
My, laptop mounts. This is like a Samba share. But I I go to and it's run Linux, but Samba is the protocol. So in any event, I go to grab one of these files or always read it into R. It's kind of like a prototyping.
28
00:03:01.724 --> 00:03:03.025
And then I get a
29
00:03:03.485 --> 00:03:05.665
path file not found. And I'm thinking,
30
00:03:06.090 --> 00:03:07.230
what's this about?
31
00:03:07.610 --> 00:03:14.735
I know I downloaded earlier in the week, and it's alongside a bunch of my other kinda our open source, like big file stuff. And
32
00:03:15.215 --> 00:03:17.075
I go into the SSH
33
00:03:17.455 --> 00:03:20.995
session to my network storage that's running Linux. And
34
00:03:21.295 --> 00:03:22.915
I navigate to that area,
35
00:03:23.959 --> 00:03:25.180
directory not found.
36
00:03:27.000 --> 00:03:28.780
Oh, no. Oh, boy.
37
00:03:29.319 --> 00:03:32.780
So I do a little poking around, and I realize
38
00:03:33.885 --> 00:03:35.745
that's not the only thing that I found.
39
00:03:37.165 --> 00:03:44.770
I am now not able to see some very, and I mean very important family media files, which if you guess
40
00:03:45.310 --> 00:03:48.450
are pictures and videos that I've recorded over the years.
41
00:03:49.475 --> 00:03:59.095
No. No. No. No. No. No. No. No. No. No. No. No. Now now I when I set this up many years ago, I did put in a couple backup strategies,
42
00:04:00.340 --> 00:04:03.800
one of which was to send my pictures
43
00:04:04.740 --> 00:04:05.640
over to
44
00:04:06.260 --> 00:04:09.080
Google Drive, albeit in an encrypted way
45
00:04:09.545 --> 00:04:13.564
so that I didn't feel like I was feeding their machine learning algorithms for image recognition
46
00:04:14.105 --> 00:04:14.685
and whatnot.
47
00:04:15.144 --> 00:04:20.630
And so I quickly dust off my notes on how to interact with that. I was using a service called Duplicate
48
00:04:21.330 --> 00:04:22.230
to get that.
49
00:04:22.850 --> 00:04:27.670
And luckily enough, I did get the majority of my pictures back, albeit
50
00:04:28.695 --> 00:04:31.035
they stopped working after 2023,
51
00:04:31.495 --> 00:04:39.250
which was odd because I didn't get an alert on that. So that's one downside. But what was not on that cloud backup
52
00:04:39.790 --> 00:04:40.690
were the videos.
53
00:04:41.870 --> 00:04:42.370
Load full transcript
So
54
00:04:43.070 --> 00:04:47.330
back to this internal setup, I have what's called a
55
00:04:47.905 --> 00:04:51.045
pooled file system of all these drives put together.
56
00:04:51.585 --> 00:04:54.965
And then there was an weekly job I would run
57
00:04:55.379 --> 00:05:04.520
that was kinda like RAID. If you ever heard of, like, how network drives are backed up in, like, a mirrored way, RAID is one way to do it. This is a different take called SnapRAID
58
00:05:05.095 --> 00:05:06.475
where it would, every week,
59
00:05:06.855 --> 00:05:09.755
funnel everything into what's called a parity drive.
60
00:05:10.295 --> 00:05:12.155
And that way, if the worst happened,
61
00:05:12.740 --> 00:05:16.840
I could restore from that parity drive and get everything back. So I figured,
62
00:05:17.220 --> 00:05:23.945
oh, yes. I I did run that job. Right? Now I go to where that file would be stored. It's like this big compressed file.
63
00:05:24.885 --> 00:05:29.145
But then my heart sank because the last run of that, apparently, was in 2020,
64
00:05:30.710 --> 00:05:31.930
and I didn't know that.
65
00:05:33.190 --> 00:05:40.985
I still ran the restore anyway just to see what happens. And sure enough, I've got videos and pictures and other important files
66
00:05:41.764 --> 00:05:42.985
up to that point.
67
00:05:43.845 --> 00:05:45.785
So I am missing now
68
00:05:46.260 --> 00:05:50.520
3 almost 4 years' worth of important content. So,
69
00:05:51.060 --> 00:05:52.520
of course, now I investigate,
70
00:05:53.060 --> 00:05:55.160
can I mount this drive somewhere else?
71
00:05:55.465 --> 00:05:59.645
Can I just take it out of this network storage and put it into, like, an enclosure,
72
00:06:00.265 --> 00:06:04.045
connect it to my laptop, see if I can somehow salvage the files from there?
73
00:06:04.470 --> 00:06:11.130
That's when I realized there's the problem. The hard drive is making this sequential kind of buzzing kind of sound
74
00:06:11.854 --> 00:06:14.275
and cannot be recognized by any OS.
75
00:06:15.455 --> 00:06:16.754
That screams
76
00:06:17.294 --> 00:06:18.275
hardware failure.
77
00:06:19.134 --> 00:06:21.440
So I have now sent this
78
00:06:22.000 --> 00:06:31.335
to a drive recovery vendor. I'm waiting to hear back for the evaluation if they can get everything back. But if they are able to get it back, I hate to say it's not gonna
79
00:06:31.895 --> 00:06:35.194
be cheap to get it back. But this is a very harsh lesson,
80
00:06:35.655 --> 00:06:39.755
folks. If you have a backup strategy, make sure to check that it's actually working.
81
00:06:40.870 --> 00:06:43.530
If you learn nothing else from this 5 minute diatribe,
82
00:06:44.310 --> 00:06:54.605
look at your backup strategy. Make as many notes as you can because future self will need it when you absolutely positively least expect it like little old me here.
83
00:06:55.385 --> 00:06:56.685
Eric, I'm so sorry.
84
00:06:57.530 --> 00:07:04.705
For our dear listeners out there, I asked Eric how his weekend was, and he would not tell me because he wanted to get my live reaction
85
00:07:05.345 --> 00:07:10.085
during the recording. And my live reaction is is despair, but I am almost,
86
00:07:10.544 --> 00:07:15.009
also not entirely surprised because I feel like story time with Eric
87
00:07:15.710 --> 00:07:17.009
probably sways
88
00:07:17.389 --> 00:07:18.110
a little,
89
00:07:18.509 --> 00:07:23.545
towards the the bad as opposed to the good if we're taking a look at the
90
00:07:23.925 --> 00:07:26.185
distribution of sort of sentiment
91
00:07:26.965 --> 00:07:47.104
around story time with their stories. I am sorry to hear that. I hope that that hardware vendor can can help you out some way somehow and it's not super expensive but, yes, that is, I think something we all struggle with is is backing up and and storage of especially, like, family media and stuff like that. I don't have a good strategy for it.
92
00:07:48.890 --> 00:07:53.470
Yeah. Oh, that that hurts my heart. That hurts my heart because I know how much work you've invested into
93
00:07:54.090 --> 00:07:56.910
building out, you know, your your hardware and software
94
00:07:57.354 --> 00:08:02.255
infrastructure in in the best ways possible and using the the best practices. So,
95
00:08:02.955 --> 00:08:10.390
I'm so sorry to hear that. Oh, I I appreciate that. But life is so ironic. Right? Of all the drives to fail,
96
00:08:11.170 --> 00:08:23.735
the one that has a majority of these family files, files, that had to be the one. I've got other nonsense on there that I could live without. It's just out of convenience, but it had to be that one. So
97
00:08:24.250 --> 00:08:36.815
on top of, yeah, this vendor crossing my fingers, I will not say who they are because I'm not sure if it's gonna work or not. So I'm not giving any free advertising here. I hope this vendor actually pulls it off. But the other lesson is
98
00:08:37.274 --> 00:08:42.660
I was kinda living on borrowed time with some of the infrastructure around this. So I am building
99
00:08:43.200 --> 00:08:52.824
as we speak. The parts are coming in the next couple weeks. A brand new server that's gonna have a much better strategy around it. So there you go. That'll be some rabbit holes.
100
00:08:54.084 --> 00:09:02.760
I does not surprise me at all. Best of luck with that. Yes. Thank you, sir. And, you know, one way or another, I'll I'll, share my learnings.
101
00:09:03.140 --> 00:09:09.475
They're they're this machine will double purpose. It will not just be a storage piece. This may be a piece where I can do
102
00:09:09.855 --> 00:09:30.735
some local Weaver machine learning stuff, AI stuff, or whatnot because I'm gonna I'm gonna spec it out pretty well for those workflows and media production. So it'll be a fun journey nonetheless. Just not one I was quite ready to do until Sure. This, certain event. Well, once you, install the Microsoft operating system and
and turn the the Microsoft recall
103
00:09:31.115 --> 00:09:49.185
switch on, you'll never have to, you'll never have to worry about backing up anything ever again because it'll just watch you all the time. You know what? Yeah. What better peace of mind than to send that over to whatever they're training on? Oh, my goodness. For those of you who aren't aware of what we're talking about, that, Microsoft kinda got in a bit of a kerfuffle when they announced this
104
00:09:49.964 --> 00:09:53.470
feature, if you wanna call it that, where they would have
105
00:09:53.850 --> 00:09:57.310
a background process on your win Windows installation
106
00:09:58.410 --> 00:10:00.990
literally every, what, I don't know, 30 seconds.
107
00:10:01.605 --> 00:10:09.705
Oh, no. I think it's less than that. I think it's, like, every second or every other second. It's gonna take a picture of what's on your your laptop screen.
108
00:10:10.670 --> 00:10:10.990
I
109
00:10:11.630 --> 00:10:21.735
wow. I mean, just wow. It is is hopefully, some of you may think, yeah, that might have some disasters associated with it and many reasons. So
110
00:10:22.035 --> 00:10:26.540
they are rolling it back a little bit in terms of how they're rolling it out. But, nonetheless,
111
00:10:27.640 --> 00:10:32.060
the the cat's out of the bag, as they say, of what they've been planning for for this. So I think,
112
00:10:32.845 --> 00:10:39.345
more to come on this side of it. But, yeah, of all the things I did not expect to see, that announcement was one of them.
113
00:10:40.310 --> 00:10:43.450
Likewise. Likewise. It just makes me wanna install Linux instead.
114
00:10:44.470 --> 00:10:54.204
No. You're not alone. There's a lot of people making the switch after that kind of news, and Apple hasn't quite done themselves any favors either with some of their decisions. But
115
00:10:54.665 --> 00:11:02.589
Onto the r stuff. Yeah. Yeah. We've, digressed enough. But, in any event, we don't have hardware failures to talk about in these highlights. Thank goodness.
116
00:11:03.130 --> 00:11:07.935
And they have been curated this week by Tony Elharbor, another one of our awesome,
117
00:11:08.315 --> 00:11:15.855
curators on the rweekly team. He's been around for quite a couple of years now. And as always, he had tremendous help from our fellow rweekly team members
118
00:11:16.200 --> 00:11:20.540
and contributors like all of you around the world with your awesome poll requests and suggestions.
119
00:11:21.640 --> 00:11:25.180
And we lead off the show with really a testament
120
00:11:25.560 --> 00:11:27.565
and a glimpse into
121
00:11:28.265 --> 00:11:32.765
the vast variety that's available to us with the nature of open source
122
00:11:33.200 --> 00:11:36.500
and especially some of the fundamental issues that can occur,
123
00:11:36.880 --> 00:11:38.740
not just from a development perspective,
124
00:11:39.200 --> 00:11:43.415
but also from a social and other type perspective as well.
125
00:11:43.955 --> 00:11:47.415
And this blog post and our first highlight comes from Kelly Baldwin,
126
00:11:47.795 --> 00:11:51.175
who is a assistant professor of statistics at Cal PIE,
127
00:11:51.580 --> 00:11:53.280
That is California Polytechnic
128
00:11:53.740 --> 00:12:03.245
State University for those that are outside of the US and may not know where that is. But in any event, she leads off with framing this discussion
129
00:12:04.185 --> 00:12:09.165
on 2 paths, if you might say, in the R community with respect to
130
00:12:09.519 --> 00:12:11.779
a lot of the ways that we handle data manipulation,
131
00:12:12.320 --> 00:12:13.220
data processing,
132
00:12:14.240 --> 00:12:16.579
and what has been perceived to be
133
00:12:16.880 --> 00:12:21.465
these separate roads traveled, so to speak. So she frames this post
134
00:12:21.925 --> 00:12:25.465
in light of Robert Frost, the road west traveled
135
00:12:26.060 --> 00:12:26.560
story.
136
00:12:27.260 --> 00:12:34.960
And she also is upfront that this definitely has some opinions. Hey, Mike and our full opinions on this show too. But
137
00:12:35.265 --> 00:12:42.005
I, as we go through this, I definitely see exactly where she's coming from, and I think it's definitely an important discussion
138
00:12:42.305 --> 00:12:42.965
to have.
139
00:12:43.670 --> 00:12:47.050
What we're talking about here are 2 major frameworks
140
00:12:47.350 --> 00:12:49.690
that have kind of, over time,
141
00:12:50.230 --> 00:12:54.915
become pretty mainstream in terms of the art community's efforts for data manipulation.
142
00:12:56.095 --> 00:12:59.875
1 is the tidy verse, which is well known by this point.
143
00:13:00.230 --> 00:13:04.250
Of course, the development of the tidy verse has been led by Hadley Wickham
144
00:13:04.629 --> 00:13:06.889
and his team of engineers at Posit.
145
00:13:07.485 --> 00:13:10.065
And then we have data dot table.
146
00:13:10.525 --> 00:13:14.865
Data dot table was around well before the tidy verse. Data dot table,
147
00:13:15.250 --> 00:13:19.350
for those that aren't aware, had its first major release in 2008.
148
00:13:20.290 --> 00:13:23.745
Yeah. That's, got a dozen in the history books on this,
149
00:13:24.145 --> 00:13:28.245
And it was originally released by the core developer, Matt Dowell.
150
00:13:28.625 --> 00:13:33.850
And there's a link in the county's post for a nice video of what inspired they are dot table
151
00:13:34.310 --> 00:13:35.530
in the first place.
152
00:13:35.990 --> 00:13:41.370
And it you know, from near the beginning, they do that table has been so influential
153
00:13:41.830 --> 00:13:42.650
for many
154
00:13:43.035 --> 00:13:44.895
in the industry and academia,
155
00:13:45.675 --> 00:13:48.495
all walks of the life, so to speak, in the r community
156
00:13:49.035 --> 00:13:54.880
for respect to its very great performance and importing large data files.
157
00:13:55.420 --> 00:14:01.520
It's got its own, you might call, DSL or domain specific language for how you conduct queries and whatnot
158
00:14:01.985 --> 00:14:04.645
and how you do, like, group summaries or filtering
159
00:14:05.185 --> 00:14:06.645
or creating new variables.
160
00:14:07.185 --> 00:14:13.120
It's got a syntax that is unique to it. And once you learn the ins and outs of it, it can be
161
00:14:13.500 --> 00:14:14.800
extremely powerful.
162
00:14:15.820 --> 00:14:18.640
And then fast forward about 6 years later,
163
00:14:19.165 --> 00:14:19.665
dplyr,
164
00:14:20.285 --> 00:14:21.665
the one of the cornerstones
165
00:14:21.965 --> 00:14:25.265
of what became the tidy verse, was released in 2014,
166
00:14:25.725 --> 00:14:30.540
again, authored by Hadley Wickham. And this, a lot of people point to this as the start
167
00:14:31.000 --> 00:14:33.660
of the tidy verse because of this new,
168
00:14:34.600 --> 00:14:37.020
at least new to many people at the time,
169
00:14:37.475 --> 00:14:44.375
way of performing these, you know, fit for purpose functions that use the data frame as, like, the main input
170
00:14:44.920 --> 00:14:50.460
such that you could combine this with the Magritter pipe and do all these nice kind of flowing
171
00:14:50.840 --> 00:14:52.700
analyses of data manipulation,
172
00:14:53.495 --> 00:14:55.435
you know, new variables, summarizations,
173
00:14:55.975 --> 00:14:56.875
group processing,
174
00:14:57.575 --> 00:14:58.235
and whatnot.
175
00:14:59.735 --> 00:15:03.070
So with this, you now have, you know,
176
00:15:03.930 --> 00:15:07.550
at at this is Kelly Podsits here, about 3 major choices
177
00:15:07.850 --> 00:15:09.230
for your data processing.
178
00:15:09.795 --> 00:15:15.255
You could stick with base r. Of course, base r, it's got, you know, plenty of ways to do these type of summaries,
179
00:15:15.635 --> 00:15:16.695
data dot table,
180
00:15:17.154 --> 00:15:18.055
and dplyr.
181
00:15:18.640 --> 00:15:21.620
And they're all going to look quite different from each other.
182
00:15:23.040 --> 00:15:24.980
There has been a bit of a misconception
183
00:15:25.840 --> 00:15:26.740
over the years
184
00:15:27.475 --> 00:15:29.495
that data dot table is
185
00:15:30.675 --> 00:15:34.770
almost directly linked to base are. That's not quite the
186
00:15:40.770 --> 00:15:43.190
perception over the years that it was so
187
00:15:43.885 --> 00:15:45.265
perception over the years
188
00:15:45.805 --> 00:15:59.850
that it was so tightly coupled with base are that it was somehow going hand in hand with that. No. No. No. That's that's definitely not the case. It's got its own, you know, framework. It's got its own syntax. It's got its own paradigms.
189
00:16:00.550 --> 00:16:01.290
And again,
190
00:16:01.644 --> 00:16:02.545
in my opinion,
191
00:16:03.084 --> 00:16:10.225
choice is great in this pay in this space. Now, sometimes the kinds of choices, well, which one do I go with? Well,
192
00:16:10.690 --> 00:16:15.430
we're not going to always
use a cliche, it depends, but a lot of it does actually depend
193
00:16:15.890 --> 00:16:19.430
on what you want out of your data processing pipeline.
194
00:16:20.130 --> 00:16:26.855
But this shouldn't be a situation where you feel like you have to pick 1 and stick with it forever.
195
00:16:27.315 --> 00:16:35.010
Just like any project, you should have the ability to choose the right framework for your requirements or for your job, so to speak,
196
00:16:35.470 --> 00:16:37.090
and what's important to you.
197
00:16:37.550 --> 00:16:38.035
But
198
00:16:38.514 --> 00:16:41.574
it's one she also talks in this post is that,
199
00:16:41.875 --> 00:16:42.375
yeah,
200
00:16:43.154 --> 00:16:45.415
sometimes people feel like they have to be loyal
201
00:16:45.910 --> 00:16:56.605
to a certain package through and through no matter what. No. We all greatly respect developers, but in the end, the choice is ours for what we choose in our data processing needs in this case.
202
00:16:57.225 --> 00:17:05.560
And you shouldn't feel bad about going from, like, a little bit of base r to, like, data dot table or maybe the tidy verse and kinda
203
00:17:06.100 --> 00:17:09.560
as you wish to be able to mix these together. You're not confined
204
00:17:10.295 --> 00:17:15.595
to one framework or the other all the time. This is entirely driven by choice here.
205
00:17:15.975 --> 00:17:19.309
And so she recommends that let's be pragmatic
206
00:17:19.690 --> 00:17:22.909
about this. Let's not try to get into these,
207
00:17:23.289 --> 00:17:25.789
you know, you might call camps or tribalism
208
00:17:26.570 --> 00:17:38.090
of having to really be gung ho about one framework and you're gonna fit this, you know, use this hammer on every job, so to speak, no matter what. Let's be pragmatic about it.
209
00:17:38.950 --> 00:17:49.174
But then she gets to the rest of the the next part of the post where she talks about kind of what's the reason that this is coming about, that she wants to, you know, put this out in the universe, so to speak.
210
00:17:49.955 --> 00:18:03.835
Well, in 2018, Mike, there was a certain event on our well, at the time was one of the leading spaces for kind of social type discussions in the art community on Twitter back when it was called Twitter.
211
00:18:04.535 --> 00:18:07.675
There was what she calls the great Twitter war of 2018,
212
00:18:08.135 --> 00:18:15.840
and take that for whatever irony you wanna read with that. But, Mike, just what in the heck for those that weren't around? What was this all about here?
213
00:18:16.620 --> 00:18:17.740
Yeah. There were some,
214
00:18:19.019 --> 00:18:19.519
accounts
215
00:18:19.820 --> 00:18:22.335
on on Twitter and some folks that I guess
216
00:18:22.795 --> 00:18:31.230
decided to for whatever reason at that point in time get get fired up about whether or not you should be using data dot table or dplyr.
217
00:18:32.650 --> 00:18:37.705
It actually led as as Kelly, I believe, points
out, to
218
00:18:38.005 --> 00:18:39.385
some positive conversations,
219
00:18:40.485 --> 00:18:49.270
between some of the the cooler heads and actually maybe the the more important folks on both sides of the fence including Matt Dowell and Hadley Wickham, I believe to the,
220
00:18:49.750 --> 00:18:50.250
development
221
00:18:50.789 --> 00:18:51.929
of the dtplyr
222
00:18:52.390 --> 00:19:00.855
package which is sort of the best of both worlds where you're allowed to write dplyr syntax that actually translates and executes
223
00:19:01.340 --> 00:19:13.285
data dot table code under the hood. So you you get your dplyr syntax, but you get your data dot table performance, which was was pretty cool. But, you know, 2018 on Twitter was a little bit of a different time.
224
00:19:14.065 --> 00:19:14.885
Your timeline
225
00:19:15.345 --> 00:19:16.164
was actually
226
00:19:16.705 --> 00:19:22.340
relevant to the people that you followed and the type of content that you wanted to see as opposed to nowadays.
227
00:19:22.880 --> 00:19:23.520
I don't think,
228
00:19:24.000 --> 00:19:26.500
I see any posts from any of my followers
229
00:19:26.880 --> 00:19:37.580
on there but I I guess I'll I'll digress. It it was, I would like to say, a better time for the data science in our community and it was a nice place to to come together as opposed to now. We have a few disparate
230
00:19:37.880 --> 00:19:42.299
places to to try to do that, Macedon being being one of those places.
231
00:19:43.035 --> 00:19:47.055
But for whatever reason, you know, most of the discourse, most of the time was great.
232
00:19:47.515 --> 00:19:48.655
And in 2018,
233
00:19:48.955 --> 00:19:56.830
a a few people decided to start, you know, throwing stones from the data dot table and tidyverse sides of the fence at each other,
234
00:19:57.130 --> 00:20:06.904
for some reason. But I I I think most of the the cooler heads out there either either stayed away and and just sort of watched with their popcorn and how silly everybody was being,
235
00:20:08.030 --> 00:20:09.870
or, you know, tried to,
236
00:20:10.350 --> 00:20:16.370
try to add their their 2¢ and make the conversation a little little more productive as I think some folks did.
237
00:20:16.905 --> 00:20:20.525
But, you know, that's that's social media, I guess, for you. And,
238
00:20:21.145 --> 00:20:23.405
for better or worse, Mike, for better or worse.
239
00:20:23.880 --> 00:20:30.300
Exactly. I think there was a lot of better, but that was one case of it it being worse. And, yeah, you know, I love
240
00:20:30.680 --> 00:20:34.605
the approach that that Kelly took to this blog post and I couldn't
241
00:20:34.985 --> 00:20:35.645
agree more.
242
00:20:36.825 --> 00:20:46.370
To me, not to draw too much of a parallel to, like, like, politics, but you don't always have to be in necessarily one camp or the other and just, you know, blindly believe
243
00:20:46.750 --> 00:20:51.725
and and associate with one side or
the other. From a project to to project basis,
244
00:20:52.585 --> 00:21:00.909
data dot table may make more sense for your project in one project and then the next one that you go to tidyverse may make a whole lot more sense to use and that is
245
00:21:01.210 --> 00:21:01.710
okay.
246
00:21:02.490 --> 00:21:05.685
Everyone listen. That is totally okay.
247
00:21:06.545 --> 00:21:07.845
You know, now DuckDV
248
00:21:08.225 --> 00:21:13.205
maybe, you know, the better solution than either one of those for your next project. Who knows?
249
00:21:13.905 --> 00:21:18.790
Like the thing that we love and that Kelly loves about the ecosystem is that we have choices
250
00:21:19.410 --> 00:21:20.550
and and that's incredible.
251
00:21:20.930 --> 00:21:24.434
And you should use whatever choice you feel makes the most sense to you,
252
00:21:24.975 --> 00:21:28.995
at the time and for the particular project that you're working on. So,
253
00:21:29.375 --> 00:21:31.875
in my opinion, you know, this is a great reflection.
254
00:21:32.870 --> 00:21:51.570
Very happy to hear that, there's been some grant funding towards the data dot table project that's going to allow that open source project to progress. That's something that we don't see a lot of the time where open source developers and community actually get get funding for their work and and for all the hard work that has gone into this project because,
255
00:21:52.030 --> 00:21:57.085
you know, if you take a look at the history of data dot table and what we're going on going on 15
256
00:21:58.105 --> 00:22:03.885
year or yeah. Something like that. Right? Going on 15, 16 years of the data dot table project.
257
00:22:05.139 --> 00:22:10.679
There's been an incredible amount of work that has has gone into it and helped it evolve and get to the place it is
258
00:22:10.980 --> 00:22:16.355
now. So it's it's fantastic to see a piece of software have that type of longevity
259
00:22:16.655 --> 00:22:19.635
and, you know, it it looks like that's only going to continue.
260
00:22:20.669 --> 00:22:21.169
Absolutely.
261
00:22:21.630 --> 00:22:31.015
And, Kelly, we'll be talking a lot about this topic more in-depth at both the USAR conference coming up in July as well as PASIT conference. So I have a talk about
262
00:22:31.315 --> 00:22:32.695
these themes. And
263
00:22:33.075 --> 00:22:38.410
what's interesting here is, as you mentioned, there is funding for this recent effort
264
00:22:39.270 --> 00:22:41.530
and, well, through, you know, a a coincidental,
265
00:22:42.310 --> 00:22:45.850
situation. I was able to hear more from Kelly herself in a recent
266
00:22:46.365 --> 00:22:50.705
meeting, but this funding is coming from a National Science Foundation
267
00:22:51.085 --> 00:22:51.585
grant,
268
00:22:52.525 --> 00:22:56.290
that was carried out, I believe, ill, back in 2023.
269
00:22:56.670 --> 00:23:03.170
In fact, we may have covered parts of this in our weekly highlights way back when the launch of what they call the data dot table
270
00:23:03.865 --> 00:23:05.005
Ecosystem Project.
271
00:23:05.465 --> 00:23:14.659
And this is being headed by Toby Hocking as well as Kelly's involved with this as well. We'll have a link to this in the supplements of the show notes here.
272
00:23:15.120 --> 00:23:23.315
But this is meant to not just look at data dot table from literally just the source code perspective, but to help fund
273
00:23:23.775 --> 00:23:24.755
the ecosystem
274
00:23:25.055 --> 00:23:28.035
around it, which is both technical and
275
00:23:28.500 --> 00:23:29.000
infrastructure
276
00:23:29.539 --> 00:23:31.559
and social and making sure
277
00:23:31.940 --> 00:23:33.320
that it is sustainable
278
00:23:34.179 --> 00:23:35.480
for the long term.
279
00:23:35.935 --> 00:23:39.555
Certainly, Kelly is gonna be speaking about these themes in her upcoming talks,
280
00:23:40.095 --> 00:23:46.660
but there is one huge difference. And when you look at the history of data dot table as opposed to the history of tidyverse,
281
00:23:46.960 --> 00:23:47.460
is
282
00:23:47.920 --> 00:23:49.300
that let's be real here.
283
00:23:49.760 --> 00:23:53.540
Who's funding the tidyverse? It is a dedicated vendor,
284
00:23:53.895 --> 00:23:54.395
ieposit,
285
00:23:55.255 --> 00:23:59.835
helping to pay engineers full time, open source engineers to work on this.
286
00:24:00.295 --> 00:24:02.790
Data. Table does not have that. It is enthusiastic
287
00:24:12.605 --> 00:24:18.544
But like many projects in open source, it is built on the community to help drive that innovation,
288
00:24:18.845 --> 00:24:20.304
drive that continued development.
289
00:24:20.870 --> 00:24:25.290
So I know part of the motivation of this grant is to help make sure that that ethos
290
00:24:25.830 --> 00:24:28.810
is sustainable for such an important piece
291
00:24:29.434 --> 00:24:33.615
of many, and I do mean many in the community that rely on data dot table
292
00:24:33.915 --> 00:24:39.100
for all sorts of uses. I mean, I just spoke of a couple of them, but I always scratch the surface.
293
00:24:39.480 --> 00:24:54.445
And I've had, like I said, great success with certain pieces of it in my workflows, and I don't feel ashamed about that. Like, Mike, you said, Mike, I wanna choose what's best for the job. And by golly, I'm not gonna have any regret because in the end, I gotta get my stuff done. Right?
294
00:24:54.990 --> 00:24:57.250
Exactly. Exactly. And it's like,
295
00:24:57.630 --> 00:25:03.495
I can't say enough. It's amazing that we have these choices. It's amazing that these choices are so robust and so powerful,
296
00:25:03.795 --> 00:25:05.575
and so well supported. So,
297
00:25:06.115 --> 00:25:21.914
you know, hats off to sort of a great perspective, I think, hereby Kelly. Fortunate enough to I believe have met Kelly at last posit conference. I think she was in our our shiny workshop which is really cool. That's right. So she she is
absolutely awesome and I'm very happy to see this blog post from her.
298
00:25:32.850 --> 00:25:40.765
Well, we're gonna go back to the development side, Mike, a little bit because our next post is gonna talk about ways that you can at least
299
00:25:41.065 --> 00:25:43.165
help future you even more
300
00:25:43.625 --> 00:25:47.430
even when you're already buying into proper version control.
301
00:25:48.130 --> 00:25:57.195
And what we're talking about here is a latest post from Al Salmon who, of course, has been a frequent contributor to our weekly both as a curator and now contributor
302
00:25:57.655 --> 00:25:59.995
to many great highlights in this podcast.
303
00:26:00.850 --> 00:26:01.510
And she
304
00:26:01.810 --> 00:26:05.030
speaks about why you should invest in
305
00:26:05.730 --> 00:26:07.430
not just doing version control,
306
00:26:07.934 --> 00:26:08.674
but helping
307
00:26:08.975 --> 00:26:12.835
future you by making what she calls small and informative
308
00:26:13.455 --> 00:26:14.274
get commits.
309
00:26:15.350 --> 00:26:15.850
Because
310
00:26:16.470 --> 00:26:18.649
I don't know about you, Mike, especially
311
00:26:19.029 --> 00:26:20.570
even now, sometimes
312
00:26:21.029 --> 00:26:27.295
when I'm in a tight bind and I realize, oh my goodness, I have about 10 files that
313
00:26:27.755 --> 00:26:30.975
I've gotta get committed now because the time's running out.
314
00:26:31.750 --> 00:26:34.090
I, I've I fall to temptation,
315
00:26:34.789 --> 00:26:35.929
hit all the checkboxes,
316
00:26:36.390 --> 00:26:41.289
hit stage, just say, get this a prod in my commit and be done with it.
317
00:26:41.654 --> 00:26:43.195
Yes. It still happens.
318
00:26:43.654 --> 00:26:49.640
Yes. I know better. And that's why this post is gonna help you figure out why what I did was such a big mistake.
319
00:26:50.600 --> 00:26:59.475
Because let's say you get to a point in time and you're either doing a code review, maybe a colleague's doing a code review for for example,
320
00:26:59.855 --> 00:27:01.794
and they see a line in your code.
321
00:27:02.174 --> 00:27:06.755
And they're thinking, well, Eric, why did you do that? Like, what was the motivation for that line?
322
00:27:07.510 --> 00:27:17.210
You don't have a comment around it because at the time, you're just trying to fix maybe fix an issue or something in your head, and then you didn't put it into prosperity and via commit or a comment.
323
00:27:18.115 --> 00:27:22.934
Well, of course, we get you can go back and look at the history of your commits. Right?
324
00:27:23.394 --> 00:27:25.735
And in fact, there is a concept
325
00:27:26.140 --> 00:27:30.880
in Git. They call it Git blame, but I I'm with my I'll hear. I hate that terminology.
326
00:27:31.660 --> 00:27:33.840
It's really not blaming anybody,
327
00:27:34.375 --> 00:27:41.835
but it's better to be called git explain. I like the way she phrases that because then in a platform such as GitHub,
328
00:27:42.360 --> 00:27:50.700
you could have the view of the code itself, I. E, the file, but then next to it, see which commit message related to that change.
329
00:27:51.385 --> 00:27:56.365
And you might see in that example that I gave that this mysterious line
330
00:27:56.745 --> 00:28:03.070
was part of like this massive 10 file commit and you just have something that says,
331
00:28:03.370 --> 00:28:08.190
get the prod or just get it done, get out of my hair or whatever you wanna call it.
332
00:28:08.730 --> 00:28:09.230
Well,
333
00:28:09.695 --> 00:28:13.154
that's not gonna help very much. But had you done small
334
00:28:13.695 --> 00:28:22.809
informative commit messages where you do, like, one file at a time or maybe a set of related changes even if they're spread across multiple files.
335
00:28:23.190 --> 00:28:37.980
That get blame methodology can be very helpful for you to go back in time and figure out what were you trying to fix. Were you trying to add a new feature? What was the motivation for that? A bit of like a a way to get a lens into your development journey
336
00:28:38.520 --> 00:28:39.740
of what happened there.
337
00:28:40.120 --> 00:28:48.905
So, again, if you do what I said was a bad thing to do and just put all these files in one big commit, you're not gonna get any real benefit out of that.
338
00:28:49.205 --> 00:28:51.385
But like I said, had you done a small
339
00:28:51.685 --> 00:28:52.905
informative message
340
00:28:53.390 --> 00:28:57.809
of that particular change, and again, it might be one file, it might be related files,
341
00:28:58.350 --> 00:29:01.890
it's gonna make it so much easier for both you and collaborators
342
00:29:02.655 --> 00:29:05.795
to figure out just what was your motivation for that.
343
00:29:06.175 --> 00:29:10.275
So that's one reason to do it. But there is another reason,
344
00:29:10.900 --> 00:29:12.520
especially if you realize
345
00:29:13.060 --> 00:29:18.040
that over time, maybe it's only like a month later, maybe it's a long time later,
346
00:29:19.105 --> 00:29:19.605
Something
347
00:29:20.145 --> 00:29:24.245
is not working, and you've got to figure out just where
348
00:29:24.945 --> 00:29:26.565
it started to not work.
349
00:29:27.150 --> 00:29:41.395
That's where Mike Sheehyah takes us onto another concept and get that I don't do enough of, but I can definitely say if you're behind on certain situations. Why don't you take us through that? Yeah. So my Elle talks about this tool that I admittedly
350
00:29:41.775 --> 00:29:46.434
do not use, this this function I guess you might call it that get offers us
351
00:29:46.780 --> 00:29:48.080
called git bisect.
352
00:29:49.020 --> 00:29:56.080
And what git bisect allows you to do is to try to identify the particular commit in history
353
00:29:56.815 --> 00:29:59.395
where your software was was working.
354
00:30:00.495 --> 00:30:05.315
And it it'll make you try some commits to help pinpoint, you know, which
commit exactly
355
00:30:05.730 --> 00:30:07.669
introduced the bug that you're now
356
00:30:07.970 --> 00:30:09.970
observing and it sort of breaks your code,
357
00:30:10.450 --> 00:30:12.309
into 2 sections sort of before,
358
00:30:12.929 --> 00:30:14.070
everything was working
359
00:30:14.455 --> 00:30:16.154
and then after sort of everything
360
00:30:16.534 --> 00:30:17.275
fell apart.
361
00:30:18.294 --> 00:30:26.240
And it will assume that all commits are up to that particular commit that you're bisecting on were good, and it's gonna make you sort of explore,
362
00:30:26.860 --> 00:30:28.879
commit by commit the the the following
363
00:30:29.340 --> 00:30:31.200
ones to to figure out exactly,
364
00:30:31.820 --> 00:30:34.425
what introduced the breaking change. And it's
365
00:30:34.725 --> 00:30:51.335
it's a really nice feature that sort of allows us to I don't know. It almost feels like the debugger in a way in in R where you're able to sort of go commit by commit very slowly and figure out exactly which one is the one that introduced that that breaking change. And and hopefully,
366
00:30:52.355 --> 00:30:54.135
if you made small commits,
367
00:30:54.914 --> 00:30:56.215
we're able to identify
368
00:30:56.755 --> 00:31:06.025
that git commit that that broke things as, you know, this small diff that that in Mel's example shows, you know, 2 changed files with 3 additions and 2 deletions.
369
00:31:07.145 --> 00:31:08.685
If we're very unlucky,
370
00:31:09.145 --> 00:31:22.080
it's going to have a message like one of those that Eric writes occasionally and I have never certainly ever ever written a commit like that that says, you know, commit a bunch of files and it's at, you know, 6 o'clock on a Friday
371
00:31:22.675 --> 00:31:27.015
and the the diff shows a 145 change files with 2,600
372
00:31:27.715 --> 00:31:29.895
editions and 22100 deletions.
373
00:31:30.850 --> 00:31:34.870
We we certainly hope that's not the case but but maybe it is. But GetBisect
374
00:31:35.170 --> 00:31:37.510
can help you get to that point.
375
00:31:38.050 --> 00:31:40.325
You know, one nice additional thing that we have,
376
00:31:41.684 --> 00:31:42.664
in our ecosystem
377
00:31:43.044 --> 00:31:43.544
now
378
00:31:43.924 --> 00:31:51.840
is is both unit testing and and services like GitHub Actions and and formerly Travis to when you do make a new commit,
379
00:31:52.620 --> 00:32:03.335
you can test, you know, you can execute your unit test to make sure that everything continues to work, after that new commit has been introduced and and this is certainly something that I I think everybody
380
00:32:03.794 --> 00:32:12.110
that uses Git can be guilty of is is not making small enough commits. I have sort of this long standing issue where
381
00:32:12.935 --> 00:32:16.635
I know that I need to make multiple changes to the same file,
382
00:32:17.735 --> 00:32:27.080
and I will make the first change and forget to just sort of commit that small change and I will make 3 different like conceptual changes within the same file.
383
00:32:27.539 --> 00:32:30.360
And now I either am at the mercy of,
384
00:32:30.900 --> 00:32:33.144
you know, trying to undo those
385
00:32:33.524 --> 00:32:34.024
particular,
386
00:32:34.404 --> 00:32:36.424
you know, changes number 23
387
00:32:37.125 --> 00:32:40.985
and just revert back to to change 1 and and make my commit message
388
00:32:41.290 --> 00:32:45.870
small and and related to that. Or try to write some 3 part commit message,
389
00:32:46.810 --> 00:33:00.940
that, you know, sort of tries to explain that the 3 different changes that took place but it's it's not good in either way is is really ideal or easy. So the best thing that I could possibly do is to stop after I make that first change to the file,
390
00:33:01.640 --> 00:33:06.620
make my commit, and move on to the second change. But but sometimes, you know, when you're in the zone,
391
00:33:06.955 --> 00:33:15.295
it's hard. It's hard to stop and and lift your fingers up off the keyboard and and remember to do that instead of just knocking everything out at the same time. But
392
00:33:15.700 --> 00:33:23.720
Git blame is and it should be called Git explain. I agree as well. I think it's a fantastic tool when we do have to go back and,
393
00:33:24.100 --> 00:33:27.375
you know, try to figure out sort of sort of what went wrong,
394
00:33:27.835 --> 00:33:29.215
what is the the status
395
00:33:29.835 --> 00:33:36.610
of, our our software at the point in time that that things went wrong, what what does our repository look like, and how can we sort of pinpoint
396
00:33:37.550 --> 00:33:47.575
where things went wrong and and what led to that. I think GitLab is a fantastic tool. I admittedly don't use it enough, but I do know the people that do use it and rave about it,
397
00:33:47.875 --> 00:33:52.580
and find it very helpful to their workflows. So it's it's one that I think my Elle is,
398
00:33:53.280 --> 00:33:54.820
inspiring me to
399
00:33:55.360 --> 00:34:00.100
dive a little bit deeper into and to start using a little bit more. So I I certainly appreciate
400
00:34:00.615 --> 00:34:02.715
the overview here. I I appreciate,
401
00:34:03.335 --> 00:34:11.210
the introduction and to get bisect as well because I think that that is gonna be a new handy tool that I'll be able to use in these, you know, tricky,
402
00:34:11.830 --> 00:34:15.610
situations where where something breaks and it's not trivial to pinpoint
403
00:34:16.310 --> 00:34:17.450
where it took place.
404
00:34:18.685 --> 00:34:43.185
I really like your your relation earlier to the concept of a good bicep and debugging your code because it made me think of a debugging technique that Bicep kinda mirrors a little bit in that if you have a long r script, wherever it's a Shiny module or any any data processing thing, for example, and you know there's an error somewhere, maybe it's a function or whatnot, but you
just don't quite know where it is,
405
00:34:43.580 --> 00:34:46.480
A lot of times, what people will do is they will
406
00:34:47.100 --> 00:34:48.000
comment out
407
00:34:48.380 --> 00:34:58.355
or start putting the browser at, like, a halfway point, and then they'll see, oh, wait. Is the error happening before this or after this? And if it's happening after somewhere,
408
00:34:58.734 --> 00:35:07.760
then you know that the rest of the code above it is working. And you kinda go in this I don't know what the proper term is, but you kinda go half by half or a certain percentage.
409
00:35:08.305 --> 00:35:15.445
And that's where get by site kinda starts you off with is you're gonna find that known point, at least that your conjecture
410
00:35:15.745 --> 00:35:21.990
is, and then you tell it, okay. Oh, yeah. This one works. I'm going to go to the next part, the next part, the next part.
411
00:35:22.290 --> 00:35:29.585
But none of this none of this is going to help you if you don't follow the advice from the start on these
412
00:35:29.965 --> 00:35:30.945
fit for purpose,
413
00:35:31.325 --> 00:35:35.105
you know, you know, targeted commit messages. And, again,
414
00:35:35.420 --> 00:35:59.930
yeah, Mike, I you've you've always been a pro with this. Like, you you don't need any advice here. But little old me, I I did some shortcuts even this year that I'm not proud of. So myel gives me a reality check that, you know, sometimes I need from time to time because I'm not perfect. What can I say? But if you wanna practice some of this in the confines of r, Nael has made an r package, which I'm going to butcher the name once again,
415
00:36:00.310 --> 00:36:00.890
of superlipopet
416
00:36:01.750 --> 00:36:03.130
or something to that effect
417
00:36:03.565 --> 00:36:04.945
where you can practice
418
00:36:05.725 --> 00:36:06.545
get concepts
419
00:36:07.325 --> 00:36:08.145
in r,
420
00:36:08.845 --> 00:36:11.425
albeit with your get client at hand
421
00:36:11.940 --> 00:36:17.000
to practice things like BISEC. Practice things like, you know, commit messaging
422
00:36:17.300 --> 00:36:19.560
or restoring or branching
423
00:36:20.045 --> 00:36:23.025
and things like that. So if this is all novel
424
00:36:23.325 --> 00:36:27.825
concepts too and you're wondering what's an easy way to kind of practice this about
425
00:36:28.250 --> 00:36:33.390
risking the destruction of a production code base, I recommend her pack as superwhippulpit.
426
00:36:35.290 --> 00:36:38.435
That's the best I can do. But that's a that's a great package nonetheless.
427
00:36:38.975 --> 00:36:44.915
That's the best I could do as well. And that it's my first time taking a look at that package, and it's incredible. It's fantastic.
428
00:36:45.390 --> 00:36:53.175
Allows you to to practice all sorts of git commands including git bisect, which is is really really cool. I think that's really powerful because it's very difficult
429
00:36:53.475 --> 00:37:01.085
to practice Git in a in a sandbox, I guess, unless you're spinning up a brand new a brand new project, but then you don't really have any history to play with.
430
00:37:02.470 --> 00:37:04.890
So this is a great great reference here.
431
00:37:05.510 --> 00:37:15.955
Yeah. And there's one other tidbit that I've seen both her mention, although be a not so much mentioned specifically, but then I see others in the community that I follow follow this trend as well is that
432
00:37:16.255 --> 00:37:22.359
at the beginning of a commit, they'll have a short phrase, maybe a one word phrase that describes the intent
433
00:37:22.820 --> 00:37:24.280
of that particular commit.
434
00:37:24.580 --> 00:37:27.855
It may be fix or feature or
435
00:37:28.475 --> 00:37:30.415
chore or things like this.
436
00:37:30.715 --> 00:37:36.180
I'm trying to opt into that a bit more because that's a handy way if you're looking at your history of your commit messages
437
00:37:36.480 --> 00:37:38.180
to isolate very quickly
438
00:37:38.480 --> 00:37:40.099
to distinguish between
439
00:37:40.400 --> 00:37:44.260
a new feature type of commit versus a bug fix commit versus,
440
00:37:44.655 --> 00:37:47.555
oh, I gotta rerun that r oxygen documentation
441
00:37:47.855 --> 00:37:58.440
again, regenerate the man pages as like a chore kinda commit because it's a chore to do. I guess that's where that naming comes from, Mike. But, have you have you done any of that in your commit messages?
442
00:37:59.140 --> 00:38:04.665
I haven't. We have some folks on my team who are are just fantastic developers who I have noticed recently
443
00:38:05.125 --> 00:38:05.785
do that,
444
00:38:06.565 --> 00:38:10.585
very much so in in all of their commits and are very consistent about it and it's,
445
00:38:11.590 --> 00:38:14.090
sort of a practice that I'm still
446
00:38:14.470 --> 00:38:22.415
maybe getting used to reading and and trying to decide whether that is something that we should try to adopt globally across the team,
447
00:38:23.035 --> 00:38:24.975
or not. You know, I think the
448
00:38:25.355 --> 00:38:30.640
idea of of creating issues and branches that reference those specific issues
449
00:38:31.200 --> 00:38:36.099
and, you know, obviously, your commit messages are are on that particular branch sort of lets me know
450
00:38:36.400 --> 00:38:38.660
exactly what is being accomplished
451
00:38:38.960 --> 00:38:41.905
here with maybe up without perhaps needing,
452
00:38:42.685 --> 00:38:44.945
all the way down to sort of the commit message
453
00:38:45.565 --> 00:38:46.545
level of granularity,
454
00:38:47.485 --> 00:38:49.745
letting me know sort of what's being worked on.
455
00:38:50.650 --> 00:38:55.070
But I I think on some particular projects, especially, maybe where it's not as
456
00:38:56.010 --> 00:38:58.590
clear cut of an issue branching workflow
457
00:38:59.055 --> 00:39:04.275
and maybe we're we're making commits to a particular branch that are across a
wide variety
458
00:39:04.575 --> 00:39:11.870
of, of types and use cases, you know, both development work, bug fixes, chores, things like that. I think that that might be
459
00:39:12.170 --> 00:39:14.090
possibly a great idea. So,
460
00:39:14.410 --> 00:39:21.654
it is something that I have have seen. I'm just not sure if I am all in on it yet, but I don't see any drawbacks to it.
461
00:39:22.194 --> 00:39:30.530
Yeah. I've I've been seeing it enough where it's like I'm gonna start paying attention to it. And maybe for my next project, I'll give it a shot. But like anything I get,
462
00:39:30.830 --> 00:39:32.930
it's not just the the the mechanisms
463
00:39:33.870 --> 00:39:39.065
of doing it. It's the discipline to keep doing it. And, again, if nothing else to take away from this,
464
00:39:39.365 --> 00:39:42.345
be kind to future you, be kind to future collaborators,
465
00:39:43.040 --> 00:39:45.380
Small fit for purpose commit messages
466
00:39:46.000 --> 00:39:58.875
will help you. Even if it takes a while to get used to, you'll thank yourself later. And, yeah, that goes with testing as well. Don't ask me why I think testing is a good thing because I've I've been bit by that too. I'll be a nut with hardware failures.
467
00:40:00.740 --> 00:40:05.560
When AI does finally get good enough, I will try to create a
468
00:40:06.100 --> 00:40:07.320
Mael hologramrubber
469
00:40:07.860 --> 00:40:18.359
duck on my desk that can just yell at me when I'm I'm doing the the wrong software development practice because I need this advice constantly and I'm very grateful
470
00:40:18.660 --> 00:40:23.960
to all these blog posts that she puts together to to remind me to, stay the course and
471
00:40:24.405 --> 00:40:25.225
continue to
472
00:40:25.925 --> 00:40:27.145
incorporate those best practices.
473
00:40:27.925 --> 00:40:32.579
Unlike some other things in AI, that is one that I would welcome to have next to me monitoring
474
00:40:33.440 --> 00:40:35.619
me through many points in my dev journey.
475
00:40:36.400 --> 00:40:37.220
Me too.
476
00:40:52.599 --> 00:40:54.619
I'm rounding out our highlights today,
477
00:40:55.400 --> 00:40:58.140
at the risk of dating myself with a reference
478
00:40:59.255 --> 00:41:04.555
here. I feel the need for something, Mike. You know what I feel the need of? The need for speed
479
00:41:05.470 --> 00:41:10.770
because it doesn't just apply to one aspect of data processing. It also applies
480
00:41:11.310 --> 00:41:12.690
to the way we consume
481
00:41:13.505 --> 00:41:15.845
data coming from these robust APIs
482
00:41:16.464 --> 00:41:18.244
and combining that with the
483
00:41:18.704 --> 00:41:20.244
very vast evolving
484
00:41:20.545 --> 00:41:21.045
ecosystem
485
00:41:21.940 --> 00:41:22.840
of geospatial
486
00:41:23.140 --> 00:41:24.280
data and performance.
487
00:41:24.740 --> 00:41:41.910
Our next highlight has the intersection of all these and definitely made me do a few double takes in
terms of the metrics that we're about to talk about here. In particular, we're talking about this post that comes from Josiah Perry who has been a long time member of the r community, and his tagline lately
488
00:41:42.290 --> 00:41:43.110
is helping
489
00:41:43.410 --> 00:41:46.230
r be built and used better in production.
490
00:41:46.930 --> 00:41:51.905
And his blog post here is his journey on making what he calls a ridiculously
491
00:41:52.445 --> 00:41:54.945
fast API client in r.
492
00:41:55.645 --> 00:42:04.039
And his day job is working for a company called called Esris, who is specializing in putting on these certain services
493
00:42:04.500 --> 00:42:05.880
to query geospatial
494
00:42:06.180 --> 00:42:11.305
data from many different development frameworks. I believe they have some host of services as
495
00:42:11.605 --> 00:42:15.065
well. Well, as I'm guessing as part of his daytime responsibilities,
496
00:42:16.085 --> 00:42:18.345
Josiah has released a new r package
497
00:42:18.890 --> 00:42:19.630
called arc
498
00:42:19.930 --> 00:42:20.830
just geocode,
499
00:42:21.210 --> 00:42:26.110
all one word, the big name here, which is an r binding and our interface
500
00:42:26.545 --> 00:42:30.165
to what they call the ArcGIS world decoder service.
501
00:42:30.625 --> 00:42:33.045
And he says that this looks like an official
502
00:42:33.700 --> 00:42:35.319
package from his organization,
503
00:42:35.619 --> 00:42:36.119
Esri,
504
00:42:36.579 --> 00:42:37.480
in this space.
505
00:42:38.099 --> 00:42:47.855
And in his knowledge, up to this point, he's got some metrics to prove it. He claims that this is the fastest geocoding library available in the entire
506
00:42:48.555 --> 00:42:49.454
our ecosystem.
507
00:42:50.359 --> 00:42:50.940
In fact,
508
00:42:51.240 --> 00:42:53.820
he's claims that our just geocode
509
00:42:54.520 --> 00:42:56.975
is about 17 times faster
510
00:42:57.615 --> 00:43:00.755
when you do what's called a single address geocoding
511
00:43:01.535 --> 00:43:03.795
and almost 40 times faster
512
00:43:04.240 --> 00:43:06.100
when doing a reverse geocoding
513
00:43:06.400 --> 00:43:08.660
lookup as compared to other packages
514
00:43:09.120 --> 00:43:11.540
in the community already in this space.
515
00:43:11.955 --> 00:43:13.975
So let's dive into this a bit more.
516
00:43:14.675 --> 00:43:17.655
His first reason for why this is important
517
00:43:18.195 --> 00:43:25.700
is that some I took for granted until a recent project, I talked about the onset with some of this podcast metadata JSON data
518
00:43:26.225 --> 00:43:28.085
is that parsing JSON data
519
00:43:28.625 --> 00:43:31.445
is not always fast, my friend. Not always.
520
00:43:31.985 --> 00:43:39.730
Many of us are using JSON Lite, the, you know, almost tried and true package offered by your own ooms for,
521
00:43:40.590 --> 00:43:43.970
consuming and writing JSON data in r.
522
00:43:45.055 --> 00:43:48.914
And it's it's it's been
a huge help to me. Don't get me wrong.
523
00:43:49.535 --> 00:43:59.830
But it does have some performance issues, especially when dealing with long text strings in your JSON data and then bringing that conversion back to an r object
524
00:44:00.130 --> 00:44:01.430
and the other way around.
525
00:44:02.445 --> 00:44:08.145
Well, guess what? Another language that starts of r comes at a rescue in in Josiah's initiative
526
00:44:08.765 --> 00:44:12.710
because there is a rust crate, that's kind of their term for packages,
527
00:44:13.330 --> 00:44:18.710
called SERDAY or SERD, I'm not sure if I'm saying it right, that handles both the serialization
528
00:44:19.275 --> 00:44:20.015
and deserialization
529
00:44:21.595 --> 00:44:23.694
of structures and rust.
530
00:44:23.994 --> 00:44:29.960
And guess what? It is very tailor made to JSON data too. It just expects you
531
00:44:30.260 --> 00:44:31.160
at the onset
532
00:44:31.619 --> 00:44:32.680
to help specify
533
00:44:32.980 --> 00:44:37.444
for your given JSON type data you want inside your your session,
534
00:44:37.984 --> 00:44:38.724
the specific
535
00:44:39.025 --> 00:44:41.605
attributes of each variable or each field.
536
00:44:42.065 --> 00:44:49.869
So in his example, he's got an address structure, if you call it, with all the different fields that would come out of this JSON data.
537
00:44:50.170 --> 00:44:52.349
And most of them, big surprise, are strings,
538
00:44:53.369 --> 00:44:59.214
but it'll give you the ability and rust to really determine what's supposed to be a string, what's supposed to be an integer,
539
00:44:59.515 --> 00:45:04.670
different types of integers. You can go, you know, really specific on all these needs.
540
00:45:05.210 --> 00:45:07.870
Now that's great and all, but how does that help with r?
541
00:45:08.250 --> 00:45:10.750
Well, there is the package called extender,
542
00:45:11.195 --> 00:45:15.135
which is kinda like the RCPP, if you will, of Rust to r.
543
00:45:15.435 --> 00:45:18.175
We'll let you tap into a Rust crate
544
00:45:18.730 --> 00:45:27.869
and bring that into r and be able to go back and forth with our functions to basically call out to these lower level Rust parts of the paradigm.
545
00:45:28.855 --> 00:45:29.734
So this,
546
00:45:30.694 --> 00:45:32.474
Serde JSON crate
547
00:45:33.015 --> 00:45:39.440
is a massive speed improvement in general for importing JSON data, serializing JSON data
548
00:45:39.900 --> 00:45:44.240
over the community counterparts as he attests to in this post.
549
00:45:44.645 --> 00:45:46.985
But that's not the only part. The other part
550
00:45:47.365 --> 00:45:54.700
is a feature that I should have known about in my research in HDR 2, but it just went over my head until this post,
551
00:45:55.320 --> 00:45:56.060
is that
552
00:45:56.600 --> 00:46:02.700
we often use HDR, HDR 2, and this is the regeneration of that, if you will, by Hadley Wickham
553
00:46:03.015 --> 00:46:04.234
to help in r
554
00:46:04.615 --> 00:46:07.194
perform these, you know, requests to API
555
00:46:07.654 --> 00:46:10.395
services. I get request, post request, and whatnot.
556
00:46:11.230 --> 00:46:18.850
And, usually, I do these requests kind of 1 at a time, if you will. Like, there's a get request. I'm gonna do that with specific set of config parameters,
557
00:46:19.195 --> 00:46:20.815
bring it back down and whatnot.
558
00:46:21.355 --> 00:46:25.375
Well, how in the world did I not know about this function, Mike?
559
00:46:25.675 --> 00:46:26.735
Rec perform
560
00:46:27.675 --> 00:46:28.175
parallel,
561
00:46:29.200 --> 00:46:42.545
which lets you do it in more than one time. Oh my gosh. Where have I been, Mike? Did you know about this? Neither did I, Eric. I had no idea that this was part of the h t t r two package now, that we have the ability
562
00:46:43.085 --> 00:46:44.465
to send, I guess, paralyzed
563
00:46:45.650 --> 00:46:50.150
request to an API pretty easily and maybe point that function towards
564
00:46:51.010 --> 00:46:54.069
a connection pool or a few different nodes, few different workers,
565
00:46:54.675 --> 00:47:01.095
to be handling requests concurrently. This makes me think of, I don't know, potential integration with the crew package or something like that.
566
00:47:01.830 --> 00:47:05.430
Perhaps this is something that you could do on your your own machine and and leverage,
567
00:47:06.070 --> 00:47:09.290
you know, the the ability to parallelize your own machine
568
00:47:09.590 --> 00:47:14.244
and and send out a few different requests, at the same time which is is pretty incredible.
569
00:47:14.625 --> 00:47:15.125
And
570
00:47:15.425 --> 00:47:24.270
there's this Twitter thread that Josiah puts, earlier on in the blog post where he's, you know, he's he's showing off the fact that he was able to geocode,
571
00:47:25.050 --> 00:47:25.550
2.6
572
00:47:25.850 --> 00:47:31.375
1,000 addresses in in 3 and a half seconds. And and somebody asked, in as a reply
573
00:47:31.994 --> 00:47:37.420
to that particular screenshot that he put up, they said, isn't geocoding always bottlenecks by the server?
574
00:47:37.880 --> 00:47:48.775
And, that is true. But I guess when you have multiple servers to span the job across and we have this beautiful function request perform parallel that I imagine brings it all back together
575
00:47:49.234 --> 00:47:49.974
at the end.
576
00:47:50.675 --> 00:47:55.940
That's that's a fantastic utility to be able to, you know, speed up,
577
00:47:56.420 --> 00:48:00.200
significantly and and this is something that I've dealt with in the past as well, geocoding.
578
00:48:01.060 --> 00:48:13.780
It takes time because you're typically going address by address and, you know, a lot of projects you'll you'll want to be geocoding your entire data frame which could get, you know, could get particularly long you know thousands tens of thousands
579
00:48:14.080 --> 00:48:15.700
hundreds of thousands of
observations
580
00:48:16.160 --> 00:48:17.300
that you need to geocode
581
00:48:17.840 --> 00:48:18.535
so it's
582
00:48:19.015 --> 00:48:24.395
really interesting to me that we have the ability, you know, not only to leverage the speed of Rust,
583
00:48:24.775 --> 00:48:26.155
for this serializing
584
00:48:26.650 --> 00:48:27.310
and deserializing
585
00:48:27.690 --> 00:48:31.070
of JSON objects which is time intensive, but also,
586
00:48:31.370 --> 00:48:34.970
being able to just break the job out into across a few different,
587
00:48:35.370 --> 00:48:36.255
nodes here which is
588
00:48:36.815 --> 00:48:48.010
is pretty incredible, something that I didn't know about. Obviously, Josiah says that you need to be a little bit careful when you are doing anything like this especially when you're sending sort of paralyzed paralyzed
589
00:48:48.310 --> 00:48:48.810
requests
590
00:48:49.270 --> 00:48:51.975
at a different service that you don't perform,
591
00:48:52.355 --> 00:48:53.175
an accidental
592
00:48:53.635 --> 00:48:59.760
denial of service attack, you know, which is where you you make way too many requests all at once
593
00:49:00.240 --> 00:49:01.060
to the service
594
00:49:01.760 --> 00:49:07.300
and bring that down. So you don't wanna be the person that does that. So so certainly be be careful
595
00:49:07.665 --> 00:49:11.045
and perhaps, you know, use a small number of workers.
596
00:49:11.744 --> 00:49:15.605
If you're just geocoding a couple thousand addresses, you don't need to spin up
597
00:49:16.065 --> 00:49:20.950
a few hundred workers or something like that to be able to do that just just
598
00:49:21.410 --> 00:49:22.950
spin up a couple and
599
00:49:23.330 --> 00:49:30.545
and maybe wait those extra few seconds that it's going to take, to be patient between, you know, spinning up a few workers and
600
00:49:30.845 --> 00:49:38.770
and many many workers. But it's really interesting because you will get, you know, these this great sort of orders of magnitude returns in performance,
601
00:49:39.470 --> 00:49:40.369
when you do
602
00:49:40.830 --> 00:49:46.485
add compute to the problem here as well as, you know, leveraging Rust for that that quick deserialization,
603
00:49:48.305 --> 00:49:54.405
of of JSON data. One thing that I will also shout out just because I was curious about this and, you know, we're
604
00:49:54.720 --> 00:49:55.700
finding all of
605
00:49:56.320 --> 00:49:57.540
these new, faster
606
00:49:57.840 --> 00:49:58.340
programming,
607
00:49:59.200 --> 00:50:02.420
software utilities out there when it comes to to data.
608
00:50:02.925 --> 00:50:06.785
And there is a DuckDb extension as well for handling
609
00:50:07.085 --> 00:50:10.220
JSON data and reading JSON data and so I would be interested
610
00:50:12.220 --> 00:50:15.440
to see how that compares to what Rust can do for parsing JSON data as well.
611
00:50:15.740 --> 00:50:29.860
But both very fast, I'm sure. Yeah. They are. I'm experimenting that a little bit too actually in my DuckDV adventures and I'll definitely come back with my findings as I get that more polish. I'll be at the hardware catastrophe, put a stop on that for a bit. But,
612
00:50:30.160 --> 00:50:30.660
nonetheless,
613
00:50:31.200 --> 00:50:34.020
I'm really intrigued by the concepts that,
614
00:50:34.565 --> 00:50:35.065
Josiah,
615
00:50:35.605 --> 00:50:38.505
parts in this post here. And then at the end, he recommends
616
00:50:39.045 --> 00:50:48.110
additional packages in the community that if you're still not quite ready for the plunge to Rust for some of these efforts, if you're not ready to build, like, an internal
617
00:50:48.410 --> 00:50:55.535
JSON parser that depends on Rust, There are some additional JSON related packages in the r community that definitely
618
00:50:55.994 --> 00:50:57.855
take a look at. He recommends
619
00:50:58.369 --> 00:50:59.109
the RCPP
620
00:50:59.569 --> 00:51:03.430
SIMD JSON package as a great way for parsing data
621
00:51:04.049 --> 00:51:14.765
as well as the y y JSON package that comes from the affectionately known cool but useless on the our community. He's got a great package called y y JSON
622
00:51:15.120 --> 00:51:16.100
and also JSONify,
623
00:51:16.560 --> 00:51:23.620
which I don't have as much experience with. But you might wanna take a look at each of those too and see it for your parsing needs or writing
624
00:51:23.984 --> 00:51:26.724
serialization needs. If that just gets you good enough
625
00:51:27.025 --> 00:51:30.964
without while being able to stay in the confines of of R directly.
626
00:51:31.345 --> 00:51:32.165
But, nonetheless,
627
00:51:32.829 --> 00:51:40.690
this is great learning for me personally as I'm starting to deal with JSON data more and more in my open source work as well as my internal
628
00:51:41.295 --> 00:51:44.515
day job stuff where we just built an API
629
00:51:45.055 --> 00:51:46.115
binding package.
630
00:51:46.735 --> 00:51:53.450
But we're running this in the day to day use with, patient level data set where there's, like, multiple visits,
631
00:51:53.910 --> 00:52:00.135
multiple, obviously, patients in a treatment group, and it's basically doing these get requests to this custom service
632
00:52:00.515 --> 00:52:01.575
1 at a time
633
00:52:01.875 --> 00:52:13.370
for each of these calls. My goodness. I could do the rec perform parallel and probably speed that up a bit. So I'm gonna have to take a look at this and hopefully not make my IT admins angry when I start to paralyze this.
634
00:52:14.325 --> 00:52:18.105
Definitely do it on a, development cluster to start. That would be my recommendation.
635
00:52:18.805 --> 00:52:19.785
Yes. Because,
636
00:52:20.405 --> 00:52:32.380
yeah. That that was another, story time from years ago when when I, was too greedy with multi cores, and I took down an entire HPC cluster. Don't be that person, everybody. Just don't be that person. I remember that
story.
637
00:52:32.885 --> 00:52:34.885
Yes. Who lives in infamy. But,
638
00:52:35.445 --> 00:52:39.225
what lives in good ways, of course, is the rest of the our weekly issue itself.
639
00:52:39.605 --> 00:52:50.490
Tony's done a terrific job as always he does with the rest of the issue. We got so much we could talk about, but we're gonna have to wrap up here with our additional fines over this issue.
640
00:52:51.225 --> 00:52:58.125
And, Mike knows and many of you know I am a retro gamer at heart, not just with retro games, but also
641
00:52:58.470 --> 00:53:04.170
I have fond memories of going to the local arcade and putting some quarters on those awesome pinball machines
642
00:53:04.549 --> 00:53:09.305
that waste a lot of hours on that. Well, there is a fun post that combines
643
00:53:09.845 --> 00:53:14.985
things like, geospatial data, API calls, and some handy visualizations
644
00:53:16.080 --> 00:53:21.460
from Rasmus Bath. He calls this the public pinball machines per capita
645
00:53:22.000 --> 00:53:26.595
looking at where pinball machines are most distributed around the world.
646
00:53:27.055 --> 00:53:33.400
And and as post surprise, surprise, the United States is in the lead with this, but Europe is not far behind
647
00:53:33.700 --> 00:53:35.000
in some of their visualizations.
648
00:53:35.619 --> 00:53:39.319
But his post goes into how he attained this data,
649
00:53:39.755 --> 00:53:42.735
loading the packages. And guess what? It's coming from an API
650
00:53:43.035 --> 00:53:44.335
just like everything else.
651
00:53:44.875 --> 00:53:47.775
He's got some, you know, really elegant code to do this.
652
00:53:48.799 --> 00:53:52.819
Really modern code here. They was using HTR 2 as well
653
00:53:53.280 --> 00:53:55.299
and some great handy visualizations
654
00:53:55.680 --> 00:53:57.605
built in ggplot for the distribution
655
00:53:58.305 --> 00:54:00.245
of these, pinball locations
656
00:54:00.625 --> 00:54:04.785
and some word clouds too. So really, really fun stuff here. And,
657
00:54:05.420 --> 00:54:09.600
yeah, it makes me get the itch to get some quarters out and find that retro arcade
658
00:54:09.900 --> 00:54:20.744
to, you know, knock out some pinball action. So that was fun. But, Mike, what did you find? Very cool, Eric. I found an oldie but a goodie. I think at the the recent,
659
00:54:21.444 --> 00:54:24.890
our conference that's held in New York by that under Lander Analytics
660
00:54:25.270 --> 00:54:25.770
hosts,
661
00:54:26.070 --> 00:54:29.050
there was a panel discussion about your favorite R package.
662
00:54:29.670 --> 00:54:31.270
And I believe it was,
663
00:54:31.670 --> 00:54:32.650
who's the author
664
00:54:33.045 --> 00:54:35.704
of the data science Venn diagram there? Drew
665
00:54:36.165 --> 00:54:36.665
Conway.
666
00:54:37.525 --> 00:54:46.570
He was being asked what his favorite R package was and and I think it was one, it was called iGraph and I think it's one that's been around for a long long time,
667
00:54:46.950 --> 00:54:50.090
for doing, I believe, network analysis type stuff
668
00:54:50.390 --> 00:54:50.870
in,
669
00:54:51.270 --> 00:54:51.770
r.
670
00:54:52.295 --> 00:54:56.954
And I saw on the highlights this week that r igraph has crossed the 2.0
671
00:54:57.335 --> 00:54:57.835
threshold.
672
00:54:58.214 --> 00:55:07.040
So it's it sounds like, you know, similar to data dot table that this is another package that has had quite a life to it, continues to be very very well
673
00:55:07.340 --> 00:55:12.694
maintained, and it's it's just awesome to see a package like that be able to have the longevity it has.
674
00:55:13.315 --> 00:55:21.100
Yeah. IGraff, I have tremendous respect for. It is the engine behind many, and I do mean many, of the r packages
675
00:55:21.560 --> 00:55:23.980
that provide some kind of network visualization
676
00:55:24.360 --> 00:55:25.100
or processing.
677
00:55:25.965 --> 00:55:28.625
My exposure to this has been using some custom
678
00:55:29.165 --> 00:55:41.730
eye graph bindings inside a widget called Viz Network, which I have a kind of a love hate relationship with, but I've done enough customization to wrangle it to my particular needs. But, yeah, iGRAS been
679
00:55:42.115 --> 00:55:50.535
around a long time, and it is prevalent in additional languages as well. But, yeah, huge congrats to that team for the 2 point o release.
680
00:55:50.870 --> 00:55:57.610
And I know, yeah, my whole biograph stays around for a long time because it is a fundamental pillar
681
00:55:57.994 --> 00:56:00.974
in these, network visualizations. So awesome
682
00:56:01.435 --> 00:56:05.535
awesome call out there. I grabbed 0.1 released in 2006.
683
00:56:06.250 --> 00:56:07.869
Even older than the data that table.
684
00:56:08.170 --> 00:56:20.325
My goodness. Yeah. As if I didn't feel old enough in this post. Good grief. What are you what are you doing to me, man? I I I need to get a youth injection or something. But what makes me feel youthful is just seeing what's happening
685
00:56:20.625 --> 00:56:24.910
in this community. Again, really great developments happening. Really great showcases
686
00:56:25.530 --> 00:56:32.664
of data science, you know, providing good to everybody involved. So where can you see this all? Where we've been talking about here,
687
00:56:32.964 --> 00:56:35.704
so many of our great wings are available at rw.org.
688
00:56:37.119 --> 00:56:37.940
Many additional
689
00:56:38.240 --> 00:56:39.940
findings here, many additional
690
00:56:40.400 --> 00:56:41.619
developments of packages.
691
00:56:42.080 --> 00:56:46.035
We need to touch on all the newer packages out there. There's so much happening
692
00:56:46.575 --> 00:56:47.555
in these spaces,
693
00:56:48.095 --> 00:56:53.780
but we invite you to bookmark that site if you haven't already to check it out on a weekly basis. And
694
00:56:54.240 --> 00:56:58.420
also, we love hearing from you in the community. There are many ways to get in touch with us.
695
00:56:58.720 --> 00:57:08.265
You can send us a contact or message on our contact page, which is in the episode show notes. So, again, keep those comments coming. We love to hear from you.
696
00:57:08.645 --> 00:57:19.190
You can also, in the modern podcast app, such as PowVerse, Fountain, Cast O Matic, Curio Castor, there's a whole bunch out there. You can send us a fun little boost along the way if you want to send us a message
697
00:57:19.565 --> 00:57:24.224
without any middle thing in between. And no harbor failures on that one either.
698
00:57:25.005 --> 00:57:34.770
But and the other way you can contact us is on social media as well. I am mostly on Mastodon these days with at our podcast and podcast index on social.
699
00:57:35.230 --> 00:57:42.385
I am also on LinkedIn. Just search for my name there. You'll find me there and sporadically on the weapon x thing with FDR cast
700
00:57:42.685 --> 00:57:50.310
and a special little shot. I didn't get to it in my stories time. But I had the great pleasure of having a, little dinner with,
701
00:57:50.870 --> 00:58:17.255
the author of GT, Rich Yone, who was in town for a local conference. So great fun talking with him, all things are, and someone he's up to. So, Rich, if you're listening, thanks for coming into town even for a brief couple of days. A lot of fun learning from you. But, Mike, we're gonna listen to get a hold of you. That is awesome. I am so excited for POSIT conferences here to be able to see some see some community faces. But, folks, until then, can get a hold of me on mastodon@mike_thomasat
702
00:58:19.670 --> 00:58:20.170
fostodon.org
703
00:58:21.190 --> 00:58:24.010
or on LinkedIn if you search Ketchbrook Analytics,
704
00:58:24.310 --> 00:58:24.810
ketchb
705
00:58:25.750 --> 00:58:27.505
r o o k, you can see what I'm up
706
00:58:28.384 --> 00:58:32.484
to. Yes. And, hopefully, I don't see any messages about any failures in your infrastructure.
707
00:58:32.865 --> 00:59:03.805
Let's call it that. Let's keep keep our fingers crossed. But, yeah, just don't do what I did. That's the best advice for today. But in any event, we thank you so much for joining us wherever you are and wherever you are in your our journey. We hope that we're a little bit of a help along the way. And one of the best ways also to help us out is just share the word. You know? If you got value out of this podcast, we'd love for you to share it around, tell your friends, and always great to expand our audience for those that are getting started with our we think our weekly is one of the best resources
708
00:59:04.265 --> 00:59:17.119
for anybody in this community. Am I biased? Absolutely. Yes. But, hey, I speak I speak the truth here, I think, in any event. We're gonna close-up shop here, and we'll be back with another edition of our weekly highlights
709
00:59:17.792 --> 00:59:18.292
next
710
00:59:20.032 --> 00:59:20.157
week.