Search Results: "Andrew Pollock"

24 December 2009

Andrew Pollock: [life] Homeowners!

There was a minor hiccup yesterday. Our mortgage broker called me up towards the end of the day in a flap because something had gone wrong on the seller's side of things, and their bank hadn't accepted the transaction or something. I still don't know the full story. Something about them missing a mortgage payment possibly. Anyway, she was able to arrange for funding and closing today, instead of funding yesterday and closing today, so the outcome was still the same. Now the real fun starts. The first thing I did tonight was program the garage door opener into the Prius' HomeLink thingy built into the rear vision mirror. It's always nice to be able to use a feature, even if it's taken 4 years.

22 December 2009

Andrew Pollock: [life] All that's left is to pick up the keys

Yesterday morning we went to the title company to do all of the paperwork for the condo purchase. I'm still not entirely clear on the whole process, but basically we signed a ton of disclosures and the loan documents, and the whole lot got notarised. I found the thumbprint requirement rather amusing. So the loan should fund today, and the title change will register with the county on Wednesday, and by tomorrow afternoon, we should have the keys. We then had to do a walk through to sign off that the property hadn't turned into a pumpkin since we put the offer in. It was only the second time I've been able to see the place, so it was good to take another look. Sarah's been doing lots of running around to organise quotes for the kitchen renovation and measure the windows for curtains, so she's seen it many more times. There's going to be a few little odd jobs that need doing around the place. There's a few lights that aren't working (presumably just bulb replacements. There's an outside cupboard that's falling apart. There's a little water feature that I think we'll just get rid of, as the pump is a waste of electricity and it'll just breed mosquitoes otherwise. It's going to be home.

2 December 2009

Andrew Pollock: [life] We're under contract

Well that all happened rather quickly. This morning, we met with our agent to go through all of the offer paperwork, at the bright and early time of 7:30am after (for me at least) a bad night's sleep staring at the ceiling. It wasn't that bad. A lot of disclosures, a lot of initialling and signing. Here's what the stack of paperwork looked like: The paperwork for our offer on the condo The existing building reports didn't come back with any red flags. There's a little bit (around $1,000) of termite damage. We put in the contract that the sellers have to fix that. The hot water tank needs to be strapped to the wall to be in earthquake compliance. We put that in the contract too. A couple of hours later, we'd got all of the paperwork out of the way, and Nick said he'd present the offer to the seller's agent at 3pm. I got a phone call at about 5pm from Nick saying that they'd accepted the offer, with all of our conditions, so we're all ready to go for closing on the 23rd. Apparently the reason the sellers are so motivated is because they borrowed against the equity in this condo to buy a house, so they're eager to close the deal. We managed to negotiate the price down slightly to $519,000 (anything lower would have been a short sale for them, and we already know all about what that can entail). Even for that price, they've made a tidy profit on the $180,000 they paid 14 years ago. So this is working out really well, timing-wise. We'll close on the 23rd, go visit Chris, Bri and Clara in Atlanta for Christmas, and then have all of January to do any work on the place before our current lease expires. Just got to wait for the finance approvals and an international money transfer now. I'm slightly miffed that I booked it yesterday at 0.90 cents, and the AUD has risen to 0.92 cents today.

1 December 2009

Andrew Pollock: [life] I think we've been bitten by the bug...

So we pretty much gave up on the condemned house. The more we hear about it, the worse it looks. Our agent got some paperwork on the red-tagging today. Apparently the large room out the front used to be a car port, and enclosing that was done without a permit. There's also a standalone room out the back that has had a bathroom added without a permit. Apparently the owner is getting fined $2,500 a day by the city until it's either brought into compliance or reverted. No idea if that's actually being paid, or who's responsibility it would become in the event of a sale, so we'll just quietly back away from that whole mess and pretend it never happened. Sarah was poking around Redfin again last night and found this property, for less than what the condemned house was going for (granted, this is a condo, not a house). We got our agent to show it to us today, and we really liked the look of it, so we're going to put an offer in on it and see what comes of it. We have to spend about three hours with our agent tomorrow morning going through paperwork. Wee. It certainly seems like a good time to be buying. Interest rates are low, the AUD is high against the USD, and prices are down.

30 November 2009

Andrew Pollock: [tech] Review: iGala digital picture frame

Now that I'm not letting the cat out of the bag (I bought these as gifts) I can write a review. The use case was pretty simple: I thought it'd be a cool Christmas present for our parents to give them something Internet-enabled that would give them regular updates on their grandchild (when he/she arrives). I was thinking a picture a day type of thing. So I hunted around for a WiFi-enabled digital picture frame, and found the iGala being sold pretty much exclusively by ThinkGeek. The reviews seemed pretty good. I know WiFi-capable frames have been around for a few years, but they always seemed to be pretty lacking in terms of WiFi functionality. Like they wouldn't do any security, or they'd only do WEP. This particular product claimed to do the whole gamut, including WPA2. The fact that it was a touch screen and ran Linux also made it appealing. So I ordered a couple of them for a few weeks before we headed to Australia, with the intention of making sure that they'd work. Here's the highlights. WPA2 didn't work (nor did WPA) Despite the software on the frames claiming to be able to talk WPA2, the frame would not associate with my Linksys WRTU54G-TM. I had to drop it all the way back to WEP to get it to connect. For me, this was the most disappointing failure. I bought the product specifically on the strength of its claim that it supported WPA2, and it just didn't work. It was also pretty impossible to debug the failure. I downloaded the latest firmware update, and that added additional settings for TKIP or AES when selecting WPA2, but neither option helped. The automatic updates are brain-dead Speaking of downloading firmware updates, the latest firmware that I downloaded and installed on the frames added automatic over-the-air firmware updates. Nice enough feature, except for the implementation. The frame tried to make an HTTP GET request for a non-existent file, every 6 seconds. So the frequency of checking alone is totally ridiculous, but couple with this the fact that it's making a GET request (this is what $DEITY invented the HEAD request for, people!) and the website has a "friendly" 404 Not Found page that weighs in at a little over 10 Kb. By my calculations, that's nearly 150 Mb of failed update checking traffic a day. Taking these frames to a backward country like Australia, where ISP users still have monthly quotas, gives the frame a pretty horrendous running cost in terms of traffic. Not to mention the outbound bandwidth requirements for the server hosting the updates. Crikey, the mind boggles. I'd have thought checking once a day and on power on would be perfectly sufficient. Transitions are unavoidable It may be just me, but I hate cheezy transitions. Digital picture frames tend to come with a myriad of them, but they all look cheap. It's impossible to tell the frame to just change the picture, it has to use at least one transition effect all the time. It defaults to randomly choosing from all the available ones. At least you can tone it down to just one. Automatic on/off time I liked that it was possible to configure operating times. No need to have the thing chewing power 24x7. It just seems to turn off the backlight outside of the programmed operating hours, so it's still doing the lame uber-frequent and bandwidth-intensive checking for updates even when it's "off". Photo check frequency is configurable Another nice feature was the ability to check for new photos at varying intervals. What I wanted for my parents was to just update once a day, so they'd get a new photo every day (assuming we put a new one in the Picasa web album that it's checking). This was very doable, and coupled with the automatic on/off time, means they should wake up to a new photo every day (that we change it). Built in photos are a bit too sticky There's 3 or 4 in-built photos as part of the firmware. If there's nothing accessible or available online, it'll cycle through these. Somewhat annoyingly, you need to have at least two photos in your online source for it to stop wanting to incorporate the stock photos in the mix. The workaround is to put the same photo in the online album twice, so you don't realise it's switching between two images. Lame, but it works... Touch screen UI was adequate Given the alternative user interface for digital picture frames is a little IR remote control and some dinky menus, the iGala was nice to configure. A full on-screen QWERTY keyboard pops up for entering WEP/WPA/WPA2 keys and configuring the Picasa/Flickr connections. Fairly responsive support The main near-showstopper for me was the lack of advertised WPA2 support. I emailed the Aequitech support folks quite a bit during my "evaluation" period. They got back to me fairly quickly most of the time and wanted to know exact details of my setup so they could reproduce it in the lab. They'd be well served having an actual ticketing system, instead of hiding behind an email address, as it made it hard to keep track of the multiple issues I was raising with them. It's written in Lua?! I have no familiarity with Lua, other than I know of its existence as a programming language. I'm curious as to what their motivation was for this language choice. All of the Lua code shipped in the complete firmware refresh ZIP files is bytecode. I have no idea if it's possible to decompile it. The CPU architecture would appear to be a Blackfin based on the few compiled binaries included in the full firmware. Easy to update Prior to the new update "functionality" I've already railed against, it was pretty easy to update. Download a ZIP file and a shell script, put them in the root directory of a USB key, and plug it into the frame and stand back. The updates don't seem to cryptographically verified (even the over-the-air ones), so I wonder if it's possible to break into the frame by way of a cleverly crafted "update". I have no idea what breaking into the frame would buy you. I don't know what sort of computing power they have. Conclusion I still think the iGala is a reasonable, if somewhat immature product. If the software is going to be actively worked on, and the support people continue to be responsive, then I think it's got good potential. For the price, I expected a more polished product, though. I received an email from their support people shortly after returning from Australia saying that they'd fixed the WPA2 problem. Unfortunately I had no intention of trying to remotely talk my parents through how to reconfigure their access point or the frame (interestingly WPA2 didn't work with their Linksys WAG54G2 either, so I'd love to know what WPA2 devices it was tested with), so it's 128-bit WEP until I next go to Australia.

Andrew Pollock: [life] When it looks too good to be true...

Yesterday, we managed to inspect the property that was for sale that we'd discovered. I think you could best describe it as a renovator's delight that's had a bit of work done on it. The kitchen is pretty new. The bathrooms are pretty good. There's some cracking around the place, and the floating floor looks like it's a bit of a dodgy job. That said, it definitely had potential, and for the asking price, assuming it wasn't structurally unsound, was something we could see ourselves doing up and flipping when we finally move back to Australia. So our agent told us we needed to get pre-approved for finance as the next step, and hooked us up with a mortgage broker, who was able to see us today. She said that pre-approval would be no problem, and we got what seemed to be a ridiculously good rate for a 5 year adjustable rate mortgage. Our agent called us back tonight and told us that there was another offer on the table for less than the asking price, and that the property had been red-tagged. It would appear that none of the modifications had permits. He's going to check with the city tomorrow to find out exactly what the nature of the red-tagging is all about, and what would be involved to get the property un-red-tagged, but I've got that feeling that it's going to be better to just walk away from it at this stage. So that's how we've spent our weekend. Speculating on real estate.

28 November 2009

Andrew Pollock: [life] Thinking about moving

Our lease runs out at the end of January, and we're thinking about moving to a bigger place. In the four years we've been here (yeah, we just crossed the four year mark the other day) we've often thought about trying to buy as well. We go through these phases where we really feel like buying, then we run the numbers and run screaming back to the warm bosom of renting. A couple of months ago we had the most serious foray into buying. We'd just checked out the models for Mondrian and we really liked the floorplan for Bleu, and found the price to be the least breathtaking of anything we'd looked at in the Bay Area. I got as far as talking to mortgage brokers and running the numbers, and the things that killed it for us were the property taxes and homeowners association fees. The monthly repayments would have been doable, but it'd have really been a ball and chain. We're over here to see the country as much as anything else, and if the mortgage is going to be a significant impedance on our ability to travel, then there isn't really any point in doing it. So we sadly passed up on Mondrian. The three bedroom townhouses in our current complex are going for around the $2500 a month mark, which is a pretty serious jump on what we're paying now for our two bedroom one, so Sarah's been scouring Craigslist for anything better. She found a 2 bedroom plus loft condo being rented privately in Mountain View, which we took at look at on Wednesday. The immediately downsides are it's older (the kitchen and bathroom are really a bit dated) and has no data cabling (this is something I've really loved about our current place) and no microwave oven included. The upsides are it's significantly bigger (about 500 square feet larger), the kitchen has heaps of cupboards, it has a washer and dryer, a lock-up garage, a small, fairly private yard (the rent includes a gardener), and it has what looks like a communal garden bed (the thing that really caught my eye were the compost bins). So I think overall, as long as we can live with the kitchen and bathroom, it's going to be an improvement on where we are now. The windows are all double glazed, so it should be fairly well insulated. It's got a gas furnace and gas hot water, and I think the landlord pays for the water, so I think the utilities would at best come out the same as what we're paying here. We've decided to put an application in for it and see what happens. The landlord is living overseas, so we're dealing with a real estate agent for the letting. Apparently we'd be paying the rent via PayPal or something. He's got a home warranty arrangement for maintenance, which sounds like it'll be pretty good. Meanwhile, Sarah was scouring Redfin and found a house nearby that is for sale (a short sale), which is pretty reasonably priced. We've called up a real estate agent, and we're taking a look at it tomorrow, just because we can.

Andrew Pollock: [tech] mirror.linux.org.au upgraded

I took advantage of the four day weekend for Thanksgiving, and finally got around to upgrading mirror.linux.org.au from Debian Etch to Lenny. The upgrade went fairly well. Notably, Drupal completely blew up, but it looks like we were still running the package from Sarge, as Drupal wasn't in Etch at all. I cut my losses, installed Drupal 6 and put something basic together from scratch. MoinMoin upgraded fairly painlessly, and I figured out how to fix Cacti for my installation at home at the same time, so that was a general win all round.

23 November 2009

Jon Dowland: shell scripts

Russell Coker writes about shellscripts. I have a different suggestion. Whenever you think that a shellscript is the right solution to a problem, you are mistaken: do it in a proper scripting language instead. Having access to proper data structures will mean you don't have to contort your code to fit values into scalar strings, or write loads of temporary files, or call cut/awk/sed/grep etc. repeatedly on the same inputs to get at different fields, etc. etc. etc. I reckon nine times out of ten it's the right decision. But when you just have to use a shellscript, use set -e (as Andrew Pollock points out, this is safer than putting it on the hashbang line and set -u too.

21 November 2009

Andrew Pollock: [tech] LVM gaining the ability to merge snapshots

I love LWN. It's the best value for money way of keeping abreast of what's going on out there. I also love LVM. I'm thrilled to learn from a comment on this article about Btrfs, that LVM is soon to gain snapshot merging support. This is going to be absolutely fantastic for rolling back upgrades that go bad. I can't wait.

20 November 2009

Andrew Pollock: [tech] "#!/bin/sh -e" considered harmful

Russell Coker advocates putting -e on the shebang line of shell scripts. I disagree. From my experience this is extremely unhelpful to people who may be debugging your shell scripts in the future. Consider this, you've added -e to the shebang of a script, and some poor schmuck down the track is trying to debug why it spontaneously exits. What's the most obvious way to do this? Run the script with sh -x or bash -x. What happens when you do this? The shebang is completely ignored, and the script is directly run by the shell interpreter. If the person doing the debugging doesn't happen to transpose all of the shell options on the shebang line to the manual shell interpreter invocation, you're going to get different behaviour. So I advocate an explicit set -e on the second line of shell scripts instead. As much as making shell scripts set -e is a good practice, it drives me absolutely batty having to deal with scripts that spontaneously exit as soon as something they run exits non-zero. Particularly when you've chained a bunch of shell scripts together, or have one sourcing a bunch of script fragments from a directory. For this reason, I prefer to write in Bash and use an exit handler, to make it very obvious when a shell script has abended due to set -e.

19 November 2009

Andrew Pollock: [life] Here we go again (~27 weeks to go)

It's looking all good, so we're game to tell the world: Sarah is 13 weeks pregnant! She had the nuchal translucency ultrasound today (which, due to the tight timing required for it, I was totally bummed to be unable to attend). The scan came back all clear, which is an enormous relief. In the nausea department, poor Sarah has had a much worse time than with the first pregnancy. Particularly on the flights to and from Australia. This makes me think it's going to be a girl (just because the nausea characteristics are totally different from the first time around). It's amazing how fast they grow in just a few weeks. Here's the ultrasound from 10 weeks: 10 week ultrasound And here's the ultrasound from 13 weeks: 13 week ultrasound

16 November 2009

Andrew Pollock: [life] Blogging on a plane!

Well, here I am, sitting in a chair at 10,000 feet (or whatever the altitude currently is), using WiFi. Writing a blog post. And we still don't have flying cars. I'm on my way to Dallas for the Ubuntu Developer Summit for the 10.04 (Lucid Lynx) release. Being an LTS release, this is of particular interest for what I do at work. Sarah's still in Australia (well she's actually on a flight to LAX as I write), so I took the VTA light rail + shuttle to the airport. I must say, aside from not being particularly speedy, it was a pleasant experience. I've finally cracked open The Audacity of Hope, which I received for Christmas or my birthday last year. I'm really loving the renovated San Jose airport. Now that all of the check-in counters have moved downstairs, they've about quadrupled the space the TSA has, which makes getting through security a much more pleasant experience. Add to that, the nice lady in the Admiral's Club kindly reseating me in an exit row, all by myself, and this is a pretty sweet trip so far. http://www.youtube.com/watch?v=8r1CZTLk-Gk

12 November 2009

Andrew Pollock: [life] RIP Stumpy

Well, she didn't make it. The diuretic the vet put her on to reduce the fluid around her heart and lungs was also causing kidney failure, so her condition wasn't treatable. She was euthanised some time today. Our neighbour Carol was able to be there with her. It really sucks that we weren't able to be there. It's still a real shock how she was a perfectly healthy cat last Friday, and now she's dead. Sarah's going to really miss her, as she was exceptionally got at being attuned to her (Sarah's) moods. Whenever Sarah was sick or just down, Stumpy would curl up with her.

11 November 2009

Andrew Pollock: [life] Well this just sucks

I'd had bad feelings about this trip, mainly because it was so short. I didn't expect this to happen though... Back story: Smudge has always been fairly wary of Stumpy, for some unknown reason (perhaps her boisterousness?) It came to a head when we did our road trip to Atlanta. We got back home, and Smudge had pooped in all the wrong places, and was hissing and growling at Stumpy whenever Stumpy looked at her the wrong way. The cat sitter plead ignorance, but something must have happened while we were away. Smudge has been pretty hopeless around Stumpy ever since. One theory was that maybe Stumpy (or Smudge) had some health problem, so we had them both checked out and no red flags were raised. The other option was to put Smudge on Prozac for a while to see if she settled down. I didn't like the idea of drugging her, so we've opted to separate them for a while. Smudge is in our bedroom and Stumpy and Lily have the rest of the house. Smudge and Stumpy only have supervised time together. We've tried a bit of play therapy as time permits, but it hasn't made much of a difference. So fast forwarding to now, and we didn't want to leave Smudge in our bedroom all by herself for the week, so we thought we'd put Stumpy in a cat boarding place, since we figured she could handle it, and let Smudge and Lily have the run of the house. Our neighbour Carol was going to check in on Smudge and Lily. All good. I think it was yesterday (my brain is not dealing with the various timezones plus jet lag) Sarah got an email from Carol saying that the cat boarding place had called her because Stumpy hadn't been eating, and was all lethargic. Carol went and brought her home, and she didn't do much better at home, she was just lying around, so she took her to our vet. She was having breathing problems, and generally showing symptoms of congestive heart failure! Her blood work was otherwise okay. The vet said they couldn't do much and needed to send her to a specialist vet at Campbell, where they could do an ultrasound on her heart. This is where she currently is, in an oxygen tent on diuretics for fluid around the heart/lungs. The prognosis isn't very good at all. She managed to make it through the night, but I don't know if she's going to make it until I can get home. I've moved my flight a day earlier to Friday night, so I can get out to the vet's on Saturday. The vet was saying that even if she does make it through this, her long-term prospects aren't good. Maybe a year. This is only a four year old cat! The vet said she has an enlarged heart, so it's some sort of congenital condition she's always had, but was probably triggered by the stress of being in the boarding place. It's just come as a total shock to us as she's always been really healthy, and the most hyperactive of the three cats. Sarah, being the cat lover that she is, is particularly upset, because this is "her" cat, and she feels terrible because Stumpy is all by herself. I'm really hoping Stumpy can at least hang in there until I get there. I don't want her to die alone, despite how frustrating she can be. We owe an enormous debt of gratitude to our neighbour Carol for doing a lot of running around for us. I don't doubt for a moment that Stumpy would be dead by now if it weren't for her.

7 November 2009

Andrew Pollock: [life] Whirlwind visit to Brisbane

Sarah's Mum is flying her back for the scattering of her grandmother's ashes, and I figured that as this will be her third trip back this year, and she's seen my family more than I have in the last 12 months, I should come as well. So I'm getting my first opportunity to sample V Australia's service. I must say that flying Virgin America to LAX and then transferring to V Australia to fly direct to Brisbane seems like a fairly civilised way to do it. Anything that involves Virgin America is always a delight. My only complaints so far are that the SFO-LAX flight left late, and the check in line for V Australia in LAX was ridiculously slow given it was so short. The time of the flight is pretty good - it leaves LAX at 10:30pm, so hopefully we'll get a semi-decent amount of sleep. It gets into Brisbane at 6:30am on Sunday, so we'll have to try and imitate the living dead for the day. I'm heading back again on Saturday, as I have to be in Dallas next week for the Ubuntu Developer Summit.

28 October 2009

Russell Coker: New Play Machine

Update:
Thanks to Sven Joachim and Andrew Pollock for informing me about /etc/init.d/mountoverflowtmp which exists to mount a tmpfs named overflow if /tmp is full at boot time. It appears that the system was not compromised. But regular reinstalls are always a good thing. On the 24th of August this year I noticed the following on my SE Linux Play Machine [1]:
root@play:/root# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda 1032088 938648 41012 96% /
tmpfs 51296 0 51296 0% /lib/init/rw
udev 10240 24 10216 1% /dev
tmpfs 51296 4 51292 1% /dev/shm
/dev/hdb 516040 17128 472700 4% /root
/dev/hdc 1024 8 1016 1% /tmp
overflow 1024 8 1016 1% /tmp The kernel message log had the following:
[210511.546152] su[769]: segfault at 0 ip b7e324e3 sp bfa4b064
error 4 in libc-2.7.so[b7dbb000+158000]
[210561.527839] su[778]: segfault at 0 ip b7eb14e3 sp bfec84d4 error 4 in
libc-2.7.so[b7e3a000+158000]
[210585.270372] su[784]: segfault at 0 ip b7e044e3 sp bff1b534 error 4 in
libc-2.7.so[b7d8d000+158000]
[210595.855278] su[789]: segfault at 0 ip b7e014e3 sp bfd18324 error 4 in
libc-2.7.so[b7d8a000+158000]
[210639.496847] su[796]: segfault at 0 ip b7e874e3 sp bf99e7b4 error 4 in
libc-2.7.so[b7e10000+158000] Naturally this doesn t look good, the filesystem known as overflow indicates a real problem. It appears that the machine was compromised. So I ve made archival copies of all the data and reinstalled it. As the weather here is becoming warmer I ve used new hardware for my new Play Machine. The old system was a 1.8GHz Celeron with 1280M of RAM and two IDE disks in a RAID-1 array. The new system is a P3-800 with 256M of RAM and a single IDE disk. It s a Compaq Evo which runs from a laptop PSU and is particularly energy efficient and quiet. The down-side is that there is no space for a second disk and only one RAM socket so I m limited to 256M that s just enough to run a Xen server with a single DomU. I put the new play machine online on Friday the 23rd of October after almost two months of down-time.

23 October 2009

Andrew Pollock: [life] Sarah's Trauma debut

The first episode of Trauma that Sarah was an extra in aired on Monday night. I'd seen a news story about how they were looking for extras for it with medical experience, and Sarah had just completed her Certified Nurse Assistant course. I mentioned the news story to her, and she signed up. Ironically, for the three episodes they've called her up for so far, the closest to using her medical experience is being a patient, and if you're lucky, you'll see her ankle. Marc was kind enough to rip out some stills from his recording of the episode.

3 October 2009

Andrew Pollock: [life] Surprise! It's a Kylie concert

Sarah told me a while ago that she was planning an early birthday present for me, but it was going to be a surprise. Last night, I found out what it was: tickets to see Kylie Minogue in concert at the Fox Theatre in Oakland. I had no idea that Kylie hadn't done a US tour before. Last night's concert was her second one ever, and was only put on by popular demand (the night before was her first ever). I've never seen Kylie live before and it was a great show. There was a DJ on stage for about 45 minutes prior to her starting. There were awesome lasers and lights, a live band, and excellent choreography. My only complaint was that the music tended to drown out her vocals a bit, but other than that, an excellent and totally unexpected night out. We nearly saw her when we were in Prague last year and she happened to be performing at the same time we were there, but I think this was a much better deal: a smaller venue and cheaper tickets. The general admission area was all of the standing areas on three levels. We could have elbowed our way right to the edge of the stage if we'd wanted to. The San Francisco Chronicle has a good review of her opening night.

23 September 2009

Andrew Pollock: [debian] PyMetrics

I recently learned of PyMetrics existence via 10 Ways To Let People Know You're A Bad Python Programmer I've yet to run it on any of my Python code to figure out how bad a Python programmer am I, but I was surprised to discover it was absent from Debian, so I fixed that. In writing this post, I just realised that I unnecessarily made it an architecture-dependent package, when it doesn't need to be. Better go fix that.

Next.

Previous.