This should be the standard :)

Someone was posting a week or two ago having done something kinda like that. Something to do with magic circles or similar, looked rad.

Yeah, not trying to dunk on other commenter, but these don't sound like complaints I experience with Python at all. Setting up the environment is a breeze with venv, package installation couldn't be easier with basic pip, and I really like having a diverse ecosystem of multiple (often high quality) approaches to solving similar problems.

Everyone's welcome to their opinion of course, but I find Python more readable than anything else and I resent the visual clutter required to make intentions plain in other languages. Feels like having a conversation where people say the words "comma", "period", etc.

I also spend more time with Python than anything else and I suspect these two facts about me relate, lol

Couldn't agree more. Field service is one hell of a drug. Money's good, variety is fun, the chaos and travel are fun too, and you learn a lot quickly. The latter often because some or all of the mfg. plant you're visiting needs you to fix your stuff so they can run, and no one is coming to BFE to help you, lol.

But that all wears off, in time, and it starts to take a huge toll like you described. Never met a long term field service engineer with a healthy home life, or with their health in general. I got out because both of mine were crumbling, for real.

Ah, alcoholic then

It's mainly a different model, but I totally sympathize that it's the opposite of welcoming or encouraging.

SO recognizes that many, many questions are really just rephrasings of the same underlying question, and the aim is to find and provide the best answer to those. It explicitly does not want to repeatedly answer the same question, and given how few people find out how it works before simply asking, they have to be pretty ruthless about it. The result is that usually the most active and fleshed out questions and answers are very informative. So there's a big upside in trade for those downsides. Answers are meant to be durable, ~singular, and authoritative.

Reddit is basically halfway between that, and Discord. Discord is the polar opposite, questions and answers are naturally ephemeral, duplication happens constantly, and quality of responses is all over the map.

I greatly prefer the StackOverflow model, and - to be very clear - I have never once asked (to say nothing of answering) a question of my own there, lmao.

Utterly tone deaf, some of these guys, it's amazing. Had a new CEO open a meeting shortly after he started with a story about visiting an apiary (bee farm) with his family. His unironic takeaway which he shared with us, somehow missing the poignant relevance of what he was saying - "It turns out the drones just don't do very much".

It was like he intended an ice breaker with a personal anecdote, and it started out fine, but he couldn't help but just tell literally all of us how he really feels. Amazing.

'twas told to me that in many ways they refuse to cooperate with our system of taxonomy at large, too freaky to ever be properly pinned down

Just wanna say, great job on the feedback reception. Critically important (and often hard!!) skill, to get the value while leaving the ego-hit. If you handle criticism this well as a non-fulltime-dev, on a project you care about and that you have solo'ed - I have a feeling you have a lot of dev potential.

Yes, this one has tasted blood before. You can tell by the way that it is.

What do you do instead for dynamic values that are needed at runtime and inappropriate to check in to version control?