I've got a bunch of Ansible scripts, written in around 2013 or so - and then constantly tweaked over the years. Code quality isn't the greatest, but I've been using them to provision a bunch of laptops, Linux PCs, etc. They work good enough that I didn't search for a replacement yet. There's always a thing which needs fixing with these scripts, which is to be expected for something which is only fired every so often.
Hardest part of using them is remembering to do any config changes in Ansible repos and not directly in config files.
I have diverging logic, branching off usernames and group memberships to treat given machine as "personal" or "work" - and then configure certain settings differently. I'm using ansible-vault for secrets like SSH keys, etc.
New machine provisioning is usually just installation of a package manager (if not present, like brew), and installation of Ansible.
I have almost exactly the same habits when using editors mentioned above. I'm not sure if I've been using Vim (neovim now) or Emacs (+evil) for longer, but both have great reasons to be installed at the same time.
This is a great feature and I did use it few times to test. However, be aware of potentially leaking your company's private or sensitive information when doing this.
OpenAI will not use data submitted by customers via our API to train or improve our models, unless you explicitly decide to share your data with us for this purpose. You can opt-in to share data.
Any data sent through the API will be retained for abuse and misuse monitoring purposes for a maximum of 30 days, after which it will be deleted (unless otherwise required by law).
The OpenAI API processes user prompts and completions, as well as training data submitted
This is anecdotal but EVGA replaced my 1-month out of warranty 970 with 1070, after the card gave up to work about 2 years ago. And I registered it after the failure, although I was able to establish that I bought the card legally and was the only owner.
All my contact with their customer support was stellar.
To provide a counterexample: I had a still-in-warranty EVGA 1080 that had a fan die. They cross-shipped me 3(!) bad cards in a row that were clearly returns they hadn't tested (two had obvious physical damage upon arrival in pristine boxes), and on the final card that sort-of worked (a 2070 I had to underclock to stop blue-screening), never acknowledged my return of one of the previous bad units, even though I sent them shipping proof from the UPS store.
When I tried to get the 2070 replaced, they refused unless I paid full retail price for a defective card I had proof I'd returned.
I really regretted buying from them at that point, and wished I just had my original card back, which they couldn't provide.
QA on their refurb units is definitely out of whack.
I bought a B-Stock GTX 580 from them which was rendering artifacts iirc. A replacement 580 also rendered the same issue. The next replacement was a seemingly new GTX 960 which has worked without issue ever since. Having received a $200+ card for $80 + some hassle was a net positive experience in the end for me.
Different locations, I'd assume. It's well known that EVGA outside of the US is... not great, when it comes to customer service anyway. Within the US itself though -- no idea!
Over the two-month period this happened, I don't think I ever spoke to the same rep twice, and several times when I referenced notes that I know for a fact $previous_guy had, $new_guy had nothing. Most (not all, but most) were nice enough on the phone. I have a feeling that turnover is/was a large contributing factor.
Some time ago I bought an EVGA 560 Ti and they threw in a 10 year extended warranty. A couple years in it failed and they replaced it with a 660 Ti. About a year later that failed and they replaced it with a 960 Ti. I appreciate their warranty policies.
I find it fascinating (in a very good way) that he does find time to code. Python is not a bad language, in all fairness, any programming language which picks your interest enough to spend time working with it is a good choice.
The added benefit of Python is the ease of using something like Jupyter notebooks, which make it trivial to iterate.
(disclaimer: I coded more in Ruby than in Python, but I still enjoy both)
> The added benefit of Python is the ease of using something like Jupyter notebooks, which make it trivial to iterate.
Although, other languages do have better REPLs, allowing easier iteration than Python's REPL. Some languages, have both a better REPL and notebook-style programming, such as F#.
But I was really more curious rather than saying which language would be "better".
