normal indeed but not what i'd consider a best practice anymore. we've moved away from any secrets in the env after the typical secrets leak when secrets popped up in some debug logging that hit datadog.
we now have a secret cache layer api and the app loads secrets securely at time of use from that api. there's also no secret-0 problem because we use IAM auth when calling the cache.
edit: for those wondering, api response time is sub 1ms (rust!)
I'm in New Mexico too, there's some creeks I frequent that are considered "navigable waterways" and unless it's monsoon season, you barely get your ankles wet lol.
At my offgrid cabin I converted a $300 chest freezer to a fridge by using an external thermostat that toggles power off/on based on temp. I have it turn on at 37 degrees and turn off at 35. It uses such little power that it's not even a factor for my small solar setup.
Indeed. Not as easy to organize as one with a front facing door, but we keep stuff organized in milk crates and it's worked great for our family for many years now.
As an EFnet admin: EFnet ;-) IRCnet is still around too with some very active chat channels (e.g. #worldchat). The networks are much smaller nowadays though.
Want to talk about a FLOSS project? Libera.Chat, OFTC, GIMPNet.
Want to just chat? Snoonet, Slashnet, Quakenet.
Want to just chat but want it to be technology focused? Darkscience, 2600net.
This is a shortlist of public networks I can recommend to a new/returning user; there are many smaller networks out there that you might discover organically with time.
[0] Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems.
I love regular expressions and figuring out the syntax to solve problems I encounter where I can use regex. Such as searching code for calls with specific named params that may be in different order across the code base. But I always have this quote in the back of my mind if I'm thinking about using regex in code, especially areas that get hit a lot.
It's really subject-specific. What I usually see is a small problem easily solved by Regex, that a few months later down the line we need to expand the regex a little bit, but that's ok it's still readable... repeat this a bunch of times and now you have a critical regex line that nobody really understands how it works and nobody ever wants to touch without it being unit-tested to death.
I am a huge, huge fan of https://regexper.com/ - paste pretty much any regex, and it will generate a visualization of what it does. It's been invaluable even just as a sanity check, it just makes it so easy to trace the flow of what a pattern is doing.
Back when I used Windows, I had an app called Regex Buddy and you could paste in any regex and it would generate a comment block that broke down what was going on. Was super useful when you come back a few months later and need to understand a complex regex
I once asked my friend: "Is there anything Regex can't do?" He replied: "Work the first time?"
And that's how I always think of Regex now. It's an incredibly powerful tool that I pull out pretty often, but if I'm doing anything beyond the most basic pattern matching I know I'm about to lose a bit of time questioning my abilities and sanity.
we now have a secret cache layer api and the app loads secrets securely at time of use from that api. there's also no secret-0 problem because we use IAM auth when calling the cache.
edit: for those wondering, api response time is sub 1ms (rust!)