Topic: practices
-
What about Engineering Principles?
There are many great resources that can be used as a manifesto for quality engineering. Having a baseline for your work can never be a bad thing; my favorites are the principles of Lean Manufacturing, Manifesto for Agile Software Development, Bauhaus Principles, and Amazon Leadership Principles. And - of course - The Frugal Architect.
-
AWS SDK: Pagination Pattern for JavaScript SDK v3
When using the AWS Software Development Kit, pagination in API responses is a common and sometimes annoying to deal with. Thanks to a shared interfaced in
@aws-sdkclients, can you can establish a common pattern to interact with AWS paginated API actions using the JavaScript SDK v3. Retrieving all AWS Accounts in your AWS Organization is a neat example use case for this. -
Semantic Releases With Github Actions
If you stick to Conventional Commits for your commit messages, you can create tags and releases with GitHub Actions for every code change you push to a repository. This is great for automated and continuous releases!
-
CloudFormation Best-Practices
You can find plenty of frameworks and tools to provision your AWS resources. Some of them do a great job for a specific purpose, others are more generic. Nevertheless, I do prefer to use native CloudFormation templates as much as possible.
-
Makefile Best-Practices
The more projects you work on, the more streamlined your tooling gets. Hopefully. Various services using different languages have different tooling requirements, of course. A sweet Makefile can be the entry to a unified tooling interface.