> Perhaps it could be this: if my value comes from running some crazy interesting high-level Math-derived ML model on data, and I’m highly paid, then the opportunity cost of becoming good at C++ is higher than if I can do the same thing in a few lines of python and just throw some more compute at the problem, since that’s a fixed cost.
Add some hyphens and commas and shed a bit of cruft, and it's fine IMO. (I hope you don't mind my speculative editing.)
I appreciate the feedback. Defending wordy stream-of-consciousness writing style is not a hill I want to die on.
I did realize that if I have to throw a million cores at something vs. 1000 perhaps it would make sense to spend the effort or buy the time from an expert in C++ so as to save on the compute cost. But then, what if those million cores are only needed for a a day or an hour? Then python or some other rapid prototyping language would make a bit more sense imo.
Add some hyphens and commas and shed a bit of cruft, and it's fine IMO. (I hope you don't mind my speculative editing.)