Re: google team and the DIY way of life

2007-11-13 Thread Siju George
On Nov 12, 2007 11:18 PM, Ted Unangst <[EMAIL PROTECTED]> wrote:
> On 11/11/07, Sean Darby <[EMAIL PROTECTED]> wrote:
> > If anybody from the OpenBSD team ever works for Google, it will certainly 
> > be a very wise move on behalf of Google for hiring them.
>
> do the people currently working at google count?  or does it have to
> be a new hire?
>

Just heard of Neils Provos.
Who else? just curious :-))

Kind Regards

Siju



Re: google team and the DIY way of life

2007-11-12 Thread Ted Unangst
On 11/11/07, Sean Darby <[EMAIL PROTECTED]> wrote:
> If anybody from the OpenBSD team ever works for Google, it will certainly be 
> a very wise move on behalf of Google for hiring them.

do the people currently working at google count?  or does it have to
be a new hire?



google team and the DIY way of life

2007-11-12 Thread xavier brinon
-- Forwarded message --
From: xavier brinon <[EMAIL PROTECTED]>
Date: Nov 12, 2007 10:12 AM
Subject: Re: google team and the DIY way of life
To: michael hamerski <[EMAIL PROTECTED]>


I'm working for a French ISP where the dev team seems to live in a
kind of secret chamber.
I tried 3 times to code my own tools, sharing it with collegues. I've
been told to quickly remove them, even if the tools helped a lot my
collegues and myself.
It's a shame, they didn't look at it and we were all back to the old tools.

It's just for me to show that sharing code inside a company and having
the ability to work with it is not available for everyone.

It's not what they do, it's the way they work that is important for me here.
I don't know how your company deals with that kind of thing, mine just don't.

you must read that post like : "hey, what you do here is great ! Even
big companies know that !"
I can post it in every open source community list, but i'm just an openBSD fan.
And Misc@ seemed the most relevant to me.

Sorry if it is not.


On Nov 11, 2007 11:15 PM, michael hamerski <[EMAIL PROTECTED]> wrote:
> > "Posted by Reza Behforooz, Software Engineer
> >
> > In my first month at Google, I complained to a friend on the Gmail
> > team about a couple of small things that I disliked about Gmail. I
> ...
>
> Dear Google,
>
> Could you get Reza to fix contact/label whitelisting in Gmail while he's at 
> it?
>
> thanks,
>
> mike



Re: google team and the DIY way of life

2007-11-11 Thread michael hamerski
> "Posted by Reza Behforooz, Software Engineer
>
> In my first month at Google, I complained to a friend on the Gmail
> team about a couple of small things that I disliked about Gmail. I
...

Dear Google,

Could you get Reza to fix contact/label whitelisting in Gmail while he's at it?

thanks,

mike



Re: google team and the DIY way of life

2007-11-11 Thread Sean Darby
On Sun, Nov 11, 2007 at 11:16:51AM -0600, Jacob Yocom-Piatt wrote:
> Nick Guenther wrote:
> >On Nov 10, 2007 5:00 AM, Sean Darby <[EMAIL PROTECTED]> wrote:
> >  
> >>On Sat, Nov 10, 2007 at 10:31:11AM +0100, xavier brinon wrote:
> >>
> >>>from the "Official Google Blog"
> >>>
> >>>"Posted by Reza Behforooz, Software Engineer
> >>>
> >>>In my first month at Google, I complained to a friend on the Gmail
> >>>team about a couple of small things that I disliked about Gmail. I
> >>>expected him to point me to the bug database. But he told me to fix it
> >>>myself, pointing me to a document on how to bring up the Gmail
> >>>development environment on my workstation.
> >>>
> >>>I know, it's obvious that it's works if you share your code and let
> >>>others submit their diffs.
> >>>Just a reminder... See Google ? they shut up and code !
> >>>  
> >>Why? (...why bother sending that to this list? fyi: this isn't a google 
> >>list.)
> >>
> >>Just curious, not intending to spark anything negative.
> >>
> >
> >Because Google Shuts Up And Codes.
> >Of course, this is off the googlepropaganda, so we don't know how much
> >we can trust it...
> >
> >  
> 
> this is likely some kind of effort on part of google or an independent 
> effort on part of one of its employees to cast google in a better light 
> here after that moron contacted theo through misc.
> 
> it's nice to see that kind of principle in place at google but is mostly 
> irrelevant outside the context of baiting devs to work for google ;). at 
> least google is trying to hire from the non-MS pool so their software is 
> not written like shite.


Good point.

If anybody from the OpenBSD team ever works for Google, it will certainly be a 
very wise move on behalf of Google for hiring them.



Re: google team and the DIY way of life

2007-11-11 Thread Jacob Yocom-Piatt

Nick Guenther wrote:

On Nov 10, 2007 5:00 AM, Sean Darby <[EMAIL PROTECTED]> wrote:
  

On Sat, Nov 10, 2007 at 10:31:11AM +0100, xavier brinon wrote:


from the "Official Google Blog"

"Posted by Reza Behforooz, Software Engineer

In my first month at Google, I complained to a friend on the Gmail
team about a couple of small things that I disliked about Gmail. I
expected him to point me to the bug database. But he told me to fix it
myself, pointing me to a document on how to bring up the Gmail
development environment on my workstation.

I know, it's obvious that it's works if you share your code and let
others submit their diffs.
Just a reminder... See Google ? they shut up and code !
  

Why? (...why bother sending that to this list? fyi: this isn't a google list.)

Just curious, not intending to spark anything negative.



Because Google Shuts Up And Codes.
Of course, this is off the googlepropaganda, so we don't know how much
we can trust it...

  


this is likely some kind of effort on part of google or an independent 
effort on part of one of its employees to cast google in a better light 
here after that moron contacted theo through misc.


it's nice to see that kind of principle in place at google but is mostly 
irrelevant outside the context of baiting devs to work for google ;). at 
least google is trying to hire from the non-MS pool so their software is 
not written like shite.




Re: google team and the DIY way of life

2007-11-11 Thread Nick Guenther
On Nov 10, 2007 5:00 AM, Sean Darby <[EMAIL PROTECTED]> wrote:
>
> On Sat, Nov 10, 2007 at 10:31:11AM +0100, xavier brinon wrote:
> > from the "Official Google Blog"
> >
> > "Posted by Reza Behforooz, Software Engineer
> >
> > In my first month at Google, I complained to a friend on the Gmail
> > team about a couple of small things that I disliked about Gmail. I
> > expected him to point me to the bug database. But he told me to fix it
> > myself, pointing me to a document on how to bring up the Gmail
> > development environment on my workstation.
> >
> > I know, it's obvious that it's works if you share your code and let
> > others submit their diffs.
> > Just a reminder... See Google ? they shut up and code !
>


> Why? (...why bother sending that to this list? fyi: this isn't a google list.)
>
> Just curious, not intending to spark anything negative.

Because Google Shuts Up And Codes.
Of course, this is off the googlepropaganda, so we don't know how much
we can trust it...



Re: google team and the DIY way of life

2007-11-11 Thread Sean Darby
Why? (...why bother sending that to this list? fyi: this isn't a google list.)

Just curious, not intending to spark anything negative.

On Sat, Nov 10, 2007 at 10:31:11AM +0100, xavier brinon wrote:
> from the "Official Google Blog"
> 
> "Posted by Reza Behforooz, Software Engineer
> 
> In my first month at Google, I complained to a friend on the Gmail
> team about a couple of small things that I disliked about Gmail. I
> expected him to point me to the bug database. But he told me to fix it
> myself, pointing me to a document on how to bring up the Gmail
> development environment on my workstation. The next day my code was
> reviewed by Gmail engineers, and then I submitted it. A week later, my
> change was live. I was amazed by the freedom to work across teams, the
> ability to check in code to another project, the trust in engineers to
> work on the right thing, and the excitement and speed of getting
> things done for our users. Engineers across our offices (and across
> projects) have access to the same code; I didn't have to ask for
> anyone's permission to work on this."
> 
> I know, it's obvious that it's works if you share your code and let
> others submit their diffs.
> Just a reminder... See Google ? they shut up and code !



Re: google team and the DIY way of life

2007-11-10 Thread Karthik Kumar
Not again!

On Nov 10, 2007 3:01 PM, xavier brinon <[EMAIL PROTECTED]> wrote:

> from the "Official Google Blog"
>
> "Posted by Reza Behforooz, Software Engineer
>
> In my first month at Google, I complained to a friend on the Gmail
> team about a couple of small things that I disliked about Gmail. I
> expected him to point me to the bug database. But he told me to fix it
> myself, pointing me to a document on how to bring up the Gmail
> development environment on my workstation. The next day my code was
> reviewed by Gmail engineers, and then I submitted it. A week later, my
> change was live. I was amazed by the freedom to work across teams, the
> ability to check in code to another project, the trust in engineers to
> work on the right thing, and the excitement and speed of getting
> things done for our users. Engineers across our offices (and across
> projects) have access to the same code; I didn't have to ask for
> anyone's permission to work on this."
>
> I know, it's obvious that it's works if you share your code and let
> others submit their diffs.
> Just a reminder... See Google ? they shut up and code !
>
>


-- 
Karthik
http://guilt.bafsoft.net



google team and the DIY way of life

2007-11-10 Thread xavier brinon
from the "Official Google Blog"

"Posted by Reza Behforooz, Software Engineer

In my first month at Google, I complained to a friend on the Gmail
team about a couple of small things that I disliked about Gmail. I
expected him to point me to the bug database. But he told me to fix it
myself, pointing me to a document on how to bring up the Gmail
development environment on my workstation. The next day my code was
reviewed by Gmail engineers, and then I submitted it. A week later, my
change was live. I was amazed by the freedom to work across teams, the
ability to check in code to another project, the trust in engineers to
work on the right thing, and the excitement and speed of getting
things done for our users. Engineers across our offices (and across
projects) have access to the same code; I didn't have to ask for
anyone's permission to work on this."

I know, it's obvious that it's works if you share your code and let
others submit their diffs.
Just a reminder... See Google ? they shut up and code !