I appreciate this. It’s a good overview of what it means to be a productive part of a larger context.

I prefer the terms “throughput” for “worker productivity” and “latency” for “work-unit productivity” but I can see why they chose to use their terms.

My poodle knows how to tap the homepad with his nose to play music. He gets up to it, taps it, and then curls down beneath it to listen. It’s very cute and definitely intentional on his part.

But he lives in NYC (Staten Island). It’s his own local government.

It is doable for many young professionals who work office jobs out of college, do not have dependents, and live with a roommate for a few years while getting established in their careers, finding a spouse, and then moving out to the suburbs.

This is just about possible in NYC if you 1) work in a high-rise by a station 2) commute during peak times with frequent trains 3) live in a high-rise by a station.

For example: Downtown Brooklyn or Exchange Place high-rise <=> WTC.

The other option would be to live within walking distance. A <20 minute walking distance to a downtown or midtown office is reasonable.

Through talks at C++ conferences and appearances on C++ podcasts:

https://youtu.be/lgivCGdmFrw?feature=shared

https://podcasts.apple.com/us/podcast/cppcast/id968703120?i=1000663536368

Swift was developed by a lot of former C++ committee members, and in C++ circles they’ve been advocating for it as a “successor language” for quite some time.

This could definitely be confusing if you don’t have that context, but making Swift useful for this kind of project has been an explicit goal of the Swift developers for years.

There’s also a whole industry of ex-Googlers reimplementing Google tooling as SaaS services to sell to other ex-Googlers at other companies.

There’s even a lookup table: https://github.com/jhuangtw/xg2xg

(some of those are open source projects, some are SaaS services)

The way the article makes it sound is, if individual employees download OracleJDK while on the company network, and use it for small personal scripts or automation, then that might be enough to trigger Oracle to act.

If your company is large enough, then enough employees may have done that to make you a reasonable target for litigation if you don’t work something out with Oracle. And Oracle is an expert at litigation.

I think that the best defense for a large company would be to IP block all Oracle domains and periodically scan employee laptops for any Oracle products (especially JDK and VirtualBox guest additions) and delete them.

You really have to treat anything that Oracle touches as malware if you want to protect yourself.