185 karma · joined March 4, 2008
As for the product, it was great to work on and there was so much potential simply left on the floor. Really a shame to see that none of that will be realized.
I highly recommend anyone using terraform start with a mono repo. Still use modules and then spread out your components but definitely don't try to split them up in separate repos because keeping the version graph together will become a real pain and is easy to mismanage.
From there, ensure any logical components have their own separate lock and state file. If you don't do this, it is going to be a game of roulette to know when this resource was last run and what might change if you roll it out. It is easy to build your own directed graph between components using data sources. These allow you to have component B read component A's state file to get the outputs it needs.
All in all, I've found most of the documentation and "best practice" in the terraform community promoting dangerous practices. I talk more about these practices in this podcast[0]
[0]: https://packetpushers.net/podcast/full-stack-journey-027-und...
It seems the anti-homebrew complaints basically amount to "I don't understand this, so I'm going to say it's bad".
The biggest reason I've seen to get rid of Macports in favor of Homebrew is software versions, Homebrew is constantly up to date and I can upgrade software with ease. Not so with Macports.
(defun maximize-frame ()
(interactive)
(set-frame-size (selected-frame)
(display-pixel-width)
(display-pixel-height))
(set-frame-position (selected-frame) 0 0))
EDIT: Should've read the help :):)
I've been unable to find any mention of using violence. But it is difficult to search for an answer.