Twitter Integration Experiment…Um, Yeah

Well, as you can see below, I tried an experiment where an extension would automatically post all of my tweets for the day in a blog post. As my tweeting has followed the pattern of my blog (although not to the same degree – I do tweet more often, I just turned this addon off a while ago, and I’m just now getting to blogging about it!), it just looks…odd. So I’m stopping that experiment. I did turn the sidebar widget back on, so at least there’s still *some* connection.

All you bloggers/tweeters out there who can post everything from significant events to the ingredients list of your last (current?) meal, my hat’s off to you. I’m just not that kind of person, I guess.

Add your comment here: * Comments(0)

Twitter Updates for 2010-01-11

  • Argh! Did a regular update on my Ubuntu desktop. The system froze, & after the reboot 1/2 the s/w doesn't work! Where's my Slackware disc?!? #
  • Re the Ubuntu failure: it was a good experiment and I'm surprised it lasted as long as it did… #

Powered by Twitter Tools

Add your comment here: * Comments(0)

Twitter Updates for 2010-01-11

  • Argh! Did a regular update on my Ubuntu desktop. The system froze, & after the reboot 1/2 the s/w doesn't work! Where's my Slackware disc?!? #
  • Re the Ubuntu failure: it was a good experiment and I'm surprised it lasted as long as it did… #

Powered by Twitter Tools

Add your comment here: * Comments(0)

Twitter Updates for 2009-08-21

Powered by Twitter Tools

Add your comment here: * Comments(0)

Twitter Updates for 2009-08-16

  • Power went out again last night, came back after I went to bed. Things are back up. I need bigger UPSes, or power storage for our solar. #

Powered by Twitter Tools

Add your comment here: * Comments(0)

OSCON Day 3: Now the Fun Begins

Tim O'ReillyMy hat is certainly off to those for whom blogging is either a way of life or a profession. I feel as though I was dragged through the day yesterday, barely able to keep up with moving from one part of the day to the next and having things register, let alone finding the time to write about it. Part of that was the convention center: having one session in an “A” room, followed by another in a “J” room meant a walk of several minutes, usually to find that the second talk had already started, and you had to catch up. The other part was the traditional OSCON “problem” of the sheer volume of things going on simultaneously, and trying to figure out where to divert one’s attention, desperately hoping that you’re going to remember enough of everything you’ve seen to be able to look it up later. Cameras, browser bookmarks, wikis and other bits of technology help, but I definitely felt, more so than previous years, that the pace yesterday seemed to be the most frenetic I’ve encountered.

The day started with the traditional welcome and keynotes, which were given by good speakers, but speaker or group agendas seemed to be in the forefront. Tim O’Reilly, who I always like to hear speak, introduced “Open Source for America”, a group wanting to raise awareness of open source in the U.S. federal government, and Dirk Hohndel from Intel spoke about netbooks in the context of Moblin becoming the OS of choice. This was interesting to me, because I first heard of Moblin last year at OSCON, but haven’t seen much about it in the intervening year, but just have this gut feeling that when ChromeOS is released, it will be everywhere. Why is that?

The highlight of the keynotes was Michael Lopp opening a sealed box of Borland’s Paradox for Windows that he’s had for 15+ years as part of his “A Brief History of Software” talk. Fun Stuff.

The day’s sessions were punctuated with the Expo Hall, which is where the break was after the keynotes. Although it feels like there’s more here this year, things seemed very crowded and close-quartered, and after the completion of the “Passport Contest” (an annual event where you get stickers from all the major booths, completing a card that you hand in for a drawing for some good prizes – I won a secondary prize last year: a stack of 15 or so O’Reilly books – so worth doing!), you were left with the feeling that you hadn’t really seen much. I hope to make the rounds again and prove that wrong (oh, and don’t get me wrong, I talked to some people about some cool-sounding things I’m going to try out!).

The sessions I chose for the day included 2 on web design aspects (interesting, but hard to have absorbed everything – hopefully the speakers post the slides), 2 on the open source stats package “R”, and a couple on the future of storage and “The Genius Programmer Myth”, a fun talk given by a couple of Google guys on team programming and the mechanics of that.

Lunch, provided by Google, was a combination of an excellent selection of seafood and other things, and some light conversation with people we didn’t know, which can be interesting.

The day concluded with an Expo Hall reception (does all convention center catering offer the same menu? Good though!), and a couple of parties thrown by Sun and LinuxFund.

In all, the consensus seems to be that we miss Portland, the conference center, while adequate, seems spread out and a little run-down, and in the end, there doesn’t seem to be as many people here (perhaps a result of the economy), and a large group of those that are seem to be locals and first-timers. On the positive side, the people here are always interesting, there’s always gems of things you find, at random most of the time, in the speakers, the talks, the expo hall and overheard conversations, that make OSCON enjoyable and worth coming out for.

Add your comment here: * Comments(0)

OSCON Day 2

With a only a couple of tutorials and an evening intro thing, there wasn’t much going on to report. My morning tutorial was Damian Conway’s “7 Principles of Better API Design”, which was fantastic. While a little Perl-centric for me, there was still plenty to take away and apply to an up-coming project of mine (although it was interesting to note that he approaches APIs in a more general sense than I had been thinking: my project is more of an API to a data warehouse). As a side note, Damian is a fantastic presenter, and he makes everything interesting and more enjoyable, and this tutorial was no exception.

The conference proper kicked off in the evening with a couple of events: the “OSCON Ignite” quick-talks (each of the 10 speakers got 5 minutes with 20 slides that advanced “automatically” every 15 seconds), which was great fun, and the Google/O’Reilly Open Source Awards.

In all, the first two days of tutorials where very good this year, with some good speakers, and some good, applicable information. Now we can concentrate on the rest of the week, which is looking fantastic: from the sessions to the exhibit hall to the parties in the evenings, it’s looking like it’s going to be a great conference!

Add your comment here: * Comments(0)

OSCON Day 1

And so it begins! The move of the conference to San Jose this year was done under the reason of out-growing Portland, mostly the convention center (which was definitely the case). However, it wasn’t hard to guess that part of the reason for the new location was proximity to O’Reilly’s offices, part of a cost-cutting measure. And in the days leading up to the conference, there were little hints that more cost-cutting was going on, but in a way that hopefully wouldn’t impact the over-all impression of the conference, especially for first-time OSCONers. On day one, a few other changes were evident, the biggest being the lack of food available before the tutorial. They provided coffee, but there was only a conference center breakfast kiosk available, selling $3 muffins. Disappointing, but understandable. In the end, if these measures simply mean that O’Reilly can continue to provide the quality conference we’ve all come to appreciate, than I applaud their efforts. We’ll see as the week progresses.

My first tutorial of the day was “Simplifying Database Design” given by Josh Berkus of PostreSQL Experts, Inc. The talk was geared to people who worked with databases on a regular basis, but learned them on the job, which was the vast majority of the audience. In the end, the information was good and well-presented, but stuff I mostly already knew, or was doing – largely because I’d done it wrong before and finally learned. Still, it was well worth it to know I wasn’t missing anything obvious.

The lunch turned out to be a very nice mix of salads and build-you-own sandwiches, with a selection of cakes for dessert. Everything was good, and I got a chance to talk to a few people. A good start in that department, and it made up a little for the lack of breakfast.

The second/afternoon tutorial for me was “Scaling a Web Application” by Duleepa “Dups” Wijayawardhana. This is a topic area I’m mostly just interested in, rather than needing (things I build tend not to have many users), but I was looking forward to learning things I could do early in a project that wouldn’t take much effort, but would ensure that if things needed to scale, I would at least be partly ready. I took away some useful pointers, with some things I can look at implementing right away, and some other things to play with, including program and query profilers.

All in all, a great start to the week! I’m looking forward to tomorrow’s tutorials, especially the one on API design, and then the rest of the week with the conference proper.

Add your comment here: * Comments(0)

Heading to OSCON 2009!

I leave tomorrow for California, spending a few days in the Berkeley/SF area before heading to San Jose to attend OSCON 2009. Each year I say I’m going to blog the conference, and each year I do a little better, with last year looking pretty good with just a slight fade-out at the end. This year should be better than ever, with Twitter along for the ride to augment my memory (look for the tweets in the side bar of this blog, or follow me!).

This year should be better than ever, conference-wise too, with a new, larger venue, and more going on. Stay tuned!

Add your comment here: * Comments(0)

My Thoughts on the New Star Trek Movie (Spoiler-free!)

“Come, come, now, Scotty. Young minds, fresh ideas.”
“Aye, and if my grandmother had wheels, she’d be a wagon.”

Kirk, Scotty; Star Trek III: The Search for Spock
(line order reversed deliberately)

The new Star Trek movie by J.J. Abrams was always intended to be a so-called reboot of the franchise, an opportunity to take the Star Trek universe in a direction that would allow for new ideas in a familiar setting. I went into this movie really excited at the potential of this, but came out pretty disappointed: as a long-time, details-oriented fan, there were too many changes for me to accept, and for reasons I can’t yet put my finger on, it didn’t quite *feel* like a Trek movie.

I grew up watching the original Star Trek series (in reruns: I’m not quite *that* old!), and from there, moved into the novels which fleshed out the characters, and especially their pasts (many of the novels in my collection deal with the time before the 5-year mission). From there came the first 4 movies (Star Trek V? I’m pretty sure they didn’t make that one…), and then it started: The Next Generation (TNG). At first I was skeptical: “that’s not really Star Trek”. But it grew on me, and they did a pretty good job of referencing things that had come before. I watched (and re-watched) every TNG episode. When Deep Space Nine started, I was watching, and liked what they did with it, but I don’t think I saw much of the last season. Then came Voyager, and I watched some episodes, mostly in the first season. While they had a great concept, the execution didn’t really hold up for me. I saw even fewer episodes of Enterprise (a show I really wanted to like), mostly because they started to take liberties with what had come before.

What has to be understood is that there isn’t just the shows, the movies and the novels. People invested into this universe in a big way (geek alert!): there were time-lines, technical manuals, and lots of meta-information that either pulled from canon (the accepted authoritative body of work), or became so. At that point, for the people who were paying attention, there was an enormously detailed universe available. Of course, that can be a curse too: there were inconsistencies, and it becomes increasingly difficult to write well in such a universe.

So while one might not blame Mr. Abrams for not wanting to bring along all this baggage, the trade-off is throwing out 40 years of world-building, and throw it out he did. Interestingly, the one thing that would have saved this movie for me (and I honestly sat through more than half the movie hoping this would happen) was if they had employed the classic Trek (and others!) device of a reset of the original time-line once the major plot-point was resolved. Of course, that would preclude sequels using the world that was built for this movie.

As for the film-making itself, I went in prepared for the shaky camera and the lens flares. The shaky camera I didn’t really notice, but the lens flares were way over-done, and became annoying after the first few minutes. I think they (overly-) contributed to portraying a bright, shiny future, but the movie failed to capture the traditional, idyllic Utopian setting which characterizes early Trek. (Oh, and Mr. Abrams? With all of those easter-eggs/references/in-jokes you put in there, to have *that* many pipes in engineering, and *not* label any of them “GNDN” was just a major oversight!)

One quick note about the characters: even accepting that this is a new Trek universe we’re dealing with, and there will be changes to the familiar characters, I really didn’t like the new histories of Kirk and Spock, especially Kirk – something just felt wrong, even if it did serve to explain later motivation, and trying to reconcile this with the fact that these were supposed to be familiar was … jarring.

This movie is an opportunity for a new generation of fans to experience Star Trek, and that’s not a bad thing. I do feel sorry for them if they then want to go back to experience the last 40 years: they’re going to be a little confused. For me, when they make the sequel (and that’s pretty inevitable), I won’t be going to see it, and I’m not at all happy about that. I wanted to like this movie, wanted to have an excuse to get back into Star Trek. But I can’t help wondering, was this movie really necessary? I think about all of the wonderful, unexplored science fiction material out there, begging to be transformed into other mediums, and wonder if the money put into this film wouldn’t have been better spent bringing something new.

Add your comment here: * Comments(2)

Next Page »