Laurie
@laurieontech.dev
Developing software one mistake at a time. LEGO obsessed.
Find the smallest non-utility functionality and see how comfortable you are parsing it. You don’t need to know the business logic, but understand the technical pattern in use.
November 6, 2025 at 12:32 PM
Find the smallest non-utility functionality and see how comfortable you are parsing it. You don’t need to know the business logic, but understand the technical pattern in use.
My experience is with DNS and there are long known but painful ways to improve on the footguns in that experience.
I would not pretend to be an expert on mitigating the risks that exist with DNS configuration today.
I would not pretend to be an expert on mitigating the risks that exist with DNS configuration today.
October 21, 2025 at 11:45 AM
My experience is with DNS and there are long known but painful ways to improve on the footguns in that experience.
I would not pretend to be an expert on mitigating the risks that exist with DNS configuration today.
I would not pretend to be an expert on mitigating the risks that exist with DNS configuration today.
I believe route 53 had an outage as part of this
October 21, 2025 at 11:43 AM
I believe route 53 had an outage as part of this
Reposted by Laurie
![A variation on XKCD's "compiling" comic:
The #1 Programmer Excuse for Legitimately Slacking Off: "US-East-1 is down."
[Two programmers are sword-fighting on office chairs in a hallway. An unseen manager calls them back to work through an open office door.]
Manager: Hey! Get back to work!
Cueball: AWS is down!
Manager: Oh. Carry on.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:u7wngvhphfoorplx5eyunsz7/bafkreic4alpbfcabkb3tvjpris5jfme3de5mjoqvjprt4venllv5mpfzme@jpeg)
Well for the draft I just finished I wrote the start/outline of 3 different posts first 😂
September 14, 2025 at 9:04 PM
Well for the draft I just finished I wrote the start/outline of 3 different posts first 😂