@mitchellh Why is no one concerned about hurting the users’ feelings when they don’t get an important feature on time?
And now, there are a lot of service features that not supported by TF in AWS
No time but UTC.
When your team spans multiple time zones, using UTC for release announcements, maintenance schedules, and incident reports eliminates confusion, ensures clarity, and keeps everyone synchronized(regardless of their location). Please.
#DevOps#SRE#remotework
@anarchyco I’d add one more thing: https://t.co/9JbSENDSG3
This isn’t replace good description, but extremely helpful on forming good git history and release notes.
Often commits atomic and self descriptive, in this case commit title could be enough:
`bump(go): Upgrade to v1.23 - task-123`
@mitchellh But what is so important and urgent about what we do that we need phones and planes? Lives don’t depend on developers, right? Can’t a meeting wait a day or even a week? Especially if it’s open source and there are no SLAs involved?it seems to me that technology can be excessive.
@joncalhoun You are right - most of smoke detecters work on the principle of light beam interruption so when the battery is low and it's a day the power is enough but when it gets dark...