Especially the last two items. One being the list in the wrap-up: good advice and the other being the one about Leo—the man who single handily derailed Perl 6. One guy is pretty-much the reason we all laugh at Perl now. I watched it happen: he refused to build a MVP, he kept throwing away working code to re-architect it bigger and more convoluted ways. There's a big lesson there for every start-up.
If you do take a look be sure to read Dan's well-written blogs about language design and implementation, especially those tagged "What The Heck Is:"
I've always held a lot of respect and sadness for Dan Sugalski. The guy was not only a brilliant architect and hacker but he had the knack for always being right. It's sad that he didn't stand his ground and was sadly pushed out of the project. I get the impression he had some tough times after that.
If any of you guys see he CV come up you shouldn't think twice in giving him a senior role.
I remember reading Dan's blog religiously when I was a college student interested in language design and compiler implementation. That's where I learned about CPS and register VMs.
Anyway, I've seen him recently pop up in a professional context. I can't find anything on the Internet about where he's working now, so on the off chance he's deliberately protecting his privacy, I won't say where. But knowing what he's working on, I think he's doing fine.
Cool, thanks for those links. I'm going to give them a read.
After a quick read of a few articles....
Hmmm. This is good stuff. I want to sit down with this and read it on my Kindle. Maybe I should ping him and see if he wants to turn this in to a Leanpub book...
http://www.sidhe.org/~dan/blog/
Of particular relevance here is his Parrot Retrospective:
http://www.sidhe.org/~dan/blog/archives/000435.html
Especially the last two items. One being the list in the wrap-up: good advice and the other being the one about Leo—the man who single handily derailed Perl 6. One guy is pretty-much the reason we all laugh at Perl now. I watched it happen: he refused to build a MVP, he kept throwing away working code to re-architect it bigger and more convoluted ways. There's a big lesson there for every start-up.
If you do take a look be sure to read Dan's well-written blogs about language design and implementation, especially those tagged "What The Heck Is:"
http://www.sidhe.org/~dan/blog/archives/cat_what_the_heck_is...
I've always held a lot of respect and sadness for Dan Sugalski. The guy was not only a brilliant architect and hacker but he had the knack for always being right. It's sad that he didn't stand his ground and was sadly pushed out of the project. I get the impression he had some tough times after that.
If any of you guys see he CV come up you shouldn't think twice in giving him a senior role.