![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/1be75b15-2f18-429d-acf7-dcea8e512a4b.png)
Me too! I am not a professional but audio support is such a point of friction for me that I’d love to see how others handle it when it’s critical to their work.
Me too! I am not a professional but audio support is such a point of friction for me that I’d love to see how others handle it when it’s critical to their work.
There’s already some good advice here, especially about virtual environments which might be the most important new concept to learn IMO. But just to let you know - it’s not just you. The most generous view of the Python package situation is that there are a lot of different ways to do it.
a stable experience that isn’t buggy
Stable has a particular meaning with distros but I think the context here is using the plain English definition of the word.
Ubuntu Breezy (5.10)
I hate seeing data encoded into magic comments, struct tags included. One of my biggest gripes with Go is that I think they should have used a different symbol to distinguish important annotations from true comments.
This is probably the worst example to choose, because in the US the generic name is acetaminophen. This is a case where the brand name actually unites understanding of a drug whose chemical name differs by location.
That being said, I still agree with the spirit, let’s stick to referring to the drug and not the brand.
Can we talk about how utterly absurd it is that there isn’t an obvious answer to this question yet? Feels like we’ve gone backwards from the AIM Direct Connect of old.
I always thought it was weird to model a game avatar after myself. I always roll the “random character” button (shout-out Monster Factory) when it’s available, keeps things simple.
In applications where I’ve needed this, I’ve taken a manual approach. Structure the function to return a single Result struct (including an error field), develop a convention for mapping function inputs to a string, then add reads & writes to a map[string]*Result
which allows me to return cached values as a shortcut. No idea if it’s the most efficient way, I’ve not actually considered finding a package to handle the process.
Edit: For more advanced behavior, what are your thoughts on the official memoize package?
The K5 has been in some sticky situations in other cities. One was toppled and slathered in barbecue sauce in San Francisco…
I don’t know why but this is just a hilarious failure state for a giant robot.
Can’t you cut out the battery code since your screenshot indicates it wasn’t used? I should be clear that you’ll have to edit some bash scripts to make what you’re asking for happen.
Looks like that config info might be defined in this script
Thanks for this, good reminder that there’s a lot of optimization I could do with my CI/CD build caching…
I will never use a terminal that requires a subscription to use my own damn computer.
Overly fine-grained “brittle” mocks are something to be wary of, I agree that you don’t want to have to change a ton of tests every time you edit the code. But the hand-wavey suggestion of “use a fake instead” with no follow up is not particularly helpful…
That was a good write up of the loop var issue, I had run into that only once and figured it was just a part of the learning curve I hadn’t hit yet. Glad to see it’s an area everyone agreed could improve!
I could redraw this whole chart using only references to pipenv based on my experiences with managing it alongside other tools (especially homebrew). It’s good at many things but is no magic bullet.
deleted by creator