nvie.com

A few days ago, people started tagging me on Bluesky and Hacker News about a diagram on Microsoft's Learn portal.

We can all pretty intuitively understand how .some() and .every() predicate expressions on lists work.

Every developer has their own favorite Git tricks they use daily.

Today, I’m thrilled to publicly announce a new open source project that we’ve been using at SimpleContacts in production for months: decoders.

Yesterday, pip-tools version 1.0 was silently released, officially introducing the pip-compile and pip-sync tools, and replacing the current pip-dump and pip-review tools.

When was the last time you looked at code someone else wrote?

I was reading Igor Kalnitsky's blog post on why Python's map() is mad, and wanted to provide a different perspective.

In my previous post, Use More Iterators, I have outlined how to harvest some low hanging fruit when it comes to converting your functions to generators.

Yesterday, a friend asked me how I would solve a certain problem he was facing.

One of my top favorite features of the Python programming language is generators.

Occasionally I've run into situations of confusion on the exact differences between the following related concepts in Python: a container an iterable an iterator a generator a generator expression a {list, set, dict} comprehension I'm writing this post as…

I used to find writing command line tools tedious.

Update (Feb 2026): This article is really really old.

In building your Python application and its dependencies for production, you want to make sure that your builds are predictable and deterministic.

Reflecting on how I build software lately, I noticed a pattern.

Today, I’m open sourcing a project that I’ve been working for the last few months.

Just a quick post to let you know that I discarded my vim-pep8 and vim-pyflakes Vim plugins yesterday in favor of vim-flake8.

Lately I’ve been getting sick of working with datetimes and timezones in Python.

It’s been quite a while since I took the time to update this blog.

Mr.

A few weeks ago, I felt inspired by articles from Jeff Kreeftmeijer and Armin Ronacher.

Note: This blog post has been written in 2010, and a lot has changed since then.

Last week, I silently tagged gitflow 0.2.

After the overwhelming attention and feedback on the Git branching model post, a general consensus was that this workflow would benefit from some form of proper scriptability.

Note of reflection · March 5, 2020 ¶ This model was conceived in 2010, now more than 10 years ago, and not very long after Git itself came into being.

A few months ago, I wrote about automatically generating classes for your Core Data entities and how to automate Xcode using users scripts, such that, when your model changed, you only needed to run your custom script again and your intermediate model fil…

When designing a Core Data data model for your Xcode projects, you can choose to create Objective-C object wrappers for your entities, so that you can profit from type-safe code.

The Core Data framework rules, and its API is really really powerful.

Cocoa offers a nice visual editor for editing NSPredicate objects templates, called NSPredicateEditor.