4 ms·

"Now we'll init a happy little project..." ERROR: CANNOT READ INPUT "Well... maybe we have a happy little full disk? Or a happy little broken pipe somewhe

"Now we'll init a happy little project..." ERROR: CANNOT READ INPUT "Well... maybe we have a happy little full disk? Or a happy little broken pipe somewhere?" 20 minutes later "Ah, it was a mis-match issue between versions 3.4 and 3.5 and our command line tools—the error message was misleading. What a naughty little error message! But now we're back on 3.4 and our tools are happy again. We'll just init this happy little project..." UNKNOWN SYMBOL 'DYNLIB_AUTOLOADER' ON LINE 836 OF ../../../BOBOLIB/INTERFACES/MAGIC_REPTILIZER.BRN "Um. Now isn't that silly, folks! We haven't even written any code, how can we have errors in it? Let me see if... no, that's not a path to anything from the current directory, so that must be from a process running with a different working directory. Let me just do a 'find'... no, no such file anywhere on my filesystem. One moment, we'll be back to painting trees in no time, I'm sure..." An hour and forty-five minutes later "Phew. There. This language's package manager had downloaded a binary for a different processor architecture, and then used it to try to build another package, and that failed. We didn't have the file mentioned in the error because that was using symbols from someone else's machine, having no relation to any files on this one. Luckily these tools let us build a package from source—except that was also broken, for another reason entirely. However! I found a link to a zip deep in a PHPBB forum that contains the fixed package, built for our architecture. The link was broken, but I was able to use the file name to find the zip on Mega. Hopefully my computer didn't catch a virus from it. Now, back to initing our HAPPY. LITTLE. PROJECT." ERROR: LIBRARY 'ROOPTYROO' REQUIRES VERSION 3.5, FOUND VERSION 3.4 Flips desk, swears, kicks everything ---- Thus ends the short career of Programmer Bob Ross.

striking 4y ago
Bob Ross was a drill instructor before he became the artist we all know and love. I think you'd have to have someone cut from similar cloth (maybe even tougher) for the programming version.
- spywaregorilla 4y ago
  A paired programmer whose partner ignores all keyboard shortcuts
- nosmokewhereiam 4y ago
  First sergeant*
- Jaruzel 4y ago
  There were also no such thing as 'happy little accidents'. Each show was meticulously scripted, and the painting you see him paint is the 3rd iteration, with a previous version off camera as a reference. Even knowing this, he still brings the joy to me, every time I watch him.
  - StrictDabbler 4y ago
    That explains why his predecessor, William Alexander, made such a terrible painting in the video embedded in this article. Other Bill Alexander paintings you can find online are competent. Uninspired but competent. The one in the "The Magic of Oil Painting III" is wretched. Clearly the three drafts are an important aspect of the final Bob Ross process.
  - Beltalowda 4y ago
    For a short half-hour show you kind of need to do that if you want to get good results; not a lot of time to take a step back and look at things, and you also want to actually have a finished painting after 30 minutes (and not 24 or 35). The general message still holds I think: "you're painting for your own enjoyment, there is no 'good' or 'bad' and the only thing that matters is that you're having fun".
foldedcornice 4y ago
This reminds me of how Harvard's CS50 course by Professor David Malan, which is an introduction to programming and computer science. In one of the first lectures, Prof. Malan shows what happens when there is an error [0] when trying to run code in C. He jokes that he thinks there are "more errors than code [he] wrote," and goes through them with a positive attitude. Throughout the course, he is also aware and openly talks & jokes about the limitations of C as a programming language, then discusses workarounds. Any feelings of frustrations due to errors are then blunted quite a bit, because of prior exposure in the lectures. It's remarkable how the tone is quite similar. Perhaps Prof. Malan is the rough equivalent of Bob Ross for programming today. [0] https://youtu.be/URrzmoIyqLw?t=2074 https://youtu.be/URrzmoIyqLw?t=2074

striking 4y ago

Bob Ross was a drill instructor before he became the artist we all know and love. I think you'd have to have someone cut from similar cloth (maybe even tougher) for the programming version.

spywaregorilla 4y ago
A paired programmer whose partner ignores all keyboard shortcuts
nosmokewhereiam 4y ago
First sergeant*
Jaruzel 4y ago
There were also no such thing as 'happy little accidents'. Each show was meticulously scripted, and the painting you see him paint is the 3rd iteration, with a previous version off camera as a reference. Even knowing this, he still brings the joy to me, every time I watch him.
- StrictDabbler 4y ago
  That explains why his predecessor, William Alexander, made such a terrible painting in the video embedded in this article. Other Bill Alexander paintings you can find online are competent. Uninspired but competent. The one in the "The Magic of Oil Painting III" is wretched. Clearly the three drafts are an important aspect of the final Bob Ross process.
- Beltalowda 4y ago
  For a short half-hour show you kind of need to do that if you want to get good results; not a lot of time to take a step back and look at things, and you also want to actually have a finished painting after 30 minutes (and not 24 or 35). The general message still holds I think: "you're painting for your own enjoyment, there is no 'good' or 'bad' and the only thing that matters is that you're having fun".

foldedcornice 4y ago

This reminds me of how Harvard's CS50 course by Professor David Malan, which is an introduction to programming and computer science. In one of the first lectures, Prof. Malan shows what happens when there is an error [0] when trying to run code in C. He jokes that he thinks there are "more errors than code [he] wrote," and goes through them with a positive attitude. Throughout the course, he is also aware and openly talks & jokes about the limitations of C as a programming language, then discusses workarounds. Any feelings of frustrations due to errors are then blunted quite a bit, because of prior exposure in the lectures. It's remarkable how the tone is quite similar. Perhaps Prof. Malan is the rough equivalent of Bob Ross for programming today. [0] https://youtu.be/URrzmoIyqLw?t=2074 https://youtu.be/URrzmoIyqLw?t=2074