Skip to main content

Waiting for unhealthily delicious sammiches



This is one of them days when I REALLY HATE MY CELL PHONE CAMERA. The camera in the Blackberry Curve is about as shitty as the cameras that shipped in the first two generations of the iPhone. It is simply terrible for anything that goes beyond scanning barcodes. What's sad is that when I got my new camera I made sure that I got a microSD card for it, so I could eject it from the camera, unplug it out of the miniSD adapter, plug it into the phone and blog from the road in all the glory that the Sony DSC-TX7 can provide. Instead, out of laziness (I had the camera with me, I never leave home without it) I tried to shoot with the cell phone, with the expected crappy results.

To add yet more insult to injury, I had done bulk imports into blogger and I triggered their captcha failsafe. If you post too often, it starts giving you captchas to make sure that you are a real person and not a spam bot. The problem is this won't work if you are trying to blog through email, only if you are at a web browser or through Picasa. This means that I had to solve a god damn captcha for every damn single photo I shot this afternoon. Ugh. It really would had been less trouble to shoot this with the camera and wait another 10 minutes until I got home to post the photos.

The only good thing were the sammiches, they were delicious even if I can't have them more than twice per month.
Posted by Picasa

Comments

Popular posts from this blog

On sleep deprivation and Incan Monkey Gods

From: Dilbert comic strip for 08/03/1992 from the official Dilbert comic strips archive. I was trying to show this strip to a coworker who is dangerously toying with the harsh mistress that is Insomnia. What shocked me is how quickly I was able to look up the strip, which was published when he was just 11 years old, and two weeks before my just-out-of-college ass shipped out to US Army Basic Training.

Add custom speed settings to your ifit map workout

Ifit.com allows you to build a workout walk/race/bike route simply by clicking on a Google Maps interface. You can then use a compatible ifit-enabled workout machine to recreate the route automatically. The problem is that the user interface still isn't final, so there are features in place that aren't exactly obvious. For example, if you create a workout your machine starts at 1 MPH, because that's the default. But how to set it to start at say, 3 MPH? Easy, just switch from map view to graph view: That button switches from the Google Maps interface to a chart that allows you to visualize and control effort: You can't change the elevation, this is fixed due to the geography that you selected. But you can drag the yellow (speed line) to change the speed of your device.  What if you want to have segments at different speeds? Easy, just click and drag and it will break the line, and you can drag each segment of the line independently: ...

Software Entropy and the Strangler Fig: Surviving a 20-Year-Old Codebase

Right now, I find myself fighting a three-front war. Front one is keeping a 20-year-old behemoth of a B2B application alive. We are talking about decades of legacy ASP.NET and VB.NET where two decades of tweaks, patches, and "temporary fixes" have become permanent, load-bearing pillars of the architecture. Every time I touch it, it feels like playing Operation with oven mitts on—spending 90% of my week untangling logic just so a simple bug fix doesn’t cause a ripple effect that crashes a critical service. Front two is modernizing the architecture. I am actively trying to implement a rudimentary Strangler Fig pattern—slowly carving out legacy functionality and pushing it into a clean, testable shared library project so we can actually run proper unit tests and stop the bleeding. Front three is modernizing the team. While keeping the lights on and quietly rebuilding the engine, I am also pushing a retraining effort to get my peers up to current framework versions and embracing ...