jjjjoe
jjjjoe on Hacker News
Where is the letter P in the second image?
Sounds like the sort of program that'd give you a 0 on an assignment if it worked perfectly but emitted a compiler warning under Sun Studio
This thinking is taught in MBA programs but does not map onto real businesses. If you're in the ice cube business and you made the profoundly unwise decision to set up vending machines in Inuit communities, you don't recover by laying off x% of both your Alaskan retail and Caribbean Cruise wholesale businesses.
I've been on the receiving end of that kind of "reorganization" and this didn't look like that.
> whatever algorithm is being used to remove people
Different functions/teams/departments seemed to use very different algorithms, suggesting there was just no leadership at all. I posted a separate top level comment, but seeing one function do last-in/first-out and another jettison its most-tenured (most expensive? non-pristine HR record? who knows!) folks makes it hard for employees to understand what the new rules of engagement are.
The reason the word "inept" keeps coming up is just how opaque and senseless to the rank and file the January 2023 layoffs were. High performers, low performers, newest hires, most tenure: we saw all kinds of heads roll. I saw a team lose its sole TL with a decade+ of tenure on the team, then turn around and hire 4-6 people to try and catch up. A growing deployment team was actively hiring before and after it got a 6% haircut.
The simplest explanation would be that every cost center/P&L had to offer up 6% of its people, regardless of that cost center's overall trajectory, place in company strategy or open headcount. And that every cost center's VP or general manager or whatever just got collared by HR, was given a list on a piece of paper and couldn't leave until they chose 6% by ...whatever metric they came up with on the spot.
Whatever actually happened I'll never know, but what I've seen was 100% compatible with that theory. Which in turn looks pretty inept.
Thinking about my own usage patterns, when I'm working from home my laptop is VPNed to somewhere reasonably close lag-wise, but certainly not within 50 miles of my house. Meanwhile my phone is studiously checking my inbox using either the local cell tower or my home WiFi.
So if I go look at my personal access logs, I see myself flitting back and forth across the country constantly. I wonder how they plan to filter out these incredibly common false positives without also clobbering detection of thoroughly-owned (consistently-flitting) accounts.
I'm unclear whether you disagree with the linked video or just Kurzgesagt as an outlet. If it's the latter, I suppose we should also link their response:
https://www.reddit.com/r/kurzgesagt/comments/10jlyyk/kurzges...Either way I don't see why one should care about funding/sponsorship in the context of a "gee whiz" video.
Absolutely! I suspect it would also alleviate a couple of headscratchers like where you spelled out "underscore" when setting a breakpoint.
The novel /referenced/ is Children of Ruin, the sequel, which is just as amazing. I assume the author is referring to the diptych by its first part's name.
Small discrepancy which might confuse exactly the readers who would enjoy the whole work.
Probably the wee Brother 3200-something you can find at any office supply store. We had a rebranded sibling sold by Dell for a decade. CUPS likes them. They're slow, but they work.
Libraries don't let you check out books which can't be replaced economically. You might have heard the word "circulating" in the context of libraries: stuff from Tom Clancy and Harper Lee and Kevin Feige circulate. Out-of-print or rare or college textbooks usually have to be read at the library, where staff discourage you pocketing or photocopying things or whatever.
The new high (secondary) school treated her like a new student, not one with a year of comically poor performance. This isn't about college or university; it's about the last few years of compulsory education, which often set the direction of one's life.
It's unwaxed, unbleached, and thick. How does that help?
$150 for 50Mbps is what I'm paying for Comcast Business, and they haven't been able to render an invoice for months.
I commented similarly elsewhere, but in my experience UPS won't ship more than one or two packages without an account. Red flags will definitely be raised if you try to smurf package shipments.
I helped a friend pack and ship a successful Kickstarter campaign. The first time we showed up at the UPS store with a minivan full of boxes they made us set up an account. They had no interest in an "anonymous" transaction for more than a couple packages.
From the spec:
Servers MUST use TLS version 1.2 or higher and SHOULD use TLS version 1.3 or higher. TLS 1.2 is reluctantly permitted for now to avoid drastically reducing the range of available implementation libraries. Hopefully TLS 1.3 or higher can be specced in the near future. Clients who wish to be "ahead of the curve MAY refuse to connect to servers using TLS version 1.2 or lower.
Things outside GCP e.g. G Suite integrations are also impacted. This is just the first status page to be updated.
EDIT: It's now posted to https://www.google.com/appsstatus
Hey, I work on public-facing support for GCP. Given the point that it's hard to see what mailing lists are available I wanted to point out
https://cloud.google.com/support/docs/groupsIt's definitely not as well-integrated as AWS' forums, but it's a starting point.
Googler here. I've flagged this (especially the part about the dropped billing case) internally.
Note that this was posted to HN around midnight Pacific, so it's quite possible nobody from the Firebase team had seen it yet.
Assuming that the appeal process is broken, or you're locked out of your account or something equally egregious: you post to one of the product-related Google Groups listed at the bottom of cloud.google.com/support. Support staff and engineers read those lists and will escalate issues.
Post to one of the product-related Google Groups like google-appengine@ or
[email protected]. We have support staff monitoring those lists seven days a week.
Hi, I manage the team. Do you have some recent examples I can show to the higher-ups? Our incentives are built around quality of work, not speed, so what you're describing is definitely not working as intended.
Cloud 1:many (community) Support here.
You absolutely do not have to pay us to report a bug, period. The same day this bug was filed, one of my colleagues ([email protected]) jumped on the report and started asking questions to determine what was happening.
It seems to me that the GP's complaint is that this process was too slow: too much back-and-forth, too little dedicated attention to get the problem figured out immediately. That's a frustration which is easy to understand.
The point about support contracts was most likely intended to emphasize that if your livelihood depends on a service, you should have an agreement in place that guarantees you can wake up an engineer on the weekend.