প্রতিলিপি 🔗
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 7/6/2024 5:00:00 PM
Duration: 4051.307
Channels: 1
1
00:00:13.985 --> 00:00:16.645
Hello, and welcome to another episode of podcast.init.
2
00:00:17.590 --> 00:00:18.410
We are recording today
3
00:00:18.870 --> 00:00:20.170
on April 21,
4
00:00:20.630 --> 00:00:21.130
2015.
5
00:00:22.390 --> 00:00:28.725
We have Tobias Macy and Chris Patti as your hosts. And today we're interviewing Reuben Lerner.
6
00:00:29.105 --> 00:00:31.205
So, Reuben, why don't you introduce yourself?
7
00:00:31.905 --> 00:00:40.570
Sure. So my name is Reuben. I've been a software developer now for, I guess, more than 20 years. Over the last few years, I've been doing,
8
00:00:40.950 --> 00:00:52.920
I would say, less and less project and development work and more and more training to such a degree that now I would say a good 90% of my work is doing training, and a huge proportion of that training
9
00:00:53.460 --> 00:00:54.600
is in Python.
10
00:00:55.060 --> 00:01:04.845
But, like, aside that, I grew up, as you can hear, in the US. I went to high school and college there. I lived in Israel though, halfway between Tel Aviv and Jerusalem and a city called Modim,
11
00:01:05.465 --> 00:01:06.605
since 99.
12
00:01:07.860 --> 00:01:08.920
That's very cool.
13
00:01:09.220 --> 00:01:15.880
Israel seems, from everything that I've heard, like a really neat place to live. It's such an interesting confluence of of cultures,
14
00:01:16.435 --> 00:01:20.615
and, obviously, it's in a really sort of interesting for better or for worse region.
15
00:01:20.995 --> 00:01:24.295
What brought you there? How did you end up deciding to move there?
16
00:01:25.810 --> 00:01:28.150
Sure. I'm I'm happy to talk about it. How long do we have?
17
00:01:28.770 --> 00:01:36.155
But, look, I I would I would say, to sort of put it in a nutshell, it's this way. I went to Jewish schools and Jewish camps, and the basic
18
00:01:36.695 --> 00:01:46.079
sort of history lesson that we got there was Jews that wanted to live in Israel over 2000 years, Wouldn't it be great if we could go back? And I sort of looked around and said,
19
00:01:46.560 --> 00:01:51.195
actually, guys, we can. We have a country again. You you might not have noticed. And
20
00:01:52.295 --> 00:01:59.595
and and the fact that, as someone in the high-tech world, I could make a decent living here just made it a a more compelling case.
21
00:01:59.900 --> 00:02:06.080
So I came here. My plan was basically to come to Israel as soon after college as possible. And about 2 and a half years after graduating,
22
00:02:06.460 --> 00:02:07.840
I paid off my loans.
23
00:02:08.334 --> 00:02:24.055
And through a lot of frugal living, I moved to Israel. And, I must say I've been very, very pleased here on all fronts. I mean, it's I'm not gonna claim that there are no problems in Israel, but I feel like, far from it. But I feel like these are the sort of the sorts of problems that I
Load full transcript
wanna wrestle with on a sort of personal
24
00:02:24.595 --> 00:02:25.095
national
25
00:02:25.635 --> 00:02:26.135
basis.
26
00:02:26.834 --> 00:02:27.235
And,
27
00:02:27.955 --> 00:02:31.495
we lived in Chicago for 4 years while I was doing my PhD coursework
28
00:02:31.875 --> 00:02:32.535
at Northwestern.
29
00:02:33.420 --> 00:02:33.920
And,
30
00:02:34.540 --> 00:02:44.935
much as I enjoyed Chicago I really enjoyed Chicago. Much under I I enjoyed living back in the US for a little while, That only cemented my my feelings that the US is a nice place. It's not here. But,
31
00:02:45.555 --> 00:02:48.295
but I actually am very comfortable with my decision to move to Israel.
32
00:02:49.110 --> 00:02:49.770
Very cool.
33
00:02:50.550 --> 00:02:51.050
So
34
00:02:51.510 --> 00:02:57.130
how did you get introduced to Python? What when did you first come across it, and what made you wanna stick with it?
35
00:02:58.865 --> 00:03:01.205
I'm not I know I've been thinking about this actually.
36
00:03:01.505 --> 00:03:07.125
I'm not a 100% sure when it was. So I'll I'll give you a little background. So I I went to MIT undergrad
37
00:03:07.470 --> 00:03:10.290
and, you have to do an undergraduate thesis when you're there.
38
00:03:10.590 --> 00:03:13.250
And I did something, this was just before the web started,
39
00:03:13.629 --> 00:03:19.135
my undergrad thesis was this new idea that you can have 1 program that spoke many different protocols.
40
00:03:19.834 --> 00:03:26.830
And it really barely kind of worked, but that's okay. It was an undergrad thesis. But in order to get that going, I went to a local bookstore,
41
00:03:27.210 --> 00:03:31.070
and I bought 2 books. 1 was on Sed and Auk, and the other was on Pearl.
42
00:03:31.555 --> 00:03:36.375
And so I was sort of really getting into Perl and I did all sorts of stuff with Perl. And
43
00:03:36.834 --> 00:03:42.840
I knew at that point, this was in the early nineties, there was a lot of rivalry between the pro world and the Python world.
44
00:03:43.220 --> 00:03:51.885
And it just sort of, out of necessity and out of interest, I started learning about Python as well. And I still sort of saw myself as more of a pearl guy
45
00:03:52.265 --> 00:03:53.405
and then sort of
46
00:03:53.705 --> 00:03:54.845
pearl committed suicide,
47
00:03:55.680 --> 00:04:02.099
and so I said, well, you know, Python is actually doing pretty great. Maybe I can do some stuff there. And so it's probably been a good,
48
00:04:02.864 --> 00:04:08.245
certainly more than 15 years. I I would say it's about 20 years at this point that I've been using Python on a regular basis.
49
00:04:08.545 --> 00:04:20.205
Sometimes more regular than others. So there was a period where I did tons of work in Python. There's a period of work where a period of time where I did tons of work in Ruby. I would say over the last, yeah, 5, 6 years that I've been getting more and more into doing training,
50
00:04:20.745 --> 00:04:23.565
the demand for Python training has been so extensive
51
00:04:24.185 --> 00:04:28.879
that many of the people who know me for doing Ruby are sort of surprised at how strong I am in Python.
52
00:04:29.180 --> 00:04:39.835
But I I see, actually, the community and the language and the the business opportunities, quite frankly, just growing and growing in Python, which is not as true for Ruby, I'd say, for now.
53
00:04:40.935 --> 00:04:46.690
Yeah. I I definitely agree, actually. I think I think that while Ruby is thriving in its niches
54
00:04:47.070 --> 00:04:49.970
in terms of Ruby on Rails and, and also
55
00:04:50.350 --> 00:04:57.905
in infrastructure as code with Chef, I think Python is is definitely gaining ground in terms of it's being used in so many
56
00:04:58.205 --> 00:04:59.825
more diverse contexts
57
00:05:00.330 --> 00:05:18.905
like in the sciences and, you know, and and obviously, there's there's web quite a bit of web programming being done with it, but also it's also doing infrastructure as code with Ansible and Salt. And, you know, it's being embedded into a 1, 000 different projects. And and and people are just recognizing that it's a really sort of good general purpose
58
00:05:19.550 --> 00:05:27.410
language that's easy to learn and and has a great deal of depth for you to grow into as you as you learn it more fully. So I I definitely agree.
59
00:05:27.935 --> 00:05:33.075
Absolutely. I'll I'll I'll say along those lines, by the way, that when I started doing training in Python, teaching classes,
60
00:05:33.455 --> 00:05:42.395
I was convinced that all of my students would be web people. So I was like, well that's what I do with it, right? So that's what everyone must be doing with it. And I could not have been further from the the truth.
61
00:05:42.715 --> 00:05:45.215
The overwhelming majority of people who are
62
00:05:45.595 --> 00:05:50.815
doing the were in my training are in, you know, automation, they're in testing,
63
00:05:51.210 --> 00:05:51.870
they're in
64
00:05:52.170 --> 00:05:53.310
big data analysis.
65
00:05:53.690 --> 00:06:00.190
All sorts of fields which, as you said now, are just growing and growing in the Python space, and are helping the language to really extend its
66
00:06:00.505 --> 00:06:08.525
tentacles, for lack of a better term, into all sorts of new areas that that I never would have imagined. And quite frankly, that I never really learned about before
67
00:06:08.930 --> 00:06:11.830
before, I was forced to teach it and deal with these people.
68
00:06:12.610 --> 00:06:23.035
Right. That's great. It and that kind of dovetails with our next question. How did you break into the field of providing Python trainings? How did you sort of get your start and make an make a name for yourself and and,
69
00:06:23.595 --> 00:06:25.450
have people beating down your door?
70
00:06:26.970 --> 00:06:31.550
Yeah. It's it's it's kind of wild. So I've been doing training so so basically,
71
00:06:32.090 --> 00:06:44.150
so I moved to Israel in 95, so it's 20 years ago. And I already had consulting work from my previous employer in the US, Time Warner. And we had a fantastic relationship. I still have a good relationship with many of the people I knew from there.
72
00:06:44.530 --> 00:07:02.290
And so I arrived doing Perl and Linux, and I was doing all sorts of stuff in those those fields. And people said to me, well, it's nice that you're doing the development. Would you mind giving us some training in this? And so I had my toes in the training water for a while, and and I did a little Python training as well here and there, but not that much. But the real
73
00:07:02.750 --> 00:07:05.970
Python training tsunami happened probably about 6 years ago.
74
00:07:06.355 --> 00:07:10.775
I was still working on my dissertation. I really didn't wanna have to deal with the training marketing.
75
00:07:11.075 --> 00:07:12.695
And I figured if I hitched my
76
00:07:13.075 --> 00:07:22.610
my wagon to a a bigger horse as it were, hard to a bigger wagon, I don't know what the metaphor is. And then even then maybe I could, maybe I could finish my dissertation faster
77
00:07:22.985 --> 00:07:24.285
and reach some new clients.
78
00:07:24.905 --> 00:07:29.760
And so I I spoke with a company called John Bryce, which is sort of the 900 pound gorilla of training in Israel.
79
00:07:30.960 --> 00:07:41.245
And I sent and and I said I'd like to do Ruby on Rails training. And they said, yeah, you know, this Ruby thing, it's kind of a flash in the pan. We don't think there's really room for training in it, but send us your resume.
80
00:07:41.705 --> 00:07:46.045
And within hours, they called me and they said, oh my god. You know how to do Python.
81
00:07:46.490 --> 00:07:52.190
We must have to do Python training. And since then, I've been doing between 2 and 3 courses a month,
82
00:07:52.730 --> 00:07:58.845
almost nonstop. And right now, we're recording this late April, and I'm almost solidly booked through the end of December
83
00:07:59.225 --> 00:08:01.245
with training. It's just Wow. Nuts.
84
00:08:01.785 --> 00:08:14.260
It it's and I love it. I really it energizes me, like, I mean, today. So I slept 4 hours last night because I was trying to get an article done for Linux Journal. I talked for 8 hours today, came home, finished the article, just did our podcast, talking to you guys,
85
00:08:14.814 --> 00:08:16.594
and I'm a zombie. No. No. And and
86
00:08:17.215 --> 00:08:25.330
when truth be told, when I'm training, it gives me such energy. I love it. I love the questions people have. I love interacting with them. I love seeing those moments
87
00:08:25.790 --> 00:08:34.195
or oh my god moments. Like, you can do all that in 1 or 2 lines? And of course, the point in Python is, yes, you can, and you can read it 6 months later,
88
00:08:34.975 --> 00:08:51.615
which was not not necessarily true for Perl or I would say even sometimes for Ruby.
Right. So so training was sort of a offshoot of my inter interactions with John Bryce. And recently, I decided to sort of now that I finished the dissertation, finished the PhD, I've returned to doing training on my own through my own company directly,
89
00:08:51.995 --> 00:08:55.615
and that has just increased the demand even more, much to my pleasant surprise.
90
00:08:56.320 --> 00:08:58.100
Great. Yeah. It's interesting to hear
91
00:08:58.640 --> 00:09:07.055
from the perspective of somebody providing training how much of a demand there really is for Python because, you know, you see all these different reports that come out about the
92
00:09:07.515 --> 00:09:11.375
comparative popularity of various various programming languages, and
93
00:09:11.810 --> 00:09:14.310
they all can be taken with a bit of a grain of salt. But
94
00:09:14.690 --> 00:09:18.949
having that type of perspective on which languages are actually in demand on
95
00:09:20.084 --> 00:09:22.504
by larger companies is really interesting, particularly
96
00:09:22.884 --> 00:09:31.930
since you're saying how a number of them were really terribly interested in Ruby on Rails, but they they really wanna learn about Python. So good to hear. Oh, for sure. So and I'll tell you.
97
00:09:32.710 --> 00:09:39.050
First of all, I I think someone in each of these big multinational companies and, I mean, companies I train for, like, I I do training in Cisco,
98
00:09:39.735 --> 00:09:40.795
HP, VMware,
99
00:09:41.375 --> 00:10:04.265
you know, EMC. These big big kind of Zendesk. These big companies where someone I think at the top basically said, we have to do some standardization. We have to choose a a smaller subset of languages to work with. And Python is good for a lot of people, and so let's just run with it. And so everything from internal web apps to big data to to, testing and everything, they're doing a lot of standardization on Python.
100
00:10:04.725 --> 00:10:18.015
And not only are they doing this in a lot of companies, but these kind of the demand is almost insatiable. It turns out that when I'm, say, at Cisco giving training, I'll often meet someone else, You know, new person, I'll say, oh, what are you doing here? Oh, I'm giving Python training.
101
00:10:18.395 --> 00:10:21.455
Like, we're both there on the same day and then then
102
00:10:21.920 --> 00:10:24.180
this is really, the demand is almost insatiable.
103
00:10:24.560 --> 00:10:47.320
And I would say it's gonna grow before it shrinks in part because such a huge number of universities are now teaching Python as an intro language. Yep. And you know that some ridiculously large proportion of those students are gonna finish school, you know, graduate from college, go off and do startups, and what language are they gonna use? Well, clearly, it's gonna be Python because that's the 1 they know best. Yep. And so we're gonna see another 5 to 10 years, I think, of this, at least.
104
00:10:47.815 --> 00:11:01.690
And unlike list for scheme, which used to be the kind of de facto standard for intro courses in in at least the the big hardcore CS schools or Java, I guess. I should Java, you know, certainly had commercial use, but lists for a scheme was really kind of,
105
00:11:02.230 --> 00:11:05.290
you know certainly, there have been successful commercial enterprises
106
00:11:05.845 --> 00:11:09.225
conducted with it, but it's not exactly what you consider a mainstream language.
107
00:11:09.685 --> 00:11:15.080
And I and I just wanna say 1 thing about that those language popularity polls that we see. So many
108
00:11:15.460 --> 00:11:22.279
times when you actually look at what metric those polls use for, like, how they determine which language is most popular,
109
00:11:22.615 --> 00:11:34.440
it's something really stupid and flawed, quite honestly. Like, it's like number of lines committed to GitHub project over the last 6 months. And I mean, you know, like, that's that's That's a win.
110
00:11:34.980 --> 00:11:38.440
Exactly. Exactly. Like, that's certainly or these days JavaScript.
111
00:11:38.795 --> 00:11:45.455
That certainly represents a certain subset of the of the computing populace, but by no means is it, like, comprehensively
112
00:11:45.835 --> 00:12:03.774
showing what language are actually most popular in use out in the world. Well, it's it's it's funny, by the way, that you mentioned Lisp and Scheme. So, like, as I said, I went to MIT, and so I was brainwashed into believing that Lisp is the best language ever, and I continue to believe that. And it actually sort of hurt me inside a bit,
113
00:12:04.390 --> 00:12:25.000
when they said they were moving away from Scheme toward Python. And the argument they used was basically the intro course has changed because computing has changed, and what we wanna teach our students has changed. And we can get those ideas across better with Python than with Lisp. I'm not a 100% sure that I agree with that because I really do think there are many things I learned both in that course and from Lisp in general that have been so
114
00:12:25.380 --> 00:12:31.080
useful. I didn't recognize at the time, of course. At the age of 18, you don't recognize anything. But Right. Years later, I'm like, wow.
115
00:12:31.505 --> 00:12:42.170
That was such a useful insight that has carried me through, and I use some of those things in my teaching even now nowadays. So I still think people should learn Lisp, but it is pretty great that they can indeed
116
00:12:42.630 --> 00:12:44.090
use a practical language
117
00:12:44.470 --> 00:12:47.530
that has theoretical depth in an intro CS course.
118
00:12:48.535 --> 00:12:49.675
So out of curiosity,
119
00:12:50.135 --> 00:12:55.975
when you're performing these Python trainings to these big companies, is there a particular language that most of the
120
00:12:56.870 --> 00:13:03.290
most of your students are coming from, or is it just sort of a mishmash of various
languages languages that they've all used before?
121
00:13:04.825 --> 00:13:06.845
Well, look. Most of my training is in Israel,
122
00:13:07.305 --> 00:13:09.325
and Israel has a very strong
123
00:13:09.945 --> 00:13:10.445
dotnetmicrosoftfocus.
124
00:13:12.480 --> 00:13:24.995
And a lot of companies I deal with are hardware companies, which means they have a c and a c plus plus focus. And so the sort of more, I don't know, high level programmers among them are the people who've been doing Java, or I guess like c sharp.
125
00:13:25.775 --> 00:13:28.995
So it's rare. It happens, I would say maybe
126
00:13:29.310 --> 00:13:30.290
10%, 20%
127
00:13:30.670 --> 00:13:34.050
of my students have a background in Ruby, JavaScript,
128
00:13:35.390 --> 00:13:37.410
you know, some some sort of high level,
129
00:13:38.030 --> 00:13:41.185
language that that I think gives them a closer insight
130
00:13:41.644 --> 00:14:00.315
into how Python works. So for a lot of them, this whole idea, like, I I always have to tell them that you're learning not just the language, but the approach. That there's no such thing here as a compiler. Yep. So you can't just write the file, throw it at the compiler, and hope that your errors will be found. You actually you actually have to think of it and you have to run it, and you have to work with the interactive shell with with IPython
131
00:14:00.935 --> 00:14:03.274
so that you can test your things and do it iteratively.
132
00:14:03.815 --> 00:14:04.315
Yep.
133
00:14:05.449 --> 00:14:06.910
Yeah. It's definitely
134
00:14:08.250 --> 00:14:17.185
very much diff 2 different things of learning a language and what it is and what the semantics are versus how learning how to use the language in
135
00:14:17.564 --> 00:14:19.324
in in an idiomatic manner. So
136
00:14:20.339 --> 00:14:23.079
Right. And I would say that over the years, I've been
137
00:14:23.620 --> 00:14:24.120
learning
138
00:14:24.740 --> 00:14:30.875
what the idioms are that surprise people or that are most useful to them, and I've tried more and more
139
00:14:31.894 --> 00:14:36.235
to gear my training in that direction. For instance, I used to almost never talk about scope.
140
00:14:36.600 --> 00:14:52.605
It's like scoping in Python, it's so obvious, until I discovered it's not. It's not to people who are not used to it. And so now I have a long section where I talk about scoping with people, and I explain to them different kinds of variables and l e g b, and how this works, and the sort of fun tricks you can play with that as well.
141
00:14:53.625 --> 00:14:59.450
And and I think that those insights, maybe they're not gonna be redefining true to false and false to true in their day to day work.
142
00:14:59.830 --> 00:15:04.090
I certainly hope not. Although, I do suggest that they do it to someone they don't like when they go to get a cup of coffee.
143
00:15:04.630 --> 00:15:05.130
But
144
00:15:05.834 --> 00:15:14.415
but, you know, understanding l e g b can really give you deep insights into how the language works and what's going wrong when you're trying something.
145
00:15:15.370 --> 00:15:19.069
Right. I'm I'm sure. And and speaking to your your point about,
146
00:15:19.449 --> 00:15:20.350
what's idiomatic,
147
00:15:21.050 --> 00:15:25.935
in different languages, that was I mean, I was a Ruby guy for years years years. I I've only
148
00:15:26.475 --> 00:16:02.495
been kind of a a Python convert. Although, I still love Ruby for the last, you know, I don't know, 4, 5 months or so. And that was 1 of the most challenging aspects of learning Python for me is so many of the concepts are very similar, but the idioms are so different. And in in kind of if you're coming from a different environment, you're used to different things unintuitive ways like the, you know, no implicit return thing. I know it's a small thing and most Python Pythonistas are like, well, why would you do it any other way? But when you use the Ruby where implicit return happens, it it it can, you know, lead to some hair pulling and, like, why won't it just work
149
00:16:02.875 --> 00:16:03.355
moments until
150
00:16:05.835 --> 00:16:09.360
yeah. That that actually, I must say, that drives me totally bonkers.
151
00:16:09.740 --> 00:16:12.959
And maybe it's just my, like, you know, Lisp, Ruby,
152
00:16:13.500 --> 00:16:14.220
even Pearl,
153
00:16:15.475 --> 00:16:22.295
Persona coming out. But, like, come on. Can't we just have implicit return? And I understand, no, everything has to be explicit.
154
00:16:22.800 --> 00:16:28.180
But, but I I really actually do miss that. And they're very I mean, also the whole thing where when you do assignments,
155
00:16:28.720 --> 00:16:40.515
like, or or I would say even, like, you know, you're sorting a list where it returns none. Like, I love getting things back and then being able to chain them. And, yes, we we have sorted and so forth, but I don't know. That's behavior that I just sort of
156
00:16:41.170 --> 00:16:46.950
shrug my shoulders at and say, well and I tell my class and I say, well, they never called me to ask what I thought. So
157
00:16:49.685 --> 00:16:55.144
that's the that's the both the the blessing and the curse of having a benevolent dictator for life. Right? As unfortunately,
158
00:16:55.605 --> 00:16:58.710
everybody has an opinion, but his is the only 1 that really matters.
159
00:16:59.430 --> 00:17:00.410
Yes. Precisely.
160
00:17:01.830 --> 00:17:06.970
So what are some of the biggest obstacles that people encounter speaking of idioms and and idiomatic,
161
00:17:07.510 --> 00:17:09.015
code? What are some of the biggest
162
00:17:09.315 --> 00:17:11.815
obstacles that people encounter when they're learning Python?
163
00:17:13.395 --> 00:17:13.795
Oh,
164
00:17:15.130 --> 00:17:19.230
So first of all, the whole dynamic typing thing, I think, really takes them by surprise
165
00:17:19.610 --> 00:17:21.630
and and sort of
gives them the chills.
166
00:17:22.144 --> 00:17:33.809
You know? So, like, just, I guess yesterday, I was doing yesterday and today, I gave the 1st day of an intro Python course to to a company here in Israel. And both days, I think because people were coming from these statically compiled languages,
167
00:17:34.190 --> 00:17:37.470
both days people I I have I have this, 1 1 of my
168
00:17:38.485 --> 00:17:45.625
1 of the exercises I give them is just sort of a number guessing game. So get raw input from user, and we're almost always using Python 2, 27.
169
00:17:46.050 --> 00:17:52.630
And so, you know, raw input, get a string, and now compare with the randomly generated number with, from the random module.
170
00:17:53.250 --> 00:18:19.434
And I do this on purpose because I know they're gonna get tripped up, and they're gonna remember the hard way that raw input always returns a string. And so someone said to myself, why don't we just declare the variable to be an integer, and then automatically raw input, when it's assigned to that to that variable, it'll become an integer. I was like, no, no, no. That's not the way it works. You can't have a variable that's a certain type. And so the fact that variables aren't type, the fact that parameters, which are variables aren't type, just gives them the willies.
171
00:18:21.960 --> 00:18:30.865
Similarly, I think oh, you know what's what's hard for them also? The whole splat argument thing. That and and keyword arguments. Yep. They think it's super cool
172
00:18:31.165 --> 00:18:50.335
and they cannot wrap their heads around it. Either it's hard for them or they don't they don't know why they would want it. I'll totally admit that I totally love it. I think it's a great feature, but I have to admit that I find it hard to wrap head around sometimes. And whenever I see it in code, I have to be like, what what's this doing again? What what
173
00:18:51.055 --> 00:18:52.575
you know, so it it's definitely
174
00:18:53.350 --> 00:19:04.355
I can definitely appreciate that it's 1 of those I mean, and for you, for someone who comes from a language like Lisp, it's like, well, of course, you have dynamic arguments. Like, why? Why would you wanna do it any other way? So it's
175
00:19:04.815 --> 00:19:12.240
it's a great feature but it can be it can when you first encounter it or even after you first encounter it, it it it can feel kind of alien.
176
00:19:12.940 --> 00:19:17.200
Yeah. It definitely took a little while for that to sink in for me when I first started using Python.
177
00:19:17.904 --> 00:19:18.965
Mhmm. Mhmm.
178
00:19:19.585 --> 00:19:24.005
Yeah. And so, I mean, 1 of the exercises that I give is, to have an XML generator,
179
00:19:24.465 --> 00:19:25.284
in a function.
180
00:19:25.650 --> 00:19:33.270
And so I say, like, you know, so the the tag name should be the first parameter, and the content should be the second parameter, and then you can take any number of keyword arguments,
181
00:19:33.865 --> 00:19:36.525
and those are turned into attributes inside the opening tag.
182
00:19:37.065 --> 00:19:37.565
And
183
00:19:38.185 --> 00:19:39.005
that usually
184
00:19:39.305 --> 00:19:53.965
confuses them because they say, wait a second, where am I supposed to use the splat? Right? Where am I supposed to get any number of arguments? It takes them a while to realize, well, first of all, just because you've learned about a tool doesn't mean you have to use it. But second of all, in that particular case, getting a default argument is typically more appropriate and more useful
185
00:19:54.345 --> 00:20:03.039
than having the splat there, you know, splat arks. Yep. But the keyword, you know, keyword arguments, well, that's just super handy. And then you can have this
186
00:20:03.340 --> 00:20:07.205
API that looks nice and does something spiffy behind the scenes.
187
00:20:08.625 --> 00:20:14.645
What's another what are other things that drive them nuts? Oh, I know. The fact that objects are totally exposed and open.
188
00:20:15.330 --> 00:21:03.565
Right? Right? Like so I even go I even go through the motions of, okay, here's our person object, let's create a getter and a setter. Then I'm like, no. Do not use these. Erase these getters and setters, we don't need them. And people will say, but but but but but we're supposed to have, you know, our objects are supposed to be black boxes. And I say, well, not really in Python. Yep. But, but, but, but, but, but, what if we want to have programmatic access or change the API over time, evolve it? Wouldn't that be better to have a getter or setter? I say, well, actually the way Python approaches this is a property. Typically my intro classes don't even get to properties. It depends on how, sort of, how the class is structured, but usually not. But I say, like, Python does have answers to these things, but they're different than the answers that you're used to. And just because the object system doesn't work or just because the approach isn't what you're used to, it doesn't make it wrong. It just makes it different, and it's a different set of trade offs.
189
00:21:04.710 --> 00:21:25.919
That's that's really interesting you say that. Properties are 1 of the things that I I kind of, like, you know, as I said, as I admitted already, I'm kind of a Python noob still. I've been using it for a few months and I I can certainly, you know, tootle along and write my code day to day and it but there are various aspects of it that I haven't quite wrapped my head around yet. And and that leads me to wonder, you know, many languages
190
00:21:26.380 --> 00:21:31.679
like there's almost nothing new under the sun in computer science. Right? Like, every language can trace
191
00:21:32.025 --> 00:21:37.085
various of its features back to some lineage of somewhere else. Where does Python's
192
00:21:37.705 --> 00:21:44.030
object system come from? Like, will that that aspect of properties and objects
working differently than you would see.
193
00:21:44.410 --> 00:21:48.110
Where do you think it it drew its object oriented inspiration from?
194
00:21:48.865 --> 00:21:50.645
Well, interesting you say that, because
195
00:21:51.025 --> 00:21:51.925
I've always
196
00:21:52.545 --> 00:21:53.045
said
197
00:21:53.505 --> 00:21:55.525
and thought, and I think it's even true,
198
00:21:56.040 --> 00:21:58.540
that a lot of the Python object system came,
199
00:21:58.840 --> 00:21:59.340
from,
200
00:21:59.960 --> 00:22:18.560
Smalltalk. So you can I mean I mean, so, you know, you you came from Ruby? You've spent some time in Ruby. Like, truth be told, if I have to teach Ruby and I have to teach Python, I often will come up with a new exercise in 1 language and use it in the other because the languages are, under the surface, very similar in some ways. And the object system is very similar in some ways, except
201
00:22:18.860 --> 00:22:31.510
Python somewhere said no, no, no. Instead of doing everything through messages, everything through methods, we're gonna turn that around, and we're gonna make everything look like data access. And so, like, properties are basically the inverse
202
00:22:31.970 --> 00:22:33.269
of Ruby's attributes.
203
00:22:33.570 --> 00:22:36.149
Where Ruby attributes, we make data
204
00:22:36.529 --> 00:22:37.750
look like methods.
205
00:22:38.255 --> 00:22:42.275
Right? And and Right. In Python we make our methods look like data.
206
00:22:42.655 --> 00:22:44.515
And I've got to assume
207
00:22:44.895 --> 00:22:50.600
that it was Guido or someone else or maybe 1 of the languages that he learned. He just really liked that approach.
208
00:22:51.060 --> 00:22:52.920
And it definitely is a bit of a
209
00:22:54.065 --> 00:22:56.885
bastardization or, like, a real revolution
210
00:22:57.265 --> 00:22:59.445
from what small talk did.
211
00:23:01.480 --> 00:23:08.540
And and I don't know. I don't know. It's it's it's an interesting approach. There's sometimes when I sort of roll my eyes and say really? We have to do it this way?
212
00:23:09.075 --> 00:23:18.135
But the whole object system I mean, basically, if you understand how attributes work, then you understand the hold on object system and inheritance, for instance, just comes straight out of that.
213
00:23:18.560 --> 00:23:23.860
You know, there's no special rule for inheritance. It's just, an extension of or a special case
214
00:23:24.160 --> 00:23:25.460
of attribute lookup.
215
00:23:25.935 --> 00:23:27.715
And that, I think, is really elegant.
216
00:23:28.095 --> 00:23:29.555
But where did it come from exactly?
217
00:23:29.935 --> 00:23:37.100
I don't know. That's a good question. I'd love to find out. Yeah. Maybe 1 of our listeners can tell us if there's gotta be some language history
218
00:23:37.639 --> 00:23:40.539
buffs out there who can who can school us on this.
219
00:23:41.000 --> 00:23:41.820
Oh, I'm sure.
220
00:23:43.105 --> 00:23:43.585
Yes.
221
00:23:44.065 --> 00:23:53.120
I'm sure another thing that people, particularly coming from things like c plus plus or Java, have trouble with is the lack of protected and private methods in Python.
222
00:23:53.900 --> 00:23:55.920
Oh my god. They go nuts over that.
223
00:23:57.180 --> 00:23:59.290
Right? Right. I I I mean,
224
00:23:59.615 --> 00:24:08.195
right. Right. Because they they sort of wonder, how is this possible? How could this language I mean, so it has dynamic typing. Everything is open. Nothing is private or protected.
225
00:24:08.610 --> 00:24:11.350
And especially, like, many of the people whom I teach,
226
00:24:11.810 --> 00:24:13.270
are in the security industry.
227
00:24:13.810 --> 00:24:21.005
And to them, this whole notion of, well, we're just gonna be really optimistic and nice and friendly, and everything will work great.
228
00:24:21.865 --> 00:24:31.010
And they say, are you kidding me? That's like, yo, and does that include everything we do professionally? Yep. And I say well maybe, but it's worked pretty well for 2 decades, you know? Right.
229
00:24:31.635 --> 00:24:36.295
And interestingly too, Python is actually quite popular in the security industry as well.
230
00:24:37.235 --> 00:24:38.615
Right. So I
231
00:24:39.020 --> 00:24:41.280
I don't know. I don't know. It's it's very,
232
00:24:43.020 --> 00:24:51.855
I I I can't explain it. I mean, I do tell them that if you really want I mean, there's always a way around it. But if you really want sort of extra security or pretend that things are private or protected,
233
00:24:52.315 --> 00:25:07.065
you can always, you know, you can always use something like a descriptor. Mhmm. But truth be told, how many people are gonna do that? Almost none. I don't know how I don't I mean, I'm sure we're gonna hear from people now. Right? But, like, how often do people really use descriptors after all? They're super
234
00:25:07.445 --> 00:25:16.310
cool, but Yep. I I think I think it's, you know, maybe 5% of the population. And that 5% might need it. Yep. But I think it's a it's a relative rarity.
235
00:25:17.810 --> 00:25:20.310
Once again, I think it comes down to just having
236
00:25:20.825 --> 00:25:33.549
to think about different ways of structuring your systems and your code, right, around this new model, this new way of working. I'm sure it's just a matter of getting people to change their mind about things is is the hard part.
237
00:25:34.169 --> 00:25:34.669
Yes.
238
00:25:35.210 --> 00:25:35.710
Yes.
239
00:25:36.544 --> 00:25:39.365
Oh, here's another thing that that that people are surprised by,
240
00:25:40.065 --> 00:25:44.005
and sort of intrigued by, which is, of course, comprehensions. List comprehensions,
241
00:25:44.559 --> 00:25:46.419
set comprehensions, and dictionary comprehensions,
242
00:25:47.200 --> 00:25:47.700
where
243
00:25:48.320 --> 00:25:50.179
they see it as almost like black magic.
244
00:25:50.799 --> 00:25:54.259
And, you
know, they see so I give lots of examples of what we can do. We usually,
245
00:25:54.755 --> 00:25:59.575
depending on the length of the course, the type of the course, we then practice it to some degree or another.
246
00:26:00.035 --> 00:26:04.429
But I know that people don't get it. Like, they don't see the sort of, okay. I have a problem.
247
00:26:05.049 --> 00:26:21.470
A comprehension is my solution, and this is what I'm gonna get back. I think part of it is just sort of years of training where if you work with functional languages or, you know, if if you use these sorts of tools like map and and, you know, reduce filter for years, then you just sort of see those as solutions to a huge variety of problems.
248
00:26:21.870 --> 00:26:24.929
But for a lot of people, all they see is this wacky syntax,
249
00:26:26.429 --> 00:26:31.330
and and they're not quite sure what they're doing or how they're getting it, but they're getting results back that don't quite make sense.
250
00:26:32.015 --> 00:26:44.830
Yeah. I was gonna say that for me, list comprehensions and dig like, comprehensions in general are 1 of the Python features that I find myself struggling with. Not because I can't understand them when someone else uses them and I see them in source code and I say,
251
00:26:45.370 --> 00:26:48.110
comprehension, it does this and thus. But because
252
00:26:48.985 --> 00:26:51.885
the the syntax is so alien to me that
253
00:26:52.185 --> 00:26:59.670
when I find I need to do something and I'll, you know, hit a code review and they'll say, well, gee, a comprehension could do this a lot more cleanly and elegantly.
254
00:27:00.049 --> 00:27:04.150
And it's like, oh, yeah. I just I never would have thought of that because it's just this
255
00:27:04.514 --> 00:27:16.260
for me, in my, you know, really limited way of thinking, it's just this bizarro world thing off in a corner somewhere that I haven't quite embraced yet. And I can only imagine other newbies have a similar challenge with them.
256
00:27:16.720 --> 00:27:23.825
Yeah. Yeah. Sure. I I often tell my students in Israel that we have an advantage because it helps to read a Liskov branch from right to left.
257
00:27:27.325 --> 00:27:30.730
That's good. Actually, just recently, like, a week or 2 ago, I I've gotta write this
258
00:27:31.370 --> 00:27:34.910
in a blog post. But I think that it can help to think of a list comprehension or a comprehension
259
00:27:35.370 --> 00:27:42.185
in terms of SQL because a lot of people know SQL. If you think of, like, the and I've also started writing my comprehensions in 3 lines,
260
00:27:42.565 --> 00:27:51.390
breaking it up. So you've got the you've got the expression you get back, and then you've got the source that you're iterating over, and then you've got your if statement.
261
00:27:52.170 --> 00:27:57.855
And I said and and I realized that if you sort of make that analogous to SQL, it's like a select call. Right? You've got your select
262
00:27:58.635 --> 00:27:59.855
from some source
263
00:28:00.155 --> 00:28:07.269
where and you're filtering it out. And once I made that analogy for people, like, really, just in the last few weeks I sort of came up with this, that I think helped to
264
00:28:07.570 --> 00:28:19.145
solidify their understanding of the syntax. It's still a little weird for them, but at least it sort of became close to something they're familiar with. No. I I totally agree. I think that's actually quite brilliant because years years ago, I worked for,
265
00:28:19.524 --> 00:28:36.955
man, I I worked for a couple of years in the financial service industry, and my boss at the time was 1 of these brilliant SQL hackers just like, you know, he said, SQL is like go. You can learn the rules in 5 minutes, but it could take years years to really appreciate all the all the all the strategies involved.
266
00:28:37.495 --> 00:28:38.395
And he
267
00:28:38.695 --> 00:28:41.740
he actually taught me a way of of structuring
268
00:28:42.040 --> 00:28:59.649
SQL, you know, query statements in exactly the same format that you're kinda talking about, like, this really rigid format with the the select part of the clause up top and then, you know, from is in the next line and where is in the line after that. And this is really sort of, like, almost visual way
269
00:29:00.110 --> 00:29:03.409
of representing the syntax. Right? So as opposed to this big
270
00:29:03.870 --> 00:29:05.409
long globby thing,
271
00:29:05.789 --> 00:29:08.735
like, it kind of the the format that you use
272
00:29:09.195 --> 00:29:18.700
shows you what the code is trying to do by virtue of the way it's laid out. And it sounds like this way that you're talking about of of of laying out list comprehensions
273
00:29:19.320 --> 00:29:20.539
does the same thing.
274
00:29:22.335 --> 00:29:27.235
Yeah. Yeah. Oh, okay. Now I definitely have to write this up at some point. Yeah. You do because I wanna read it.
275
00:29:28.815 --> 00:29:31.320
Yeah. It's definitely a very interesting metaphor. It's,
276
00:29:33.080 --> 00:29:33.960
thinking about it, it's that
277
00:29:35.000 --> 00:29:39.019
you're very intuitive when you approach it in that manner. So, yeah, that's great.
278
00:29:39.655 --> 00:29:42.155
So another question we have is,
279
00:29:43.175 --> 00:29:50.220
how does teaching Python differ from teaching other languages? Are there different approaches that you would take for when you're
280
00:29:50.920 --> 00:29:54.380
teaching a Python course versus, say, a Ruby or a Pearl course?
281
00:29:55.865 --> 00:29:59.485
So first of all, like, the the Ruby and Python courses I teach,
282
00:29:59.945 --> 00:30:06.760
at least the language parts, like, it's not doing, you know, web stuff or something. Quite frankly, I just steal from each language. I I really see the languages
283
00:30:07.060 --> 00:30:18.025
as sort of similar enough to each other. Obviously, there are differences. Obviously,
so so here for instance, when when I'm talking about Ruby, I have to talk about blocks. I have to talk basically about functional programming
284
00:30:18.485 --> 00:30:19.145
way earlier.
285
00:30:19.525 --> 00:30:31.825
So with my Python course, I basically say, listen folks, this section of functional programming on comprehensions and passing parameters, which are functions, like, this is the hardest part of the course. And if you don't get it, it's not you.
286
00:30:32.225 --> 00:30:39.605
And and you don't need it to be a Python programmer. But in Ruby, if you don't get blocks, you're sunk. Mhmm. So so that's 1 difference.
287
00:30:40.065 --> 00:30:48.390
Trying to think what else. I think in Python, you could go way, way farther also without creating classes. Right? You don't need to create classes. You
288
00:30:48.690 --> 00:30:51.054
you don't need to create methods either. And
289
00:30:51.355 --> 00:31:03.030
so we can sort of I I spent the first day to day and a half of my Python courses just talking like we don't even create functions, we're just using the built in data structures and methods. And then we do functions. And then we talk about objects at the end.
290
00:31:03.410 --> 00:31:09.885
In part because I think it's really important that people get these basics down, in part because you can. Yep. But again, in Ruby, you sort of need to be
291
00:31:10.665 --> 00:31:16.650
mixing and matching a lot more to get the so so that people can get it. Because if you don't know what a class is in Ruby, once again, you're sort of
292
00:31:18.170 --> 00:31:21.850
sung. I totally agree. And I actually think I think that,
293
00:31:22.570 --> 00:31:25.150
that's kind of 1 of the the awkward bits
294
00:31:25.530 --> 00:31:26.030
around
295
00:31:26.465 --> 00:31:32.645
learning Ruby because I've certainly encountered quite a number of of introduction to Ruby, learning Ruby kind of books where
296
00:31:33.185 --> 00:31:34.005
they either
297
00:31:34.870 --> 00:31:40.490
show objects right upfront or they wait till the very very very very very end of the book.
298
00:31:41.030 --> 00:31:51.919
And and in Ruby's case at least, you get to the end of the book and you get to objects and you're like, why didn't you teach me that in chapter 1 because it would have made a whole lot of things. A whole lot clearer and and you know easier
299
00:31:52.460 --> 00:31:56.240
and, I can I can see what you mean though? Python kind of has different
300
00:31:56.765 --> 00:32:02.385
aspect to its soul and that you really don't need to use objects for a significant amount of like
301
00:32:02.685 --> 00:32:05.825
great procedural coding with some really, you know, deep,
302
00:32:06.580 --> 00:32:10.120
useful data structures, you really don't need to use objects unless
303
00:32:10.659 --> 00:32:13.240
the the problem domain really calls for it.
304
00:32:13.915 --> 00:32:14.415
Mhmm.
305
00:32:15.675 --> 00:32:36.054
Right. We don't even had some sort of blog post, I think about a year ago, maybe 2 or 3 years ago at this point, where he he was asked how do I make my Python programs faster? And my guess is he's asked this so often. They finally just got sick of it. He said, okay, folks. I'm gonna write down my notes. And 1 1 of the first things he wrote was don't use objects. Like just use the built in data structures.
306
00:32:36.434 --> 00:32:42.940
They're fast, they work, They're intuitive. They've been really highly refined and optimized over the years.
307
00:32:43.480 --> 00:33:02.740
And and why not? And that's something else people sort of need to shed. That if you're coming from, say, the Java or the c sharp world, you know, someone wants to write hello world, their first instinct is, oh, gotta write a class. And at the time that we saw, no, no, no, slow down. What problem are you trying to solve? And and what the analogy I often use is, like, you wanna have a a toolbox,
308
00:33:03.215 --> 00:33:07.635
and then pick the right tool out of the toolbox, not just pick the first thing that that comes to mind.
309
00:33:09.215 --> 00:33:30.460
Right. Absolutely. And then it also strikes me listening to you that, languages like closure as a for instance, which, you know, is enjoying quite a burst in popularity lately. It doesn't have objects either. And and, you know, people are just using the data structures that it pretty much provides and and using those as building blocks. And obviously, people are doing some pretty amazing, pretty complex things
310
00:33:31.000 --> 00:33:39.155
once again without objects. So it's just a matter of sort of breaking out of your usual mode of thought and embracing a different a completely different
311
00:33:39.855 --> 00:33:41.475
model for doing your work.
312
00:33:42.000 --> 00:33:42.500
Actually,
313
00:33:42.800 --> 00:33:44.660
thank you. You you inspired
314
00:33:45.040 --> 00:33:48.580
a a pick that I hadn't thought of previously that I'll put in our pick section.
315
00:33:49.120 --> 00:33:49.860
Oh, good.
316
00:33:51.735 --> 00:33:57.434
So what sorts of materials or medium do you use for training people in Python?
317
00:33:59.309 --> 00:33:59.809
So,
318
00:34:00.190 --> 00:34:18.240
this has been going through a bit of an evolution over the years and I'm always looking for for new things. So I I'm a big emacs user. Right? I went to MIT, went through the brainwashing process. Back when I was there, like, back when I was there, even the secretaries used emacs. So, like, obviously, the students were gonna use it. And, you know, my my dotemacs file has
319
00:34:18.540 --> 00:34:29.915
been steadily growing over 20 plus years. Every so often I prune it. Every so often I say, really? What's this doing in here? But I just use that. And and I tell my students, you don't have to use emacs. Right? Like, there are some weird people who don't. So I'm
320
00:34:31.610 --> 00:34:37.210
Sickos. Sickos. That's what I call them. I actually tell
my students they should use PyCharm just because they need something that's a little,
321
00:34:37.530 --> 00:34:38.750
shallower learning curve.
322
00:34:39.210 --> 00:34:56.180
So I use emacs, and then I used to use just the regular old Python shell. And someone said to me, we weren't using IPython. I said, oh, yeah. I've heard of it. I'll try it. And of course I tried, I said, oh my God, this is so much better. But I could not use IPython notebook just because I do a a lot of my examples, a lot of my demos are with files.
323
00:34:56.640 --> 00:35:03.425
Oh, yeah. And then at some point don't know exactly when, but at some point the iPad notebook let you do files. I said, oh, wow. That's amazing.
324
00:35:03.805 --> 00:35:04.865
And so literally
325
00:35:05.165 --> 00:35:09.339
a month or 2 ago, I switched to doing all of my live coding demos, and I have a lot of them
326
00:35:09.880 --> 00:35:15.740
when I'm teaching. Because if people ask me a question, I want them also to get the feeling that if they have a question when they're working,
327
00:35:16.040 --> 00:35:18.994
they should turn to IPython, and they should try it. What
328
00:35:19.295 --> 00:35:30.390
happens if the only answer to that is, let me try? Not, oh, boy, I should look it up. Now looking it up is not bad, but but that's why you have this this beautiful sandbox of the interactive, you know, the REPL.
329
00:35:30.770 --> 00:35:31.270
So
330
00:35:31.650 --> 00:35:45.829
I I've lately, over the last, I think, month or 2, I've been using a hyphen notebook. And then my my my standard thing at the end of each day is people send me email who are in my class, and I send them a zip file with all the exercises to this like, basically solutions that I've solved in front of them of the exercises,
331
00:35:46.530 --> 00:35:48.309
plus the slides in pdf,
332
00:35:48.690 --> 00:35:51.670
plus now I can send them the IPython notebook, and they can then replay
333
00:35:52.135 --> 00:35:54.075
everything that I demoed to them in the lecture.
334
00:35:54.775 --> 00:35:58.235
So IPython notebook has become, like, an essential part of my teaching as well.
335
00:35:58.695 --> 00:36:02.369
A third thing is the Python tutor. I don't know if you're familiar with the Python tutor site.
336
00:36:02.670 --> 00:36:03.170
Pythontutor.com.
337
00:36:04.349 --> 00:36:24.415
Oh my god. It's amazing. It's ama I I forgot the name of the person who did it. It's beautiful and fantastic. The number of occasions at which someone says, yeah. But why so for instance, I I have an example I often use where I create a small list, you know, my list equals a, b, c. And then I create a larger list, like, big list equals my list, my list, my list. So now we have
338
00:36:25.135 --> 00:36:27.235
4 names for the same list.
339
00:36:27.535 --> 00:36:29.155
And I show them that if you change
340
00:36:29.535 --> 00:36:40.809
index 0 0 of the big list, you're really changing the original my list as well. At this point, people's noses sort of wrinkle and they are kind of wondering what's going on. And I pulled the Python tutor which has a dynamic,
341
00:36:41.845 --> 00:36:42.905
dynamically generated
342
00:36:43.285 --> 00:36:43.785
graphical
343
00:36:44.565 --> 00:36:45.065
display
344
00:36:45.445 --> 00:36:51.990
of the innards of your Python program, and they can see the arrows, they can see the boxes, and it just becomes instantly clear.
345
00:36:52.770 --> 00:36:57.670
Wow. That's that's really that's really awesome. I I did not know about that and I will definitely
346
00:36:58.985 --> 00:37:05.245
plan some quality time to go play with that because as I said, there are definitely a few Python concepts that I could use some
347
00:37:05.625 --> 00:37:08.640
brushing up with and that sounds like a really useful tool. Thank you.
348
00:37:09.200 --> 00:37:15.380
Sure. Sure. I've I've come across it before, but, it's been a while since I've had call to use it. So definitely thank you for the reminder.
349
00:37:18.835 --> 00:37:24.535
So I understand that you recently wrote a book called practice make Python, if I'm correct.
350
00:37:24.835 --> 00:37:30.510
And I'm just wondering if that's something that you generally use as a follow-up reference for your trainings.
351
00:37:31.690 --> 00:37:32.190
So,
352
00:37:32.810 --> 00:37:37.790
it was basically suggested by my students. I think it was about a year ago, a little less than a year ago.
353
00:37:38.214 --> 00:37:39.595
Over the course of 2 weeks,
354
00:37:40.295 --> 00:37:45.434
after every class or during the breaks, people would say to me, okay, listen. We're taking a 4 day course.
355
00:37:45.734 --> 00:37:46.635
That's great.
356
00:37:47.220 --> 00:37:53.160
But there's always gonna be this gap between finishing the course and then wanting to use the information in our actual work.
357
00:37:53.539 --> 00:37:55.079
Where can we go to get exercises?
358
00:37:55.694 --> 00:38:00.835
I said, well, you know, there's Zed Shaw's learning Python the hard way. And they said, yeah. Yeah. We've done that. Okay. Next.
359
00:38:01.615 --> 00:38:02.194
I said,
360
00:38:02.895 --> 00:38:06.240
I don't know, but it sounds like a business opportunity.
361
00:38:07.500 --> 00:38:08.319
So basically,
362
00:38:08.619 --> 00:38:13.119
I said what I asked them what would happen if I gave you a book or sold you a book
363
00:38:13.545 --> 00:38:17.165
with 50 exercises that would force you to really think in Python,
364
00:38:17.705 --> 00:38:25.070
and then you would have to work at it but it would probably give you some benefit? And they all said, oh my god. I would definitely get that. Now they're all liars because they didn't all get that. But
365
00:38:26.570 --> 00:38:27.790
I will hunt them down.
366
00:38:28.330 --> 00:38:31.310
But, basically, what I do is I I wrote up 50 of the exercises
367
00:38:31.875 --> 00:38:35.655
that I most like using in my courses either as demos or as
exercises
368
00:38:36.035 --> 00:38:36.855
that I see
369
00:38:37.395 --> 00:38:42.610
give people that moment that they're forced to work. And sometimes the solution is as little as 1 or 2 lines.
370
00:38:42.910 --> 00:38:47.170
But getting to those 1 or 2 lines is the magic and is where the learning really comes from.
371
00:38:47.575 --> 00:38:55.670
And so I I wrapped up the book. I guess I finished writing it about, I don't know, probably January or something, January or February. And I've
372
00:38:56.050 --> 00:39:04.675
been slowly, very slowly but surely making videos to accompany it for people who want that package. But that's just time consuming and I'm so busy with other things. It's taking way longer than I would like.
373
00:39:05.315 --> 00:39:11.255
But the the book is not a tutorial, because I I really think that there are enough tutorials out there in Python.
374
00:39:12.569 --> 00:39:21.565
The world doesn't need another tutorial. The world needs something for after you're done with the tutorial. And so what I call my book is it's like your second Python book, or it's the book to read after you've taken a course.
375
00:39:23.305 --> 00:39:29.609
That's really awesome because I I I'm definitely in that category of I've read some of the tutorials. I read, you know,
376
00:39:30.089 --> 00:39:37.545
dive into Python. And as I say, I've been using it at work now for 4 or 5 months. And and so I'm definitely past the intro phase,
377
00:39:37.925 --> 00:39:59.655
but I'm not really to the point where, like, you know, when you're in that kind of tentative stage where you're not quite comfortable with every aspect of it and it's not like it doesn't feel like that really well used tool that like, you know, just sort of, like, fits in your hand like it was meant to always be there. I'm not there yet and I think something like this book could be incredibly useful to get me there.
378
00:40:00.380 --> 00:40:08.880
Good. I hope so. And and I've been very fortunate also. A lot of people who have read it have, emailed me with corrections or suggestions or insights.
379
00:40:10.155 --> 00:40:13.135
And and I like that. And and and also when I'm teaching, like, from my perspective,
380
00:40:13.915 --> 00:40:27.945
what's what's most important both from my perspective as a teacher, but also for the learning process is the interactions. It's the asking questions, it's the wrestling with things, it's the talking it out talking it through. So, fortunately, in Israel people are not bashful, and they are more than happy to say
381
00:40:28.725 --> 00:40:32.425
that's stupid or that's a terrible idea or what do you think about this and really challenge me.
382
00:40:32.805 --> 00:40:34.905
But I really think that that helps with the learning.
383
00:40:35.270 --> 00:40:35.770
And,
384
00:40:36.150 --> 00:40:39.450
so I've also been learning from the people who've written the book and sending me all suggestions.
385
00:40:39.990 --> 00:40:47.115
And so, if anyone out there gets, you know, gets the book and and has ideas, suggestions, improvements, that would be fantastic. I mean, I would say
386
00:40:47.415 --> 00:40:47.915
easily
387
00:40:48.215 --> 00:40:51.355
easily half or more, probably even 2 thirds of the exercises
388
00:40:51.975 --> 00:40:54.875
were either inspired by or improved on
389
00:40:55.240 --> 00:40:59.339
by students in my classes who gave me feedback and and really helped me to refine them.
390
00:41:01.079 --> 00:41:03.319
That's very cool. And speaking of getting the book,
391
00:41:03.640 --> 00:41:06.345
Reuben has very kindly offered a,
392
00:41:06.725 --> 00:41:09.465
discount code, which we'll be passing on to our listeners.
393
00:41:09.845 --> 00:41:21.250
You can find it in the show notes rather than us trying to say it and and having it come across garbled or anything. We'll just put a link to the book and the awesome discount code there for in case you wanna avail yourself of this resource.
394
00:41:22.615 --> 00:41:26.234
So, in your freelance work, what portion of your projects use Python?
395
00:41:28.535 --> 00:41:31.820
Interesting. You should say that. So so that's, of course, the question.
396
00:41:32.360 --> 00:41:48.410
So for years, actually, it was kind of embarrassing that I was doing most of my freelance work in Ruby and most of my training in Python. Obviously, I was using Python in multiple different ways, but it was sort of like this, you know, Bruce Wayne Batman kinda thing, I guess. I'm not sure which Python fits it to, so I'll let you guys figure out the analogy where.
397
00:41:49.930 --> 00:42:01.165
I've always had some clients who use Python, sometimes more, sometimes less. There have always been some people using it for whether it's database work or web stuff. And, certainly, I've always done some projects on my own with it.
398
00:42:01.465 --> 00:42:06.365
But truth be told, it's really only since I've started getting heavily into the training
399
00:42:06.665 --> 00:42:19.065
that I've been diving myself into Python and using it for more and more things and trying to find sort of the the corners of of different stuff. So, recently, I've been asked to do more and more training using NumPy, SciPy, big data types of things.
400
00:42:19.445 --> 00:42:28.210
So there, I've started just sort of doing it on my own. But the number of actual paid projects I've done over the I actually, that's not true. In the last 5 years,
401
00:42:28.670 --> 00:42:32.610
the number of paid projects I've done in Python, I would guess is about 10%, 20%
402
00:42:32.910 --> 00:42:33.535
at most.
403
00:42:34.095 --> 00:42:42.914
There was a period maybe 10 years ago when all of it was in Python. I did some stuff on the web with XO. I did some stuff just with databases, with Postgres, with all sorts of analysis.
404
00:42:43.260 --> 00:42:48.000
So it sort of come comes and goes. And I I think this is 1 of those periods now where
it's what's coming. Like,
405
00:42:48.300 --> 00:42:55.415
I I think it's safe to say that over the next year, probably, the overwhelming majority of my work will my project work will be in Python.
406
00:42:56.515 --> 00:43:12.445
You know, listen, as far as, you know, you mentioned you you're embarrassed to say whatever. Don't be. As far as I'm concerned, it's tool to task. Right? Like, I mean, if your clients are willing to pay you and they want Ruby, and that's the kind of work that you, you know, wanna be doing or need to be doing, then by all means, use Ruby. As far as I'm concerned,
407
00:43:13.860 --> 00:43:20.600
I love Python. I think it's a great language. I love Ruby. I think it's a great language, but they're just tools. Like, I think that this kind of, like,
408
00:43:20.914 --> 00:43:22.055
crazed partisanship
409
00:43:22.355 --> 00:43:24.214
is something that we can leave behind.
410
00:43:25.394 --> 00:43:27.974
I think I think especially in the polyglot
411
00:43:28.640 --> 00:43:33.779
era that we're kind of entering, so many companies now are as much as, you know, some are standardizing
412
00:43:34.160 --> 00:43:50.390
a lot or kinda saying like, well, what is Python good for? Let's use it for that. What is, you know, Closure good for? Let's use it for that or whatever the case may be. And I think that's an attitude that we should all embrace. I I I agree. I wrote this blog post probably like a year or 2 ago where I I said,
413
00:43:50.869 --> 00:43:55.845
I I made the analogy that Ruby is Oscar and Python is Felix from the Oscar.
414
00:43:58.065 --> 00:43:59.925
That is totally apt.
415
00:44:01.160 --> 00:44:05.500
And and, you know, you can learn from both of them and you can join both of them and each of them has their quirks.
416
00:44:06.040 --> 00:44:07.980
But but the the the the,
417
00:44:09.035 --> 00:44:10.335
like, knowing both
418
00:44:10.635 --> 00:44:12.895
is really where the the the the interesting,
419
00:44:13.435 --> 00:44:14.175
things happen.
420
00:44:15.329 --> 00:44:24.390
So just wondering if you've seen a change in the demand for Python skills in the time between when you first started using it or using it professionally at least and most recently.
421
00:44:25.045 --> 00:44:26.585
Would it have been up, down,
422
00:44:27.205 --> 00:44:28.025
or both?
423
00:44:28.885 --> 00:44:31.065
Up, up, up, up, up. It's it's crazy.
424
00:44:31.765 --> 00:44:32.265
So,
425
00:44:32.750 --> 00:44:33.490
you know, back
426
00:44:34.190 --> 00:44:36.290
in the stone age, you know, 20 years ago
427
00:44:36.750 --> 00:44:38.130
when I started using Python
428
00:44:38.430 --> 00:44:57.970
you know, when I when I got to Israel, basically, and I said to people I do you know, at that point, it was mostly Pearl and Linux. People looked at me like I had, you know, fallen off from the moon. Like, Pearl, Linux, open source? What is this thing? Oh, yeah. It's that it's that thing that's not Windows. And the
fact that only Windows and decent Hebrew support only made it harder for
429
00:44:58.349 --> 00:44:59.410
it to break in.
430
00:44:59.925 --> 00:45:02.505
But over the years, I've seen a growing
431
00:45:02.805 --> 00:45:05.865
interest in Python, and then it was like this explosion
432
00:45:06.165 --> 00:45:10.950
about 5 years ago. It was just it's just unbelievable. There's now, as I said, insatiable demand
433
00:45:11.490 --> 00:45:26.350
that, I even had these guys. I gave a talk about Ruby, I guess, about 2 years ago. And there were 2 people who came there, and afterwards, they came up to me and they said, listen. We're not really interested in Ruby. We're really interested in Python, and we're hoping that someone who came to your talk
434
00:45:26.730 --> 00:45:31.790
who knows Ruby will be interested in learning Python and working for us because we can't find anyone.
435
00:45:32.405 --> 00:45:36.105
Like, the demand is so crazy. They were, like, poaching people from other languages.
436
00:45:37.045 --> 00:45:39.625
And and I said, I I have bad news for you guys.
437
00:45:39.930 --> 00:45:43.550
The only thing rarer in Israel than a Python programmer is a Ruby programmer.
438
00:45:44.569 --> 00:45:46.349
So, good luck with that approach.
439
00:45:46.650 --> 00:45:50.065
But the the the demand is growing as I think the
440
00:45:50.765 --> 00:45:54.465
as I think for for a variety of reasons. First of all, companies are taking it seriously.
441
00:45:54.765 --> 00:46:00.290
They're realizing this is not a toy language. This is a serious language you can use to solve serious business problems. And
442
00:46:00.990 --> 00:46:09.105
and, I mean, what I have to tell people is in the sixties seventies, what we cared about with programming was that the darn thing worked. If it worked, we were delighted.
443
00:46:09.405 --> 00:46:12.545
In the eighties nineties, what we cared about was, did it work fast?
444
00:46:12.940 --> 00:46:15.520
And nowadays, what we worry about is is it maintainable,
445
00:46:15.900 --> 00:46:19.200
and does it let my programmers achieve maximum velocity?
446
00:46:19.955 --> 00:46:23.175
And so, Python just hits the sweet spot on that, because nowadays
447
00:46:23.555 --> 00:46:37.605
people are expensive and computers are cheap. And so if I can get a 10 times or 5 times, even 2 times increase in my programmer productivity, but it means I have to spend 20% more on on servers, Who cares? Right? Like, that's totally worthwhile.
448
00:46:38.225 --> 00:46:42.565
And a lot of the companies, I think, have done the math and said, yeah. That's good for us.
449
00:46:42.950 --> 00:46:57.965
Why should we spend tons of money? A lot of people come to come from MATLAB. Right? I've been surprised by the number of people I teach you are MATLAB users. They're like, yeah. We're gonna use scipy and NumPy because it's free. And do you know how much it costs to get these libraries in MATLAB? I said, actually, I have no idea.
They said, oh, they cost a lot
450
00:46:58.345 --> 00:46:59.165
per seat,
451
00:46:59.465 --> 00:47:00.285
per year.
452
00:47:01.270 --> 00:47:02.150
So so the
453
00:47:02.870 --> 00:47:11.585
it's really it's astonishing. It's astonishing to see the number of companies, people, places that are interested in Python. And, really, I think it's just it's just
454
00:47:12.685 --> 00:47:37.940
growing. I bet. And it must be really exciting actually for those people moving to Python from MATLAB because MATLAB is an awesome tool. But with something like Python, you have this incredibly rich ecosystem of not only can you do your numerical analysis, but you can bring in, like, you know, statistics and data analysis with Panda or, like, you know, or or image processing with PIL or 1 of these other tools. And, I mean, you just have this amazing,
455
00:47:38.560 --> 00:47:49.645
you know, plethora of of tools to draw from and you don't have to think in terms of well, gee, if I wanna use this, I'm gonna have to pay another $5, 000 or I I have no concept as the amounts involved.
456
00:47:50.010 --> 00:47:50.510
Money
457
00:47:50.970 --> 00:47:53.470
just isn't an issue because most of them are free.
458
00:47:53.770 --> 00:47:56.030
It's gotta be incredibly liberating for them.
459
00:47:56.730 --> 00:47:57.230
Right.
460
00:47:57.725 --> 00:48:04.065
Right. They no longer have to make decisions on do we have the budget to use this? It's is this is this the most appropriate tool?
461
00:48:04.560 --> 00:48:07.780
And people just like the language. They they they like it.
462
00:48:08.640 --> 00:48:11.220
They like its breadth. They like its depth. They like the community.
463
00:48:12.035 --> 00:48:12.855
And you see,
464
00:48:13.155 --> 00:48:35.150
I mean, in addition to for all the specific stuff, just today I had people in my class who, who are big users of R. Now I used R in my dissertation analysis. I love R. It's really great. And R's big claim to fame is that it does and it's a statistics language. It's a great language for that. And it has a huge sort of like, you know, PyPI has a huge number of packages. So r has a similar number of packages than what they call c,
465
00:48:35.835 --> 00:48:36.735
yeah, CRAN.
466
00:48:37.380 --> 00:48:39.400
Lots of packages for doing statistical analysis.
467
00:48:39.860 --> 00:48:52.875
But I see little by little by little, people are contributing to Python, to scipy, numpy, and all those packages. And I think in a few years, we might see Python eating R's lunch in that sense. It can't yet because it doesn't have the same
468
00:48:53.335 --> 00:48:54.795
plethora of modules,
469
00:48:55.410 --> 00:48:57.670
but it's getting there for enough people.
470
00:48:58.130 --> 00:49:02.549
And then you're gonna have another bunch of people who who are just, like, you know, stoked to use Python
471
00:49:02.849 --> 00:49:07.655
and are contributing to the community also. It's it's almost a a matter of increasing returns.
472
00:49:08.595 --> 00:49:12.960
Yeah. I've heard anecdotally about a lot of people moving from R to Python, particularly
473
00:49:13.260 --> 00:49:14.720
when they want to productionize
474
00:49:15.180 --> 00:49:17.279
what they're what they've been working on. So
475
00:49:17.579 --> 00:49:25.925
they may use R for doing the research and development phase of a project, but when then when they actually need to handle larger volumes of data, they move it over to Python because
476
00:49:26.305 --> 00:49:32.070
my understanding is that when you start loading large datasets into r, it just really starts to slow down. So
477
00:49:32.950 --> 00:49:37.130
Yeah. That's not the reason my dissertation was so late, but I'm willing to blame that.
478
00:49:40.645 --> 00:49:43.065
That's great. So what kinds of projects
479
00:49:43.365 --> 00:49:48.025
might you encounter that would cause you to choose a different programming language from Python?
480
00:49:50.530 --> 00:49:51.030
Question.
481
00:49:51.890 --> 00:49:57.349
Well, first of all, there's just, like, the the fun and experimenting kind of thing. Right? Like, so I I really
482
00:49:57.845 --> 00:49:59.625
I I wanna try more closure
483
00:50:00.005 --> 00:50:08.480
and and play with that, especially it's software transactional memory, which I would not be surprised if it ends up in in Python at some point in the future, but obviously doesn't exist now,
484
00:50:09.100 --> 00:50:14.800
because it just seems like an incredibly cool concept, fun thing to play with. And, of course, it's Lisp, so it must be good.
485
00:50:16.955 --> 00:50:28.970
Look. If I were writing and and no 1 should ever trust me if I do write such a thing. Right? But if I were writing an system, if I were writing a desktop application, 1 of those things, where speed is really crucial,
486
00:50:29.590 --> 00:50:38.135
then I think, you know, I would I would choose a a real systems programming language. If I'm writing something that needed to scale massively or that really, really, really needed threads
487
00:50:38.515 --> 00:50:39.895
that were truly parallel
488
00:50:40.275 --> 00:50:41.575
and could not use processes,
489
00:50:41.875 --> 00:50:43.175
I would use something else.
490
00:50:43.850 --> 00:50:44.650
I still
491
00:50:45.050 --> 00:50:55.285
because I've used Ruby and because I've used Rails and Sinatra for so many years, that's still sort of my first inclination of what to use for web stuff. So my website, for instance, runs in Sinatra.
492
00:50:55.665 --> 00:51:03.970
And, you know, it's totally great. It works fine for my purposes. If I were doing it from scratch today, would I use Flask maybe? Maybe. Maybe not. Who knows?
493
00:51:04.510 --> 00:51:16.655
But I would say for the the like, your average project like, here, for instance, here's a here's a, story. So I run I live in the city of Modi'in halfway between Tel Aviv and Jerusalem. And when I got to the city in 99,
494
00:51:17.115 --> 00:51:21.070
I started or I I guess I I sort of took over an email list for people who live here.
495
00:51:21.550 --> 00:51:27.890
15, I guess, you know, 16 years later, we now have 3, 000 people on the email list. And it's, you know, a local forum.
496
00:51:28.244 --> 00:51:34.825
And I decided a few months ago that it was just not worth my while to run an email server of my own anymore. So I decided to move everyone to Google Groups.
497
00:51:35.125 --> 00:51:38.460
Well, Google Groups only lets you I asked people to move themselves.
498
00:51:39.000 --> 00:51:50.994
Half of them did that. So that left me with 1500 people to move. And Google Groups only lets you add a 100 people at a time manually each day. So I wrote I was like, well, how can I figure this out? I know. I'll use Python. I know. I'll use sets.
499
00:51:51.375 --> 00:51:59.720
And, like, in a few lines of code, basically, I was able to download the list from my old system, download list from Google Groups,
500
00:52:00.020 --> 00:52:08.685
turn each of those using a set comprehension into a set, do set 1 minus set 2, grab a 100 people, and there you go. Now I have a 100 people I'm gonna move today.
501
00:52:09.145 --> 00:52:13.950
And and so it's those sorts of applications that are just so trivially easy to do in Python
502
00:52:14.250 --> 00:52:18.270
that I I find my like, that this is, like, clear that I would use it for.
503
00:52:18.994 --> 00:52:22.615
Yeah. Yeah. Yeah. But, like, system stuff, systems, embedded,
504
00:52:23.075 --> 00:52:31.250
web, still for me, I think I I would look at other languages first. But that might happen less and less over the coming years. I wouldn't be surprised, in fact.
505
00:52:31.869 --> 00:52:35.410
Right. I'm I'm glad you mentioned Closure. I I know I find that language
506
00:52:35.725 --> 00:52:47.250
particularly exciting as well, because of the software transactional memory aspect, especially when you start to realize that the way it handles data structures being atomic by default, like threading just becomes,
507
00:52:47.630 --> 00:53:00.605
you know, concurrency just becomes such a dramatically easier problem to reason about. I think that is a really cool concept and it isn't and that's gonna be 1 of my picks is 1 of his talks where he discusses some of the aspects of that. It's a really cool talk.
508
00:53:01.230 --> 00:53:02.290
Excellent. Excellent.
509
00:53:03.309 --> 00:53:09.809
So let's, unless anybody has anything else, let's move on to the picks, shall we? Reuben, why don't you list your picks?
510
00:53:10.375 --> 00:53:21.049
Okay. So I'm going to mention a few things here. First of all, so I I run a few different in addition in my copious free time, right, to my training and my development work and book writing and whatnot.
511
00:53:21.510 --> 00:53:24.569
So I've got this site that I've been running for a few year a few years.
512
00:53:24.869 --> 00:53:27.575
A few months now. It's about 6 months called dailytechvideo.
513
00:53:28.035 --> 00:53:28.855
So it's dailytechvideo.com.
514
00:53:30.194 --> 00:53:36.430
And the idea is that every day, I find a really great conference talk or other video that explains something
515
00:53:36.730 --> 00:53:38.270
typically about software,
516
00:53:38.650 --> 00:53:40.990
typically about open source dynamic languages
517
00:53:41.305 --> 00:53:48.799
or databases or web stuff. Because, hey. What do you know? I'm interested in open source dynamic languages and databases and web stuff. And,
518
00:53:49.200 --> 00:53:54.240
I have a little intro, and I describe the talk. And that's been going on, as I said, for a while. And,
519
00:53:54.799 --> 00:54:04.055
so far, it's been getting some attention, and I'd be very curious to hear from people what they think and, if there are any talks that they're interested in. Certainly, there are plenty of Python talks in there, not surprisingly.
520
00:54:05.120 --> 00:54:09.940
Number 2 oh, well, anyway, I'll I'll just move on to sort of other interesting picks.
521
00:54:10.480 --> 00:54:10.980
So
522
00:54:11.440 --> 00:54:12.400
I've been,
523
00:54:12.815 --> 00:54:23.960
among the places I go to do training is in China. I've been there, I guess, 6 times, 7 times in the last 3 years. I'm going twice more this year. And I just think it's super fun and super cool. I'm learning Chinese.
524
00:54:24.260 --> 00:54:27.400
I I just really, really enjoy traveling there. And so
525
00:54:27.714 --> 00:54:28.694
part of my obsession
526
00:54:29.395 --> 00:54:34.615
has been reading books about China and interesting analysis. And so a book that I read just recently,
527
00:54:34.915 --> 00:54:42.530
by Evan Osnos, who was the New Yorker's correspondent in China, it's called Age of Ambition, Chasing Fortune, Truth, and Faith in the New China.
528
00:54:42.910 --> 00:54:44.690
Brilliantly written, brilliantly recorded,
529
00:54:45.125 --> 00:54:45.625
fascinating
530
00:54:46.085 --> 00:55:05.165
book. Either if you do go to China or if you don't go to China, it's still worth reading about what is really going on there and how is the government trying to influence people, influence policy, and how are people sort of pushing back? And in what ways is it the way we would expect in the west and in what ways is it not? Peter Hessler also wrote some great books. He's another, good person who wrote about
531
00:55:05.465 --> 00:55:12.579
that. But I guess my final pick, it's only here once. Right? So I've gotta, like, give you the whole surveying. It's this book that came out a few a a few years ago, actually.
532
00:55:12.880 --> 00:55:16.579
It's called mindless eating, why we why we eat more than we think.
533
00:55:16.960 --> 00:55:18.740
And it's this guy named Brian Wensink
534
00:55:19.105 --> 00:55:21.125
who is a professor of
535
00:55:21.425 --> 00:55:22.645
marketing at Cornell,
536
00:55:23.345 --> 00:55:30.060
and he has done some of the most
brilliant psychology experiments I've ever heard of. Because basically what he does
537
00:55:30.360 --> 00:55:34.540
is he's trying to figure out what influences people to eat more or to eat less.
538
00:55:34.920 --> 00:55:43.645
So for instance, he'll go to a restaurant, but not just any restaurant, a test restaurant that's used by the restaurant school at Cornell. So it's designed for people to do experiments,
539
00:55:44.025 --> 00:55:45.325
usually experiments in management.
540
00:55:45.670 --> 00:55:56.535
And half of the room will hear 1 type of music, and the other half of the room will hear another type of music. And then they measure how much does the music affect how much food you order, and it actually has an effect.
541
00:55:56.835 --> 00:56:01.975
Or how much will you spend? Or what happens if you have empty plates? And so on and so forth. And so
542
00:56:02.390 --> 00:56:05.770
I I just find, like, the the experiments were brilliantly designed,
543
00:56:06.150 --> 00:56:07.210
hilariously funny,
544
00:56:07.510 --> 00:56:10.010
and, very insightful to human behavior.
545
00:56:10.715 --> 00:56:14.335
And I think I've covered now the world and psychology
546
00:56:14.795 --> 00:56:21.190
and computer stuff, so there's really nothing else that else left to, to recommend. So the the the those are my picks.
547
00:56:21.569 --> 00:56:25.910
That last pick is is awesome, I have to say. I mean, with, you know, obesity being
548
00:56:26.485 --> 00:56:30.345
viewed as kind of a worldwide problem in the developed world at least,
549
00:56:30.725 --> 00:56:36.970
you know, it's it would be really interesting to see some of the insights as far as why people do what they do. Very cool.
550
00:56:38.309 --> 00:56:44.410
So, those are some great picks. I'll move along to my picks now. I usually have a beer pick because I like craft beer,
551
00:56:45.015 --> 00:56:46.075
better for worse.
552
00:56:46.695 --> 00:56:54.170
And, I just encountered a local beer or comparatively local. I live in the Boston area. And so this is from Spencer, Massachusetts
553
00:56:54.710 --> 00:56:58.330
Town closer, you know, more around Mr. County, where I grew up.
554
00:56:58.790 --> 00:57:02.170
Spencer Trappist Ale, the Trappist monks there
555
00:57:03.075 --> 00:57:05.095
brew a really nice Belgian beer.
556
00:57:05.395 --> 00:57:07.655
And a lot of the time, I find that American
557
00:57:08.035 --> 00:57:08.535
breweries
558
00:57:08.994 --> 00:57:11.175
trying to do Belgian style beers,
559
00:57:11.770 --> 00:57:15.230
kinda with a few exceptions, fall flat in the face. Because
560
00:57:15.770 --> 00:57:19.950
the thing that makes Belgian beers kind of amazing is that they have this
561
00:57:20.410 --> 00:57:20.910
incredible
562
00:57:21.595 --> 00:57:26.734
sort of depth and fruitiness and and real complexity. Like, you know, it comes from the yeasts
563
00:57:27.035 --> 00:57:27.934
in those breweries
564
00:57:28.474 --> 00:57:34.160
being, you know, breeding in captivity for generation after generation, creating these just awesome flavors.
565
00:57:34.620 --> 00:57:38.160
And the trap is to kinda nailed it with this. It's it's 1 of my favorite
566
00:57:38.540 --> 00:57:39.040
domestic
567
00:57:39.565 --> 00:57:42.625
Belgian style ales and and I highly recommend it.
568
00:57:43.244 --> 00:57:43.744
So
569
00:57:44.125 --> 00:57:45.025
as far as
570
00:57:45.325 --> 00:57:46.305
technical picks,
571
00:57:47.060 --> 00:57:53.320
as I mentioned, Reuben inspired me to recommend pick Rich Hickey's talk, the value of values.
572
00:57:53.805 --> 00:57:56.464
And, this was a keynote for, I think,
573
00:57:56.845 --> 00:57:58.545
either a closure or a JVM
574
00:57:59.244 --> 00:58:01.665
conference where he basically talks about how
575
00:58:02.000 --> 00:58:05.860
so many of our basically, all of our current programming languages
576
00:58:06.320 --> 00:58:09.700
were designed around this place based programming paradigm.
577
00:58:10.155 --> 00:58:16.095
You know, was a memory saving technique where you had this place. It was a variable and you permuted the state,
578
00:58:16.475 --> 00:58:19.960
of that of that value variable to make various things happen.
579
00:58:20.339 --> 00:58:25.799
But in the modern era where we have gigabytes of memory, there's kind of no point to that model anymore
580
00:58:26.155 --> 00:58:35.695
and there's a new model that can really change the way you think about solving problems and make your life dramatically easier. So I love that talk. I recommend it highly.
581
00:58:36.700 --> 00:58:38.720
The next pick is a,
582
00:58:39.099 --> 00:58:45.895
a VIM plugin. My VIM is my editor of choice at least for now. I I like it quite a bit. I thought I liked you guys. Boy.
583
00:58:47.155 --> 00:58:50.775
Tobias uses emacs. You're all good. You have an emacs lover in our bit.
584
00:58:52.069 --> 00:58:58.170
And I used EMAX for years. I just I I got to the point where this shows how old I am. Back at the time,
585
00:58:58.470 --> 00:59:00.089
you know, we had old
586
00:59:00.625 --> 00:59:02.805
pre Intel Unix class workstations
587
00:59:03.345 --> 00:59:11.690
with very limited, you know, amounts of memory and disk allocated per user. And and I just got to the point where waiting for emacs to load was just like, I feel like I'm spending
588
00:59:12.070 --> 00:59:29.790
years of my life, which is really silly now because on our again, in our modern machines, there's absolutely no, like, emacs comes up like poof, you know, no problem at all. But I I hit by that point, I had switched to Vim and my my brain kind of works in Vim. But You Complete Me is a really neat editor for doing,
589
00:59:30.890 --> 00:59:31.630
auto completion,
590
00:59:32.250 --> 00:59:33.870
syntax based and otherwise.
591
00:59:34.485 --> 00:59:43.720
And it it's it's, written in c plus plus which is kinda nice as opposed to some of the others which are written in
higher level languages like Lua or or and the like.
592
00:59:44.119 --> 01:00:00.660
So it's pretty snappy and it it does the job. Building it and installing it is a bit of a pain but it's worth the it's worth the exercise to get there, at least in my limited experience. That's the correct 1. It's actually written in Python and the compilation step is actually just for the c plus plus c and c plus plus bindings for it.
593
01:00:01.140 --> 01:00:06.200
Oh, really? Oh, I didn't know that. Oh, very cool. Well, it's pretty snappy in any case. Thank you, Tobias.
594
01:00:06.500 --> 01:00:11.895
E Tobias actually recommended this to me earlier, so I was kinda passing that along. And my last pick is,
595
01:00:12.455 --> 01:00:23.920
something because I'm mostly a Mac guy. I, you know, do most of my day to day work on Linux servers but I love having a Mac as my primary desktop environment. There's this awesome little tool called SizeUp
596
01:00:24.540 --> 01:00:26.755
that lets you sort of assign,
597
01:00:27.375 --> 01:00:28.835
it basically lets you manipulate,
598
01:00:29.535 --> 01:00:33.235
OSX Windows in any way you can possibly, you know, imagine
599
01:00:33.650 --> 01:00:35.350
flipping them from monitor to monitor,
600
01:00:35.730 --> 01:00:38.710
adjusting their size and position etcetera etcetera
601
01:00:39.090 --> 01:00:40.869
all with, you know, a keystroke.
602
01:00:41.734 --> 01:00:49.755
And for me, I'm I'm partially blind and mice are like anatomy to me. Like, if I have to touch the mouse, my productivity takes a significant nosedive.
603
01:00:50.280 --> 01:00:58.105
So having a small tool like this, and it is commercial, but, you know, it costs some really small amount of money. I forget exactly what,
604
01:00:58.665 --> 01:01:01.325
is huge because I can really sort of, like,
605
01:01:01.625 --> 01:01:07.340
drive my environment like a Corvette as opposed to flailing around with the mouse like a really hapless person that I am.
606
01:01:08.700 --> 01:01:12.240
So, I think that's about it for pics for me. Tobias, how about yours?
607
01:01:12.940 --> 01:01:21.045
So harking back to the theme of practicing and using practice as a way to really learn a language, there's a really great web based
608
01:01:21.665 --> 01:01:23.525
environment called Check. Io
609
01:01:24.220 --> 01:01:26.160
that is, somewhat gamified
610
01:01:26.859 --> 01:01:27.920
way of
611
01:01:29.100 --> 01:01:31.440
performing a number of different practice problems.
612
01:01:31.820 --> 01:01:32.320
So
613
01:01:33.494 --> 01:01:41.900
it's got a nice really nice visual aspect to it, and there are different islands. And each island has a different sort of a theme to it. And each of the problems
614
01:01:42.200 --> 01:01:46.380
has a little bit of a story blurb to go with it that presents the particular
615
01:01:47.000 --> 01:01:49.180
problem that you're trying to solve using Python.
616
01:01:49.545 --> 01:01:52.605
And 1 of the things that really makes it great is that once you've submitted
617
01:01:52.985 --> 01:01:58.125
a solution, you can put it up for review, and other people in the community can
618
01:01:58.829 --> 01:02:07.170
post reviews on your code to either, you know, congratulate you on a job well done or to give you tips on different ways that you could achieve the same
619
01:02:07.944 --> 01:02:18.150
result, and you can also look at other people's submissions so that you can learn that way. You know, you're all solving the same problem and you can get an idea as to the different ways people are approaching it, so it's really interesting.
620
01:02:18.770 --> 01:02:20.230
Guido actually occasionally
621
01:02:20.849 --> 01:02:21.670
hops in
622
01:02:22.290 --> 01:02:24.770
and provides some reviews of people's codes. So
623
01:02:25.335 --> 01:02:26.875
Oh my god. That sounds terrifying.
624
01:02:30.375 --> 01:02:44.680
So, yeah, it's a cool little tool. I haven't had as much time to use it recently as I would like, but definitely worth a look, particularly for people who are looking for a way to get some practice in the language, but don't necessarily have a project that they're working on with it.
625
01:02:45.975 --> 01:02:47.515
My next pick is
626
01:02:48.855 --> 01:02:55.530
I guess you could kind of call it a toy, but it's something called snap circuits. And what it is is a way to
627
01:02:55.990 --> 01:02:58.330
introduce people to the world of electronics.
628
01:02:58.950 --> 01:03:05.015
So rather than having to have a soldering gun and a bunch of spools of wire to build different circuits,
629
01:03:05.555 --> 01:03:06.295
it uses
630
01:03:06.675 --> 01:03:18.615
snaps just like you would find on your clothing, and it's got a grid based board that the different components snap onto, and then they snap to each other to form the actual circuit. So it has batteries, and then it'll have
631
01:03:18.915 --> 01:03:19.415
photoresistors,
632
01:03:19.955 --> 01:03:24.535
regular resistors, DC motors, and all kinds of different components. And
633
01:03:25.750 --> 01:03:28.730
1 of the things that's really great about it is that you can actually
634
01:03:29.190 --> 01:03:36.515
start with a really small base kits to get a feel of something that'll work for you or your kids. I actually got it for my my older son.
635
01:03:36.974 --> 01:03:48.369
And then they have expansion kits. So you can rather than having to go out and buy the big kit all in 1, spend the extra money, you can actually just get an expansion kit that'll turn your small kit into the bigger 1.
636
01:03:48.705 --> 01:03:57.365
So it's a really great idea, really great execution, and it also comes with a project booklet of different circuits that you can use and teaches you about why it works the way it does.
637
01:03:59.050 --> 01:04:04.030
For my next pick, I recently got a new Android tablet, and I spent a little
638
01:04:04.605 --> 01:04:10.225
spent a little while researching it,
trying to figure out which 1 to get. I ended up going for the Nvidia Shield tablet.
639
01:04:10.925 --> 01:04:13.825
So it's marketed as a gaming tablet, but
640
01:04:14.170 --> 01:04:15.630
I don't use it as such.
641
01:04:16.330 --> 01:04:22.510
It's just a really powerful, really great tablet, 8 inch. It comes with a built in stylus, which is really useful
642
01:04:23.484 --> 01:04:27.825
for taking down quick notes where I would otherwise pull out a notepad and a pen.
643
01:04:28.204 --> 01:04:28.704
It's
644
01:04:29.085 --> 01:04:31.005
powerful. It's got 2 gigs of RAM and,
645
01:04:31.589 --> 01:04:34.329
some crazy number of cores with a NVIDIA
646
01:04:34.950 --> 01:04:37.450
GPU built into it. It's got a great screen.
647
01:04:37.910 --> 01:04:41.785
And for and for all that, it's actually really affordable price.
648
01:04:43.204 --> 01:04:50.450
And then the other pick that I'm gonna choose is the Samsung Go mic, which is what I actually have been using to record these episodes.
649
01:04:51.070 --> 01:04:53.570
It's really nice, well designed microphone,
650
01:04:54.190 --> 01:04:56.770
very small and compact, easy to transport.
651
01:04:57.494 --> 01:05:06.630
And 1 of the really nice things is that if you get 1 of the USB on the go adapters, you can actually plug the microphone into your tablet and have a portable recording
652
01:05:08.710 --> 01:05:10.650
studio. And my last pick,
653
01:05:11.029 --> 01:05:11.849
we recently
654
01:05:12.150 --> 01:05:13.289
signed up for,
655
01:05:13.750 --> 01:05:16.535
something called Zoho Apps, which is sort of
656
01:05:17.155 --> 01:05:22.695
a competitor to Google Apps, but it has a free tier as well as number of paid tiers and has a really
657
01:05:23.119 --> 01:05:25.299
pretty impressive suite of different
658
01:05:25.680 --> 01:05:32.740
products that you can use along with it. Most recently, I was poking around and found out that they actually have a password vault that you can use for sharing
659
01:05:33.185 --> 01:05:37.365
credentials between different people in an organization. It has mail, docs, calendar,
660
01:05:37.825 --> 01:05:40.005
and overall, it seems to be really well executed.
661
01:05:41.130 --> 01:05:44.670
So Yeah. I'm I'm pretty impressed with that 1 as well actually. Tobias
662
01:05:45.130 --> 01:05:46.190
prodded me into
663
01:05:46.490 --> 01:05:53.505
hit switching to it from from the goog for our show notes and, for, you know, our internal documents and the like. And
664
01:05:54.045 --> 01:05:57.345
I'm pretty impressed thus far. It's pretty it's pretty well put together.
665
01:05:58.299 --> 01:06:10.295
Alright. So, Reuben, we wanna thank you very much for taking the time to join us and speak with us today. And for anybody who would like to follow you or find out more about what you're up to, what would be the best way to
666
01:06:10.835 --> 01:06:12.455
find you or contact you?
667
01:06:13.875 --> 01:06:15.859
So my website learner.c0.il.
668
01:06:16.880 --> 01:06:18.980
From there, you can get to my blog,
669
01:06:19.359 --> 01:06:19.859
log.learner.c0.il,
670
01:06:21.119 --> 01:06:21.975
strangely enough.
671
01:06:22.455 --> 01:06:24.395
I'm on Twitter as atruvinmlerner.
672
01:06:26.055 --> 01:06:27.435
And so basically, everything
673
01:06:27.735 --> 01:06:28.475
I do
674
01:06:28.775 --> 01:06:37.900
sort of publicly, whether it's webinars, books, announcements, blog posts, either my blog or my Twitter feed or both, well, we'll have them. And I'd be delighted to hear from people,
675
01:06:38.200 --> 01:06:38.700
email,
676
01:06:39.185 --> 01:06:39.685
Twitter,
677
01:06:39.985 --> 01:06:45.445
you name it. I'm always delighted to hear from people who have questions or comments or just wanna get in touch and say hi.
678
01:06:47.185 --> 01:06:47.685
Great.
679
01:06:49.269 --> 01:07:00.615
Yes. Thank you very much for for for, taking the time to talk to us, Ruben. It's been it's been really great. My pleasure. Thanks so much for having me on, and good luck, with the podcast. I know it's relatively new, but hopefully, it'll be a big success.
680
01:07:01.075 --> 01:07:02.855
Thank you. We're hoping so as well.