gresrun

"Rich asshole makes demeaning comments about situations they don't know" More at 11.

Seriously though, how out-of-touch do you have to be to think that entire organizations full of smart people are so incompetent as to have 100% bloat?

  Could you lay off 50% of Google today and still have a functional, competitive product tomorrow? Yes.

  Would you still have a functional, competitive product in 2 years? No.

Engineers are building and maintaining the product, SREs are keeping the jobs, servers and infrastructure humming, sales is bringing in new clients and keep existing clients happy, marketing is... OK maybe Google does need a marketing overhaul...

Deep cuts will also signal to employees and competitors that blood is in the water. Any remaining loyalty would evaporate and MSFT, AAPL, AMZN, & META would all be eager to scoop up that talent to build competing products to Google Search & Ads and bolster their cloud & AI offerings.

Disclosure: Google employee

How do you handle versioning? Are there any guidelines/rules one must abide by?

It looks like you using Flutter's Dart<=>JSON serialization; do you recommend using built_value for immutable data structures?

Do you support protobuf/cap'n'proto?

L3 is entry-level for fresh college grads.

That's a dangerous, biased assumption.

While I'm 100% positive the details of operational concerns like this are classified, there are 2 distinct types of submarines today with 2 different objectives:

1) Attack Submarines (e.g. Los Angeles-class & Virginia-class for USN) which usually roam within a designated operations area, surveilling, tracking, and generally keeping tabs on other nations' surface & sub-surface fleet dispositions. These subs typically have multi-week sorties and may intermittently surface for surveillance & comms.

2) Ballistic Missile Submarines aka "Boomers" (e.g. Ohio-class for USN) which are given a strategic area in which to operate and their objective is to remain silent & undetected, waiting for the hopefully-never-coming order to launch their SLBMs. These subs usually have multi-month sorties and often don't surface until the end of their patrol.

Context: Staff Eng @ Google for 7+ years

1) This is solved by 2 interlocking concepts: comprehensive tests & pre-submit checks of those tests. Upgrading a version shouldn’t break anything because any breaking changes should be dealt with in the same change as the version bump.

2) Google’s monorepo allows for visibility restrictions and publicly-visible build targets are not common & reserved for truly public interfaces & packages.

3) “Code churn” is a very uncharitable description of day-to-day maintenance of an active codebase.

Google has invested heavily in infrastructural systems to facilitate the maintenance and execution of tests & code at scale. Monorepos are an organizational design choice which may not work for other teams. It does work at Google.

In sidemount diving, each diver carries two completely independent tanks & regulators, one on each side of their body.

While it is used primarily in cave diving because it is more streamlined and less likely to collide with cave ceilings and features, I find it also quite comfortable for recreational dives with a pair of AL40s.

It’s also a fun conversation starter with other divers who are curious about my gear!

Would love to see your set up!

If you’re only getting 500qps out of Netty something is deeply wrong with your set up. I’ve written multiple HTTP & socket servers based on Netty (albeit 6+ years ago) and they all could handle 20kqps+.

I tried to file a report with video evidence from the car 2 years ago. I was never able to get through to anyone at the police who would take the report, just passed to a voicemail and no one ever called back or acknowledged the report.

FYI, any email-ish looking value works. E.g.: [email protected]