Helpful questions

Avoiding accidental complexity should be a top priority when helping build or solve multifaceted issues. One of the best ways to avoid this complexity is to be organized and concise, and get a check by someone with lots of experience on that thing.

I’m not at the point where I consider myself an expert on most things, but I appreciate the following: an experienced individual steps back and worries a lot more about why before how.

• Why do you want to build this app with micro-services?
• You really think we need to migrate all of our apps from AWS to GCP?
• Kubernetes, really? We have 6 users.

I also believe that in situations like these, constructive criticism, especially from an experienced reviewer can be highly beneficial. Many people will take offense to helpful questions, but seeing it as efficiency can help all parties involved.