Press "Enter" to skip to content

37 search results for “better writer”

efface[john-mccarthy;universe]

centaur 0
John McCarthy, creator of Lisp and one of the founders of the field of artificial intelligence, has died. He changed the world more than Steve Jobs ... but in a far subtler way, by laying the foundation for programs like Apple's Siri through his artificial intelligence work, or more broadly by laying the foundation for much of modern computing through innovations like the IF-THEN-ELSE formalism. It's important not to overstate the impact of great men like John and Steve; artificial intelligence pioneers like Marvin Minsky would have pushed us forward without John, and companies like Xerox and Microsoft would have pushed us forward without Steve. But we're certainly better off, and farther along, with their contributions. I have only three stories to tell about John McCarthy. The third story is that I last saw him at a conference at IBM, in a mobile scooter and not looking very well. Traveling backwards in time, the second story is that I spoke with one of his former graduate students, who saw a John McCarthy poster in my office, and told me John's illness had progressed to the point where he basically couldn't program any more and that he was feeling very sad about it. But what I want to remember is my first encounter with John ... it's been a decade and a half, so my memory's fuzzy, but I recall it was at AAAI-97 in Providence, Rhode Island. I'd arrived at the conference in a terrible snafu and had woken up a friend at 4 in the morning because I had no place to stay. I wandered the city looking for H.P. Lovecraft landmarks and had trouble finding them, though I did see a house some think inspired Dreams in the Witch House. But near the end, at a dinner for AI folks, I want to say at Waterplace Park but I could be misremembering, I bumped in to John McCarthy. He was holding court at the end of the table, and as the evening progressed I ended up following him and a few friends to a bar, where we hung out for an evening. And there, the grand old man of artificial intelligence, still at the height of his powers, regaled the wet-behind-the-ears graduate student from Atlanta with tales of his grand speculative ideas, beyond that of any science fiction writer, to accelerate galaxies to the speed of light to save shining stars from the heat death of the universe. We'll miss you, John. -Anthony Image stolen shamelessly from Zach Beane's blog. The title of this post is taken from the Lisp 1.5 Programmer's Manual, and is the original, pre-implementation Lisp M-expression notation for code to remove an item from a list.

Taking Criticism

centaur 0
At Comic-Con I catch up with a lot of old buddies, particularly one of the Edge who's solidered through many drafts of my early stories. He's got a script he's working on, and is making a lot of progress. In contrast we know a friend who's written a dozen scripts and is making no progress at all. Why? One of the conclusions we came to is that it's important to accept criticism of your work. Timely feedback is critical to improved performance - but you must respond to it. I think writers should put down all their dumb ideas and then convince everyone that they're brilliant. Your quirky ideas are your contribution - I mean, who'd think a story about a naked blue guy and a homeless vigilante investigating a murder would make one of the greatest comics of all time, but hey, that's Watchmen. But you've got to sell those ideas. "Ideas are a dime a dozen, but a great implementation is priceless." So if you show someone your story with a naked blue superhero and they don't buy it - you have to fix your story. That doesn't mean you take out the naked blue guy, even if your critics want you to. It's your story, and just because it doesn't work for someone they may not know the right way to fix it. It's up to you, the author, to figure out how to solve the problem. Readers give bad advice about how to fix stories because people are notoriously bad at introspection. If someone gets a funny bad feeling about the manuscript, they may latch on to the most salient unusual feature - not realizing it's the bad dialogue or structure which gives them indigestion. But authors are also notoriously bad at accepting criticism because they take the criticism as a personal attack. But if you get criticism on your story, you've done a great thing: you've produced a story that can be evaluated. Authors are also bad at accepting criticism because they have fragile little egos. But you can't afford to explain everything away. If people are complaining about your story, they did so for a reason. You need to figure out what that is - and it's your problem, not theirs. So, if you get criticism on your story you don't think is fair, you get one --- ONE --- chance to explain yourself. If your critic doesn't immediately get it, then --- even if you don't agree --- say, "Yes, thank you, I'll take it under advisement." Then put it in your trip computer and remember it for later. If others see the same thing, you have a problem. If you personally start to feel even slightly the same way, you have a BIG problem. But your biggest problem is not taking criticism at all. Me and my friend have encountered a fair number of leaders whose egos are so fragile they've insulated themselves from all criticism. You can still achieve some degree of success in an echo chamber if you're willing to critique yourself and you have high artistic standars. But usually it just makes for unnecessarily flawed stories, movies and products - and an unnecessary slide towards the dustbin when your ideas stop working. So if you're lucky enough to have someone who reads your pre-baked work and gives you feedback, listen carefully, explain at most once, and take the criticism gracefully. Your art will be the better for it in the long run. taking criticism graciously -the Centaur

Oh, the point … what Warren Ellis uses.

centaur 0
books, montalbano, reflected books, and gabby Oh, there was a reason I got on the Warren Ellis kick. He posted a note on what he uses to write. Maybe I'll me-too sometime and post a note on the tools I use, already having done the why and the how, but for now I wanted to focus on the following piece of wisdom from Warren Ellis which should be familiar to anyone who's ever worked on a Ph.D. thesis:
Back-ups. Oh, my god. Burning your stuff to CD or DVD is not good enough. Trust me on that. Things go wrong. Understand that Storage Will Always Fail. Always. I have a ruggedised, manly and capacious 32GB USB memory stick that can withstand fire, water, gunshots and the hairy arseteeth of Cthulhu itself — but my daughter decided she wanted to liberate one of my bags for her use, took the stick out of it and put it ’somewhere safe.’ It has never been seen again. Storage Will Always Fail. Dropbox is your friend. 2GB of storage for free, a frankly superb little piece of software that syncs your stuff off into the cloud as easily and simply and clearly as possible. I know writers, artists and tv producers who swear by Dropbox, and so do I. I have Dropbox on both computers. If you have a smart phone of the iOS or Android type, you can also have an Dropbox instance on your phone, a fact that’s saved my arse more than once. I also auto-sync Computer 1 hourly to Jungle Disk. Very cheap, very good. My media library lives on another storage service, Zumodrive, that lives both in the cloud and on my machine as a z:/ drive. (The Zumodrive application also lives on Computer 2.) Also, I do all mail through Gmail. Which means that a copy of every document I send off lives in the Gmail cloud. And every five minutes or so, a Western Digital 1TB MyBook copies everything on Computer 1’s desktop. Paranoid? Yes. Covered? Yes.
Got that, everyone? If you write, especially if you want to do it for a living, go do something like this. And for God's sake, please, keep a copy offsite. I know too many people who have lost their homes and their art or writing to fire. -the Centaur Pictured: Books, Montalbano, reflected books, and Gabby - a reminder to me that my library is a potential firetrap (God forbid!) and that I should be better at storing stuff offsite.

Guest Posting for Blogathon at A Novel Friend

centaur 0
My friend from the DragonWriters, Trisha Wooldridge, is participating in the Blogathon - sort of the 24 Hour Comic Day for bloggers - and I'm sponsoring one slot with a donation to Bay State Equine Rescue and a guest post on "Greed and Charity". A teaser:
At the beginnings of their careers, a lot of authors and other creative types are obsessed with making money off what they produce and are deathly afraid of people stealing it. I've seen people charging their friends for copies of short stories printed in magazines, putting their artwork on the web behind passwords or with huge watermarks, or pricing their software out of reach of the people who want to buy it. But this doesn't help them - in fact, it hurts. And I'm here to tell you to give stuff away for free.
If you want to read the whole post, please check it out at her blog, A Novel Friend - it should go up sometime this weekend. -the Centaur

15 Books

centaur 0
shoulder cat sees farther

Recently I got nailed with the following note on Facebook or Myspace or some other damn thing:
"Don't take too long to think about it. Fifteen books you've read that will always stick with you. First fifteen you can recall in no more than 15 minutes. Copy the instructions into your own note, and be sure to tag the person who tagged you."
Well, neo-Luddite that I am, I don't want to encourage this whole walled-garden social networking thing, so I'm not going to post a note there until I can effortlessly crosspost with my blog and everywhere else. But I can come up with 15 books:
  • Godel, Escher Bach: An Eternal Golden Braid by Douglas Hofstadter
    Convinced me to get into Artificial Intelligence. I've probably read it half a dozen times. Has a fantastic layered structure that Hofstadter uses to great effect.
  • The Society of Mind by Marvin Minsky
    Opened my mind to new ways of thinking about thinking and AI. Also read it several times. Has a fantastic one-chapter-per-page format that really works well to communicate complicated ideas very simply.
  • The Feynman Lectures on Physics by Feynman, Leighton and Sands
    Taught me more about physics than the half-dozen classes I took at Georgia Tech. I've read it now about four times, once on paper (trying to work out as many derivations as I could as I went) and three times on audiobook.
  • Programming Pearls by Jon Bentley
    Opened my mind to new ways about both thinking and programming. The chapter on estimation blew my mind.
  • Atlas Shrugged by Ayn Rand
    A true epic, though it's probably better to start with the Virtue of Selfishness if you want to understand her philosophy. Every time I think some of Atlas Shrugged's characters are ridiculous parodies, I meet someone like them in real life.
  • Decision at Doona by Anne McCaffrey
    I must have read this a dozen times as a child. I still remember two characters: a child who was so enamored of the catlike aliens he started wearing a tail, and a hard-nosed military type who refused to eat local food so he could not develop cravings for the foods of (or attachments to the cultures of) the worlds he visited.
  • The Belgariad by David Eddings
    A great fantasy epic, with all of the scale but none of the bad writing and pointless digressions of The Lord of the Rings. I've heard someone dismiss Eddings as "third carbon Tolkien" but, you know what? Get over yourselves. Tolkien wasn't the first person to write in the genre, and he won't be the last.
  • The Hobbit by J.R.R. Tolkien
    All of the adventure of the Lord of the Rings, but none of its flaws. The long journey through the great dark forest and the Battle of Five Armies still stick in my mind. I like this the best out of what Tolkien I've read (which includes The Hobbit, the Lord of the Rings, and the Silmarillion, and some other darn thing I can't remember).
  • The Dragon Circle by Stephen Krensky
    Loved it as a child. Still have a stuffed dragon named "Shortflight" after this book.
  • Elfquest by Wendy and Richard Pini
    Another true epic, this time a graphic novel. Resonates with me in a way that few other fantasy epics do. I have the first 20-issue series in a massive hardbound volume which is now apparently worth a shitload of money. Out of my cold dead fingers, pry it will you.
  • Paradigms of Artificial Intelligence Programming: Case Studies in Common Lisp by Peter Norvig
    Yes, your programming can kick ass. Let Peter show you how.
  • Reason in Human Affairs by Herbert Simon
    Helped me understand the powers and the limits of human reason, and why we need emotion to survive in this complicated world.
  • The Seven Habits of Highly Effective People by Stephen Covey
    More than anything, I appreciate this book for a few key vignettes that made me realize how important it was to understand other people and where they are coming from, and not to impose my own preconceptions upon them.
  • The Art of Fiction: A Guide for Writers and Readers by Ayn Rand
    Straight talk about fiction from one of its most effective writers. You don't have to agree with Ayn Rand's personal philosophy or even like her fiction books to learn from this book; half her examples are drawn from authors she personally doesn't agree with.
  • In the Arena by Richard Nixon
    Straight talk about surviving in politics from one of its most flawed yet effective masters. A glimpse into the workings of a brilliant mind, broken down into different sections on different aspects of life. Don't bother reading this if you feel you owe a debt to your personal political leanings to say something nasty about Richard Nixon in every sentence in which you mention him simply because Nixon did some bad things. (Note: I think that Nixon's alleged crimes are the worst of any President, because they attacked his political opponents, undermining our democracy. However, his political philosophy, once divorced from his personal paranoia, is something very important people need to understand).
What did I forget? The Bible, The Chronicles of Narnia by C.S. Lewis, Das Energi by Paul Wilson, The Celestine Prophecies by James Redfield, Jonathan Livingston Seagull by Richard Bach, One Two Three Infinity by George Gamow, The Screwtape Letters by C.S. Lewis, Unfinished Synthesis by Niles Eldredge, Neutron Star by Larry Niven, The Gods Themselves by Isaac Asimov, the collected works of Martin Gardner, Usagi Yojimbo by Stan Sakai, Albedo Anthropomorphics by Steven Galacci, and of course, Van Nostrand's Scientific Encyclopedia, the Volume Library, and before that, back in the dawn of time, the World Book Encyclopedia. Read into that list what you will.

Blogosphere, consider yourselves tagged - your turn.

-the Centaur

Renewing the Library

centaur 1

Recently I started to notice that the design of the Library is getting long in the tooth.  One friend who was a web designer commented that it looked very "old Internet".  I've watched another friend innovate on his blog design while mine was staying still.  Work on my wife's web site made me revisit some of my choices, adding a description and picture but making few other changes.  I know the site needs a redesign because I have a lot more material coming out soon, but the final trigger was when I couldn't attend a talk and looked up one of the authors to learn more about their work - I think it was Oren Etzioni - and I was struck by his straightforward site design which enabled me to quickly find out what he was working on.

SO, I'm redesigning the Library.

I'm an artist in addition to an author and researcher, so simply gutting the site and making it simpler wasn't my goal: I have specific ideas about what I want the site to look like, and I started designing a new one.  Partway through that redesign, I noticed that I was doing a fair amount of research work - examining other blogs that I admired, investigating blog widgets, investigating CSS and HTML advances, researching color theory and design principles - but not blogging any of it.  In fact, come to think of it, typically when people redesign their sites they put all their work under a bushel, trying to hide their planned change until the last possible moment, possibly exposing it to a few trusted users in beta or with an alternate link prior to springing it on the world as if freshly formed and fully new.

Well, phooey on that.  The thought process that a web designer goes through producing a web site is interesting (well, to other web site designers, anyway) and provides a valuable resource to other designers doing their work.  I wished that other people had blogged the process that they went through and the alternatives they explored, as it would help me make my own choices - but you know what?  I don't control other people.  I only control me.  And if someone else hasn't filled the gap, then it's my own responsibility to come up with something to meet my needs. 

SO, I'm going to blog the redesign of my blog.  How "meta".

There's far too much to put into a single blog entry, so I'll start off going over the thought process that led to the design in more detail, then explain my strategy.  The first thing that I did was look at other web sites that I admire.  Earlier when working on my wife's web site I found a number of beautiful looking blogs, but when I started the redesign, I started my search over, focusing on sites of artificial intelligence researchers, bloggers, writers, and artists, trying to find ones I instinctively admired with interesting ideas, features or appearances that I could steal.  Some of these included:

  • Oren Etzioni's Home Page: Quickly Present What You Are Doing
    An "old school" (not that there's anything wrong with that) web site from an academic researcher, it has an "old style nav bar" up top that quickly tells you how to find his publications.  Below that is text which points you to his research projects and most cited publications.   From this I gleaned:
    • Organize your work into logical areas
    • Make navigation between areas easy
    • Put things people want up up front
  • Rough Type by Nicholas Carr: Put Your Content Front and Center
    Featuring a straightforward design that gets you straight to his content, Rough Type also has an author blurb and a pointer to his most famous article, "Is Google Making Us Stupid?" and his book "The Big Switch" The key points I gleaned from the site:
    • Get your content out front and center
    • Tell people who you are
    • Point them to your best work
  • Vast and Infinite by Gordon Shippey: Show the Author, Try Fun Features
    Written by an old buddy from Georgia Tech, Vast and Infinite isn't that different from Rough Type.  However, he's constantly innovating, adding a site bio and author picture, tweaking his banner, adding shared items and flickr gadgets and more, whereas my blog tends to stand still.  The lessons from this:
    • Show people your picture
    • Keep your content front and center (sound familiar?)
    • Trying out new technologies generates interest in the site
  • Home Page of Jim Davies: Show the Author, Organize Your Site Logically
    Jim Davies is another academic researcher, with a much more modern site.  Like Oren Etzioni, he has a navbar, but also a large picture, a more detailed description, and links to his art, store and blog.  Unlike Oren, each area of the site seems a little more organized, without the duplicated links to publications and the odd inclusion of news articles in his personal page.  Jim takes this further by having extra blogs just for rants and links.  My takehomes were:
    • An academic site can have a modern design
    • Showing people your picture creates interest
    • Don't be afraid to segregate content into areas
  • Marvin Minsky and John McCarthy: Tell People About Your Work, and Share It
    Two of the greats in artificial intelligence have interesting sites filled with lots of content.  Both start with a description of them and their work and then continue with many, many links to their most prominent work.  Minsky puts up chapters of his most recent book; McCarthy includes a lot of narrative that gives context.  What I like:
    • Tell people what your site is about using narrative
    • Put work you are interested in front and center
    • Fill your site with lots of content
  • Greg Egan's Home Page: Fill Your Site With Lots of Content, and Share Your Research
    Greg Egan is an author I admire primarily for his novel Permutation City and his short story Dark Integers, though I have more of his books in the queue.  His site's layout is a little harder to read than some of the others, but it is filled with pointers to all of his work, to the research that he did to create the work, and applets and essays related to his work.  The takehome from this firehose is:
    • Fill your site with lots of content
    • Share the research you did on how you p roduced your work
    • Don't be afraid to promote your work by showing it to people

There was one more site that kicked this all off, which I will hold in my pocket for a minute while I talk about opinions.

Unlike Jacob Nielsen, I don't have research backing up these conclusions: they're really just guesses about what makes these site work, or, worse, just my opinions about what it is that that I like about these sites.  What's dangerous about opinions is that recent scientific work seems to indicate that they're often post-hoc explanations of our instinctive reactions, and they're often wrong.  So, to combat this tendency, I looked at other resources that specialize in information about good design of web sites to try to get information about what I "should" do.  I don't pretend I've absorbed all the information in these sites, but am simply including them to show you the kinds of things that I looked at:

  • Jacob Nielsen's UseIt.com: Make your site fast, simple and standards based
    Jacob Nielsen's site on web site usability is so simple it hurts my eyes.  I don't like to actually look at it, but I do like the ideas.  He's got a breakdown of recent news on the right and fixed web site content on the left; the idea of the breakdown is good but seems opposed to my goal to work with Western left-to-right reading.  Jacob points out that he uses no graphics because he's not a graphic designer, and that's fair; but since his site is unpleasant for me to read I only loosely follow his recommendations.  But one cool thing about his site: if I resize the browser his content stays divided more or less the way he's put it because the structure is so simple and well designed.
  • But What Are Standards?  W3C and Webmonkey
    The W3C is the official source of standards for the web like HTML and CSS, but I've always found their standards hard to read (and I've read many, many of them over the years).  The new site redesign they're testing seems to make it easier to navigate to find things like the CSS Standard, but it is still hard to read and lacking the practical, let's get started advice that I want.  Back in the early days of the web, I used Webmonkey as a source of good tutorials, but the site seems crufty and broken - trying to narrow in on the CSS tutorials got me nothing.  I have a number of offline books, however, and am a whiz at reverse-engineering web pages, so when I get to the CSS articles I will detail what I learn and what sources I use.
  • CSS in Practice: FaceFirst.us and CSS Zen Garden
    I know the designer of FaceFirst.us, a social networking site, and in exchange for me beta testing his site he turned around and gave me a tutorial on how he uses CSS in his process to ease his site design.  In short, like Nielsen, he recommends separating the "bones" of the site from the content using CSS id's and classes.  One example he showed me was the CSS Zen Garden, which has fixed content that is modified radically just by stylesheets.
  • But What Did Your Thesis Advisors Do? Ashwin Ram and Janet Kolodner
    I also dug into what Ashwin Ram, my thesis advisor, and Janet Kolodner, a member of my thesis committee and my original advisor, did with their web pages.  Both Ashwin and Janet have profile pages back at the College of Computing, but they also have richer pages elsewhere with more detailed content.  I have no intention of slavishly copying what my thesis advisors are doing, but as far as the research part of my web is concerned they're similar people solving similar problems whose solutions are worth looking at and adapting for my own use - why, yes, my Ph.D. was in the case-based reasoning tradition, why do you ask?  On that note, it occurs to me to look at other colleagues' web sites, like Michael Cox's site.

Standards, shmandards, cool sites and web lights - all well and good.  My brain exploded, however, when I saw Warren Ellis's web site (billed as a blog for mature adults, so it's occasionally NSFW - be warned).  In my mind, Warren's site had a number of great features:

  • Show the Author's Name:
    The author's name is hugely printed across the top - so you immediately know who this is, as opposed to say my dumb blog where my name is printed in 2 point type.  And Warren's domain name is also his own name plus dot com, so that he can actually show his name and site name in the same logo.
  • Keep the Text to the Left:
    The text of all the articles is corraled to the left margin so they can be PRINTED, aligned to the top of the page so it dives into the header and is immediately visible.  Almost as if Warren's site was designed knowing that the majority of the people who read the English language read it from left to right, therefore the text should appear where their eyes go.  This pattern, plus the pattern of the rest of his design, is consistent with putting the good stuff in the F-shaped heat map that typical users eyes take when scanning your page.
  • Use the Middle of the Page:
    There is a bar of links in the MIDDLE of his page, immediately to the right of the articles, which puts it close to the golden ratio of the horizontal space of his site design (as viewed on my monitor).  This "linkbar", held in place by CSS wizardry and a black magic compact with the Old Ones,  contains permanent site features that most need to be linked - message board, mailing list, comics, his novel, his agents, and his bio inline.  Think of it as sexier version of Jacob Nielsen's "Permanent Content" box.
  • Put Sparkly Things to the Far Right:
    Beyond the linkbar are all the cool fun site features like a search bar, podcasts, images and other nonsense, which are fun to look at but less important.  On my site, some of these are on the right, or even at the very bottom of the page; on other people's sites they appear on the left, distracting Western readers from the article and possibly shoving the right ends of the articles over the printable width of the page.  Ellis' contract with Cthulhu and the hellish powers of the W3C enable him to safely corral these fun elements to the right where they belong.

The linkbar was the most mindblowing thing.  It eats into the banner.  It's readily visible.  It leaves the text on the left, but it's close enough to be visible on most monitors.  The whole site is 997 pixels wide, so it will fit on a typical 2009 web screen, but if your screen is smaller, first you lose the fun sidebar, then the important linkbar, and only then do you lose the text.  Even better, since the li nkbar CSSes its way into the banner, the size of the site is controlled by the header image so it won't get wider.  So your Nielsen-style variable content is always visible on the left, and your important fixed content is always on the right, and God willing it will never get hosed by someone resizing their window.  Once I saw that, I decided I'd done enough work researching, and it was time to start redesigning.

SO my first step is to unashamedly steal Warren Ellis's linkbar.

Immediately I sent out my secret agents out to download his HTML and CSS and transport it to my secret lab so I can take it apart piece by piece until it has no secrets left.  Of course, some of Warren Ellis' choices won't work for me, so I will have to do a lot to adapt the ideas he and his team used in his site design.  And simply imitating the form of Warren's site won't be successful, any more than just making a movie just like Star Wars called Sky Battles would be immediately successful.  (Battlestar Galactica fans, take note: while I loved the show, I think it's fair to say that it took the reinvention of the show to really produce a success, which was based on making the show interesting in its own right and not copying Star Wars).

The outer form of his site is the product of his inner success - he is a popular, prolific author with a message board, mailing list and weekly online comic he uses to promote his other writing and books, which makes the prominent placement of the message board agents and books highly important in the linkbar.  Starting a message board and getting an agent won't help me.  I, in contrast, am a jack of all trades - developer, researcher, writer, artist - using this blog as a tool to force me to stop being a perfectionist, complete my work, and put it out in front of people.  So my goal is to make sure this website displays my content, prominently surfaces the areas of interest I work in, and has a few flashy features to attract attention to individual items of more permanent interest.

In upcoming articles I will detail my original constraints for the blog version of Library of Dresan and why those constraints failed as the site evolved over time, my goals for the new site design, what I think I understand about how wide to make your web pages and where to put your content (and where I got those crazy ideas) my move to the use of CSS and my attempts to make the site work well on screen, on printers and phones, my attempts to better exploit Blogger, Flickr and other web gadgets, and the work that I'm doing investigating color theory and generating the new art assets that will make up the site.

Hopefully you'll enjoy the process, and when it's done, that you'll enjoy the site more.

-the Centaur

People who can think

centaur 2
I was going to start this article by tossing up a shout out to taidoblog, andy fossett's in-depth analysis of taido, but it then occurred to me that taidoblog is only the most recent of a whole category of blogs and articles that I've only recently started to notice, and even more recently started to truly admire: people who can actually think.

The object of inquiry of andy fossett's taidoblog is taido, his (and my) chosen martial art. This alone would capture my interest, but what's always struck me is not just andy's subject, but his method. He puts deep thought into his chosen interest: he maps out the landscape of practice, critically evaluates existing opinions, formulates radical new ideas, and puts them all to the test. He's not afraid to boldly throw out bad traditions OR to slavishly follow traditions that work, at least until he has learned all he can and/or developed something better.

Big Jimmy Style is the platform of Jim Davies, a similar investigator whose chosen interest is research and science. He and I don't see eye to eye in areas like healthy eating, environmentalism and voting, but I don't personally know anyone who puts deeper thought into artificial intelligence and cognitive science research - what it is, why it's important, how it should be done, and what it's goals are. Jim regularly holds my feet to the fire in our private correspondence, and in his blog he continues the tradition of calling bullshit when he sees it and constructing frameworks that help him tackle hard problems.

The strength of Gordon Shippey's Vast and Infinite comes from his clear personal philosophy, strong scientific training and strength of character. While at this instant his blog is suffering from Movable Type's "I'm busy this month" whitescreen, Vast and Infinite is the sounding board for G'hrdun's ongoing exploration of what works in the work place, a topic of deep personal interest that he explores from a clear objectivist ethical perspective informed by his psychological knowledge, scientific training and personal experience. If you watch long enough you'll also see scientific/libertarian analysis of modern political and scientific developments.

Scott Cole's The Visual Writer has always been overwhelming to me: there are more ideas bouncing around on his site than I've ever been able to mine. For a long time I read his articles on the theory of writing stories but his philosophical articles are just as interesting. While there are some areas he and I might disagree on particular points, on the majority of writing topics he's explored more issues that I was even aware existed.

And then of course, there's Richard Feynman's blog The Smartest Man In the World. Actually, it's not, and he disliked that title, but we can only wish Feynman hadn't died before blogs came to being. In lieu of that, I can recommend The Pleasure of Finding Things Out, which, despite some people's complaints that it rehashes his other books, does a good job of putting in one place Feynman's essential thoughts about the scientific method, the importance of integrity, the difficulty of not fooling yourself.

The point of me mentioning all these people is that they're good examples of people who are thinking. They aren't just interested in things; they're actually cataloguing what they see, organizing it, judging it, evaluating it; deciding what they want to do with it and formulating opinions on it. In andy's writings in particular he goes further: he's not willing to settle just for opinions, but must go test it out to find out whether he's are full of shit or not. And at the highest level, Feynman integrates challenging his own ideas and reporting the results of his challenges into the very core of the his being - because he who sees the deepest is the man who stops to clean his lens.

That's what I want to be when I grow up.

So go check 'em out.
Because everything is interesting if you dig deeply enough.
-the Centaur

Can't find what you're looking for? Try refining your search: