Red Hat stands behind the code
Cool OpenStack video with footage of Red Hat engineers at the OpenStack summit in Hong Kong last month.
[ Home | Articles | Account | People | Projects | FAQ ] Red Hat stands behind the code
Cool OpenStack video with footage of Red Hat engineers at the OpenStack summit in Hong Kong last month.
OpenStack Meetup, Cincinnati
Last night I attended the OpenStack meetup in Cincinnati. It was a lot longer drive than I anticipated, as it was on the north side of Cincy. But it was worth the drive. There were only five people there including myself, and although there was nothing formal planned in terms of a presentation, we had a great conversation around what we do in our various jobs with OpenStack, and I think we all learned something new about the OpenStack world in the process.
If you're in the Cincy/Louisville/Lexington area, and you're interested in future meetups, please let me know (rbowen at red hat dot com), so that we can get you included in those announcements. I'd really like to do something in Lexington, so that I don't have to drive so far. ;-) So if you're in Lexington and are interested in, or are using, OpenStack, please ping me and we'll set something up.
How Not To Program
Today I saw this tweet:
Proposing a game to cheer up our programming newbies: Experienced coders, let's share code snippets we wrote after half a year of coding.
— Lena Herrmann (@kilaulena) November 26, 2013
And it took me back ...
2000, I was attending YAPC. I had been doing Perl stuff for several years at that point, and had written, among other things, a web calendar app called Hypercal. Calendar math was something I was very interested in at the time - particularly non-Gregorian calendars.
While at YAPC, I had several conversations with people about calendrical calculations, and on improving the core Perl date/time libraries. It was, in fact, immediately after one of these conversations that I attended a talk titled something like "how not to program", which featured spectacularly bad code examples from published works. I *think* that the speaker was MJD, but this was a long time ago.
As I watched the speaker expound on the horrors of the code he had found, I gradually realized that this was MY code that he was lambasting. As it happens, an early version of Hypercal had been used as an example in a Japanese book on CGI programming. I still have a copy of it somewhere, I'm sure, but I expect it's out of print now. But, there it was, on the big screen, for everyone to see.
It was truly awful code, and it could have been a truly humiliating experience, had I not, by that time, progressed a ways past my early errors. What's amazing was that, at the time, there were few enough people producing Open Source web apps that my dreadful code ended up being an example worth putting in print.
I often think of that incident when helping beginners. It's good to remember that 1) everyone you meet knows how to do something you don't, and 2) no matter where you are now, at one point you were a clueless beginner.
Syndicated 2013-11-26 22:01:23 (Updated 2013-11-26 22:01:24) from Notes In The Margin
How Mr. Weasel was made an outcast
This is "How Mr. Weasel was made an outcast", from the book Mother West Wind "How" Stories by Thornton W. Burgess. I haven't recorded something in a long time, but hopefully will do more of these in the weeks to come.
Listen to it HERE, or subscribe to my podcast to listen to it in your favorite podcast app.
Syndicated 2013-11-21 02:34:13 (Updated 2013-11-21 02:34:14) from Notes In The Margin
Mulled wine and a nice tree
7 years ago this evening, I knocked nervously on Carie's door. We had a date to make mulled wine. Yes, it's an odd first date.
We made several bottles of mulled wine, a few of which we still have. I said that one of her paintings was "nice". Yep, I really did. "Nice." Sheesh.
Eventually, it was time to go, and I said I'd like to see her again some time.
And here we are. And, seven years on, it just keeps getting better all the time. If there's a regret, it's that I didn't find her sooner. The nice painting hangs over my desk. It's still very nice.
Dan Radez on OpenStack
I spoke with several Red Hat engineers at the OpenStack Summit last week in Hong Kong, about what they work on with the OpenStack project. Here's Dan Radez, talking about what he does.
See also TryStack.org
You can listen to this conversation HERE, or subscribe to my podcasts to listen to it in your favorite podcast app.
Samson Go Mic
I recently acquired a Samson Go Mic. It's awesome. I'm so used to having to shout into my mics that it's actually taken some adjustment to go back to talking at a normal volume, and also reduce the mic volume, to get audio that isn't clipped.
I did a couple of interviews in Hong Kong last week, and realized, when editing the result, that I didn't have the selector switch set correctly. There's a little slidey switch on the side, and the manual has a lot of technical jargon about what settings to use.
Here's the summary: The circle makes the mic dual-sided, which is good for interviews. The one that looks like pacman makes it one-sided, which is good for just recording yourself. I have no idea what the one in the middle does.
I just had it set on the wrong setting, so it didn't pick up the person I was interviewing very well. So ... problem solved.
Syndicated 2013-11-14 20:29:47 (Updated 2013-11-14 20:29:48) from Notes In The Margin
Flavio Percoco on OpenStack Marconi
Last week at the OpenStack summit in Hong Kong I talked with Flavio Percoco about the Marconi project, which is incubating in OpenStack.
You can listen to this conversation HERE, or subscribe to my podcasts to listen to it in your favorite podcast app.
RDO on the FlossWeekly show
This morning I had the privilege of being on the FlossWeekly show, with Dave Neary, talking about RDO and OpenStack. You can watch the show at twit.tv/show/floss-weekly/273.
Time Warner Cable tech support
After a few days of network dropouts, and one day of working at Joseph Beth to get more reliable network, I finally decided to call Time Warner to ask them to fix their network.
The short form is, as I'm sure you already guessed, is that they declined to do so, rather choosing to blame it on me. They suggested I had stuff connected incorrectly, that my wireless router was the problem, and so on. And of course, several iterations of "turn it off and on again."
While I totally understand that tech suppose has to assume that the person calling doesn't know anything, there aught to come a point in these conversations when they are authorized to go off-script and recognize that I might know something about home networking. I'm not a CCNA, but I've been running a home network for close to 20 years, and I know to turn it off and on again, several times, before I subject myself to the pain of calling customer disservice.
So, the final result was that the entire phone call boiled down to them assuming that I have something wrong on my end, and they're not going to fix anything.
The network dropouts continue today, although it's better. I've only lost my VPN 3 times today, as compared to 20 or 30 times on Tuesday. So maybe they actually fixed something and just chose to tell me that they think it's my problem.
I wonder if there's some legal reason (i.e., not wanting to get sued) that causes them to not accept responsibility for anything.
I also wonder what other options I have for internet in Lexington. I also wonder why I'm paying so much for so little, but that's a question for another day.
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!