This title needs to be disambiguated. I had assumed that most musicians, and especially prog metal bands, were non-profit by default. I was curious why that had to be made explicit!
I'm a big fan of capturing the toolchain(s) with the repo. I have had to hack this for embedded toolchains out of necessity for years (decades?) using VirtualBox on a Mac. I still have a Windows 95 VM sitting around containing a copy of Keil or something that is the only known way to rebuild the code for a certain weird-ass micro from some consulting gig in the late 90's. I wonder if it still boots? Hopefully, that customer forgot about me...
Copilot is going to really rock the numbers on lucrative unhose-your-sucky-codebase consulting gigs. I'd feel gleeful about that but those gigs are the definition of soul-sucking so I guess still no free lunch.
This seems to broadly conflate CS and Software Engineering. The differences have been covered elsewhere. Stuff like cognitive vs. physical science, (mostly) thinking about thinking instead of thinking about things, or quotes like "A computer is to computer science as a telescope is too astronomy." To be fair, the fact that a lot of us got CS degrees, but really ended up doing software development probably doesn't help clarify matters. The university I went to had a separate degree for Software Engineering and, frankly, it looked pretty boring to me. Even though I was a full-on coder before I got there. Perhaps there is no hope?
Not really on topic, but it has been "interesting" to watch the cheating progression unfold in fitness games (Zwift, etc.) where it essentially IS digital steroids. Although often done in a very analog way, like attaching drill motors to $10k carbon bike frames to get that pro-level rush of achieving 5w/Kg for hours at a time. A Movistar contract, no doubt, arriving shortly...
I think you are on to something here. Make all elevators in hi-rises down-only and all stairwells up-only. Convert falling excess desk-jockey blubber into usable electricity while lowering rate of CV disease and generally improving fitness. Downside is probably a lot of BO that didn't exist before.
Seems reasonable. March/April is the end of the Concept2 indoor rowing annual "season" and I noticed that I had put essentially the same distance on my rower last year as my truck.
I told a fairly obnoxious and (in my mind) idiotic customer to "take a chill pill" on a conference call. This did not work out well. I did call them back and apologized before my management told me too, but I'm claiming no credit there, that was just pure self-preservation kicking in. On the plus side, after that day, I (slowly!) started to understand how salespeople can be really, really good at a really, really hard job. I very much enjoy sales now and I think I have a lot more empathy for where my customers are coming from thanks to that very dark day.
Maybe not for general-purpose computing. I've used it for on-the-fly code generation (hacking display rotation into the Windows 3x BitBlt engine) and programming special-purpose media accelerators. In both cases you end up creating a bunch of convenience #defines or macros that generate the bits, which immediately takes you back into tiny language territory rather than pure machine code. The relative ease of creating new programmable hardware in FPGAs is another place this might occur.
The university I went to had used Xerox Sigma 6/7/9s. One of them is now in the living computer museum. Yeah! After programming 6502 assembler in high school, having multiple blocks of 16 32-bit registers was breath-taking. My brain was wired to the 6502 X/Y/A thing so I doubt I ever used more than 5-6 of them at a time. After doing a lot of 8-bit micro and X86 assembly, doing ARM assembly for the first time felt similarly freeing.
Ya, have a cat who took on 2 copperheads at once with great delight. I won't say I rescued him but I did get him out of there with some blood loss (mine). Maybe a study on the cat - mongoose correlation?
Compared to this? "You should at least read the whole abstract before assuming you understand it." I can do the math for you, but it would be great if you could pitch right on in there yourself.
Indeed. The thing that caused me to actually move stuff off AWS to GCP was that you could deploy generic Node Express apps as Firebase Cloud Functions (and then Cloud Run). I knew I could move those anywhere if I needed to.
Probably would have been better for the author to have taken the "don't sell out to a single cloud vendor API" angle. But I guess no clicky-baits for that approach. I've been screwed over by both AWS and Azure, and never by GCloud, but that doesn't mean I trust any of them.