This is AI generated.
435 karma · joined February 23, 2012
The "narrative" was right. There are actual outages now unlike earlier. It's not like twitter engineers were holding up the servers to the light for there to be outages the moment they're gone. Systems run on their own just fine, until something does go wrong. And if there's nobody there to fix it, something usually small blows up. Enough of these and users start to notice degraded performance and outages.
So, it's sometimes nice to have periodic validation that you're keeping true to the course / indication that you need to make a few minor adjustments, etc. That's on your side.
From your manager's side, if they find something isn't working, they don't need to wait 3/6 months to bring it up at which point there isn't much you can do to get back the lost productivity.
Everyone who is a manager actively makes independent contributions for a not-insignificant portion of their work-week.
So, when we have 1-on-1s with them, we can actually discuss improvement avenues from the same vantage point. Not some spreadsheet pushing manager who has no clue how to measure engineer-productivity or performance.
When they do code reviews, their comments serve as an important learning opportunity, pointing out good practices/conventions, etc.
And finally, when you disagree, it's backed by the validity of your points as 2 engineers, rather than their authority as a manager vs you, their direct report.
I can't remember the number of times they've shut down someone's production workload without notice or warning, gave them no way to resolve/rectify any supposed infraction, and gave no way to contact them to appeal the decision.
I once had to resort to numbering my points and just referring the boilerplate responses (few and far inbetween as they were) back to the numbers over and over until I finally gave up, moved away and never looked back.
/s
I know, they need to register in some jurisdictions but should be much more widespread.
You can operate like "Oh it's just someone's home, we're all just being civil to each other" in which case, have a conversation; permanent irrevocable ban is not it, or "Here's our 100 page T&Cs. We have all the control and can dump you whenever we see fit for whatever reason and we don't have to tell you" in which case, go through the legal process of getting each and every property properly registered and licensed and operate like a real business. Can't have it both ways.
Now I'm sure it's easy to see the above comment somewhat conflates the Airbnb hosts with the Airbnb corporation. And that's intentional.
"Don't throw out the rulebook in a fit of passion. You'll regret it. We did" - Dan Fried
Might I add, if you weren't a party to an experience, an off handed observation that those are just subjective experiences, is frankly not yours to make.
Such (pro)active denial usually indicates the denier has something to hide. Now that may not be the case here. But assuming you're right about this not being a Google problem but just small pockets like sexual harassment and racism.
Doesn't google still hold talks about racism & sexual harassment? I'm pretty sure they do. So why the voice against this talk, and this issue specifically?
The lesson to be learned is, if you are offended by someone saying they experienced oppression/discrimination, really, look inward.
If person A slaps person B and person C goes "I didn't experience anything. There are no slaps in this company", does that sound reasonable?
While Apple may have had to spend money setting up the specific assembly line, fabrication plants, train staff, etc because they simply didn't exist prior to their requirement, the fact that they were able to set it up someplace, and continuously feed raw materials, parts, labour etc with dozens of redundant suppliers for EACH component, is what indicates manufacturing capability.
Manufacturing is more ecosystem than "capability".
Github indeed has somewhat superior code-review tools. But I've found Gitlab to be perfectly adequate.
When it comes to CI/CD, Gitlab CI blows Github Actions out of the water by a HUGE margin.
So, if I just wanted a tool that got things done for me, instead of fragmenting myself with Github + Github Actions + TravisCI / CircleCI, etc, I'd just get one Gitlab subscription and call it a day.
But regarding the categories, Gmail doesn't automatically expose these to IMAP. But there is something you can do even if a bit hacky.
Create 5 labels named after the 5 Categories. Then create 5 filters each of which look something like this.
Search criteria: "category:primary" -> Apply label "primary".
Repeat the above step for all the categories. Et Voila. Your categories will appear in IMAP as folders of the same name.