41–50 of 169 posts
Earlier quoted context omitted.
Wow, plumbum, despite it's unfortunate name, looks awesome. I will definitely try it next time I write a script.
how is the name unfortunate? from the site: > Plumbum (Latin for lead, which was used to create pipes back in the day)
Maybe I’m just being paranoid.
Ugh, typing `await` for every command is terrible. JavaScript's async-by-default model is clearly not a good fit for this use case.
Although this would be fighting the language...
In my first job I gave a try at using Python for scripts. It was a terrible idea, as I now had 3 problems instead of 1: 1 - Writing scripts, plus: 2 - Installing Python in every host that needed to run those scripts 3 - Maintaining Python and the necessary dependencies up to date in each host / container. (2) and (3) are trivial when done just once in your own computer, but end up being a huge time sink for larger he…
That's why Perl is my go-to choice for glue scripts. It's almost always installed by default, it has stayed consistent for decades without any breaking changes, its regex support is by far the best around, and its almost as good as the shell at gluing commands together.
Earlier quoted context omitted.
This isn't correct: if a Googler writes some code from scratch, which is unrelated to their work, on their personal time, and using their personal laptop... then it's definitely not owned by Google. There could be gray areas where code ownership could be disputed, but in general your employer owns only the intellectual property it paid for. Source: I'm a Googler (until next month).
Are you sure? Not in the “haha, yes of course”, in the “I’ve spoken to HR and have it writing” kind of way. I’ve heard this is not true from others, it is simply true in certain geographical regions where local laws override the contract you signed.
I'm having a hard time believing that Google uses this much internally. Is github.com/google just a place where Googlers can put personal projects to get additional exposure?
The copyright of the thing Googlers build on their oswn time are usually owned by Google and so it ends up on the Google org if they want it on GitHub. They usually have a disclaimer like "this is not a official Google product..."
There are some exceptions depending on local laws and contracts though, so it’s only mostly and not always true.
Earlier quoted context omitted.
how is the name unfortunate? from the site: > Plumbum (Latin for lead, which was used to create pipes back in the day)
Yes, but the name choice was quite intentional and probably giggle inducing. This is about as toilet humor as it can get.
Earlier quoted context omitted.
Are you sure? Not in the “haha, yes of course”, in the “I’ve spoken to HR and have it writing” kind of way. I’ve heard this is not true from others, it is simply true in certain geographical regions where local laws override the contract you signed.
"The provisions of this Agreement requiring disclosure and assignment of Inventions to Google do not apply to any invention that I have developed entirely on my own time without using any of Google Property (as defined below) or Google Confidential Information, except for those inventions that either (i) relate at the time of conception or reduction to practice of the invention to Google’s business, or actual or demo…
That's the catch. Not related to what _you_ do at Google, but related to _anything_ that Google does. Pretty much all the stuff I wanted to work on in my spare time while employed at Google could be seen as related to Google's business/research, as Google does a lot of things. And that's how Google seems to read this too, considering how the Open Sourcing documentation [1] is written.
[1] - https://web.archive.org/web/20210710210932/https://opensourc... “As part of your employment agreement, Google most likely owns intellectual property (IP) you create while at the company. Because Google’s business interests are so wide and varied, this likely applies to any personal project you have. That includes new development on personal projects you created prior to employment at Google.”
Earlier quoted context omitted.
The copyright of the thing Googlers build on their oswn time are usually owned by Google and so it ends up on the Google org if they want it on GitHub. They usually have a disclaimer like "this is not a official Google product..."
This isn't correct: if a Googler writes some code from scratch, which is unrelated to their work, on their personal time, and using their personal laptop... then it's definitely not owned by Google. There could be gray areas where code ownership could be disputed, but in general your employer owns only the intellectual property it paid for. Source: I'm a Googler (until next month).
Source: I'm a Googler that went through the process before.
Edit #1 for all Googlers reading this: search "IARC" internally and you should land on the proper page to kickstart the process.
I personally find Ruby's built-in shell features more ergonomic: `cat package.json | grep name` branch = `git branch --show-current` `dep deploy --branch=#{branch}` if $?.success? [ "sleep 1; echo 1", "sleep 2; echo 2", "sleep 3; echo 3", ].map { |cmd| Thread.new { %x(cmd) } }.each(&:join) name = 'foo bar' `mkdir /tmp/#{name}` if $?.success?