Meet the team
MicroB is composed of a number of Nokia engineers as well as many more
unmentionables. Since the unmentionables are well unmentionable, I'll start by
describing what would make a normal team.
What does it take to make a product?
- Managers! (lots of them, the more the merrier)
- An Architect (one is a good number)
- User Interface Designers (the fewer the better)
- Release Engineers (one is usually sufficient)
- UI Engineers (a couple will do)
- Core Developers (a handful is best)
- Testers (the more the merrier)
- Localizers (perhaps a couple dozen, but you'll never meet them)
- More Testers (to complain about the same things that the other testers were
testing, but claim that they're problems with the localized versions)
- Add-ons (OK, these are optional, and aren't really part of the product)
- Platform developers (these are an external resource who if you're lucky
might be around to ask for features when you don't have time to talk to them)
- Triagers (you can never get enough)
So who can you actually meet?
Some of our managers have introduced themselves publicly, so I suppose they're
Who's the architect?
Who is the User Interface Designer?
- Sorry, he doesn't seem to have a presence.
- So all I will say is that it isn't
tigert, but he's a public figure, and
I think he'll occasionally answer questions. So, I suppose you can ask him. :)
Who works on the User Interface?
Well, our team is actually quite small, so most of us do double or even triple
duty. So I'll list someone here:
Who is a core Developer?
Who are the Testers?
- This is where you come
please join us
:). We can always use more testers.
Why do you have a web designer?
We were just lucky, I guess.
- Adobe Flash, it's not made by
our group. Yes people work on it. But they're not in my group, so I can't say.
- Mozilla Add-ons. Definitely not really
a part of our group. And to use these, you'll need someone to repackage them.
Who triages browser bugs?