1. Write a new libc and get it used all over Google, generating lots of users automatically; or
2. Shepard Google's adoption of code some other folks wrote.
1. Write a new libc and get it used all over Google, generating lots of users automatically; or
2. Shepard Google's adoption of code some other folks wrote.
However, as the person who actually runs the relevant promo committees for the org, both would be fine, i'd care a lot more about why the choice was made.
Painting 100k people with a brush of "can't be objective" based on no data is probably the most biased think i've actually seen in a long time.
Yes, having experience is still better than outright making things up because you have neither the experience, nor data or any kind of basis for a claim.
I have helped people on my team write promotion packets in both forms. Both worked perfectly well.
If one goes with option 2, he/she may have many more achievements to write on his/her promotion packet during the time he/she would have spent implementing a new libc. So I hardly think promotion is the incentive here.