lawrjone

12 ms·

121.
Weird stuff and how to test it(blog.lawrencejones.dev)
17 points by lawrjone 4y ago|7 comments
122.
by lawrjone 4y ago
It's a Twitter thread and hopefully you'll forgive that, but contains some useful tricks we've used just this week to get our CI times down. Before this we saw branch builds take ~8m and deploying to production up-to 14m. Now
123.
Tricks we used to get our CI builds below 5M(twitter.com)
3 points by lawrjone 4y ago|1 comments
124.
by lawrjone 4y ago
Author here! Sharing a technical write-up of our recent incident where our service repeatedly crashed due to a poison pill event in the async workers. Interesting from a general incident coordination angle, but also in terms of mitigations
125.
Incident review: Intermittent downtime from repeated crashes(incident.io)
2 points by lawrjone 4y ago|1 comments
126.
by lawrjone 4y ago
Written by my colleague Danny, this post refutes the detailed incident plan we often find in large organisations. Those plans rarely work: they can often impede response, as responders struggle to follow a complex flow-chart that may have c
127.
Ditch your overly detailed incident response plan(incident.io)
2 points by lawrjone 4y ago|1 comments
128.
by lawrjone 4y ago
I’ve posted the first half of this series before, which introduced workflow concepts and the front end builder. This is the second part, which focuses on the infrastructure that drives the workflow executor. Whenever you’re building an exec
129.
Building a Workflow Executor on Postgres(incident.io)
2 points by lawrjone 4y ago|1 comments
130.
by lawrjone 4y ago
Awkwardly, I think this is probably because their blog has gone through several rewrites and it probably hasn't preserved the original text very well. I'm no longer at the company so can't fix it, apologies!
131.
by lawrjone 4y ago
Of course GoCardless have to invest engineering effort into scaling the technology they use. The company doubles in size every year, with totally different products and use patterns. If you're under the impression that purchasing an Or
132.
by lawrjone 4y ago
Author of the article here, and thought it's worth noting on: > No non-productive environment can help you: They don't have the same data or they do have the same data but the statistic sampling was slightly different. GoCardle
133.
by lawrjone 4y ago
Well this is funny: I'm the author of this post, and pleasantly surprised to see it coming around for a second time! If you like this content, there's a bunch more on my blog that you'll probably like too: https://
134.
by lawrjone 4y ago
Author here! This is a write-up about how we built a core part of our product, which is the workflow engine. Workflows are more complex than most of our features, powered by something akin to a small programming language designed to help mo
135.
How we built our workflow engine(incident.io)
4 points by lawrjone 4y ago|1 comments
136.
by lawrjone 4y ago
Written by my colleague Lisa, this is a punchy write-up of three lessons learned during the first year of incident.io's life. Lacking a hackernews account she's asked me to post, but I'll relay any comments her way :)
137.
What I learned as employee #2 at a scaling startup – year 1 at incident.io(incident.io)
2 points by lawrjone 4y ago|1 comments
138.
by lawrjone 4y ago
Hey all! Today we're ( https://incident.io ) releasing our on-call pay calculator for free, removing the need for an incident.io account entirely. That means if you use PagerDuty for on-call, you can use us to calculate exact
139.
We're making our on-call pay calculator free(incident.io)
2 points by lawrjone 4y ago|1 comments
140.
by lawrjone 4y ago
I mentioned this above, but unlike an investor you don't have to pick a start-up that exits successfully for you to gain really valuable experience that can help you on your own. Pick a company with a team you respect, a product you co
141.
by lawrjone 4y ago
As an incident management tool, getting certified was a thing we knew we needed early. Gotta hand it to Chris (one of our founders) who came from being Director of Platform at Monzo (a UK neobank) and had spent years battling auditors, and
142.
by lawrjone 4y ago
This is... Almost exactly how I feel, to the detail. Glad I'm not alone in that!
143.
by lawrjone 4y ago
Yep, perhaps I should have said if you can't create an exceptional environment – of which team, culture and mission are all parts – then you can't expect exceptional outcomes. Hiring people who have experience in those environment
144.
by lawrjone 4y ago
I think the thing about starting your own start-up without experience seeing what works elsewhere is you're highly unlikely to avoid making some big mistakes. If you've spent time in a growing company and at least seen how things
145.
by lawrjone 4y ago
I'm not sure most successful tech start-up founders have management consultant backgrounds, I've not seen that at least! Speaking to the point about not having been a founder myself: you're right, and hope I was clear about t
146.
by lawrjone 4y ago
I'm not sure I agree with the comparison of picking a start-up to join being the same as one you might invest in. At least, in terms of this article, a start-up that has growth ambitions and has just raised a round is a great bet. Unli
147.
by lawrjone 4y ago
Totally accept this as a critique of the article! I think the content is still useful, though. Especially as it gives some examples of the type of challenge that appear routinely when scaling a company, and why experience seeing this before
148.
by lawrjone 4y ago
Chris (one of our founders) just pointed out that we (incident.io) are signed up to the future founder promise: https://github.com/StellateHQ/future-founder-promise So we are doing exactly this, which is cool! I think
149.
by lawrjone 4y ago
I think I failed to communicate this nuance in the article, but my major point was how to most quickly develop the experience you'd need to start your own company. I'd imagine McKinsey is a great place to see loads of companies an
150.
by lawrjone 4y ago
I think these programmes are awesome! We have a few people who are explicitly at incident.io to gain experience of how to build companies. It may be that they won't go to do this, but their time here will put them in a great position t

More ›