"command": "source $(dirname ${config:python.pythonPath})/activate && make devserver",

"problemMatcher": []

},

{

"label": "Open Site in Browser",

"type": "shell",

$(PELICAN) $(INPUTDIR) -o $(OUTPUTDIR) -s $(PUBLISHCONF) $(PELICANOPTS)

if test -d $(BASEDIR)/extra; then cp $(BASEDIR)/extra/* $(OUTPUTDIR)/; fi

cleanbranches:

git remote | xargs -n 1 git fetch -v --prune $1

request again to the origin, or if requests should be auto forwarded from http to https, and

various other settings. The behaviour screen looks something like:

By default, all items for your distribution are governed by the settings on this Default

Behaviour. What's really cool/handy is you can define multiple behaviours based upon request

Tomorrow conference season continues for me as I'll be attending the 7th annual

Polyglot Unconference in Vancouver, a favourite event of mine. I'll likely blog about what

I see there, but you can also read about what I've seen in prior years in my posts from

If you've never done anything with the Django admin before, this might seem like

magic, 1-line to get a nice date filter in place:

As you click those filters, the changeset view will adjust to only those records

which meet that criteria. All this for 1-line of code. Yup, Django's pretty

Sweet, and this resulted in an image size of *381MB*, a savings of *NEGATIVE 2MB*.

Wait.... WAT?

So I *removed* some stuff and ended up with an image that's a few MB's *larger*?

How does that work?

Browser Caching" by setting a particular HTTP header on resources that don't change

often (ex: images). It'll look something like:

Specifically you set the

[`Cache-Control` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control)

By the time that "later" happened and I turned off the Lambda, I had accrued around 1.1

million Lambda requests:

But that's nothing:the real problem was that each one of those lambda calls represented

a PUT to a S3 bucket.

PUT's with S3 are actually one of the more expensive operations. For the `ca-central-1`

region where I host my stuff, it's currently $0.0055 per 1,000 of them. This sounds crazy

cheap, and it is, but when you're doing about 1.1 million of them, well, that adds up:

Queue the Iron Maiden -- 6, 6, 6, THE NUMBER OF THE BEAST!

But in the end I got a funny picture, this is the graph of my S3 bill for the month of

April:

Ouch, that's a pointy point in my pride.

Now when you change an image in a Git repo and do a `git diff` while in iTerm

you'll see a preview of the original image and the changed image. Example:

The above image is the original, the 2nd image is what I changed it to. Note

that because imgcat is iTerm specific, it won't work in other terminals. If

you do a `git diff` in a different terminal (ex: the integrated terminal in

VS Code) you'll see just the ordinary blank output:

Screenshots showing the settings:

cover: static/imgs/code_quality_2x.png

summary: A couple links related to pull requests and reviewing them, and things to do and/or avoid.

XKCD ‘Code Quality’, copied under CC BY-NC 2.5](https://xkcd.com/1513/)

Today I have a few links related to pull requests and doing code review. I've definitely

I currently use the "broken-ass giant desk that was a hand-me-down from someone

in my building when I was a teenager" desk. It weighs a metric ton, is ugly, the

gear I use. Often people in tech can be caught up with the latest & greatest (and most expensive),

but you can do a lot with not a ton of money.

cover: static/imgs/polyglotconflogo.png

summary: I got to go back yet again for the 7th Annual Polyglot Unconference in Vancouver. Let's recap.

YVR for the annual [Polyglot Unconference](https://www.polyglotconf.com). This event, now

in it's 7th year, has been a favourite of mine for some time as it's a great (and very

affordable) opportunity to network with a bunch of other technologists, hear about new

organizers to allow the dot voting to happen online rather than the mob around the post board.

A screenshot of how it looked while voting was going on is below:

It really worked quite well, was much more organized than the paper board, and it made it

much easier to figure out which talk to go to.

Note that these are both on by default (at least in the current version). Once you save

a Python file, Pylint warnings will show up in the problems view:

Note that that screenshot also illustrates how you can filter the problems view down to show just Pylint

warnings by entering "pylint" into the search box. Also note that clicking any of those will open up

This worked, but gave the following image:

Wait, what? Where's the text? And why is the image so small? Looking into the original

image before the cropping I found these problems were there. As it turns out, there's two

With this in place we get:

Ahh, much better.

tags: lambda,serverless,microservices,aws,python

cover: static/imgs/python-logo-master-v3-TM.png

use of [Lambda](https://aws.amazon.com/lambda/) and

[API Gateway](https://aws.amazon.com/api-gateway/) as a tool for building scalable microservices in Python. I largely

focussed on taking an existing tutorial, and building out some unit tests for it, as well as some supplementary scripts

`PASSLIB_BUILTIN_BCRYPT="enabled"` where you're running passlib. With Lambda, setting some env variables is easy, you

can do this in the web interface:

Doing this, I no longer got a `MissingBackendError`, but now there was a new problem:

Yup, apparently that plain Python version is in fact just way too slow. You can extend the timeout value for a Lambda

function on the Configuration tab under advanced items:

It's worth noting this can increase your costs with Lambda, as pricing is execution-time related.  With that change in

place (50 seconds is crazy, but just trying to get it to work), I got a new error, this time from API Gateway:

To begin with, here was my old bash prompt:

That prompt has a bunch of things in it, and shows:

Now open up a new terminal and you should see the default Starship prompt

which is actually quite sophisticated out of the box:

Your output may vary, as many of the items in a Starship prompt are dynamic

depending on your current context. In this you can see:

This gives a prompt like the following:

Pretty sweet, lots of dynamicism where needed, but still has all the things I

liked from before. Defintely took some time to get this just the way I liked it,

summary: Shell Tip Of the Day - Interactively deleting Docker images with Bash's select statement

![Sometimes when you learn about a hammer, everything looks like a nail....]

([source](https://devrant.com/rants/752222/if-all-you-have-is-a-hammer-everything-looks-like-a-nail-this-was-something-whic))

Sometimes when you learn about a hammer, everything looks like a nail.... In

Bash's `select` statement to interactively select untracked files in a Git repo.

Today I found another use for the `select` statement -- deleting local Docker

the input string on a double dash and then prints just the first column (the ID

in our case). We then just echo it back to `docker rmi`. This works, and I

tweeted it at Eric Promislow who was the person who demoed

which was where I first saw the trick:

summary: Shell Tip Of the Day - Selecting untracked files

Today's tip of the day is a follow up from something I learned at

to use ```select``` with the Bash shell for interactive goodness.

At Polyglot I saw an example that looked like this:

RELATIVE_URLS = False

FEED_ALL_ATOM = "feeds/all.atom.xml"

DELETE_OUTPUT_DIRECTORY = True