Jeremy Satterfield

Full-stack engineer with over 19 years of experience building web applications and APIs primarily using Python and Django.

Over the course of the last several days I've been plagued with a couple pretty massive performance issues running MySQL under Docker(-compose) in our developer environments.

I recently realized I have several open-source projects I'm a maintainer or owner of which I've never really discussed on this site or on social media.

A couple of years ago I was working with a couple other languages beside Python and began to get frustrated with their virtualenv equivalents.

This past week I gave a short presentation at the monthly TulsaWebDevs meeting about setting up a secure website using Let's Encrypt.

Securing Your Website With Let's Encrypt Securing Your Website With Let's Encrypt (In Under 5 Minutes) Jeremy Satterfield http://jsatt.com https://github.com/jsatt @jsatt jsatt@jsatt.com Web developer for over 9 years.

Today I finally figured out the solution to a problem I've been trying to solve for a while.

So I just spent a couple of hours banging my head on a ridiculous PyMox mocking issue and though I'd share.

Anytime I see someone turning an instance method into a property on a Python object, I always have to step back and rethink whether it's really the right thing to do.

Update 2017-11-02: Celery 4 now adivises against inheriting from Task unless you are extending common functionality.

A while back I was working on my podcast client and ran into an issue downloading large files.

Similar to the object-level readonly field from my previous post, there are some cases where we want to exclude certain fields based on what object the user is trying to access.

DRF has tools to control access in a few ways.

Being a fan of good testing, I'm always trying to find ways to improve testing on various projects.

I've often found Python's context managers to be pretty useful.

Anyone running an API that can be reached by the outside world should most definitely be concerned that someone might pummel their server by making a massive amount of requests to that one endpoint that requires a bunch of on-the-fly calculations.

I'm a web developer and homebrewer from Tulsa, OK with an affinity toward open-source.

When working with Django Rest Framwork a few months back, there were a few road blocks that we ran into.

I'm a big fan of proper unit testing with mocking.

I've been huge fan of Django's class-based views (CBVs) since I first tried them out in Django 1.4.

This is going to be a fresh attempt to start blogging again on a regular basis.