Home
JBQ's blog [entries|archive|friends|userinfo]
Jean-Baptiste Queru

[ website | JBQ's home page ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Links
[Links:| Mobile version ]

And in work-related news... [Jul. 5th, 2008|10:34 am]
[mood | groggy]

It's been more than 3 months since I last wrote about work and Android.

Recently, I've been using a device running Android a lot more than I previously had. I have to say it's getting really good. There are still a few areas that need a bit more polishing before the first devices can ship, and there are a few areas which aren't quite as good as I'd like them to be but won't be changed for the first release, but as far as I can tell the months (and, for some, years) of hard work have put us on track to ship some good devices according to our internal schedule and within the timeframes that we had previously announced.

Overall, comparing those Android-running devices to some non-Android phones that are currently on the market, I have to say that Android is playing with the very best when you look at the overall package. Because there are so many phones out there, there are many areas where those first Android devices won't be the absolute best (and in fact in the majority of areas you could find at least another device that is better), but there are also some areas where I'm convinced that it's really going to out-class everything else. The openness to third-party applications is one of those areas. Overall, the devices I've seen are going to be playing in the top class.

The software platform itself is going to be open-source (and therefore will be available both to hobbyists and to phone manufacturers for free with no strings attached). The software is going to be carrier-grade, which will open the door for mass shipments, which in turns will open a wide market for third-party developers who want to use Android as a development platform. And, last but not least, from the very first day those devices will be able to run third-party applications, without any need for certifications or approvals, in a secure environment. We've even had preview SDKs available for almost 8 months, so that developers have been able to get a feel for the way the platform works well in advance of the first devices being available, which means that they won't be surprised by the entire platform and will be able to get applications ready very soon after devices become available.

Right now, we're hitting some trickiness in managing the expectations of the developer community. On the one hand, they'd like a new SDK (the one they currently have is several months old). On the the other hand, what they really want is to get some devices and an SDK that matches those devices, since in the end there's no point developing phone apps if those apps can't run on phones.

Any time that we spend preparing an SDK before the final phone software is ready that could have been spent working on the actual phone software introduces additional delays in shipping the phones and the final SDK (since we'll obviously want to have an SDK out that match the shipping devices as closely as possible).

We're also in a phase where we're doing a lot of API polishing, changing things that can't be changed without breaking some compatibility and therefore couldn't be changed easily or at all after the first devices ship. Our latest internal full-stable variant isn't compatible with our bleeding edge (the bleeding edge being the one closest to what we're planning to ship), so if we did an SDK right now it still couldn't be used to develop applications for the devices that will ship.

Based on all that, when developers ask for an SDK roadmap, the answer is likely to be pretty amusing: the real roadmap we have is to ship devices as quickly as possible. Any work on getting an SDK ready can really only happen on the team's proverbial copious spare time, which we have essentially none of since any time we can spend making the framework better for the long term is likely to be an excellent investment.

There's good news, though: there's always a fairly large amount of time between the point where the phone's software is finalized and the point where the phones are commercially available, since acceptance, production and logistics take time. Unless some disaster strikes, there should be plenty of time after the final software is finalized to prepare a matching SDK and make it available well ahead of the availability of devices, so that developers have plenty of time to port their software to that SDK before they get a chance to test it on devices. Because, let's be honest, it's grossly unreasonable to pretend to ship software that runs on just about any platform without seriously testing it on actual hardware, which means that external developers won't be able to reasonably ship applications on the same day the devices become available, they'll have to test and debug first, and therefore all they need a new SDK for before the final devices are available is to get ready to test and debug, not to be ready to ship.

In the end, none of this should be a surprise to anyone who has experience in the cell phone industry, it's all consistent with best industry practices, with what has been announced and confirmed already, and with just plain logic. Nothing to see, really, move along.
link7 comments|post comment

Did Apple get out-Appled? [Jun. 11th, 2008|06:47 am]
[Current Location |Google shuttle]
[mood | disappointed]

Apple is one of the rare companies that manages to maintain an image in the public mind that they stand for the little guys. Part of that comes from being an outsider, and part of that comes from creating outstanding products (engineer burnout be damned).

As an example, Apple has stood a firm ground on downloads for 99 cents, on the ability to play downloaded music on multiple machines and multiple devices and even to stream it. The iPod outclasses every single other portable music player out there by a wide margin.

Yet, with the iPhone 3G, Apple's image just took a dent as Apple got out-Appled by AT&T. No matter how you look at it, Steve's Reality Distortion Field (TM) couldn't hide the fact that this time AT&T was holding the stronger position at the negotiating table. With their exclusivity contract and a pipe that funnels enough money into Apple's account to make a visible dent on their bottom line, AT&T was able to raise the prices of their side of the deal while Apple had to lower their prices. Overall, the iPhone 3G with its mandatory 2-year contract costs $1880, whereas the older version used to cost $1840. Admittedly the difference is about the same as the inflation over a 1-year period, so it doesn't cost more in relative terms, but it's important to see that Apple is cutting into their margins while AT&T is growing theirs (especially as stupid Americans who sign contracts without reading them will buy iPhones instead of buying iPods, cutting into Apple's margins even more).

To make things worse, the old iPhone used to be unique in the way you didn't have to deal with long lines, slow processes, and stupid salesmen (and stupid saleswomen, that's an area where sexes are definitely equal). You could just spend a few minutes online, order your phone, and a few days later after it got delivered you just plugged it into your computer and activated it - just what you'd expect from an Apple product. With the new iPhone, that's gone. You've got go to an Apple store (if you're lucky to have one not far from where you live), which might even require some crazy parking or transportation schemes as some of them are very inconveniently located, or (god help you) you'll have to deal with AT&T and their slow-as-molasses customer representatives (I feel ashamed that those sloths would pretend to represent me).

AT&T has almost succeeded in hammering Apple back down to the level of being just yet another phone manufacturer. You can already bet that the next iPhone will only be sold in AT&T stores, that it'll cost $99 with a plan that'll cost $80 a month. And people will continue buying them and getting themselves locked up be evil contracts from evil companies.
link10 comments|post comment

High gas prices: live with the consequences of your choices. [May. 29th, 2008|06:57 am]
[Current Location |On the Google shuttle]
[mood | bitchy]

The price of gasoline (petrol for my UK readers) has been going up in the US, and it now costs about 3 times as much as the lowest I've seen it in my 10 years living here, now reaching 4 USD per US gallon.

And yet I can't get myself to call this expensive. At the current exchange rate, that's equivalent to 0.67 EUR per liter, i.e. not even half the current prices in France. Looking at historical prices in France, that was the price there in 1982, 26 years ago, not adjusted for inflation. By the time you adjust the prices for inflation, you realize that gasoline costs less now in the US than it ever did in France in the last 50 years, and that in fact since 1973, i.e. over the last 35 years, gas in France has almost always cost more than twice as much as it currently does in the US.

Now, I realize that many people in the US currently feel the squeeze of the price of gas (and of just about everything else whose price indirectly includes the cost of some gas or diesel fuel). But you've got to look around: look at the number of cars on US roads that weigh more than 1.5 metric tons (about 3300 lbs), that have more than 4 cylinders, more than 2 liters of displacement, or more (and possibly much much more) than 100 hp. All those aspects are not strictly necessary, they's just conveniences or luxuries. By buying or driving such cars, you implicitly accept that those unnecessary and luxurious aspect of a car will cost you extra gas. The notion that oil prices were going to go up had been around for years, so you can't say you didn't see the increases in gas prices coming.

The average real-world combined mileage of cars in France, right now, is 33 mpg. We're talking about existing cars that are currently on the road, not just new cars, we're talking about combined city + highway mileage, not just highway, and we're talking about real-world mileage, not an estimate in a lab in ideal conditions. And yet with all that people in France barely drive more than 7500 miles per year, because France has good public transportation at the urban, suburban and national levels. So, all you big wasteful US car manufacturers, stop your whining about not being able to reach 35 mpg in 2020, pretending that the technology doesn't exist, because the technology already exists. Mr Lutz, your real problem is that you haven't spent your R&D dollars wisely, so stop spreading FUD as an excuse for your own mistakes.

So, to everyone in the US who has been teasing Europeans for driving light cars with small engines: as it turns out, Europeans know how to make cars too, they're just optimizing for a different goal. How does "we told you so" sound?
link20 comments|post comment

No wonder it was hard! [May. 24th, 2008|09:45 pm]
[Current Location |Home]
[mood | excited]

I feel stupid.

So far I had been enjoying playing Everyday Shooter on the PS3, in a twisted way as I used to find the game atrociously hard, and I hadn't managed to play through the 3rd level (there are 7). And today, by accident, I discovered why: I hadn't figured out that you could change the number of starting lives, and I must have set it accidentally down to 1 at some point in the past. With only 1 life, no wonder it felt too hard. Bumping my life count to 3, I was able to beat the 3rd level with no problem, and I had enough credits to buy myself 3 extra lives, so that I can now start with 6 lives, which is enough to get me quite further in the game.

Now I've got to figure out that 4th level.
link2 comments|post comment

Why Star Trek Transporters can't happen [May. 18th, 2008|10:05 pm]
[Current Location |Home]
[mood | quixotic]

Well, in other countries they might be possible, but in the US there's no chance that we'll ever see Transporters just like they have in Star Trek: those things would need to get approved at least by the FDA, FAA, FCC and DOT, as well as DHS, CIS and TSA, and who knows whether the CDC and FTC would also have something to say, and maybe even the NRC. On top of that keeping the FBI, CIA and NSA happy would make things even harder. Don't even get me started about the SSA and IRS.

Gotta love the TLAs (three-letter agencies).
linkpost comment

Plane ticket annoyances [May. 18th, 2008|01:09 pm]
[Current Location |Home]
[mood | happy]

I've just spent literally hours today (not counting some time yesterday and a bit in the days prior) hunting for plane tickets at decent prices for our vacation in Europe this summer, going to my brother's wedding and to see my in-laws in Greece.

If we had taken the exact flights on the exact days that we wanted, the total cost would have been over $5000. I wasn't very happy about such a price. After some long and stressful research (with many situations where a flight would be quoted for a certain price, but then at the moment when I wanted to pay the fare would grow by 50%), and with a little bit of flexibility, I've been able to cut the overall cost of the entire trip by almost half. It's still a bit pricey, but I think that I got reasonably close to the base price.

I did manage to avoid connecting in the US on the way back (which is always very risky because of potential immigration delays), but unfortunately I didn't manage to avoid London (which means that we'll have to follow the UK's restrictive rules about carry-on luggage). I also managed having more than one connection in any given day, though we do have situations where we take the last flight of the day on some of the routes we fly, and we have one case where we have a long drive right before a flight.

Ultimately, we got tickets for 11 flights (well, technically I bought tickets for 12 flights, but I'll skip one of them as the ticket prices changed under my feet as I was booking). We'll be flying on 3 different airlines, through 5 airports.

I've noticed very clearly that once you do a few price searches on a given route, the price increases for a few hours (at least that's what I saw on both United and Lufthansa), so it's somewhat clear that one possibly strategy is to find the flight you want (which can take a few attempts), wait a few hours, and book the flights.
linkpost comment

Canon equipment sold by weight? [May. 10th, 2008|06:21 pm]
[Current Location |Home]
[mood | content]

I took the plunge today and bought some camera equipment that I had been looking at for a while.

I bought a 135/2L lens - a lens known for being remarkably sharp. It's also surprisingly heavy for its size, coming in at 750g, because of course of the large glass elements.

I got a 1.4x extender to use with my 400/5.6. Sometimes 400 is a bit too short, and Canon doesn't have longer options that fit my budget, so I figured that the extender was the way to go. The 400 should be sharp enough to stay usable even with the extender.

Finally, I got a Digital Rebel XSi (a.k.a. 450D, a.k.a. Kiss Digital X2) with its 18-55 IS kit lens, primarily to use with my 300 and 400 lenses (and of course with the 400 combined with the extender). Eugenia and I might also use it as a walk-around point-and-shoot when we want a better quality than a plan pocket camera but don't want to bother with the 5D.

The funny thing is that all 3 of those items have a cost that's almost proportional to their weight. Maybe Canon started to sell their equipment by the gram (BTW, that'd be about $1.30 per gram based on what I bought today, though I know that the rule doesn't hold throughout the entire range).
link2 comments|post comment

How the best do it [Apr. 29th, 2008|09:38 pm]
[Current Location |Home]
[mood | calm]

The design director of the NY Times explains why the Times looks so good and works so fast on so many browsers and platforms (and talks about many other things, but that's not my point here). The reason is simple: they do it "the hard way". Joel Spolsky put it very well: where there's muck, there's brass: the big money is in doing hard things, not in doing easy ones.
link1 comment|post comment

Outrageous reactions [Apr. 29th, 2008|06:43 am]
[mood |outraged]

( You are about to view content that may not be appropriate for minors. )
link8 comments|post comment

Big date [Mar. 31st, 2008|07:08 pm]
[Current Location |Home]
[mood | nostalgic]
[music |Johnny Cash - Hurt]

Today is a pretty interesting day for me, it's one of those days that I'll probably remember for a while:

-it's exactly my 10th anniversary in the US.

-the first stage of my green card just got approved.

-my previous company, Openwave, announced that they were stopping R&D efforts on their client product line, on which I had worked for more than 6 years.

Oh, and just in case that wasn't enough, I've also reached a good milestone at work, a former co-worker from Be and Openwave just started today on Android, and it's the 10th anniversary of Mozilla being open-sourced.
link3 comments|post comment

I want an Android phone! [Mar. 23rd, 2008|11:10 am]
[Current Location |Home]
[mood | cheerful]

Now that I get to play with Android devices every day (well, when I'm at work), I'm getting excited about the possibilities of such devices. I'm really looking forward to those being available for retail sale so that I can get one that I can actually use in the real world.

Looking at the Android world, the amusing part is that few people seem to have experienced first-hand the reality of mobile software cycles: it might not be obvious from the outside, but by the time a version 1 of anything comes out there've often already been years of development behind it, and the product cycles are typically of the order of 10 years (from the point where someone has an idea for a product to the point where that product has disappeared from consumers' hands). From that point of view, it's unreasonable to look at the very first device that ships with Android and to reach an immediate conclusion about the success or failure of the platform. Some aspects will be great, some aspects will be rough, which is to be expected with any 1.0 environment.

If you assume that new versions come out once a year (which is really the right cadence in this industry), if a version 1 is released in year N, by the time it really hits the shelves, hits people's hands, and the company that made the product gathers significant valuable feedback, it's pretty much already too late to incorporate much of that feedback in the version 2 that gets released in version N+1, and it can only get used in version 3 (in the year N+2). For a product that gets released in 2008, it is important to think of 2010 as the point where feedback can really be take into account.

Even worse, if you realize that a version 1 is often released without all the features that were originally planned for that version and that version 2 is the first version that contains everything that people had originally envisioned, it takes up to version 4 to really take all the feedback into account.

From my point of view, the data at which we'll be able to look at Android and to decide whether the product got something achieved isn't 2007 or 2008, it's 2010 or 2011. That's the way things work in this industry.
link7 comments|post comment

Photography equipment [Mar. 23rd, 2008|08:33 am]
[Current Location |Home]
[mood |spendy]

I'm very happy with my photography equipment, and yes CAS (Canon Acquisition Syndrome) keeps itching the back of my mind. I've reached the point where every new purchase is $1000 or more.

I've been thinking of the following pieces of gear:

-A Canon EF 135/2L: just about everyone who touches one of those says it's one of the best lenses they've ever seen. It's not quite as legendary as the 200/1.8L, but it's still a remarkable lens. It is sharper wide open than many lenses when stopped down, and when stopped down it is sharper at the edges than many lenses in the center. While my 70-200/4L is pretty good, especially at 135mm and stopped down a bit, the 135/2L would allow me to get a similar image quality while opening by 3 more stops.

-A Canon MP-E 65/2.8: that's a dream come true in terms of ultra-macro, allowing to take pictures with a diagonal of 1/3 of an inch, i.e. 5x more magnification than "regular" dedicated macro lenses, or 20x more magnification than most zooms. Given that I already have a strong tripod, a remote release, a macro focusing rail and a ring flash, it doesn't seem so unreasonable.

-A Canon Digital Rebel XSi: the 5D is great for all-around photography, but when it comes to using telephotos its large pixels prevent me from getting the best out of my existing lenses. I'd like to know whether the XSi can focus with f/8 or f/11 lenses when in liveview before I buy, as that's quite an important aspect for me (and if it can't I might go for a cheaper XTi instead).

-A Canon TS-E 90/2.8: tilt-shift lenses are fun to use, they allow for some funky special effects, but I don't know whether I'd use it more than a few times for the fun of it.

-A pair of studio flashes. A pair of good monolights with matching stands and light modifiers would let me play with light indoors. Once again it's not clear that I'd use those a lot, though.
linkpost comment

Enjoying the week-end [Mar. 23rd, 2008|07:49 am]
[Current Location |Home]
[mood | rejuvenated]

So far, this has been a very enjoyable week-end. I've been catching up with sleep (after two hard weeks at work), and I now feel (relatively) rested. Eugenia and I went to eat out in our "usual" restaurants for dinner on Friday and lunch on Saturday.

We also went out for a bit of photography in Foster City. Eugenia got me a 16GB compact flash card, and I'll be using it to shoot RAW+JPG (so far I had only been shooting JPG). I discovered along the way that my 5D was still running its original firmware (I hadn't had any problem with it, and therefore I had no reason to upgrade), and that that firmware couldn't deal with cards larger than 8GB. I installed the latest firmware, discovering along the way that firmware upgrades could only be done through cards smaller than 2GB, and voila, my 16GB card was fully recognized. I can now take approximately 700 shots with the best possible image quality that my camera will get, without changing the memory card or the batteries, and that is pretty cool.
linkpost comment

Addictive work [Mar. 13th, 2008|08:04 pm]
[Current Location |Google bus]
[mood | high]

The current phase in our development cycle at work has been an opportunity to play around with my schedule, to see how long I can work every day when I'm having fun doing it.

The problem is that I can't seem to find my limit. 12+ hours a day at my desk is definitely not a problem. I'm just having fun putting something together. It's simply addictive, and I guess I'm becoming a workaholic again, without the love-hate relationship that I had felt the last time I worked so much.
link3 comments|post comment

Am I becoming younger? [Mar. 12th, 2008|08:02 pm]
[Current Location |Google bus]
[mood | amused]

The other day, Eugenia and I went out for dinner, I ordered a cocktail, and the waitress asked to see my ID (and she really wanted to see it, she made me take it out of my wallet entirely). This must be the third time this year that someone wants to see my ID when I purchase alcohol.

I was already well several years over the legal drinking ago when I moved in the US, and that was almost 10 years ago. I guess I must still look pretty damn young (or at least I must look like it's hard to put an age on my face with the big bushy beard).

Amusingly, I've noticed two things:

-There are 3 stores where I routinely buy alcohol but that have never asked for any ID.

-There seems to be an inverse correlation between the price of the alcohol I buy and the probability of getting carded. I guess that the assumption is that people below legal drinking age can't afford to buy the good stuff.
link4 comments|post comment

Pixel counts and pixel sizes [Mar. 8th, 2008|06:56 am]
[Current Location |Home]
[mood | calm]

There are some interesting thoughts about pixel counts and pixel sizes in Michael Reichmann's PMA 2008 thoughts.

While Michael's overall thoughts are definitely right on target, I'm afraid that his numbers might be a bit off, in a way that makes some potentially significant differences.

Michael properly recognizes that the pixel size is an important indicator of how a camera will behave, and that pixels that are too small are ridiculously useless. What he seems to have lost track of is the fact that pixels in point-and-shoots have become really tiny, much smaller in fact than he postulates. He says that point-and-shoots might now have pixels as small as 2.8 microns, maybe even smaller. In fact it's been a while since pixels became smaller than that: the batch of 2/3" 8MP cameras that shipped 4 years ago already had pixels that measured 2.7 microns, an in fact Reichmann himself wrote about that in his review of the Sony F828.

The reality is that point-and-shoots have shrunk their pixels from 2.7 microns about 4 years ago down to 2.4 microns, then 2.2, then 2 microns, and now (with the latest batch) 1.8 microns is quite common (some even go smaller).

Michael is correct when he says that such tiny pixels will cause severe issues with noise: for all I know sensors are still limited to storing at most 1000 to 1200 electrons per square micron. With pixels of 1.8 microns, that means that each pixel is unlikely to hold more than 3900 electrons when fully saturated. Let's assume that there's a 5-stop contrast in a given scene (an evenly lit scene with normal whites and normal black objects, e.g. a bride in a white dress and a groom in a black tuxedo) which is actually not bad at all, and that the camera will be able to meter to exactly bring the sensor to saturation without overexposing, the dark areas will still only get about 120 electrons per pixel (and it's not obvious that colors will be accurate in the highlights when shooting so close to saturation). With 120 electrons to work with, the signal to noise ratio will be about 11:1, i.e. 21dB, i.e. there'll be quite some noise in the dark areas.

If that sounds low, you need to realize that I was talking about ideal conditions: in real-world scenes, light isn't quite even, and in fact it's not uncommon to see a range of 7 or 8 stops across a scene (a bright object in sunlight next to a dark object in the shade will do just that), and sometimes you'll have to bump the sensitivity. I won't even talk about a worst-case scenario with such a camera, but each stop of contrast and each stop of sensitivity costs 3dB in the dark areas, so you can easily figure out where this is going.

Worse than that, those pixels are so small that the lenses that are typically associated with them can't possibly create sharp details (and by that, I mean "details so sharp that the resulting image would be visibly less sharp if there were fewer pixels on the sensor). I have a rule of thumb about that: a lens and a sensor are reasonably well-matched when the peak sharpness of the lens is reached at a numerical aperture that's approximately equal to the pixel size in microns. Let's take the example of the recently announced Sony W300: pixels are 1.8 microns, lens is f/2.8 - f/5.5. Even if we assume that the lens is perfect wide open, that lens would probably be a good match for a 6MP sensor, and that's only for the wide end - by the time you use the zoom, the image quality will degrade even further. To be honest, with such a camera, in spite of is 13.6MP output, I wouldn't bother capturing images larger than 8MP at the wide end and 3MP at the long end. OK, so storage is cheap and capturing 13MP images doesn't cost much, that's true. Still I wouldn't expect the resulting pictures to hold enough quality to print much beyond 8x10 when captured at the wide end, and 4x6 at the long end. Of course, that depends a lot on subject matter, and some subjects might be just fine when printed at larger resolutions, but in general everything will lack texture when captured with such cameras.

On the other hand, Michael Reichmann doesn't think that there's a need to go to pixels much below 5 microns for DSLRs. In general I'd agree with him based on the aforementioned rule of thumb: few lenses peak below f/5. That being said, there are today DSLRs available with 5 micron sensors (the 10MP 4/3 ones), so the notion of having such pixels isn't outlandish. Michael also suggests 60MP medium-format sensors, whose pixels would be 5.4 microns across, and it's reasonable to assume that a 35mm lens can be slightly sharper than a MF lens (since where are fewer design constraints). Michael also has his numbers wrong, and a full-frame 35mm sensor with pixels of 5 microns would have 34.5MP, and not the 25MP that Michael mentions. I'll go even further, and I'll say that pushing down to 4 microns wouldn't be outlandish, since there are some lenses that are so good that f/4 is a reasonable shooting aperture: even Canon's cheap ($300) 50/1.4 would do just fine at this aperture, and all the Canon L primes between 24 and 135mm should be able to produce very good images on pixels as small as 4 microns. Seeing how camera manufacturers have no second thought pushing cameras with pixels much smaller than the lenses can resolve, I'll disagree with Michael here and I'll say that we will eventually see full-frame 35mm DSLRs with pixel counts of 54MP or more. The real question is to know what to do with such images. We're talking about massive prints here, 24x36" at 250 dpi, 40x60" at 150 dpi. Since I currently print 18x24" at 160 dpi, I can really say that such print sizes aren't a stretch at all. The real problem is the cost of printing such sizes: in a nutshell, a printer capable of printing 40" wide costs $5000, and having such prints made in a print shop will take you down $200 per print (or more).

All that being said, I'm still happy with my Canon 5D. It's generally well matched to my lenses and my printer, and while I'd be happy with a few more pixels there isn't anything else available today at a price point that would satisfy me. Until I see a successor to the 5D with about twice the pixel count, I don't have any reason to consider a replacement (and even then I'd end up having to upgrade the printer, and at that size the printer costs as much as a camera, though in that case I might end up skipping one size and jumping directly to an even larger format).
linkpost comment

Misleading Toyota ad [Mar. 6th, 2008|08:56 pm]
[Current Location |Home]
[mood | amused]

There's a toyota radio ad those days, that says something like "spin around town in the 37 mpg corolla", or at least something along those lines, and in my opinion it's quite misleading, as the EPA estimates for the corolla are actually 28 mpg in city driving.

Now, of course, I drive my V8 camaro around town, get about 16 mpg, and I've just made a $65 fillup, my most expensive ever in the US, so who am I to complain about the difference between 28 and 37 mpg?
linkpost comment

Anagrams [Feb. 27th, 2008|09:29 pm]
[Current Location |Home]
[mood | bouncy]

I've been playing with a anagram server to see what I could get out of it.

For my name, I got "Antique Jasper Tube" (my favorite so far), "Bitter Japan Queues", and "Japanese Brute Quit".

For Eugenia's (using the official spelling of her first name), I got "In Agile Love".
linkpost comment

Openwave browser [Feb. 13th, 2008|06:47 am]
[Current Location |Google bus]
[mood |proud]

Openwave announced new client products yesterday, and more specifically introduced Surfer, its latest and greatest browser.

It makes me pretty proud to see the V6, Mercury and Surfer browsers mentioned together. I had quite some involvement in V6, since I wrote the memory manager, the window manager, the global error handling, and I was the czar of the public APIs, of performance and of the memory footprint. I did a lot more in Mercury and Surfer, where I was designed many of the core data structures (and some of the algorithms) and most of the fundamental APIs, and implemented the entire skeleton of the rendering engine. Back when we started working on Mercury, we already had Surfer in the back of our heads, and I'm very happy to say that the architecture held itself very well through the years - the system didn't need any re-architecture since 2003, and even when some unforeseen use cases showed up everything was flexible and scalable enough to take care of the new features with no drama.

The sad part, though, is to see how a lot of the engineering talent that was involved in those projects has left Openwave. Once we got past the initial ramp-up, a lot of the heavy lifting was done by a team of 5 people, and none of them remains at Openwave (we're at Google, Yahoo, Apple, Mozilla, and... retired). Pretty much the same can be said about MIDAS, where many of the original members of the engineering team have left (and many of those who left are now at Google).

There's a good side in such a situation: it gives people some good opportunities for growth. I wouldn't have grown into managing a team of a dozen people if a manager above me hadn't left. Losing some key talent in my team also allowed some people to step up, sometimes in ways that were unexpectedly successful. The bad side, of course, is that losing senior engineers tends to lose a lot of technical knowledge about the products. that's especially true in companies that don't have enough engineering discipline to write appropriate documentation, and/or when the people who leave understand the design philosophy of the product (which is very hard to document anyway, even in environments where documentation is normally well written).
link1 comment|post comment

Finally, some action! [Feb. 11th, 2008|07:03 am]
[Current Location |Google bus]
[mood | curious]

Openwave issued 4 press releases today, 2 about new products, and 2 about customer activity. I'm looking forward to seeing those new products gain traction, and those customer-related activities be followed by more.

The odd part is that those announcements didn't seem to get the stock price moving (at least no more than the usual noise) as of 7am PST. What's up with that?

Update (9:45am PST): All right, the stock is moving up a few percent.
link2 comments|post comment

navigation
[ viewing | most recent entries ]
[ go | earlier ]