Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lawrjone
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
31.
▲
by
lawrjone
2y ago
I'm the author of that MacBook blog post. I wouldn't say it was a waste of time, in that it helped us feel very confident about the ROI for upgrading, and the results have been really meaningful for our team. I wouldn't agree
32.
▲
by
lawrjone
2y ago
I wouldn't say this applies to cloud providers, they have a very different business on their hands. But for SaaS in general I think the trend is noticeable? Twitter led the way with massive layoffs in engineering often in the roles aro
33.
▲
by
lawrjone
2y ago
I'm not totally certain you can attribute it to this. I know there's a bunch of work going on to migrate things into Azure after the MS acquisition but it feels like more of an industry trend that we cut engineering spend at the c
34.
▲
by
lawrjone
2y ago
The industry made a general decision after ZIRP ended to deprioritise availability after years of historic levels of engineering investment. It's no surprise we're now feeling those effects but damn, GitHub and other services lik
35.
▲
by
lawrjone
2y ago
This guidance is actually super important, as contexts are expected to be modified in a code flow and apply to all functions that are downstream of your current call stack. If you store contexts on your structs it’s very likely you won’t th
36.
▲
by
lawrjone
2y ago
Yeah most people talking here are unlikely to have worked on large scale Go apps. Managing a god-level context struct with all the fields that ever could be relevant and explaining what they mean in position independent ways for documentati
37.
▲
by
lawrjone
2y ago
Author here! It’s a fun problem to solve and one I’ve come across before when trying to alert on your monitoring tool being down, but slightly different when it’s your product. Hopefully interesting if you’ve hit similar puzzles before.
38.
▲
by
lawrjone
2y ago
I’m one of the engineers on the team with Sam and can vouch for how impactful all the work he’s done has been to creating a great Observability setup. Well worth a read!
39.
▲
by
lawrjone
2y ago
Yeah I found this really off putting: it’s not possible for you to have several goals that are all ‘paramount’, and the word ‘seamless’ adds nothing in every place it appears! I wish it didn’t turn me off the content as much as it does but
40.
▲
by
lawrjone
2y ago
Don't these people already have the option of running open-source tools like Netflix's Dispatch or Monzo's Response? If they have the open-source options why would they pay for the hosted services?
41.
▲
by
lawrjone
2y ago
Thanks for the repost!
42.
▲
by
lawrjone
3y ago
That's for posting this! I'm one of the engineers on the team who built On-call, so if you have any questions about how we did it (like how we handle redundancy, observability, etc) then I'd be well up for answering. It'
43.
▲
by
lawrjone
3y ago
Fwiw as a medium spend (250k to eventually grow into 1M+ year) GCP customer we had the same deal with product roadmaps shared up-front under NDA etc. And never did I miss something in GCP that I could find in AWS. Not sure the breadth is ad
44.
▲
by
lawrjone
3y ago
Not the author but a colleague of Milly's: it's been awesome watching the team build this and everything they've learned along the way. I think these features are a great example of how AI can fit alongside expert human work
45.
▲
by
lawrjone
3y ago
It would work for most of our business reporting, but BigQuery is so good at what it does and cheap that it doesn't make much sense to avoid it. We also have some parts of our dataset that are complicated to compute. An example is that
46.
▲
by
lawrjone
3y ago
I don’t think we did consider this, probably because we have a preference to buy instead of build with tools like these and prefer a team who can respond to our feedback. It looks like a promising tool though! I’m sure we’ll blog about our
47.
▲
by
lawrjone
3y ago
This sounds really awesome, I will note that I put this data stack together by myself in about 1 week when we were just ten people in the company. Obviously very different resource constraints than Meta, so worth considering which situation
48.
▲
by
lawrjone
3y ago
Data like this allows us to be extremely customer focused and help direct investment for the business, such as what features we build on and when. We also use the same data pipeline to power a lot of our data product features which customer
49.
▲
by
lawrjone
3y ago
The product provides login and sign up with Slack which means all product plans include SSO under whatever scheme the Slack workspace is provisioned with. The SAML feature in the Pro and up plans is about hooking us up directly to your iden
50.
▲
by
lawrjone
3y ago
We do very similar things ourselves: our insights product ( https://incident.io/learn ) uses Metabase to power the dashboards. The data that goes into those insights can be quite complex and the queries are actually threading
51.
▲
by
lawrjone
3y ago
This is an article from Jan 2022 when we were a company of 10, and now are a company of ~80. Worth some observations that: - We're still using Fivetran for the EL stages. Costs are much more significant than they were before and we
52.
▲
by
lawrjone
3y ago
I'm not sure it's so steep: Starter is $16/user, Pro is $23/user (with the $10k minimum) and then Enterprise is expecting 100+ (into the many thousands) of users and companies often want to discuss that pricing alongside
53.
▲
by
lawrjone
3y ago
We do frequently adjust the codebase to improve build times, but the developer productivity hit we’d take by splitting our app into several microservices would be much more substantial than much slower build times than we currently see. We’
54.
▲
by
lawrjone
3y ago
I think we’ll definitely see AI find its way to the notebook tools. Funny enough, you can ask the model to give you an iPython notebook of its workings if you want to move your analysis locally, so in a way it’s already there! On the proces
55.
▲
by
lawrjone
3y ago
Hahaha yep, Milly won the lottery on this one. We chose the person who was doing most builds that week to give it to, so it’s well deserved!
56.
▲
by
lawrjone
3y ago
Am OP: the Docker for Mac daemon can claim a lot of system resources and the FS can have a lot of latency. This means devs have less system memory available for their host because it’s in the VM, battery is often harmed because the VM box i
57.
▲
by
lawrjone
3y ago
Hahah good question: 2.5 days all in, including building the new hot-reloader which fixed a number of outstanding bugs. - 1 day for hot-reload (I don’t think this should count tbh) - 1 day for messing with data - 0.5 day for write-up Assumi
58.
▲
by
lawrjone
3y ago
The machines haven’t arrived yet but I wouldn’t expect we’d have the data to prove this out. As you’ll know, number of tickets complete is a weak proxy for value delivered, and can be so wrong as to imply a team that you know is 2x as produ
59.
▲
by
lawrjone
3y ago
Author here: this probably took a 2.5 days to put together, all in. The first day was spent hacking together a new hot reloaded but this also fixed a lot of issues we’d had with the previous loader such as restarting into stale code, which
60.
▲
by
lawrjone
3y ago
Author here! We’re using the new OpenAI assistants with the code interpreter feature, which allows you to ask questions of the model and have OpenAI turn those into python code that they run on their infra and pipe the output back into the
More ›