Skip to main content

PyCon SQLAlchemy tutorial slides

My SQLAlchemy tutorial went pretty well for the most part. It was a fast pace but most people kept up pretty well. If I did it again I would add more of an intro to ORM in general for people who had never used one, but over half the attendees had used SO or django's or tried SA already. I would also paste more code from my slides into the samples download to save people typing during the exercises (I had some, but I would do more next time).

I think most people liked it; the main exception was one fellow who was in way way over his head and visibly pissed about it. (I used a list comprehension at one point and he had no idea what it was.)

The slides are here. (The .py files referred to in the slides have also been moved to the jellis/ subdirectory.)

Comments

Tim Parkin said…
You'll never get the level right for everyone and it's a lot better to pitch higher than lower. At least the guy went away with a big list of things to learn about which should be worth the price of admission itself :-)

As it is, I've looked through the slides and I really, really wish I'd been there .. Congrats!!

Tim
10:46 AM
Lee Capps said…
I knew the tutorial would be over my head (it said so right there in the course description) and signed up anyway for precisely the reason Tim gives. Realistically, I'm not going to learn SQLAlchemy and stored procedures and triggers and so on in a couple of hours. But now I know what I've got to learn if I want to use any of these tools.

That having been said, I did at least know what a list comprehension was, and I've used SQLObject a bit.

My only suggestion would be to encourage pairing on your exercises. I didn't have a clue where to start and didn't at first have your slides to refer back to; I don't think I was the only one. So waiting around for the solution was a bit of dead time.

Cheers!
3:19 PM
Jonathan Ellis said…
Pairing is a good suggestion. Thanks!
6:09 AM
Anonymous said…
is there possibility to get complete lecture toghether with slides?

The best would be flash movie (or sth) but simple audio file would be enough.

If not, Jonathan - maybe you can record it?
2:52 AM
Jonathan Ellis said…
Sorry; I'm happy to post the slides but I don't have an extra three hours to repeat the lecture/explanation into a mic. (Let alone post-processing to clean things up.)
7:55 AM
Post a Comment

Popular posts from this blog

A week of Windows Subsystem for Linux

I first experimented with WSL2 as a daily development environment two years ago. Things were still pretty rough around the edges, especially with JetBrains' IDEs, and I ended up buying a dedicated Linux workstation so I wouldn't have to deal with the pain.  Unfortunately, the Linux box developed a heat management problem, and simultaneously I found myself needing a beefier GPU than it had for working on multi-vector encoding , so I decided to give WSL2 another try. Here's some of the highlights and lowlights. TLDR, it's working well enough that I'm probably going to continue using it as my primary development machine going forward. The Good NVIDIA CUDA drivers just work. I was blown away that I ran conda install cuda -c nvidia and it worked the first try. No farting around with Linux kernel header versions or arcane errors from nvidia-smi. It just worked, including with PyTorch. JetBrains products work a lot better now in remote development mod...
Post a Comment
Read more

Python at Mozy.com

At my day job, I write code for a company called Berkeley Data Systems. (They found me through this blog, actually. It's been a good place to work.) Our first product is free online backup at mozy.com . Our second beta release was yesterday; the obvious problems have been fixed, so I feel reasonably good about blogging about it. Our back end, which is the most algorithmically complex part -- as opposed to fighting-Microsoft-APIs complex, as we have to in our desktop client -- is 90% in python with one C extension for speed. We (well, they, since I wasn't at the company at that point) initially chose Python for speed of development, and it's definitely fulfilled that expectation. (It's also lived up to its reputation for readability, in that the Python code has had 3 different developers -- in serial -- with very quick ramp-ups in each case. Python's succinctness and and one-obvious-way-to-do-it philosophy played a big part in this.) If you try it out, pleas...
9 comments
Read more

Why PHP sucks

(July 8 2005) Apparently I got linked by some PHP sites, and while there were a few well-reasoned comments here I mostly just got people who only knew PHP reacting like I told them their firstborn was ugly. These people tended to give variants on one or more themes: All environments have warts, so PHP is no worse than anything else in this respect I can work around PHP's problems, ergo they are not really problems You aren't experienced enough in PHP to judge it yet As to the first, it is true that PHP is not alone in having warts. However, the lack of qualitative difference does not mean that the quantitative difference is insignificant. Similarly, problems can be worked around, but languages/environments designed by people with more foresight and, to put it bluntly, clue, simply don't make the kind of really boneheaded architecture mistakes that you can't help but run into on a daily baisis in PHP. Finally, as I noted in my original introduction, with PHP, ...
30 comments
Read more