Why is it, that whenever I think things will calm down, they do the exact opposite?
Well — you should know by now that the PyCon 2011 Call for Proposals is up — we’re accepting main conference talks, poster sessions and tutorials, all at once. The main conference proposals are due by November 1st — so I’d recommend getting those talks in! Also, you should know that we’ve announced our first keynote speaker — Hilary Mason! Really, really looking forward to that.
Over on the sprints side — Brian Curtin has done several blog posts — the first details the “getting started with Python-Dev” guide he’s been shepherding for the project. I’d recommend taking a look — you can send feedback to sprints@python.org. The second is a note on the fact we have our first company donating actual funds to the project (via the PSF) — Trading Technologies. This is awesome news.
If you want to do a sprint — and you want some money to help out, please, please, please send an application to sprints@python.org — we currently do not have any sprints lined up in the near future (We are sponsoring the ?http://www.pymntos.com/ sprint occurring tonight — they’re porting Mutegen to python 3). If you need help, or want help sending out a call for a sprint, contact us too. Our goal is to help everyone get sprints up and off the ground.
Also, if you want to help out with the sprints project — please let me know. We need bloggers, writers and other people to help further “the cause”.
Finally, I’ve been spending the majority of my time once again blogging for my employer (Nasuni) — if you’re interested, I recently did a series on “The Cloud” (focusing on Private vs. Public clouds), while Rob (my boss) did a fantastic post on the real cost of a gigabyte in the cloud:
The company I’ve worked for since July of last year — Nasuni Corporation (a startup in Massachusetts) has gone live! This is the culmination of a lot of hard, but exceedingly fun and exciting work over the past months.
The Nasuni team is an excellent one — and one I am very, very proud to be a part of. Our product is called the Nasuni Filer — a simple-to-use, versioned, encrypted and cloud-storage backed virtual NAS (network attached storage) server (click here for more information).
Without going into all of the features, our goal in making this was to make cloud storage simple, accessible and secure — and I know we’ve accomplished all three. All you do is download it, boot it and start using it — once you do so you have access to truly unlimited storage. It’s an unlimited filesystem for the cloud. Here’s the elevator pitch:
Nasuni has developed a virtual file server, called the Nasuni Filer, that delivers unlimited file storage and complete file protection for businesses. Working in partnership with leading cloud storage vendors, the Nasuni Filer leverages the vast capacity of the cloud to store and protect company files offsite, while retaining the local functionality and performance of a traditional NAS.
This technology allows businesses to use the cloud provider of their choice as a replacement for traditional primary storage. Snapshots, file versioning, and offsite storage are integrated into the file server itself — ensuring business file are safe and secure at all times. No need to manage complex backup and DR schemes — if the file server is running, files are protected.
We’ve launched the Beta of the product today — anyone can sign up, download and use it. Anyone can give us feedback and suggestions — I encourage all of you who might need something like this to download and give it a try. If you want — go check out the videos we’ve put together showcasing the Filer (and better yet — check out the awesome animated cartoon we have on the front page).
Most of you know that my blog is mainly Python oriented. Suffice it to say, Nasuni — and the Nasuni Filer make use of Python for a wide range of tasks. We use Python, Django and as much of the Python ecosystem as we can to drive everything from the website, to the GUI on the appliance itself — Python is part of the DNA of the company, and it has served us well. Without Open Source and Python — I don’t think it would have been possible to build what we have built in as little time as we have.
We have a strong dedication to not just Python, but open source in general (and a fair number of us will be at PyCon this month). As time progresses, now that we’re exiting stealth mode we plan on possibly open sourcing stuff we feel would benefit the community. Some of us already push patches back where and when we can, but as I said — as time progresses this involvement will only increase.
So not only am I proud to announce the product, be part of this team and to see what we’ve made, I’m also happy to thank so many people in the Python and OSS community which have helped us reach this point.
I don’t talk politics or current events here — mainly because I’d come off a a Lolbertarian whack-job, but I just had a serious “what in the crap?! moment when I checked my 401k:
Personal Rate of Return from 01/01/2008 to 10/09/2008 is –41.9%
This is one of the moments I look at my daughter and think about the future and get really sullen, so instead, I’m going to go back to solving technical problems as I can’t even rationally discuss this in my own head.
For the past year I’ve had the exciting opportunity to be a father — it really is fantastic, especially now that new parts of her personality is coming through and she’s in the “crazy aboriginal where are your pants” stage.
However, on the flip side, it’s a lot of work — tiring work. It also comes with a side-effect. Disease. I’ve been sicker the past year than I ever have been in my life. I think I end up with a cold or something else every month. I’ve had sinus infections, colds, Hand-Foot-and-Mouth and lack-of-sleep induced insanity.
Good times. At least I got to see the new batman movie, which was amazing. I’m going to go blow my nose again.
In addition to the Python sprint day work I am doing (as well as pymag stuff) I’ve been editing the obligatory “zomg baby is walking” video, which is below.
It’s funny — she’s been close, and doing short spurts, but last night it was like her walking switch just “came on”.
Earlier this week — I made the rather difficult decision and resigned from my current job. Yes — I have a new one in the bag.
The job I resigned from has been one of the best, most rewarding jobs in my career. I’ve had the luxury of working with some of the best engineers I have ever met, on a problem/solution that is, by far, the best in it’s class.
I’ve been working with what I count as my second family for close to five years. You don’t walk away from something like that lightly, or without good reason.
My reason was simple: I enjoy startups. I love blazing trails, exploring technology. I love pushing boundaries and making something tangible and new where there was nothing before. It’s why I love software.
Some people would say that software is not a painting — and to an extent, they are right. But the pride you feel when you see your software come alive, get adopted and grow day after day is much the same feeling of accomplishment and pride you get when you do finish a work of art.
Personally, I feel that startups engender the wild west — all ideas are open and ready to be explored, much of the territory is uncharted, and you remain (in many cases) unencumbered by processes, bureaucracy and history.
That all being said — it’s not without an aching heart that I say good bye to my friends, colleagues and the product I helped usher into the world. Both the product, and the people remain best-in-class, and I wish both the company, and the people the best in the future.
The great (and sometimes bad) thing about startups though, is the fact that if you live in a place where startups are always coming and going (i.e: Boston) then sooner or later, you’re going to end up working with many of the same people again. Due to this, I’m ultimately OK with saying good bye to many of the coworkers I have today, because I will see them again in due time.
That all being said — I have a new job (obviously). Later this month I will begin working for an Acton, MA startup called Blackwave. I’ve had the pleasure of meeting the people there and exploring the technology, and I have to say I got that old spark back in my head. The spark that keeps you up at night thinking about how to solve The Problem and how to test The Problem. The one that makes you get up early to write notes down to yourself like “if we simply change x here and here, then in theory we can cut our testing to y…” and so on. It’s the spark of inspiration.
In speaking with them — I wanted to solidify something that’s been chewing at me for a little bit — and that’s having some amount of freedom to contribute to open source — in my case, Python-Core and python-related projects. I’m happy to say, Blackwave was more than willing to express their support and openness to contributing to the community. I can’t go into details — but with any luck, I should be able to be a lot more open with much of my work, and also give a lot back.
Again — with that all being said — I will take this one opportunity to say — yes, Blackwave is hiring. If you’re a python/java/c/c++ person, or you just love doing QA and testing and are looking for a small, fast moving team — and live in the Boston/Metrowest area (southern New Hampshire is OK) — go ahead and drop me an email. I’m definitely putting feelers out for any Pythonistas in the area who are looking around. I’m doubly interested in Pythonistas with a QA background to help focus on test engineering/automation.
Send your resumes to me (jnoller at gmail dot com)!
I’m looking forward to the upcoming months with excitement.
The least you could have done is told me that anytime it rains, the nicely finished tiled basement area, the one holding my computers and livelihood floods. I realize, that had I known that the nicely finished basement with the tiled floor gets flooded every time it rains because of the half-assed code violating installation of the sewage pump in the garage allowing water into the house, I would not have bought the house.
In addition to the hidden plumbing issues, the veneer you added to the area (which floods anytime it rains for more than 10 minutes) to hide the fact there is a flooding issue was a nice touch.
I understand I have only myself to blame — after all, I should have torn up the floor and pulled apart everything to find out the fact it floods (every time it rains) and that the upstairs bathroom has a rotted floor, a bum toilet and issues with the sheet rock (rotted).
I have no recourse against you, the inspector, or anyone. Instead, you, a couple with a small child saddled another couple (with a small infant child like yours) with this house.
When I started the purchasing process, I began it with excitement. Now I sit in a house I have lived in for less than a month, but spent most of my money on, with my feet in a standing pool of water as I type this — the gently splish splish of my feet in the ice cold water reminding me of how much I wish you were here so you could help me mop, for the fourthfifth sixth time.
Oh, but mopping doesn’t help — but you knew that. You knew that the reason there were tiled floors in this part of the house is so that there was “no long term damage” to the area (which floods every time it rains).
So thank you for not telling us the house floods every time it rains. You’ve helped us build up so much character knowing never to trust anyone, even if they are another young couple with a small child — just like us.
Unlike you, I’m honest and responsible, and I’m going to fix this mess you’ve left me with, so my wife, daughter and I can live happily here in our first house which floods every time it rains.
A recent post on the pycon blog has me rethinking using Twitter or Jaiku for “micro blogging” (especially during a con). I’ve personally not used either one of them, but my preference would be to try out the now-not-accepting-new-users Jaiku.
How many people out there in the #pythonweb are using these?
Edit: I’ve signed up for both twitter (username: jessenoller) and Jaiku (username: jessenoller). Now I have to write a python app that dual-posts to both. Who knew social sites would be such a pain? :)
Edit2: I signed up for pownce too. God. That’s facebook, linkedin, pownce, jaiku, twitter, and a blog.
It’s been a nutty last few weeks. The work in the salt mines has been especially busy, and well — overly salty. Some would say it was too salty for consumption.
Wife, Baby and I are settled into the new place — yes, the various sundry problems including flooding, flooring, bathrooms and other cruft was resolved post-haste and satisfactorily, albeit expensively.
In other news, things should hopefully start calming down — so I can pick up on the non-salt-mine-or-parenting work (i.e: more delicious Python goodness).
In addition to all the craziness — Abby is crawling, and climbing now. Both of these new developments in addition to the new digs means “lots of stuff to get into” — you know you’re going to have a problem when you see her make a beeline for a power cord.
Lots of changes: I’m looking for PyCon as a chance to meet some people I’ve met before (although briefly) and meet a lot of new people. Hopefully, while I’m there I’ll be able to jump start a few “non salt mine” projects that have been sitting in the queue, and get some more article fodder over to Doug and Brian.
Of course, I can’t wait for summer. I think there’s going to be something inspirational about coding from a hammock.
Quick Python trivia question: Near as I can tell, Guido works half-time on Python over at Google. Is there anyone in the world, aside from Frank and Ted, getting paid to work full-time on Python?
As a guy who gets obsessed about the hammer he uses to build a house — I wonder what it would be like to design hammers for a living?
I’ve mentioned this before — on Jan 4th, I ended up closing on my first house. The primary driving force of course being my now nearly seven month old daughter, the secondary driving force is well — owning a house.
Both my wife and I were excited, ecstatic even. I mean, it’s not a palatial mansion by any stretch — but it was ours.
Then, things went sideways. After closing, after we start painting — we find a problem. A big, glaring problem. That problem happens to be a leaking toilet — that has apparently been leaking for some time (measured in potentially years) into the sub flooring. This means all the wood beneath the tile floor under the toilet it rotten and moldy, and that dampness and mold may have spread to the rest of the flooring and areas.
We found this pulling the toilet to put in a new one — now, instead of a cheap plop-in-a-new-toilet, we’re staring down the barrel of a much larger “strip to the walls due to rot and mold” deal. We can’t move in, and we didn’t even imagine this would happen.
Rotten wood, mold. The works. And no, it’s not covered, and it is no ones responsibility (or rather, no one is liable). Nope, we just get left holding the bag. The inspector found a tangental issue: but not the primary issue, so no one was technically the wiser.
Stupid toilets. From now on I’m only buying houses without running water, in non-flood plains in areas with no termites. Also the house will be made of stone.