Yan Cui
I help clients go faster for less using serverless technologies.
- 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 4 ways I can help you:
- If you want a one-stop shop to help you quickly level up your serverless skills, you should check out my Production-Ready Serverless workshop. Over 20 AWS Heroes & Community Builders have passed through this workshop, plus 1000+ students from the likes of AWS, LEGO, Booking, HBO and Siemens.
- If you want to learn how to test serverless applications without all the pain and hassle, you should check out my latest course, Testing Serverless Architectures.
- If you’re a manager or founder and want to help your team move faster and build better software, then check out my consulting services.
- If you just want to hang out, talk serverless, or ask for help, then you should join my FREE Community.