lawrjone

39 ms·

211.
Building safe-by-default tools for a multi-tenant Go appp(incident.io)
2 points by lawrjone 5y ago|1 comments
212.
by lawrjone 5y ago
Author here! We're pretty keen on fast CI times, from the developer happiness angle to agility when you want to roll-forward a bad deploy. Our ideal is less than 5m from merge to production, and were unhappy when our pipeline became &g
213.
Deploying to production in less than 5m with a hosted container builder(incident.io)
4 points by lawrjone 5y ago|1 comments
214.
How incidents made me a better engineer(incident.io)
3 points by lawrjone 5y ago|1 comments
215.
by lawrjone 5y ago
We have some terraform that generates each developer their own GCP project, along with all the infrastructure and build pipelines they'd need to run their stack themselves. It looks something like this: module "incident_io&q
216.
by lawrjone 5y ago
You're totally right on the OC vs OT- we couldn't use OT when I first put this together, as the StackDriver plugin wasn't compatible. We also found it didn't work out-the-box with a load of our stuff (notably the GCP cli
217.
by lawrjone 5y ago
Urgh, yes. This is a really difficult place to be coming from, and I totally feel your pain! My background was working as an SRE at GoCardless, starting when the company was around ~30 and leaving at around 700. During that time we did the
218.
by lawrjone 5y ago
Sentry ( https://sentry.io/ ) has been building a load of tracing functionality, and the Javascript client captures logs and requests leading up to an error by default. I've used this in the past quite a bit, and found i
219.
by lawrjone 5y ago
That's really interesting! In terms of incident.io, we're a team of 3 engineers (looking for more!) and a company of 6 in total, so our priority was on buy and not build. But in my most recent experience at a larger company (finte
220.
by lawrjone 5y ago
That all sounds very normal to me, and it's what I'd expect most people do. The bit that surprised me is more likely due to my background being mostly Ruby/similar based, which is around debugging highly concurrent apps. Our
221.
by lawrjone 5y ago
Author of the post here. We're a super small start-up, but with prior experience of great observability toolchains. Been really surprised at how little effort it required to get a richly integrated trace and logging setup, using Cloud
222.
Logs and tracing: not just for production, local development too(incident.io)
66 points by lawrjone 5y ago|25 comments
223.
by lawrjone 5y ago
Am on the team with Sophie (author) and am really glad we managed to avoid building our own feature flagging system. Seems like a thing companies love to build themselves, given past experience.
224.
by lawrjone 5y ago
Author here: have worked on many incidents, big and small. The most painful mistakes I've made have almost always been due to assumptions, either incorrect or posing as facts. This article talks about a specific incident that was plagu
225.
How to avoid bad assumptions during incidents: trust, but verify(incident.io)
2 points by lawrjone 5y ago|1 comments
226.
by lawrjone 5y ago
Yep, this is particularly relevant when building pagination. If you use the primary key, which itself is sortable and based on a sequence, you might be surprised when you skip over rows that were yet to be committed because the IDs won&#x27
227.
by lawrjone 5y ago
Author of the post here: what you say about pulling yourself away and recovering really resonates with me. What I'm working on is absolutely a factor in my interest, and how much energy I'm able to give- equally, how much the work
228.
by lawrjone 5y ago
I think you make some really good points here. I had a few experiences like the one you describe: I recall a small side project where I would wake, work for ~14hrs until I slept, then rinse and repeat for a few days until I got the work don
229.
by lawrjone 5y ago
> I've had managers try to nanny my working hours like this. It wasn't fun. I know they thought it was a good gesture, but if I have a spare hour or two in the evening and a good idea I want to try out before bed, I don't
230.
by lawrjone 5y ago
> New college grads can really struggle with finding balance after transitioning out of college > Ambitious juniors often see this and decide to go all-in The most common issue I see with dedicated juniors is when work is, by a large
231.
by lawrjone 5y ago
I really empathise with your experience of lockdown- Covid has taken a big toll on a lot of people, myself included. Especially at the start of lockdown, I developed a habit of working on a side project at the weekend. I found myself slippi
232.
by lawrjone 5y ago
Yep, this type of gesture speaks volumes. It's saying the company is expecting you to value your personal life and health alongside your work, and demonstrating that it's ok to work however works best for you. As many others have
233.
by lawrjone 5y ago
I've been lucky to have a number of great role models in my career, some of which shaped my opinion on hard work and how to find balance. I know the concept of "hard work" has come up recently, so figured I'd share my ex
234.
On working too hard: finding balance, and lessons learned from others(blog.lawrencejones.dev)
174 points by lawrjone 5y ago|93 comments
235.
by lawrjone 5y ago
Really appreciating the work incident.io have been doing- we've started using the tool at GoCardless and seen some really marked behavioural changes that I've really enjoyed. Having spent a while training the SREs at the company i
236.
Leaving a company you like: reflections on GoCardless(paprikati.github.io)
9 points by lawrjone 5y ago|1 comments
237.
GoCardless launches open banking payments, new alternative for one-off payments(gocardless.com)
2 points by lawrjone 5y ago|0 comments
238.
by lawrjone 6y ago
There's an excellent talk from Nick Means (GitHub) called "Who Destroyed Three Mile Island?". Link: https://www.youtube.com/watch?v=1xQeXOz0Ncs One thing it discusses is how the alerts inside the control hub
239.
by lawrjone 6y ago
Author here! If you have any cool ideas of how to use this new feature, I'd be really interested to hear them. One suggestion that is probably a terrible idea is bundling other go binaries into your app. Say fzf, which really wants to
240.
Embed a JavaScript website inside a binary with Go 1.16(blog.lawrencejones.dev)
2 points by lawrjone 6y ago|1 comments

More ›