On the way to see The Avengers today, my wife suggested that we rent Bixis and see if we liked them. Here’s what we liked:
Here’s what we didn’t like:
We had the convenience of paying for the bikes, plus the added exercise of walking the whole way. And since we didn’t get the bikes, we didn’t have the hassle of returning them. So I guess that’s a win?
While attempting to standardize the testing of a code base, I’ve been trying to enable Spring’s test-level transaction management. In a nutshell, if you run a properly configured test within Spring’s test transaction framework then then the test does not actually commit anything to a database.
It should be as easy as annotating your test class like this:
@ContextConfiguration(locations="application-context.xml") @TestExecutionListeners({TransactionalTestExecutionListener.class}) @TransactionConfiguration(transactionManager="myTxManager") @Transactional
This loads the application context from the classpath and then manipulates the transaction manager named myTxManager to roll back the database transaction when the test is complete. The problem I have is that the application context file isn’t on the classpath. To make it even more interesting, it’s stored on a different place on each developer workstation. There’s already a utility to discover the file, I just need to hook it into the context loader.
After nearly eleven years, I recently left Intelliware and have accepted a new position at Autodesk. It’s a weird thing in today’s environment to work anywhere for as long as that, and it’s doubly weird to leave after that time.
It works for me, though. I’m a good fit for the new position, and the challenge will be good for me. It’s tough to leave a small company like Intelliware, where I felt (and still feel) real kinship with the management and ownership teams. I knew my work made a difference, but it kind of feels like a big-fish-in-small-pond situation. I’d like to see what I can do in a much larger company.
It appears that the answer is “yes”.
Here’s my story. In order for my wife and I to make it my family’s Thanksgiving dinner, we had rented a car for Saturday, October 8, 2011. We showed up at the rental location (for reference, it was the Bloor St E location, in the Hudson Bay building concourse) at the appointed time, and arrived to chaotic scene. There was a dude at the front of the line yelling at a couple of workers and a huge lineup of people that stretched out of the office. It quickly became apparent that there weren’t any cars, there hadn’t been any cars for quite some time, and that there weren’t going to be any cars anytime soon.
For reasons that I’m not quite at liberty to go into (even on a blog that no one reads), I’ve abandoned the idea of creating an iOS app for the time being. I’ll still use this blog to map out some technical stuff – there’s some JavaScript I’d really like to play with – but my Big Top-Secret Project is off the table for now.
So I guess there’s no reason not to describe my intended project. It was a wine review database. Here’s the use case: you read a wine review in the paper on Wednesday, but when you’re in the liquor store the next day, you can’t remember what you’re interested in buying. Boom! You simply pull out my app on your phone and sort the available reviews by date, find your review, find your wine, and get all drunkified.
Against my better judgement, I bought my wife a Playbook for her birthday. She’s basically married to her BlackBerry, with me being the newcomer to the relationship. And while I’ve become an Apple fanboy over the last year, she’s equally comitted to RIM.
From some experiences at work, I knew that the Playbook was a little flaky. I thought maybe that was me being over-critical of it based on the experience of developing for it – surely RIM can’t hate its users as much as it hates developers. It turns out I was wrong.
It’s now officially been over a month since I last updated. It’s a little disappointing: I’m sort of striving for weekly updates, and I’ve let the project lapse for several weeks. I’ve got the usual excuses: work has picked up, summer is a difficult time to stay inside and code, and, honestly, it’s turned out to be more of a chore than I expected. Today is Labour Day and I spent it napping and hanging out with my wife when I meant to spend at least a few hours coding.
But I’ve been thinking about apps in the background. Specifically, I’m going to write a drinking companion app branded for drunks.ca. I’m going to use the Google Maps stuff I’ve been doing for a client at work and marry it to an iPhone app that will tell you where you can drink, how to get there, and how to get home (that is, it will provide a list of cab phone numbers for your local area). This isn’t something that I expect anyone to pay for, but I think some of my friends could get a kick out of it.
One of the problems I knew I would have with using Rails is that I don’t know a thing about Ruby or Rails. That’s the point – I wanted to learn at least the outlines of the language, and I learn best when I’ve got a project to use as an excuse to learn things. And since my method of learning this stuff has so far been randomly googling stuff as I need it, I was bound to run across different ways of doing things.
For example, when I wanted to create a drop-down select box, I followed these steps:
The last time I touched this code I created an entity named Review that referenced a Publication. I’d like to modify Review to also have a Reviewer. (I’ve decided that Publication and Reviewer are for my purposes independent – a Reviewer is a person and a Publication is, well, a publication. While there can be a relationship between them (e.g., Ebert usually writes for the Chicago Sun-Times), that relationship doesn’t always hold for the entirety of a reviewer’s career.
The first thing to do is create the Reviewer entity. For now, reviewers only have a name.
rails generate scaffold Reviewer name:string rake db:migrate
Now that I’ve got a basic app in place, I’d like to start fleshing it out. I’ve veered off from the Ruby primer and will pick stuff up from the web as I need to.
Today I’d like to set up the Review entity. In addition to the normally-entered data fields (date, URL and full text of the review), each review belongs to a publication. I’d like to select the publication from a drop-down list.