majormunky
Joined 7 years ago
Joined 7 years ago
People working in customer support, from my experience, sort of see the anti-survivorship bias working in action. Not many people call up to say how well something works. I would agree with you though on good Salespeople (ones that do try to understand what customers need and all that, not necessarily ones that sell the most) knowing what the customer wants/needs.
Generally speaking the only thing I'm holding in my .env file is the Django secret key, and the debug flag, so, pretty limited use case, but works well I think. I manually create the .env file when setting up my site, so none of it goes into any repos.
As a side note, my 2019 Subaru Crosstrek can't seem to show the backup camera, and deal with me turning the physical radio volume dial down at the same time. I think the computer in a car should be up-gradable.
Edit: a macro example, which I think may be the more common route of doing this type of stuff? https://lisp-journey.gitlab.io/blog/common-lisp-macros-by-ex...
In lisp (and code is data, data is code), the function is also a list, so you would be able to use all the normal programming tools to iterate over the list, add new items to the list, etc, which can change how the function runs.