…it is useful to use appropriate HTTP status codes [and] [i]t is this desire for traceability that requires additional work, and that typical Internet searches have difficulty resolving quickly.

OpenAPIv3 can be leveraged as a single source of truth when building AWS REST API Gateways. Terraform configuration can pull it in, and AWS vendor extensions ensure that API Gateway integrations are stood up.

[@ControllerAdvice] can reduce and centralize a great deal of code, allowing for deep introspection surrounding one or two files rather than digging through hundreds of lines of code and error-throwing locales.

[A]in’t no engineer got time for [manually-updating and -tracking architecture diagrams]; that’s a moving target and a fool’s errand to keep updated!

These things are wicked fast

Ooh, shiny!

Ooh, shiny!

What exactly am I about to take to production?

If I can draw it, I can build it. Maybe you’re like this too.

It’s really awkward to know what to pick next in the AWS certification ecosystem.