Gary’s Guaranteed Rooter

Friday night started “one of those” weekends. Laurie called me in from the other room, because water is flowing from under the toilet. The wax seal has failed. hint: this is not good.

Worse, our other one has been, well, offline for a few weeks because we dropped a shampoo bottle in it and it’s been on the “we can’t fix it ourselves, so we need to get someone out here to take care of this” list.

So we got everything under control, got towels down, etc. and since it was late, got to bed. In the morning, I called the plumber, Gary, at Gary’s Guaranteed Rooter. We’d used him before when we got that slab leak that needed some major surgery. He agreed to get out here as soon as he could.

And literally, as soon as I got off the phone with him, we started getting sewage back out of the bathtubs, and up around the toilets. So it wasn’t (just) a bad wax seal, but a full sewage blockage.

And hilarity ensued. And Gary got a second phone call, and re-arranged his other appointments, and generally got his butt out here as fast as he could, pulled off a miracle or two, got everything cleared up, the toilets fixed, and just because he could, fixed a dripping sink while he was here.

I know enough about plumbing (thank you, This Old House) to know when I shouldn’t be mucking with it, and enough to have some idea what needs to be done. Gary’s now pulled out butt’s out of the fire twice, and he’s not only a good plumber who knows his stuff, he gives a damn. If you need a plumber, from San Jose up the peninsula, he’s a good option to have, especially when the, um, stuff is hitting the fan. In this case, literally.

And despite short notice turning into this oh-my-god emergency, his prices are fair. His number is (650) 766-7821; it’s one you probably want to stick in your address book for that day when you really need it, because when you really need it, you don’t want to go thrashing around trying to figure out who to call…

(And now life is back to normal, although one of the bathroom rugs is a goner; all of the towels have gone through the “sanitize” cycle, and hopefully, we won’t have to worry about this for a while. We’ve been in this house since the mid 90’s, and this is the first time we’ve had this problem. Hopefully, with a bit of scheduled maintenance, we can keep it from happening again…)



Posted in For Your Consideration, Silicon Valley and the San Francisco Bay Area Tagged , , |

Blackbird IDs…

One of the birds that has been hanging around Coyote Valley this winter is the tri-colored blackbird, a species that is seen almost exclusively in California, and has been in decline in recent years, so it’s one that birders and Audubon is tracking and working to help conserve.

It’s nice that a flock of a couple hundred decided to stick with the blackbirds in the south county because otherwise, adding them to the year list means a trip into the central valley and a bit of luck. I ran into them where you normally run into blackbirds — around the cows.

120101 140716 chuq

At first approximation, the way you tell the tricolor from the red-winged blackbird in the field is the epaulet. In the adult male, the red-winged shows, well, red here in California (in other regions, it’s a red/yellow combo, but in California, the yellow is mostly hidden when the bird isn’t flying or displaying). The tricolor shows a white stripe where the red is mostly or completely hidden.

As I was going through my photos, however, I ran into these birds. One is white. One is — well, more of a cream color. Which led me down the path of taking much closer looks at the birds in terms of the ID.

If I’ve got the ID’s right (always an open question around my life), the one on the right is a tricolor. It also has the black and much thicker bill, a slimmer body shape. The bird in the middle is the red-winged. I’m thinking this is a younger bird starting to move into adult plumage, which is why the epaulet is a creamy yellowish rather than bright screaming yellow honker yellow and red; I think the red is hidden here, and the yellow in the epaulet is in process of arriving. But if you look you can see a much thinner bill, the feathering in general has a different shine, and the bird looks chunkier to me.

A nice reminder not to over-rely on any single field mark, because female and juvenile birds will mess you up badly if you do…

(the bird on the left? it’s a brown-headed cowbird. The blackbird flock, which was extended all over the pastures when I was there, is a few thousand birds, including these two species, plus Brewer’s, plus a good number of cowbirds, and of course, our dear friends the European Starling. Better birders than I estimated the tricolor numbers at a couple hundred or so…).


Posted in Birdwatching

Onward into 2012….

I’m not a huge fan of resolutions. It’s too easy to decide to start something, and then the first time you miss it or get it wrong or wake up without motivation, the resolution is broken — and that gives you permission to say “I tried, oh well” and give up. You’re setting yourself up to not succeed by making it easy and painless to fail.

The change of the calendar is a convenient time to remind yourself to step back and consider, take stock, and draw lines on the map that leads to tomorrow and align the ship to follow those lines. Even if you aren’t sure you know what the destination is, it never hurts to think about it and make sure your course is bringing you closer.

What I try to do is identify what commitments I have, and what interests me — and then prioritize to see where my time needs to go.

A huge part of this is deciding what NOT to do. I don’t know about your life, but in my life, there are many things I’d love to do — from picking up my clarinet again to restarting my needlepoint — but I don’t, because I’ve found if I start doing too many things, I end up doing none of them well. One of the challenges here is keeping the list short enough that the ones that make the list thrive, without making the list so short you end up regretting leaving something off it.

Once I chose those priorities for the next {choose period of time}, it’s about defining tasks and goals to drive them forward. Sometimes this process takes no time at all, because it’s obvious. Sometimes it takes days, or weeks, or months. And sometimes, you just leave it as “to be determined” because you won’t know until you get there…

So my roadmap for the next year? Here’s the 30,000 foot view:

  1. My family — because nothing is more important. We lost Archie this year, which is a painful reminder that it’s never safe to assume for tomorrow, and that makes it even more of a priority to myself that I not take this part of my life for granted.
  2. Myself — one of the realizations I had over the last year is that I was constantly deferring things that mattered to me because others wanted me to do things that mattered to them, and that I had hit that point where I was starting to resent how much of my time was being used by others. The answer (once I realized this) was simple: to make sure I prioritized myself into my list and make sure I didn’t commit myself to the point I had no time for my own needs. I’ve been trying to do that more in the last year, and surprisingly, the universe didn’t implode. So now, I plan on making sure I reserve time for my own interests and needs as a formal part of my planning and not just deal with it in terms of “whenever everything else is done”, because it turns out, “everything else” never is done…
  3. My Job — many people I talk to about this forget to add this item to the list (“it goes without saying!”), but in reality, to find the right balance in life, you have to balance everything in it. Your job is going to take a lot of your time, your energy and your brain. It can add stress or create enjoyment (or both!) — it’s going to affect everything else in your life. And it pays your rent and your bills, and so it deserves to be consciously prioritized into your life (see note 1). My job is important to me. Beyond being my primary income, it’s always an important part of my identity and self-worth. I won’t thrive if i don’t give it proper respect and plan to give it the time and energy it needs to be successful. And if you don’t understand that and plan for it, you’ll tend to under-estimate your commitments to it, and end up overcommitting on other things and have to figure out how to squeeze it all in… (see note 2).
  4. My website — I’ve consciously chosen not to push my online web “stuff” too hard, leaving it more as “the places i hang out” rather than try to turn it into some kind of “personal brand” portal thingie. It’s allowed me to just keep it casual and informal and, like the Apple TV, enjoy it being in “hobby mode”. But as I look forward into things I want to try to accomplish over the next couple of years (see points 5, 6, and 7) it’s clear that has to change, and so now is the time to start shifting gears and work and making my blog and site and the other pieces of online life that touch each other ready so that when these other initiatives start happening the site is ready to support them properly. So I’ve started a project to put in place a better online infrastructure and presence to start creating what I’ll want for these other initiatives.
  5. My photography — as a practical reminder that all your planning means nothing in the face of reality, I thought I knew what I was going to do with my photography in 2011; I came home from the Yosemite trip completely frustrated and unsure what direction to head. I think I’ve figured it out and I’m ready to push myself forward again (but the details will need to come some other time…)
  6. My writing — 2011 was a year where I went from “no, I’m retired” as far as any non-blog writing to “hmm. I want to write”. As it turned out, I did very little writing, but a lot of thinking and a lot of research, especially into the emerging ebook revolution and the disruption it’s causing traditional book and fiction publishing. This also caused me to realize that Palm/HP’s “employees can’t publish apps” policies were fundamentally incompatible with (see note 4) and when it became clear the efforts to fix this were going to get stonewalled again, made me start thinking about choices about what I wanted and what was standing in the way of that. Moving into 2012, I’m still frankly in thinking and research mode, and I don’t know where, if anywhere, this is going. But my novel keeps scratching at the garage door and saying “hey, remember me? let’s talk”.
  7. My app development — I’m not the first person who worked in Developer Relations to wake up one day and say “I have this neat idea for an app”, and I’m sure I won’t be the last. In fact, right now I have three, none of which are related to photography, photo books or fiction. No idea where this is going, or if it will, but the reality is it was 100% incompatible with working at HP and that wasn’t going to change, so I left it in the “maybe someday” place. Now that those conflicts are gone from my list, it’s time to start thinking about what “maybe someday” means. right now, all I know is that the first platform will be IOS (sorry, webOS fans; when HP has hardware to sell again, I’ll think about it), but I don’t know how viable the ideas are or whether I really want to invest the time to head down this direction. Or if I’ll have the time to invest. But it’s been increasingly — interesting — to me, so I’m committing time to figure it all out and see what happens.

And those are the things that made the cut. I expect it’ll keep my busy. And there’s only one given — when I look back at this list in a year, things are going to have changed along the way. But at least I know where I am and what direction to go in to get to where I want to be, and that’s a start….


Note 1: I’ve done a lot of research into this over the years, primarily because there have been times in my life when I realized it was a mess and I had to get my act together. I’ve also talked to lots of folks I know about this to learn from them, or to help them understand things I do they might want to try for themselves. One common thing we do that I believe is a mistake is not include “the given things” into the priority list “because they are givens”.

When you do that, however, it’s really easy to take things for granted, or not put the right priority on things, or to write up a priority list that is what you “should” do vs. what you really end up planning to do. For instance, if your family is first, but you’re putting in 60 hour weeks at work and never home for dinner, aren’t you really lying to yourself (and your family?) — these things do nothing for you if you lie to yourself. It is better to be honest to yourself about this in private than be politically correct about it and share. And if you aren’t honest to yourself, you’re going to end up with problems.

Note 2: This is, ultimately, teaching yourself that there are only 24 hours in a day, 7 days in a week, 52 weeks in a year, and physics wins; given that, you have to figure out how to allocate your time across your priorities to fit it all in and still get what you want to accomplish done. (see note 3).

Note 3: And when you come back to this list in a few weeks or a few months, if you find that where you’re putting your time isn’t aligned to what you said your priorities are, you either need to rearrange where you put your time, or fix your listing of priorities. Especially early on, we tend to lie to ourselves about our priorities, doing the “should be” list instead of the “will be” list. And a big part of going through these exercises for me is to make sure where my time goes is in sync with what’s important to me — and making sure I understand what’s important to me, so I don’t waste time on low priority things and later regret not doing things that are important to me. (because if you finish a higher priority thing, then you can add something else to the list and start doing it. If you don’t get to a higher priority thing because you’re off playing with other toys — you’ll end up regretting it down the road. assuming you aren’t lying about priorities, of course. (see note 2).

Note 4: I know I’m going to have to try to explain this; at some point, I will try. Suffice it to say for now that the policy was that if you were employed by them, you couldn’t independently publish apps on any platform (webOS or not), and especially not on webOS. And while some of this was ambiguous (was a Kindle ebook covered? who knows? could I get a straight answer? Hell no) I didn’t want to risk HP making claims on my personal IP (like my photos) because I published them as a photo book that happened to go through an app store. So I just decided to put any work on these things on hold until it was, ahem, no longer a problem.



Posted in About Chuq

Changing of the Guard (and letting it down at the same time)

I want to wish a happy, healthy and prosperous 2012 to you all.

2011 was one of those years where the more I try to explain it, the less it seems to make sense. The early part of the year was challenging and full of potential; the latter half of the year a roller coaster of stress and futility.

What I can talk about now that the dust has all settled is that 2011 started with me actively interviewing, after some rather unfruitful discussions with HP about role and salary. I was, in fact, in discussions with one of the big silicon valley companies that build things you probably have in your data center about coming on board to architect their social media policies when HP did an unusually smart thing and hire Richard Kerris. Richard and I sat down, and he outlined his plans for DevRel and where my role mattered, and he promised to fix as many of my issues as he could, and asked for time to try. He impressed me enough, and the product and team were important enough to me, that I pulled out of my interviews and dug back in for yet another round with the forces of webOS chaos.

For the record, he did solve most of them, except for the employee publishing rules and the salary. And he tried on both of those, but Ruby was strongly against allowing employees to also publish apps, and ultimately, a flotilla of HP Vice Presidents got overruled by a lawyer on that one. And salary, well, once again, HP bureaucracy is in some ways reportable to nobody, including vice presidents. Good luck, Meg. You’ll need it, because when lawyers and clerks set policies the overrule your executive management, good things rarely happen.

(how was life inside the webOS bunker? Let me put it this way. during my tenure at Palm/HP — just under three years — I had six direct managers, averaging about 5 months per, ranging from a first level manager to directors to a couple of VPs. I reported to, or up to, eight different VPs in that time. One of my direct managers (the last one) and two of those VPs are still with HP. Does that give you a sense of how well things were going in the organization? yeah, I think it does. Apple in the worst of days — the dark, damp days of Spindler that made you want to wake up screaming, but you couldn’t because you weren’t asleep — were never as bad as these last few months in Leoville. Seriously).

But early on in 2011, we had hopes. We really were thinking that the TouchPad wouldn’t suck. It shipped. Reality: it didn’t suck. It was a decent 1.0 product. It also didn’t sell. Disappointing. Frustrating. Recoverable. Something to build from, which we were.

And then we woke up one morning, and Leo had decided to take PSG, the PC hardware division, out behind the barn and shoot it. And evidently because the webOS group also had hardware, we got taken out behind the barn and shot, too. Just in case. However badly it was implemented there is in fact a rational reason behind his decision on PSG, although as Meg found out when she ran the numbers Leo didn’t do, it’s the wrong decision. I can’t for the life of me understand why he shot webOS hardware as well, or remotely think that he understood what he was doing of the implications of it. And from that point on, the year turned into a movie based on a Kafka novel.

A kafka novel with what seems to be a happy ending. I gave it a month, expecting HP to get its act together and sell us, hopefully to Amazon. When that didn’t happen and it seemed increasingly remote that it would, I decided it was time to get out and started ringing up the network. And now I’m at Infoblox.

I’ve been there just long enough to meet my cohorts, start learning names and find the bathroom. I haven’t talked about it much because there’s not much to say right now. They have some interesting technologies, they need some social media and community things done, and the building is full of fun and interesting people. So we’re going to go off, figure it out, get it built and make it happen. I’m going to mostly keep it off stage here for now, because there’s really not much to talk about.

My change of venue does change the dynamics of this place somewhat though. My self-imposed restriction on talking about Apple is dead, given I no longer work for a direct competitor and there’s no longer that patina of conflict of interest (but let’s be honest, we were never a competitor of Apple. Maybe worried them a bit at times, but we never remotely put enough units in the market successfully or sustained our momentum to be considered as competing). Ditto wading into the whole mobile space. How far I’ll wade into both topics, I haven’t decided. But I do expect to.

But one thing I’ve come to realize is how — careful — this blog’s gotten. If you look at the blogs I posted as influencing me the other day you’ll see one common trait is that they aren’t afraid to have an opinion and an attitude. Just by sheer necessity I was always fairly careful about what I said when I was at Apple (mostly), and that caution was encouraged at Palm and HP as well. For a company that paid me to be out there  and conversing with the developers, they were usually worried about losing control of the discussion, so “don’t say that” was a common refrain heard around the offices. I think that bled out onto my personal blog, too, and it’s gotten pretty bland. I need to change that, re-inject my personality and opinions into it more.

Over the last few months I’ve been working with a couple of people to help them understand what I’ve come to call this life of “typing without a net”, the part of marketing where there is no script, you don’t rehearse and ultimately, you can’t control the message, merely influence and contribute to it. this new world of social marketing scares the absolute crap out of traditional marketing folks, and some of what I’ve tried to do is help them understand how to leverage the interactivity and conversational aspects of marketing. With some success, I think.

A reality of this kind of work is that if you slip and screw up, you fall a long, long way. Just ask certain people who found that out the hard way in the last week. I’ve come to realize there’s a flip side to that, though. If you allow yourself to get too careful, you may never slip, but you lose a lot of your ability to motivate and influence, either. So one change to the site I plan on bringing because of my change of venue is to get a bit more energy and opinion to my writing again. No risk, no reward. And now, there’s no real reason to be so damn careful.

So we’re going to try to liven this place up a bit; not be so paranoid about subjects that might upset folks or get me one of those “why did you say THAT?” emails from PR… and we’ll see what happens.

welcome to 2012. I can’t decide which I’m happier about — that 2011 is finally over, or that 2012 is a blank slate just waiting to be scribbled on… either way, let’s go!

Your (not so) humble servant,


(p.s. — a couple final notes on HP and webOS, and then I’ll close the book on that for a while and look firmly forward instead: while it’s been fairly trendy among the webOS fans to blame HP for all of webOS’s problems, in my opinion, most of the damage was self-inflicted. If you want to assign percentages, give 70% of the failure to the Palm side, and 30% to the HP side. And realize that if HP hadn’t stepped up and bought us, we’d have run out of money and failed. Any other buyer most likely would have grabbed the patents and run, so at least HP gave us a second chance to make it work. which we flubbed. HP has a set of challenges that I think are going to make Meg’s life challenging for a while — but Palm had a legitimate chance to make it work with HP’s support, and couldn’t. Mostly, blame us for that. And you’ll have to buy me a beer some time to get my opinion’s of why, at least for now…

And I know it was frustrating to many that it took so long for Meg to decide to keep webOS going and open source the technology, but to be honest, she did the right thing, and she took the time to understand the situation. Leo made some amazingly stupid decisions in haste, without appropriate research to understand the implications, and in reality, I don’t think anything was going to “fix” webOS by the time he was retired out and Meg stepped in — it was seriously damaged by those moves, and while it was painful to live in limbo like we did, she couldn’t fix the problem by making the same mistakes and making decisions quickly in ignorance of the details. So she gets full credit from me for taking the time to make the right decision, not a fast decision, even if waiting for it wasn’t fun. And I think she has the strategy most likely to give webOS a shot at returning from the dead again — but it’s going to take time.  It may not work, but the alternative was to give up and go home, and HP is investing a hunk o’ money in giving it a shot. Give them some credit for that, and support in helping them try to make it happen…)


Posted in About Chuq

The new Gig — Now at Infoblox

quick note since I’ve got nine zillion things going on and no time…

I started the new gig this morning. I’m now the Technical Manager for Bloxtools at Infoblox in Santa Clara, California. Myself and my new cohort in crime (who will play the part of Community Manager) are coming in to support and build a community around these tools, and to help define a plan for for enhancing the tools and making them a more powerful and useful part of the Infoblox products suite.

What’s this mean? well, when we figure it out, we’ll know. Part of what made this an irresistible challenge was that it’s really a blank slate; great challenge, great opportunity. And it’s going to allow me to help build a new community from scratch, which I was looking to do, and get back more to my roots and be more technical than I was at HP.

Everyone I’ve met so far has been great, the company feels like a nice, comfortable fit, we don’t have CEOs randomly blowing up divisions because he’s bored, and I get to go off and figure out a bunch of stuff. I’m going to be busy for a while, but in a good way.

And then there was the money… Which frankly, HP was rather reluctant to part with, even going back 18 months when I first had that discussion with Ben and Dion…

More on all of this when I have time, and a chance to start figuring out the details…


Posted in About Chuq