total 328K
| Mode | Links | User:Group | Size | Date | Name |
|---|---|---|---|---|---|
| -r--r--r-- | 4 | coronado@devlog | 1.592K | 2026-05-30 | log-2026-05-30.mdACTIVE |
| -r--r--r-- | 3 | coronado@devlog | 1.773K | 2026-05-10 | log-2026-05-10.mdACTIVE |
| -r--r--r-- | 4 | coronado@devlog | 1.186K | 2026-05-03 | log-2026-05-03.mdACTIVE |
| -rw-r--r-- | 1 | coronado@blog | 5.664K | 2026-03-21 | anki-gets-you-cracked.mdACTIVE |
| -rw-r--r-- | 1 | coronado@blog | 3.717K | 2026-03-18 | when-the-craft-starts-talking-back.mdACTIVE |
| -rw-r--r-- | 1 | coronado@blog | 1.359K | 2026-02-19 | hello-world.mdACTIVE |
Week 03. This one was a mix of leveling up on AWS and starting to think more seriously about production readiness. P.S: Sorry for the delay was travelling but here it is!
I picked up an AWS book and have been reading through it alongside actually using the services (S3, Amplify, EC2). Huge difference between watching a tutorial and understanding why things are set up a certain way. The book's been helping me fill in gaps I didn't even know I had — networking, IAM best practices, service limits, that kind of stuff.
Started using AWS Amplify for my Next.js app. The DX is honestly pretty smooth you connect your repo, configure the build settings, and it just handles deployments. Way less friction than manually wiring up EC2 for a frontend. Still figuring out some of the finer details around environment variables and custom domains but so far so good.
This is the new chapter. I've started adding monitoring and logging practices to my upcoming SaaS. It's one of those things you know you should do from day one but always push off. Not this time. Setting up structured logs, health checks, and making sure I actually have visibility into what's happening when things inevitably break at 2am.
More on this as the stack takes shape.
Stay tuned.
Will post my app soon as well :)
-- End of preview --