13:34
ORMs and Their Discontents: PGXPUG Day OSCON 2010 Presentation
Here are the slides for my talk at PGXPUG Day OSCON 2010.
13:34
Here are the slides for my talk at PGXPUG Day OSCON 2010.
13:30
The slides from my talk, Introduction to PostgreSQL are available here.
14:19
The archive video for the February 9, 2010 SFPUG meeting is now available: Read the rest of this entry »
19:46
Brent Simmons has a very good piece about switching away from using Core Data to using SQLite directly in his iPhone app. Substituting “any common ORM” for “Core Data” (which, after all, is all Core Data is) and “any SQL database” for SQLite, he encounters the most common problems that plague those trying to develop scalable solutions on top of ORMs.
13:21
The archive video for the December 8, 2009 SFPUG meeting is now available: Read the rest of this entry »
16:02
The archive video for the November 10, 2009 SFPUG meeting is now available: Read the rest of this entry »
19:23
In part 1, we ran down a list of the standard Django features for controlling transactions. Now, we’re going to look at some ways to optimize how these tranactions happen.
14:40
Django has quite a bit of code in it devoted to transaction management. Although the documentation goes into quite a bit of depth on transactions, I’ve never felt that the docs by themselves let you build a good mental model of how transactions actually work. So, I decided to approach it experimentally: Build a small Django app, and see how the various options actually work.
20:13
I love object-oriented programming. The first time I ever encountered an OO language or framework (Object Pascal and MacApp, thank you for asking), it was as if the heavens opened. It simply made sense to me as a way of structuring programs, and I’ve been wedded to it ever since. (As it turns out, if you do the right paperwork, you can marry a concept.)
So, I think object-oriented programming is the bee’s knees. And, in this post, I’m going to tell you to not use it.
12:22
No, I’m not going to write another Git vs Mercurial post that really digs into them, because… well, if you are using one or the other, it is probably for reasons that don’t have much to do with your preferences.
In strictly my opinion, for personal use, I like Mercurial. For projects that use Git, I use Git.
My two sentence summary is: Mercurial is your smart friend who likes to explain things to you. Git is your genius coworker who sighs and rolls his eyes every time you ask him a question.