- YahooArchitect, Senior Principal Engineer, 2013 - present
- Google (Android)Senior Software Engineer, 2007 - 2013
- Openwave (Mobile Browser)Software Engineering Manager, Mobile Browser, 2001 - 2007
- Be (BeOS)Software Engineer, 1998 - 2001
- École Polytechnique, FranceMathematics, Physics, Computer Science, 1994 - 1997
- ENSEEIHT, FranceComputer Science, Software Engineering, 1997 - 1999
A reminder in case some people missed my earlier post on that subject (and my apologies for people who are seeing essentially a duplicate):
Yahoo is hosting an event in our NYC office in the evening on Mar 20, i.e. in 10 days.
I'll be there and I'll talk about Android, about Yahoo, about Android at Yahoo. There'll be some quick presentations, and plenty of opportunities to mingle and chat.
Be sure to sharpen your resume.
Want to get invited? Please enter your info at http://bit.ly/NYAndroidTechTalk
Yahoo is hosting an Android event in our New York office, in the evening on March 20.
We'll talk about Android Development, about Yahoo, about Android Development at Yahoo, and especially about the role that Yahoo's NYC office plays in those. I'll be covering the architecture side of things.
You can expect some brief presentations from a few people, including yours truly, as well as enough time to mingle, chat, exchange ideas, answer questions.
This is also a good time to have an up-to-date resume ready.
Register at http://bit.ly/NYAndroidTechTalk
Let me know in the comments what you'd like my presentation to be about :)
- What process does your team take to outlining new applications/features in applications?
- What tools and processes does your team use for testing (unit/instrumentation)
- What are you using to build UI going forward? Activities/Fragments? Something else? Expand...
- If/when/where you're "native" (in the Java-sense, not necessarily NDK) vs. non-native (HTML)
Looking forward to getting on the list ;-)
As an Android user, I appreciate when applications closely follow the Android design guidelines.
However, there's one tiny bit of the guidelines that keeps surprising me, and that's the overflow menu on the bottom action bar (whether a plain split action bar or a contextual action bar). That pattern is used so rarely that I got very strongly used to the overflow menu being on the top-right.
Sadly, as much as I can feel that something isn't quite right for me, I don't know what would be really right.
-The bottom bar is a great way to display more icons than the top bar would hold, since it's guaranteed to hold at least 5 icons, so it can't go away.
-Generally speaking, spreading the actionable icons over both bars makes them hard to scan at a glance, to the point where that's impractical.
-I wonder if leaving the overflow menu on the top bar while the other icons go to the bottom bar would work. Being somewhat isolated and in a very constant position, it's conceivable that the user might be able to "see" it even while scanning the bottom bar. However, that still has drawbacks: a user scanning the top bar would think that there are no actions beyond the ones in the overflow menu, and a user scanning the bottom bar start-to-end would not land on the overflow menu as the last item for actions beyond the ones already shown as icons.
Following the rules is hard. Breaking them is sometimes even harder.
As usual, this is my personal opinion, not my past, present (or future) employer's.
I've been having a lot of fun at Yahoo over the last few months, and I really like that Yahoo is really thinking mobile first at all levels. Of course, who says "mobile" says "Android", and I'm an Android guy at heart, so I'm naturally excited about all the possibilities.
To make the Android future even better and to make it happen even faster, Yahoo needs more Android people, especially engineers. We're hiring, mostly in Sunnyvale (Silicon Valley) and in New York, with a few possibilities in San Francisco as well.
If you want to be part of the team that shapes that future, email me your resume at firstname.lastname@example.org
Here's the official job description for mobile engineering. I actually had a hand in writing it! TL;DR: if you're a solid engineer and you've played with mobile, we've got a seat for you.
Yahoo is the world's biggest startup!
The Mobile & Emerging Product group is building the beautiful mobile apps that inspire and entertain hundreds of millions of users daily. Our applications range from communications to content, from search to sports, and from entertainment to finance and rank among the top in their field. We are committed to delivering a superb user experience and are just scratching the surface! We are hiring engineers to make our apps even better and to drive the evolution and expansion of our current applications portfolio into new technology areas and market segments.
Our mobile engineers build Android and iOS applications. They work closely with designers and product managers within small "pods" that each build one application, which creates the ideal environment for agile methodologies. They can solve problems on their own or in teams, which gives them endless opportunities to communicate and to self-organize. Some work on development, others on quality. Our team structures encourage trust, learning from each other, having fun, and attracting people who are passionate about what they do. Teams use common IDEs for their respective target platforms; they are familiar with the object-oriented APIs they build upon, and they are not afraid of debugging and optimizing.
Some mobile engineers are at Yahoo as interns or as their first job; others have 10 years of experience or more. They are all strong programmers and strong computer scientists. They have usually been involved in mobile applications before joining Yahoo, but their backgrounds are quite varied. Most of them have at least a B.S. in computer science or engineering, with an M.S. opening up the most interesting opportunities.
The road ahead is exciting, and our team is moving fast. Your work will be seen and touched by millions of people, worldwide. If you believe you have what it takes to help shape our future then look no further, apply now, and get ready for the ride of your life!
-BA/BS in Computer Science or related technical field or equivalent practical experience.
-Programming experience in Java, or Objective C, or C++
-Experience in mobile application development.
-Strong foundation in computer science, with strong competencies in data structures, algorithms and software design optimized for embedded systems.
-Deep technical knowledge of Android or iOS mobile application development.
-Knowledge of Android or iOS UI frameworks.
Yahoo is focused on making the world's daily habits inspiring and entertaining. By creating highly personalized experiences for our users, we keep people connected to what matters most to them, across devices and around the globe. In turn, we create value for advertisers by connecting them with the audiences that build their businesses.
Since I was born, my home planet did 14650 revolutions onto itself, i.e. approximately 40 orbits around its star.
I'm 40 years old.
Thanks to everyone who's been sending me wishes. I won't be able to reply to each individual message, but please know that I appreciate them all the same.
40 years ago...
-The Bretton Woods system had recently collapsed and the world money system was very unstable. The US dollar hit its then lowest value against gold.
-The 1973 Arab-Israeli War was slowly starting to wrap up.
-Oil was scarce and rationed in the middle of the 1973 oil crisis. 55 mph speed limit in the US, early daylight savings time
-Tunisia and Lybia somewhat merged for a few days.
-President Nixon was in the middle of the huge mess with the Watergate.
I'm in a good mood today, and in the spirit of sharing here's one of my Software Engineering secrets, in one sentence:
"Assumption is the Mother of all Fuckups."
I used to have that quote printed and taped to my whiteboard, until I learned to recognize cases where I was making the kind of assumptions that could lead to difficulties.
They're talking about Bordeaux reds here, not whites (which are also worth looking into), and more specifically about the higher-end Bordeaux.
What can make those wines unusual to connoisseurs used to Napa and Sonoma Merlots and Cabernets is how long the Bordeaux need to age. One of the worst things you can do to a Bordeaux is to drink it too young. Even the lower-end ones benefit from 5 to 10 years, while the better ones often peak between 10 and 15 years of age.
If you're going to be buying high-end red Bordeaux, Bourgogne or Côtes du Rhône wines, which all need to age, you need to have a dedicated wine fridge that'll keep your bottles horizontal at a constant appropriate temperature, so that they can age properly. 55°F (12°C) is a good starting point, which is considerably less cold than a kitchen fridge. Unlike wines that only need to age 1 or 2 years for which you can somewhat get away with a rack at room temperature, too much damage would accumulate from keeping a bottle that way for 5 to 10 years.
Even a basic wine fridge beats having none at all, and a good wine fridge costs between $10 and $15 of bottle capacity, which is reasonable compared to the cost of the wines you might put in there.
For years, I got used to the philosophy of setting goals that are very ambitious, that can't be achieved with certainty, such that they give a sense of direction. For my readers familiar with the movie "Office Space," that's the difference between making the goal 10 pieces of flair or 50 pieces of flair.
The federal government, via NHTSA, sets a minimum bar for crash safety: on-center head-on collision at 35mph. The requirement hasn't changed for years. It sets the bottom bar, below which cars are considered so unsafe that they can't legally be sold in the US.
On the other side, the insurance industry, via IIHS, runs its own series of tests, and (more importantly) they keep adding new tests as soon as enough cars get close to the existing bar. Unlike the government that needs to juggle multiple goals (fuel economy, cost, competition, protectionism), the insurance industry has a narrower goal: they want to reduce how much they pay as a result of accidents.
IIHS isn't in the business of designing tests that all cars pass, because car manufacturers would then have no incentive to improve the cars. Instead, IIHS designs tests that most cars initially fail, forcing car manufacturers to actually improve the cars.
As a result, every single time IIHS adds a new test, car manufacturers have the same reaction, like a broken record: essentially "our cars pass the government tests", which really means "our cars aren't so grossly unsafe to be illegal". And, yet, we saw it with the side impact test, we saw it with the roof test, and we're going to see it with the small-overlap test: within about 5 years, cars will be modified to pass the new test, and IIHS will introduce a 5th test in their procedure.
What that next test will be is anyone's guess. I can imagine two directions:
-on-center rear-end test at 50mph (which is really two tests).
-adding crash test dummies of different sizes, to represent a 95th-percentile male and a 5th-percentile female.
It's a cat-and-mouse game, and it makes cars safer. I like it.
I'm sitting at work trying to have breakfast in the café, and I'm laughing so hard that I can't actually eat. My coworkers around me are giving me funny looks.
If you know anything about the community of OS-level Android hacking, read the comments on the original thread. Read ALL the comments. I bet you can't make it to the end without a real-world LOL.
Kudos to T-Mobile for jumping into the thread with the official corporate account and having fun with the rest of us. They manage to remind us that they're real people, which is very #uncarrier.
Welcome to the Tied House Brewery & Cafe | The South Bay's Origi...
The South Bay's Original Microbrewery Since 1988!
Factory Images for Nexus Devices - Google Support for Nexus Phones and F...
Factory Images for Nexus Devices. This page contains binary image files that are provided for use in restoring your Nexus device's origi
The Free Software Definition - GNU Project - Free Software Foundation (FSF)
Since 1983, developing the free Unix style operating system GNU, so that computer users can have the freedom to share and improve the softwa
Mt. Rose Ski Tahoe - Tahoe's Highest Base Resort, Closest to Reno.
Mt. Rose Ski Tahoe - Tahoe's Highest Base Resort, Closest Tahoe Ski Resort to Reno.
Imus Geographics | The Art of Cartography | USA Map
"This one will remain a classic!" – Stuart Allan, Raven Maps. "This is the map of the U.S. you've been waiting for....abs
Orion Telescopes: Save on Telescopes & Binoculars! - Telescope.com
Telescope.com: The friendly telescope experts at Orion Telescopes will help you choose the right telescope. Same-day shipping. 100% satisfac