Operations
-
How to write an issue ticketWhen you file an issue for a developer to work on, you can make it easy on that developer, or you can make it very frustrating. Learn More...
-
How to write a bug ticketFixing bugs requires certain information. Learn how to file bug tickets that developers can fix. Learn More...
-
How to file a Pull RequestCode needs to be reviewed before its merged. Learn how to make that process easier on your team. Learn More...
Code Patterns
-
Naming ConventionsNaming is critical for communication, speed, and modeling. This post describes a number of important names to learn and use. Learn More...
-
Banned TermsAvoiding bad names is as important as using good names. You should avoid these terms when naming your own app or package classes, methods, and properties. Learn More...
-
Packaging code for appsCode has to go somewhere. Learn how to breakdown directories and files in an effective way. Learn More...
-
Consistent code orderingReading code quickly depends upon consistency in coding practices. Apply these code ordering policies throughout your code for faster reading and easier review. Learn More...
-
Developer logsThe most popular debug tool is print statements littered through code. They get the job done, but they can expose sensitive data, cause performance problems, and fill your terminal with noise that hides the important details. Learn how to fix these issues with loggers. Learn More...
Patterns
-
FlowsUser journeys should be quick to assemble, re-arrange, extend, and compose. Learn how to use Flows to accomplish these goals. Learn More...
Testing
-
Custom MatchersWhen tests fail, you have to find the root cause to fix them. A helpful way to find the root cause is with descriptive Matchers that understand your data structures. Learn how to create your own. Learn More...