I wrote this article with one mouse click
coding.pressbin.com
coding.pressbin.com
1) Identify data source
2) Extract value from data source
3) Spit out templated content pieces extracted from data source
4) Farm out templated articles to freelancers for thickening up, Demand Media style
My client from this summer who paid me to do it for the average value of particular college degrees is launching sometime in the next week or so. I'll happily play show-and-tell with the non-proprietary parts if folks want, after it launches.
Unfortunately, I should have spent more time "thickening them up" -- after the first half dozen or so, AC began rejecting them for being too similar to each other.
But yeah, the potential is definitely there.
And $3 per article can also add up, if you have a scalable solution.
I'd love to hear more about this, thank you.
This is a weird example, but look at Groupon. One of the main reasons it's so big is the custom, humorous descriptions that go along with each item.
If newspapers want to survive, they shouldn't be automating their content- it just makes it more generic and forgettable. Nobody wants to read an article that a computer wrote.
Personally, I never read those. I skim the headline, and look at the deal details if the topic interests me and is a really good deal.
There's a difference in content though; with deals I just want the hard facts. With many news articles, I want some well-written copy to add context to otherwise meaningless/bland data.
For the Powerball results, the sentence format is a bit more engaging and I can skim it as fast as I would skim a table. If nothing else, it makes me feel like the publisher cares more about the reader.
Groupon feels that this is valuable enough that they hired 100 new people for their editorial department just in November*.
Some of the best hackers and coders I've met were the laziest folks around; but they'd spend hours working to automate a 1-minute monotonous task.
I'd gotten a new manager in the old department, and I don't think I'd had enough time to get over an initial bad impression. I was the night shift guy, on a help desk, and the call volume was generally low. To help better justify the use of my time, I was tasked with some additional duties, like processing account delete requests and other tedium.
My manager at the time found fault with the fact that I had written a series of scripts to completely automate the additional tasks I'd been assigned, and considered me lazy.
In the interview, I was asked the question "How do you respond to the accusation that you sometimes cut corners?"
My answer was something like "I think cutting corners is a good thing. If there's not a requirement for square corners, and the rounded corners don't impact the quality or integrity of the work being performed, and if the corners aren't irreparably damaged in the process, I think that taking the more direct path of least resistance is not a bad thing."
I got the job, and I was later told that the manager was very impressed with the answer.
Uhhh, that was a roundabout way of saying "I agree."
Certainly holds true here, but I think the real value from things like these is beating the task.
I've been keeping a running count of time spent on various activities this month, for giggles. Total support time for BCC in the last two weeks: eight minutes. The machine has been humming so efficiently I burned some time yesterday just to check that the whole thing hadn't been hit with a meteor or something.
For instance, I suspect that part of the inspiration for Appointment Reminder came from Patrick's own realization of how valuable the automation of small tasks can be (chasing down missed appointments, in this case).
---
To go off on another tangent, this is akin to eliminating technical debt from your workflow. By taking time to "refactor" certain tasks by doing them in a more efficient way, you get a net savings going forward. You can increase your ability to take on new tasks by increasing the efficiency of existing ones.
In keeping with the refactoring theme, if you have tasks that don't scale well, you may need to spend more time on them in a crisis. For example, in the event of a site outage you might suddenly have a deluge of support emails. Having support tickets be automatically created would save you n*60 seconds of copy/pasting.
This is already done in the sports area, which is significantly more complicated: http://mediadecoder.blogs.nytimes.com/2009/10/19/the-robots-...
EDIT: Okay, I'll just repost a comment from about a month ago here, that was upvoted instead of downvoted and yet made exactly the same point:
This is a threaded comment system. We can have as many discussions about something (post or other comment) as we want: go off on wild tangents, point out the spelling, have a pun thread, mention patterns of blogging/commenting the parent fits into, reply to the author on a separate subject, share anecdotes related to the subject of the post, and actually talk about the content of a post or comment, all at the same time, without breaking anything. That's what's so neat about threaded discussion: it doesn't require the "comparative notability" that a linear conversation needs in order to function.
In this case, we can have a discussion about combining hacking skills with a completely separate career, and then have a tangential discussion about using DSLs to generate text, with neither conversation interfering with the other. No one has to be "missing the point," and in fact jerf could be contributing elsewhere in the discussion alongside his creation of this tangent.
I never said "this guy should have written a DSL instead", which I didn't say because it would be an asshole thing to say. I said that this task screams for a DSL, and that's only more true if this guy isn't a programmer.
Old: 2010Lottery Results
New: 2010 Lottery ResultsThen, you can scrape or find large databases of consistent information and deploy very large sites.
The trouble is getting google to fully index these sites. It requires a good amount of link building both to the madlib pages and the home page to get enough juice for the crawlers to spend time on the site and get things indexed.
They can be very useful sites to build for a variety of reasons, and can actually add some value depending on the data you're publishing
For workflow tasks, Automator.app on OSX is pretty great, even for non-programmers. There's probably something analogous on windows/other OSes.
For document generation... that seems like a fun weekend hack. I'm imagining some kind of more configurable madlibs-style app.
http://www.horniman.info/DOCUMNTS/HOWTO.HTM
Scroll down to section 6, "Webpages" for explanation of this topic.
The generated website is also live online at
so the generated HTML can be easily inspected.