Awesome post about how Twitter analyzes data in real time.
Just did my head in trying to grok the ramifications of installing a JRubyOnRails app on a Windows Machine where SHIFT-JIS is the default encoding. This may not be a problem in general, but the app calls external executables regularly.
| — | Scott Berkun, How to call bullshit on a guru |
| — | Why the Lucky Stiff |
I was actually looking to connect Facebook and Github (Programmer Site). Couldn’t resist capturing the list of things people are trying to connect to facebook.
Recently I’ve been using a lot less twitter. Perhaps it’s just that I tend to be very verbose, but I struggle to put anything meaningful into 140 characters. Links to my blog posts are all well and good, but I’ve never been able to get on board with the torrent of retweets and mass link spamming.
Tumblr has an interface that allows me to post items that are longer than a tweet but lack the polish of what I’d expect to put in my Wordpress blog. It also allows sharing of links and other forms of media.
I’m not going to abandon twitter altogether, it’s still interesting to follow various different people, I just don’t feel that its as good a platform for interacting as its made out to be.
I know I’ve been both frustrated by this and guilty of this in the past. There is a high barrier to entry when contributing patches to a given piece of software.
I’m working on a prototype at the moment that requires me to insert data into offline tables (offline as far as Documentum is concerned). The examples that I’ve found all resort to specifying the exact structure of the table.
create table DMI_OBJECT_TYPEx (
R_OBJECT_ID VARCHAR2(16) NOT NULL,
I_TYPE NUMBER(10,0) NOT NULL,
I_PARTITION NUMBER(10,0) NULL);
The example above is smaller than most of the tables I have to create. The weakness with this is that you have to look up the table structure. The writers probably chose this method because the much simpler syntax shown below also brings any data that is in the table.
CREATE TABLE DMI_OBJECT_TYPEx AS SELECT * FROM DMI_OBJECT_TYPE;
My initial thought was why not copy the table and then just truncate it, but after a bit of searching I stumbled upon the solution. Essentially adding a WHERE clause to the end of the query that never evaluates to TRUE enables us to take the structure without the data.
CREATE TABLE DMI_OBJECT_TYPEx AS SELECT * FROM DMI_OBJECT_TYPE WHERE 1=2;
