Published April 15, 2015 ·
4 Minute Read ·
∞ Permalink
Managing different versions of Python is a pain. For example, if you’re working
on two projects that use different versions of Django, it gets really hard to
keep your virtual environments in order, and you have to remember to activate
the right one every time you work on a project. But what if you could just
switch between Pythons and virtual environments with a simple command; or, even
better, if you didn’t even have to issue a command but your tools knew which
version of Python and which virtualenv to use?
Published January 5, 2015 ·
2 Minute Read ·
∞ Permalink
One of the big things I took away from Just Fucking Ship (which yes, you
should buy and read immediately thanks for asking) was that I should plan for
the “worst case” scenario. I put that in quotes here because I’m not talking
nuclear war here; the worst case is closer to “the dinner is inedible ok fine
buy a pizza.” So when I was planning out the launch schedule for
setattr I thought of some worst case scenarios:
Published December 8, 2014 ·
2 Minute Read ·
∞ Permalink
Let’s cut to the chase: today, setattr season 1: developer tools is
available for preorder on Gumroad, with release January 6, 2015. It’s going to
cover:
Published December 1, 2014 ·
2 Minute Read ·
∞ Permalink
When you’re building API integrations, how do you test the part of your code
that talks to the remote server? I used to run a subset of tests against that
part of the code very infrequently, rather than testing all the code on every
commit. This saved a little time, but unfortunately still meant my tests were
dependent on an external service plus I wasn’t always testing the affected
code. That’s a really good way to get sporadic build failures!
Brian Hicks