Someone sent me this: "“Building Skills in Python” – Steven F. Lott".

I had a vague idea that this book would get some traction. This response was surprising. I guess I should get to work on the upgrades.

And focus on the "no-nonsense" comment.

Just saw this for the first time today: http://cwe.mitre.org/top25/ I'd always relied on this: https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project Both are really good lists of security vulnerabilities. I once had to listen to a DBA tell me that "we don't know what we …

I've been unsubscribing from some junk email recently. The user story is simple: As a not-very-interested person, I want to get off your dumb-ass mailing list so that I don't have to flag your crap as spam any more.

The implementations vary from good to evil. Here's what I've found …

During chapter technical reviews, the question of technical depth has come up time and again. Essentially, in every single chapter. In the older Building Skills in Python book, there are a number of topics that feel "digressive" to the reviewer and editor. Too much depth.

However, there are a number …

Just started learning about "Hackerspace". Without really knowing what I was doing, I fell into the 757 Labs Hackerspace. The 757 Python Users' Group, specifically. What a great idea. Bright people. Interested in the same area of technology. It's like hanging around with sailors at a marina.

Read this: How Ma Bell Shelved the Future for 60 Years.

AT&T firmly believed that the answering machine, and its magnetic tapes, would lead the public to abandon the telephone.

How many good ideas are set aside by managers who simply don't have a clue what users actually want …

Read this: "How to explain why multi-threading is difficult".

We need to talk. This is not that difficult.

Multi-threading is only difficult if you do it badly. There are an almost infinite number of ways to do it badly. Many magazines and bloggers have decided that the multithreading hurdle is …

The "default" template I chose was too narrow for presenting code samples. Changed it.

Here's a pretty simple set of use cases for a code-kata database application.

This is largely transactional, not analytical.

It's a simple inventory of ingredients, recipes and locations.

Tonight (May 25th). Red Dog. Colley Ave. Ghent. I'll be wearing my Stack Overflow shirt. I'll be there about 7. I know that at least one other person won't be there until 8.

The Meetup link.

I like this meetup idea a lot. Probably because the WFH life-style is a …