HN Explorer

lawrjone

↗ HN profile [ 84.7 ms ] full profile
Karma
0
Created
()
Submissions
0
  1. Building AI skills like checklists (blog.lawrencejones.dev)
    2 points 0
  2. Comparing GPT-4.1 against other models in "did code change cause this incident"

    We've been testing GPT-4.1 in our investigation system, which is used to triage and debug production incidents. I thought it would be useful to share, as we have evaluation metrics and scorecards for investigations, so…

    1 points 0
  3. 1 points 0
  4. 1 points 0
  5. 1 points 0
  6. 1 points 0
  7. Ask HN: Any good 2023 retros out there?

    I find writing a yearly retro a great way to reflect and get closure, and have just finished mine for 2023: https://blog.lawrencejones.dev/2023/ Have other people done the same or seen any good ones? I love getting a…

    6 points 1
  8. 1 points 0
  9. 1 points 0
  10. 1 points 0
  11. 1 points 0
  12. Uptime, status pages, and transparency calculus (blog.lawrencejones.dev)
    3 points 1
  13. Trade-offs from using ULIDs at incident.io (blog.lawrencejones.dev)
    4 points 1
  14. Looking back at 2022 as my first year at incident.io (blog.lawrencejones.dev)
    2 points 1
  15. Weird stuff and how to test it (blog.lawrencejones.dev)
    17 points 7
  16. Tricks we used to get our CI builds below 5M (twitter.com)
    3 points 1
  17. Incident review: Intermittent downtime from repeated crashes (incident.io)
    2 points 1
  18. Ditch your overly detailed incident response plan (incident.io)
    2 points 1
  19. Building a Workflow Executor on Postgres (incident.io)
    2 points 1
  20. How we built our workflow engine (incident.io)
    4 points 1
  21. What I learned as employee #2 at a scaling startup – year 1 at incident.io (incident.io)
    2 points 1
  22. We're making our on-call pay calculator free (incident.io)
    2 points 1
  23. Want to found a startup? Work at one first (blog.lawrencejones.dev)
    318 points 155
  24. Adding latency: one step, two step, oops (blog.lawrencejones.dev)
    2 points 1
  25. Handling third-party provider outages (incident.io)
    2 points 1