Yan Cui
I help clients go faster for less using serverless technologies.
This article is brought to you by
The real-time data platform that empowers developers to build innovative products faster and more reliably than ever before.
- 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:
- 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.
- Do you want to know how to test serverless architectures with a fast dev & test loop? Check out my latest course, Testing Serverless Architectures and learn the smart way to test serverless.
- 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.