I’ve never used Pub/Sub or Cloud Run, but have been quite happy with BigQuery and GKE.
1,202 karma · joined May 21, 2015
https://www.thelis.org
I’ve never used Pub/Sub or Cloud Run, but have been quite happy with BigQuery and GKE.
I’ve been an exec, founder, CEO, and board member at various stages of successful (IPO) /unsuccessful companies (acqui-hire) companies. And the common thread at every stage is that the most successful companies had management teams that worked well together to optimize for the business.
So instead of spending your energy on reading / learning more about tech, I’d recommend you spend your energy learning more about business (I’d probably start by asking the CEO & the rest of the mgmt team for advice on what to learn.)
- $0 - $1M-ish, hire a part-time bookkeeper
- $1M - $5M-ish, get a director of finance / controller, who can manage AR/AP, audit, ASC 606, basic financial modeling, and your key rev benchmarks.
- $5M+ is when I'd consider hiring a CFO, but it really depends on your growth rate. You can probably get to $10M+ with a good dir of finance if you get them to hire a good FP&A person.
Re: "fancier machine learning" -- I've seen different flavors of RNNs & LSTMs have some success in analyzing time series data. I've struggled to get them to work on real-world (i.e., messy) data, but have had some encouraging results with a transformer encoder-only NN.
The problem with time series forecasting in general is that they make a lot of assumptions on the shape of your data, and you'll find you're spending a lot of time figuring out mutating your data. For example, they expect that your data comes at a very regular interval. This is fine if it's, say, the data from a weather station. This doesn't work well in clinical settings (imagine a patient admitted into the ER -- there is a burst of data, followed by no data).
That said, there's some interesting stuff out there that I've been experimenting with that seems to be more tolerant of irregular time series and can be quite useful. If you're interested in exchanging ideas, drop me a line (email in my profile).
Similarly I think we’re in for a wild ride on AI and figuring out its implications. There’s a ton of obvious use cases today but I’m really interested in the ones that aren’t obvious right now.
Mostly notes to myself, and I’ve got a half-baked post on LLMs that I’ve been working on (as that’s been my area of recent interest).
Remote: Yes, or in Boston
Willing to relocate: No
Technologies: Kubernetes, Envoy, LLMs, service mesh, Hugging Face, Python, SQL, BigQuery, DBT, LangChain, Docker
Résumé/CV: https://www.linkedin.com/in/richardli/
Email: rdl@amorphousdata.com
I posted last month and had a few worthwhile conversations, so posting this again!
I'm an entrepreneur & product person. I've been an exec at two successful exits (Duo, Rapid7) and started my own company (Ambassador Labs) whose story is still being written. I'm super-interested in LLMs and what issues people are running into. So I'm interested in anyone who could use a product person for a part-time consulting gig. The more interesting the consulting, the less you need to pay me! :)
Some examples of work I could do would be helping you tell your story, building a sales deck, or maybe figuring out what you could do with all the new AI stuff. Or something else. Thanks for reading.
https://www.theguardian.com/us-news/2020/feb/18/are-plastic-...
My general view is that glass is super-durable, microwave-safe (I would never microwave Tupperware), and the cost tradeoff is minor, so it seems worthwhile. That said, if I order takeout and it comes in a plastic container that's hot ... I still eat it :).
* We use silk dental floss (we use Radius)
* We use glass storage containers instead of Tupperware
* For cooking, we use All-Clad.
* If a recipe calls for non-stick (e.g., pancakes) I use a braiser from Le Creuset, which works reasonably well.
(Edited: formatting)
So this is a bit of an odd post, but I thought I'd try this out!
I'm an entrepreneur & product person. I've been an exec at two successful exits (Duo, Rapid7) and started my own company (Ambassador Labs) whose story is still being written. I'm super-interested in LLMs and what issues people are running into. So I'm interested in anyone who could use a product person for a part-time consulting gig. The more interesting the consulting, the less you need to pay me! :)
Some examples of work I could do would be helping you tell your story, building a sales deck, or maybe figuring out what you could do with all the new AI stuff. Or something else. Thanks for reading.
Now that I'm spending time learning AI, it feels the same -- but the innovation pace feels at least 10x faster than the evolution of the cloud native ecosystem.
At this point, there's a reasonable degree of convergence around the core abstractions you should start with in the cloud-native world, and an article written today on this would probably be fine a year from now. I doubt this is the case in AI.
(Caveat: I've only been learning about the space for about 4 weeks, so maybe it's just me!)
If you expense your cell phone bill every month, then it's reasonable for other employees to expect the same, if they're also using it for work.
Better to get the board to sign off on a slightly higher salary to offset these expenses, IMO.
There's a bunch of semi-opinionated tools like Skaffold: Garden, Tilt (just bought by Docker), Docker Compose, and of course, the trusty ol' shell script powered by kustomize.
We wrote Telepresence because we found that everyone has their own snowflake-ish workflow once you get beyond the base case of "build container, kubectl apply", so we decided to focus just on the inner dev loop, and then integrate with your preferred workflow. YMMV.
This of course may be true for some communities, but certainly not the case for L7 proxies. In fact, at the time, the opposite was true: NGINX & HAProxy were content in slowly supporting their (captive) customer bases, with little incentive to innovate. This is why Lyft went off to build Envoy Proxy. At GA, it supported features such as HTTP/2, native observability, hitless reloads — none of which were easy / possible to do in NGINX or HAProxy at the time.
> Connection/service proxies are a dime a dozen. I suspect you could have picked nginx, haproxy, or the Linkerd proxy and been just as well off.
Linkerd proxy didn’t exist then (there was an early version of it, written in Scala IIRC; the Rust version didn’t come along to quite some time later).
I agree that there are many options for service proxies. I’ve found, though, that the Envoy community has been pushing innovation in the space quite aggressively.
Here's the initial video where Matt Klein introduces Envoy: https://www.microservices.com/talks/lyfts-envoy-monolith-ser....
If you want to buy commercial support for Envoy & Istio, Tetrate certainly is an option.
(Note: I am/was the CEO at Ambassador Labs, which organized the Microservices Practitioner Summit where this talk occurred.)
One of the reasons why we adopted Envoy at Ambassador for our API Gateway was precisely because there was no single _commercial_ entity who controlled Envoy.
As a note, technically Google & Lyft are VC-funded, so that’s true, although I wouldn’t put Google in the startup category, and Lyft’s business model is unrelated to Envoy.
(Because in improv, if you object to something, you can just stop the show.)
It works really well in a professional setting, too. Try it!
The cynic in me says: this is great marketing, because the best Sequoia fund is the early stage fund (always oversubscribed) and now as an LP you can't invest in just the early stage fund. (But the reality is I bet they forced early stage fund LPs to invest in their growth vehicles anyway, so there is no material change other than marketing. Which is very good.)
The article says "Equity will be your largest driver of compensation at a startup." as the rationalization of why it focuses on that.
Based on my past experiences, I would say that the learning, network, and reputational effects resulted in far more wealth to me over the medium-term than any incremental change in equity or salary.