Yan Cui
I help clients go faster for less using serverless technologies.
This article is brought to you by
Don’t reinvent the patterns. Catalyst gives you consistent APIs for messaging, data, and workflow with key microservice patterns like circuit-breakers and retries for free.
- Use 4-space indentation, no tabs
- Wrap lines so that they don’t exceed 79 characters
- Use blank lines to separate functions and classes, and larger blocks of code inside functions
- When possible, put comments on a line of their own
- Use docstrings
- Use spaces around operators and after commas
- Name your classes and functions consistently; the convention is to use CamelCase for classes and lower_case_with_underscores for functions and methods
- Always use self as the name for the first method argument
- Don’t use fancy encodings if your code is meant to be used in international environments
Naming conventions:
Variables / functions – use_lower_case_separated_by_underscore
Class names – UseCamelCase
Error classes end in Error, i.e. MyError
Whenever you’re ready, here are 3 ways I can help you:
- Production-Ready Serverless: Join 20+ AWS Heroes & Community Builders and 1000+ other students in levelling up your serverless game. This is your one-stop shop for quickly levelling up your serverless skills.
- I help clients launch product ideas, improve their development processes and upskill their teams. If you’d like to work together, then let’s get in touch.
- Join my community on Discord, ask questions, and join the discussion on all things AWS and Serverless.