Like jchw said, this was a single-day project (although I did the writeup for it the next day).
I went from 0-prototype in one sitting; I think that was around four or five hours of work? Then I went home, had dinner, and spent maybe three hours optimizing and cleaning it up.
edit: I should say, i have done a lot of dumb things like this and I'm pretty sure it would have been at least a week of work for me 2 years ago. "making the computer do dumb stuff" is a skill like any other!
Doing that in a single day is impressive. Took me two days to do my much simpler version that just prints it using Unicode symbols for legacy computing.
> I didn’t have the time to find a good general-purpose algorithm: I was working on this the night before weekly presentations at the Recurse Center and I wanted to present it the next day!
Hi! I'm the author.
Like jchw said, this was a single-day project (although I did the writeup for it the next day).
I went from 0-prototype in one sitting; I think that was around four or five hours of work? Then I went home, had dinner, and spent maybe three hours optimizing and cleaning it up.
edit: I should say, i have done a lot of dumb things like this and I'm pretty sure it would have been at least a week of work for me 2 years ago. "making the computer do dumb stuff" is a skill like any other!
Thanks for taking the time to respond, pretty impressive stuff!
Doing that in a single day is impressive. Took me two days to do my much simpler version that just prints it using Unicode symbols for legacy computing.
From the article:
> I didn’t have the time to find a good general-purpose algorithm: I was working on this the night before weekly presentations at the Recurse Center and I wanted to present it the next day!
...
> I built this in a single day
No estimate of hours, though.
My browser was apparently bugged, and it didn't show the article the first time... I see it now and am going through it. Thanks for mentioning! :)