<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>nielsole</author><text>Another random selection:&lt;p&gt;* When choosing internal names and identifiers (e.g. DNS) do not include org hierarchy of the team. Chances are the next reorg is coming faster than the lifetime of the identifier and renaming is often hard.&lt;p&gt;* The industry leading tools will contain bugs. From Linux kernel to deploy tooling, there are bugs everywhere. Part of your job is to identify and work around them until upstream patches make it to you if ever.&lt;p&gt;* Maintaining a patched fork is usually more expensive than setting up a workaround&lt;p&gt;* Your hyperscaler cloud provider has plenty of scalability limitations. Some of which are not documented. If you want to do something out of the ordinary make sure to check with your account rep before wasting engineering time.&lt;p&gt;* Bought SaaS will break production in the middle of the night. Your own team will have the best context and motivation to fix&amp;#x2F;workaround them. When choosing a vendor, include the visibility into their internal monitoring as a factor for disaster recovery (exported metrics and logs of their control plane for example)</text><parent_chain></parent_chain></comment><story><title>General guidance when working as a cloud engineer</title><url>https://www.lockedinspace.com/posts/001.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>throwawaaarrgh</author><text>Truth is an interesting concept. It&amp;#x27;s often subjective and has many forms. Within the context of the cloud, almost all cloud services are only mutable, so &amp;quot;truth&amp;quot; is whatever the current state of the cloud actually is. Whatever is in Git is merely &lt;i&gt;idealism&lt;/i&gt;.&lt;p&gt;Whatever you are maintaining, read the docs completely first. And I mean cover to cover. Not just the one chapter you need to get a PoC up and running. You will wish you had later, and it will come in handy many times over your career. Consider it an investment in your future.&lt;p&gt;Read books on microservices before you implement them. Whatever two-line quip you read on a blog will not be as good as reading several whole books from experts.&lt;p&gt;Docker multi-stage builds won&amp;#x27;t work in some circumstances. Build optimization eventually gets complex, the more you rely on builds to be &amp;quot;advanced&amp;quot;.</text><parent_chain></parent_chain></comment><story><title>General guidance when working as a cloud engineer</title><url>https://www.lockedinspace.com/posts/001.html</url></story>