lawrjone

18 ms·

151.
by lawrjone 4y ago
Thanks!
152.
by lawrjone 4y ago
I am absolutely not saying you can't do this. In fact, GoCardless is an example of a company started by very young founders with little start-up experience, and is now a unicorn. The difference is that if you have this experience when
153.
by lawrjone 4y ago
Specifically, high growth is useful because you can spend a few years there and get experience of doing many things at several different company sizes. It means you get several opportunities to learn how to do a specific thing, and see how
154.
by lawrjone 4y ago
Yeah, this recommendation only works if you can make the most of opportunities at whichever company you've joined. I got lucky, in that GoCardless gave me a load of opportunity and I grew a lot with the company, which opened more doors
155.
by lawrjone 4y ago
I'm first employee at a start-up now, and while not a founder, the experience I have from seeing this stuff in previous companies totally changes the game. When we decide to do something, such as make key hires, build new teams or inve
156.
by lawrjone 4y ago
Author here! I've been speaking with friends about starting their own companies recently, and one thing it's made me consider is what experience would best prepare you to become a founder. Having spent my career in start-ups, the
157.
Want to found a startup? Work at one first(blog.lawrencejones.dev)
318 points by lawrjone 4y ago|150 comments
158.
Adding latency: one step, two step, oops(blog.lawrencejones.dev)
2 points by lawrjone 4y ago|1 comments
159.
by lawrjone 4y ago
Written up a case study of testing in production from a complicated migration between two infrastructure providers. In this case, finding a way to experiment in production was a great way of derisking the work we needed to do. Even so, we d
160.
by lawrjone 4y ago
Hey folks, Sharing an article written by a colleague about how to handle third-party outages, think AWS/GCP going down. As engineers, you get used to people hammering on your door when there's an AWS outage asking "why don&#x
161.
Handling third-party provider outages(incident.io)
2 points by lawrjone 4y ago|1 comments
162.
by lawrjone 4y ago
Someone said similar in another thread: https://www.reddit.com/r/devops/comments/ve9jge/how_do_you_c... My answer is yes, the on-call compensation is more about keeping healthy dynamics of on-call than i
163.
by lawrjone 4y ago
My experience is mostly in a company of about ~700, working in a regulated environment (payments). This guide is how we ran incidents, or at least at the top end of the complexity of each section. So if by small you mean companies under 150
164.
by lawrjone 4y ago
You've got to laugh or cry: the new traffic caused us to hit some Netlify edge function issues and we went down for a bit :( Happy to say - having opened an incident - that we're now back up, and don't expect to hit any more
165.
A practical guide to incident management(incident.io)
132 points by lawrjone 4y ago|36 comments
166.
by lawrjone 4y ago
Hey Hackernews! I work at incident.io, where we’re building an incident management platform that helps your organisation deal with incidents at scale. Today, we’re launching a set of resources intended to help those building their own incid
167.
by lawrjone 4y ago
This week I spoke at PlatformCon about Growing into Platform Engineering, sharing my experience leading such a team as we scaled the engineering org. Given my talk notes were pretty detailed, figured I'd turn them into a blog post that
168.
Lessons learned while growing into Platform Engineering(blog.lawrencejones.dev)
1 points by lawrjone 4y ago|1 comments
169.
How to empower your team to own incident response(incident.io)
1 points by lawrjone 4y ago|1 comments
170.
by lawrjone 4y ago
Posting on behalf of a colleague, this is a great article about the challenges involved in developing a build-it-support-it culture. Martha (the author) has experience of this at a company attempting to make this change, as an IC experienci
171.
by lawrjone 5y ago
Author here I work at incident.io, where we use Go as our primary language. Getting Go to integrate well with Sentry (our exception tracker) was more fiddly than expected, so we've written up our approach in case it's useful to ot
172.
Making Go errors play nice with Sentry(incident.io)
1 points by lawrjone 5y ago|1 comments
173.
by lawrjone 5y ago
Author here! I was recently asked for the most impactful piece of code I'd written, and thought I'd write-up my answer. I think it's cool that it: - Took very little time to write - Avoided a costly alternative - Is hard to j
174.
My Most Impactful Code(blog.lawrencejones.dev)
2 points by lawrjone 5y ago|1 comments
175.
by lawrjone 5y ago
Yeah, I think this is personal preference at this point. I find TS to be pretty great, especially in how you can use the type-system to help you build your code. If your goal is not that, then we'll be aiming for different things. >
176.
by lawrjone 5y ago
> you will have to test it anyway most likely I think we're cross talking. One of the primary advantages of this approach is that when you add a new value to that switch, your compiler will tell you about all the parts of the codeba
177.
by lawrjone 5y ago
100%
178.
by lawrjone 5y ago
You're right, which is why we don't need types, I guess? I'm being facetious, but if you're using a statically typed language you've already bought into types helping you across your codebase being worthwhile. Equal
179.
by lawrjone 5y ago
I should say, we have absolutely no performance requirements, at least in terms of what this will do. If we could add 10% developer efficiency for 20% performance hit, we'd take that in a heartbeat. The nanoseconds this construct might
180.
by lawrjone 5y ago
Hey, thanks for the response! I disagree with you that this is non-idiomatic Go code, but that's by-the-by: no one can agree on what the idiomatic way really is, anyways. On your solution: you're right in that you can define separ

More ›