Restoration is hard when health and safety are in question. Good luck to these ops folks <3
[1] https://www.datacenterknowledge.com/archives/2008/06/01/expl...
1,959 karma · joined December 5, 2012
Strict over Duck typing. Funct over Imp coding.
Async over Blocking. KV over ACID.
Keeps BigData humming.
Restoration is hard when health and safety are in question. Good luck to these ops folks <3
[1] https://www.datacenterknowledge.com/archives/2008/06/01/expl...
For example, I trialed major security vendor's enterprise product. They required their app be granted Admin on the GitHub org. All they needed to do was create issues, PRs, and read source code for analysis. There are scopes for that.
I was eventually on a call with a principle engineer in this company, who kept saying they needed this permissions, and I kept showing him the API docs that showed that wasn't so. Eventually he said, "well, we won't _use_ all those permissions, so just give them to us anyway, because it's easier this way." Sure, I'll give you the ability to change all my code, add/remove users, drop repos... etc, and trust that some day, when you're hacked, someone will not use those over granted permissions maliciously?
Security is hard. Be careful what permissions you give your 3rd party GitHub integrations.
That's my hangup. The fact that admin/root level accounts can be accessed with "credentials" alone, rather than only via SSO/MFA/Yubikey. Were these service accounts, what happened to least privilege?
GCP has sided with an "easy out of the box experience". For example, a new project has a "default" network with some permissive firewall rules. A savvy operator wouldn't build things this way, but for a first time user, the cloud is daunting and a JustWorks™ experience gets them moving quickly (e.g. so they can SSH into their VMs easily).
Now, once you've gotten your feet under you, and want to build a solid cloud setup, you'll add Organization Policies [1] like "Skip default network creation", and all new Projects will be completely closed off from the web by default, at the cost of all networking being more complex. Once you're ready for this, turn it on.
So, how should a SaaS database work? Should you have to learn all the intricacies of sharding, partitioning, indexing, SELECT, FROM, HAVING, FULL/INNER/OUTER JOIN, WHERE, GROUP BY, LIMIT, before you write your first query? This is a long standing yin/yang question of product UX. What user persona and UX do you design for on the experience and complexity spectrum.
[1] https://cloud.google.com/resource-manager/docs/organization-...
Better still, after you grow a bit, use a GCP reseller (SADA and DoIT are great) or a usage commitment with your account manager for a nice discount. I've never heard of one of those accounts getting turned off in the middle of the night.
Sure, it sucks to hear of account lockouts like this, but productionizing your finances is part of the startup lifecycle.
[0] https://cloud.google.com/bigquery/docs/querying-partitioned-...
We need your help to put our $40MM series C raise to work and keep scaling up. We’re bringing AI and cloud scale to software testing at mabl.
We’re a 100% serverless operation built on Google Cloud Platform that rapidly develops and deploys features on a CI/CD model. Five years in, we’re a recognized industry player and growing our engineering ranks to keep building out our platform.
Our open positions:
- Software Engineer (various levels and areas)
- DevOps Engineer / Sys Admin
- Support Engineer
- Inside Sales Engineer
Our stack is built with modern Java 11, TypeScript, and some Bash glue
Drop me (an engineer), any questions joe at-symbol mabl.com, and checkout our careers site [1]. We can’t wait to work with you.
Want GKE to run multi-zone, or Spanner to run multi-region, just check a box (and insert coin).
You're employer had a cakewalk seeing what you were posting if you did it from the office. :/
I'm often a power user. I know all the features and shortcuts of the tools I use. All too often, these get removed. I recall being on a feedback call with a UX study, and complaining about a feature I use, and many friend use, that was recently deleted from the product. "Oh, no one uses that" was the response from the UX/PM.
So, I think there is a lot more in common than you think between HN and SO.
When I visit some public high schools in suburban CT, they look nicer than my college campus.
When I visit public schools in rural VA, they're a cluster of trailers and dilapidated structures that don't even have air conditioning, let less modern amenities.
So, maybe it's the taxes, or the highly active parents, or donations, but there's a visible difference, more than "$200" per student. Of course, how far and effective each dollar is WRT to outcomes is a different matter.
President of my undergrad college made $884K last year [1], but a medical school professor made nearly $2M.
1. https://nonprofitlight.com/ny/rochester/university-of-roches...
Most people fill their car weekly or less. Heck, since the pando, I do it less than once a month.
For state colleges, they're often some of the highest paid employees in the state. [1]
1. https://www.espn.com/espn/feature/story/_/id/28261213/dabo-s...
You can already to this
1. Visit Settings > Actions > General Actions Permissions > Policies
2. Select "Allow non-org actions and reusable workflows"
You can then allow GitHub authored actions, verified publish actions, and OR provide an explicit allow list of actions.
[1] https://cloud.google.com/storage/docs/storage-classes#coldli...
I really wonder what these Altassian restore tools look like it if takes "hundreds of engineers across the company" to restore 400 accounts. Are backups siloed across many teams?
This is why I always advocate for all variables/dimensions to have the units in the name (e.g. `billable_seconds`).
Once you get bought out, you'll likely need to integrate or replatform to the buyer's tech. Just look @ Google acquisitions. They spend the next few years paying down tech debt and scaling, so don't waste your time on that pre liquidity event. Spend that period of time on product improvements and market expansion.