Totally valid, I should have written it as, "current employment, current/previous equity."
1,288 karma · joined August 16, 2015
- https://www.ariss.org/uploads/1/9/6/8/19681527/k9jkm_2012_sy... has a good overview of how to hit the ISS (and other sats)
- https://www.va3hdl.com/projects/gpredict-and-hamlib is the software stack you probably want to play with
Remote: Yes
Willing to relocate: Yes (SF, Seattle, Austin)
Technologies: Product leader, platform builder, API enthusiast
Résumé/CV: linkedin.com/in/asciimike
Email: hn at mikemcdonald dot co
Experienced product manager looking for a director role in AI infrastructure, platforms, or tooling. I build platforms that developers love, historically at Firebase, Google, GitHub, and most recently, Crusoe, where I built a GPU IaaS platform that powers many quickly growing AI startups and an increasing number of enterprises.
If you're pushing the boundaries of AI/ML and need compute to help get there, shoot us an email at sponsorship at crusoecloud dot com and we'd love to chat!
Your read on the situation is spot on, and no, it doesn't look like it's been "fixed" (mostly because "fixing it would re-introduce the same potential vulnerability).
- The [Firebase technical screen](https://startupandrew.com/posts/how-firebase-interviewed-sof...) would have been much easier with something like this, as it was Just Another Optimization Problem™. Part of me wants to try it again with Picat!
- He's doing other very interesting things with programming languages, e.g.: https://github.com/obi1kenobi/trustfall
Yes and no ;)
The original release of the Realtime Database didn't have security rules (though they were thought of at the time), and they were added in late 2013/early 2014 (IIRC). At that point, in the name of "easier getting started experience (don't force users to learn a custom DSL)", the default rules were `read: true, write: true`. As you might expect, it resulted in a high potential for this type of thing, and sophisticated customers cared _a lot_ about this.
This changed at some point post acquisition (probably 2016?) when the tradeoff between developer experience and customer security switched over to `false/false` (or picking something slightly more secure than `true/true`.
Firebase Security Rules were upgraded and added to Firebase (Cloud) Storage and Firestore, with both integrations being first class integrations, as _the whole point_ of those products was secure client-side access directly to the database from day 1.
The tricky part of all of any system in this space was designing a system that's simple enough to learn, highly performant, and also sufficiently flexible so as to answer the question "allow authentication based on $PHASE_OF_THE_MOON == WAXING_GIBBOUS" or some other sufficiently arbitrary enterprise parameter. Most BaaS products at the time optimized for the former, then the latter, and mostly not the flexibility; however, over time, it turns out that sufficiently large customers really only care about the last one! Looks like Firebase solved this recently with auth "blocking functions" (https://firebase.google.com/docs/auth/extend-with-blocking-f...) which is sort of similar to Lambda Authorizers (https://docs.aws.amazon.com/apigateway/latest/developerguide...), which I believe is a pretty good way of solving this problem.
Disclosure: Firebase PM from long ago
- https://sambanova.ai/ (Enterprise AI and dataflow-as-a-service for established models)
- https://www.cerebras.net/ (AI accelerator, trying to compete with Nvidia)
- https://www.graphcore.ai/ (Another AI accelerator company, UK based)
- https://femtosense.ai/ (Sparse NNs on very low power chips, cool hardware and software challenges)
- https://sima.ai/ (ML accelerators for embedded applications)
- https://ambiq.com/ (Not AI, but low power chips for wireless using some fancy tech that reduces energy leakage)
- https://www.esperanto.ai/ (RISC-V based Tensor computes chip, founded by Intel Hybrid Parallel Computing Vice President Dave Ditzel)
- https://www.furiosa.ai/ (AI accelerator company which show good results in MLPerf benchmark)
- https://groq.com/ (From the team that built the original TPU at Google)
- https://lightmatter.co/ (Light tubes instead of copper)
- "need" to operate in China
- The Chinese government requires majority state ownership of enterprises
I don't think the conditions are the same in Europe, especially given the historical precedents of Safe Harbor/Privacy Shield/etc.
> Or just app engine honestly.
As a former App Engine PM and PM of Cloud Run, this warms my heart to hear--I'm glad folks love to use it :)
It's been a few years since I've worked on these products, but they were designed to be composed and used by each other. Cloud Run provides an autoscaling container runtime with Knative compatible API; Cloud Build (and Container Registry) + Cloud Run = App Engine, App Engine + CloudEvents = Cloud Functions.
With a Knative compatible API, you can theoretically take those primitives and move them to your own K8s cluster, managed (GKE/EKS/AKS) or self-managed, giving folks a tremendous amount of flexibility down the line if/when they need it (hint: the majority of customers didn't, and the fully managed services were great).
Totally. A year or so ago they installed a protected bike lane on 23rd st crossing 25 onto water st (to connect to the south platte river trail/REI), but then it snowed and people ran over all the rubber protectors because they couldn't see them. They've since added higher reflectors, so at least they learned from their mistakes! I have a bunch of the same style on 17th by Sloan's lake, so I feel decently protected from that area to the stadium and onto the south platte river trail.
Is there a source for this? I live in Denver and am currently staring at a dozen Lyft scooters and a few bikes parked on the corner next to my apartment. Lime also operates scooters and bikes, which I usually see parked across the street at the apartments next door.
There are a few places that are geofenced (e.g. along 16th St Mall), but judging by how many people I see riding them on e.g. Cherry Creek trail as I'm biking, I don't think they're generally banned.
The main issue right now is that all the flight schools are booked up and you can't get a DPE booked less than two months out.