Older blog entries for davidw (starting at number 419)

Why I prefer text to video

Videos are becoming more and more common on the internet, and for some things, like mentos and diet pepsi, they're hard to beat.  For things I'm seriously interested in, though, I prefer text.  Here's why:

  • Text goes at my speed.  I read quickly, and certainly faster than people can talk.  If I want to slow down and reread something, I can do that too.
  • Video, outside of actual video chats, is not interactive, so I don't get the benefits of being there, being able to interrupt, ask questions, and so on, that can make the 'in person' experience superior to just reading about something.
  • Text is searchable and indexable.  I can search within a page, and it's also more likely to be visible to search engines.
  • Text is easy to scan and glance at.
  • Given the ease of scanning text, it's also easier to filter: "is this something I want to invest more time in reading?".  In the time many videos use for people to simply introduce themselves, I could have already got an idea of a document is worth further perusal.
  • Text is easy to manipulate; cutting, pasting, quoting, etc... are all easy.
  • I don't have to put on headphones to read text if my wife is sleeping and I'm working late.
  • Text has good, and highly visible conventions (various headings and subheadings) for indicating subsections of a large document and what they may be about.

Syndicated 2011-07-25 21:07:42 (Updated 2011-07-25 21:16:57) from David's Computer Stuff Journal

The Long Tail of the Clued In

Nearly three years ago, I wrote an article comparing Linode and Slicehost  having been first a Slicehost customer and then switched to Linode.  I would have been happy to stay with Slicehost, because they seemed like good people, but the 64bit vs 32bit issue, especially, tilted things very far in Linode's favor.  I thought the results were damning, and many people agreed with me, judging by the number of people clicking through the affiliate link I added later.   Based on some comments I read from this guy, who did a similar comparison, at http://journal.uggedal.com/vps-performance-comparison/ I think that between the two of us we drove a lot of customers towards Linode.


Those articles have been out there for years, and are very easy to find with Google.  Curious to monitor the situation, a while ago, I set up a Twitter search feed for "Slicehost vs Linode" to see if people were talking about my article, and what other people were suggesting.  Overwhelmingly, those suggestions have been for Linode too.

Recently, Rackspace, who acquired Slicehost several years ago, announced they would be shutting down Slicehost and transitioning their customers to Rackspace: http://www.readwriteweb.com/cloud/2011/05/rackspace-shutting-down-sliceh.php

And yet - people are still asking about Slicehost vs Linode on Twitter!

This is a useful reminder to me of how much, in our profession (and likely others, but I'm going with what I know) there is a core of the very clued in, who follow all the latest trends (and, negatively, fads too, at times), and are highly informed about everything that's going on.  Outside that, though, there is a pretty  long tail of people who are much less informed.  That's not a criticism of those people, either; perhaps they follow the latest developments in gold mining technology or something else that's much more relevant to their lives than "computer stuff".  It's something to keep in mind when marketing things - you think that everyone must have got the message, that no one could possibly not know what's going on, but it's actually quite difficult to really, reliably communicate something to a broad range of people.

Syndicated 2011-07-14 08:48:17 (Updated 2011-07-14 09:20:18) from David's Computer Stuff Journal

Nokia -> Samsung

While I'm keenly interested in where mobile phone technology is going, I've never been much for living on the cutting edge of new and expensive phones.  I originally wrote Hecl for the humble Nokia 3100, and got a Nokia 6210 classic a few years ago.

For the first time in... probably something like 10 years, I got something that wasn't a Nokia: a new Samsung phone with Android.  I find it interesting because my own, small purchase appears to very closely mirror a broader trend in the market.

Since more or less the day it came out, Android jumped out at me as the place to be for an open source guy like me, and indeed, I'm quite happy with the phone, even though it's towards the low end of the Android range.  It does everything I need though - music, GPS, photos, email, Kindle, etc... etc....

To tell the truth, even though it's a cheaper phone (around 140 euros) than the Nokia, it does far more.  To some degree, that's of course to be expected, because the Nokia is at this point something like 3 years old, but going from the traditional rocker switch to a touch screen is really a night-and-day difference.  Many of you are probably saying "duh" at me and wondering what sort of luddite I am, but like I said, I started hacking on Android when it came out, but it took me a while to finally get one.

For a few things like making calls, the Nokia experience is in some ways still superior.  It's got 'call' buttons that you can hit and be talking to people in short order, but for most of the rest of the applications and software are just night and day better on the Android phone.  Gmail and Maps both strike me as something I could use more readily, rather than the hacky, slow Gmail that ships for Symbian.

And of course, with a slightly bigger screen, the web is also a bit better.

More than anything, it feels a lot more like a 'system' rather than a very, very solid core phone/sms system with some other junk bolted on. 

Syndicated 2011-06-24 13:17:18 (Updated 2011-06-24 13:50:38) from David's Computer Stuff Journal

Summary: Built To Sell - Creating A Business That Can Thrive Without You

Many small business owners start a business with the idea of greater freedom in mind, yet end up chaining themselves to something that takes even more dedication than a regular job.

This book discusses the dos and don'ts that business owners need to be conscious of in order to create a business that is independent of its owner(s) in order to be able to sell it.  It does so in an easy to read format that's a bit of a gimmick - a fictional story illustrating the authors points.  Like most business books, the core idea isn't that hard to explain.  the book even includes a handy summary of the main points, which I'll paraphrase here:

  1. Focus on one thing you can do really well; even a service business can be 'productized' by creating a standard service that is the focus of the business.
  2. If your business revolves around one or two key clients, the risk inherent in that approach will lower the value or scare of potential buyers completely.
  3. Put a process in place, from sales through production.
  4. Don't "be" your company.  If the company is all about you, what's a potential buyer really getting if you sell it and leave?
  5. By focusing on products, you can charge up front rather than having poor cash flow.  If you pay people to work on a project for 3 months, and don't get paid for another month, you are, by the end, out 4 months salary while waiting for the payment.
  6. Say no to projects outside the scope of your business.  Only by focusing narrowly can you really excel at what you do.
  7. Spend time doing some research and calculations to estimate your potential market size; buyers will want to know this.
  8. If you have a business that has sales people, hire at least two so that they'll compete with one another.
  9. You want people who are good at selling products, not services; the latter will want to tweak your offering for each and every client, rather than selling it as-is and trying to find how it can meet the customer's needs that way, which is the best strategy for a product.
  10. If you were previously running a more 'generic' services company, and you switch to a more productized approach, be prepared to take a hit the year when you switch.
  11. Potential acquirers will want to see at least a couple of years of steady growth with the new model after making the switch.
  12. If you grow, you'll need a management team that can work without you.  Put an incentive system into place to reward their loyalty and results.
  13. When looking for an adviser to sell your company, aim for one where you will not be the largest or smallest client.
  14. If your adviser really only has one company in mind to sell yours to, they may be trying to sell you off cheap as a favor.
  15. Consider how much you could grow with the resources of a buyer.  Think big, and show them what kind of growth could happen with the right backing.
  16. Think and speak like a product business with 'customers' rather than 'clients'.
  17. Stock options are more complex than simpler options like bonuses that are paid out over a period of time, in terms of ways to give people an incentive to stay.

All in all, it was an enjoyable read, with solid points.  Even if you have no intention of selling your business, thinking of the business itself as a sort of "product" that is not dependent on you to work correctly is a sensible way to go about creating and growing a business.

He's certainly not, nor claims to be the first one to discuss this idea, and indeed references the well known E-Myth Revisited which focuses less on selling a business, and more on how to go about extricating you and your skills from the business.

Syndicated 2011-05-23 14:09:40 (Updated 2011-05-23 16:07:15) from David's Computer Stuff Journal

Welton's Law of Trite Business Advice

 

“For each and every bit of trite business advice, there is an equal and opposite bit of trite business advice”

"Fail fast" vs "be persistent"

"The first person to mention a number in a negotiation loses" vs "by saying a number, you frame the negotiations"

"Ideas don't matter" vs "the Number One startup killer ... making a product for which there is no interesting market"

"Do something you're passionate about" vs "where there's muck, there's brass"

"Business plans are a waste of time" vs "failure to plan is planning to fail"

There's some valuable lesson behind all of these; I'm not saying these are bad advice.  What I'm saying is that if it were so easy, more people would be doing it successfully.  In reality, it's very difficult.

What are some of your favorite equal and opposite bits of business advice?

Syndicated 2011-04-30 11:44:58 (Updated 2011-05-10 09:42:18) from David's Computer Stuff Journal

13 Apr 2011 (updated 13 Apr 2011 at 18:06 UTC) »

For sale: LangPop.com

I've been running at capacity for a while now, and something went "snap" recently, so I decided to take a few days off to clear my head a bit.  One of the things that came to mind is that I have too many 'side project' things.

I have had lots of fun (and a few flame wars) over the years with LangPop.com but I decided that it's another thing that should probably go, in order to simplify my life some.

It's a fairly popular site amongst programmers, as I think it's the best of the bunch in terms of guaging an admittedly tricky subject like language popularity, but there's lots of room to add to it.  I've got various ideas for whoever ends up buying it!

About money: it doesn't earn a lot.  Programmers, I think, are fairly blind to advertisements.  In the right hands I think it could do better, but most likely, it would work best as a bit of branding/advertising for your own business, much as TIOBE's index has spread their name far and wide.

For the time being, I'll accept private bids, and depending on how well that does or doesn't go, may consider using something like Flippa.com later.  Write me at davidw@dedasys.com if you're interested.  I'd be happy to share some numbers and information with you.  Perhaps I'll update this posting with them too.

What you get: everything!  Historicaly data, code, scripts to manage it, the domain.  It could use some cleaning up and love, but it does get the job done.

Running it just takes a few minutes a month, so I could hold on to it with no trouble, but I've decided that I want one less thing to think about.

Update: Some Numbers

In the last year, according to Google Analytics, the site had: 174,645 visits.

In the last month, it had 17,047 visits.

Revenue? Think of it as zero and you won't be too far off.  You would have to rework things significantly to make money from ads on it, I think.  

Hosting costs?  Not sure, particularly, it's on my Linode.  It utilizes Ruby on Rails, but creates static HTML pages, so it's fairly cheap.

 

Syndicated 2011-04-13 12:40:03 (Updated 2011-04-13 17:10:01) from David's Computer Stuff Journal

You win some, you lose some

A bit more than a month ago, I had the random idea to try building and selling a web site, at the same time.  The idea was that the more people bid, and requested features, the more I'd work on it.

It didn't work out.  I got a bit of money out of it, but  certainly not enough to cover my time at an hourly rate.

I suppose the lesson is that a month simply isn't a lot of time for something to mature: it'd probably be best to work on something on and off for a year, give it some time for traffic to build up, and so on, if the goal is to sell it.

However, in any case, I think I'm pretty convinced that my next projects, like LiberWriter, will involve for-pay products.  At heart, I'm not really a business guy, so picking the simplest possible business model probably makes sense: you pay me, I give you something.

Hopefully, I'll be able to write about those in the "you win some column", but I thought I'd let people know how the experiment went.

Syndicated 2011-03-19 10:01:29 (Updated 2011-03-19 10:16:37) from David's Computer Stuff Journal

Coming Soon: Easy Kindle Publishing with LiberWriter.com

The Kindle isn't the most beautiful device out there - it's not "beautiful", the keyboard takes away some elegance, but I'm absolutely smitten with mine.  I like to read, a lot, and being able to instantly beam books to my house is just fantastic.

Kindles and other devices like them are also changing the world of publishing, going from the known world of physical books that can't be easily copied to another information good like movies or songs with something of an uncertain future.

Yet they're also opening up many possibilities: thanks to Amazon's Kindle Direct Publishing program, it just got very easy to publish books to a platform that a lot of people regularly search for good things to read.  Once upon a time, "vanity publishing" was something done by those who simply wanted to see their names in print, but couldn't actually find a publisher, and thus carried some stigma.

Now, though, why not publish something you've always wanted to?  Granted, without an editor, and publisher to promote your work, you probably won't become rich or famous, but many people write for the enjoyment of doing so.  And who knows... there are already several cases of people publishing directly to the Kindle and making a decent income at it.

Indeed, I have several things I'm thinking of writing about that clicked when I found the Kindle publishing program.  Maybe now it's time to dust off some ideas I've had and start working on them a little bit at a time.

Then, of course, my geeky side took over and I started wondering how the mechanics of it actually work.

Messily, it turns out: the preferred format for Kindle authoring is variant of HTML that's not at all what we're used to in these days of ever more potent CSS.  The good side of it is that books mostly come out looking the same on the Kindle, and the end user can control how they want to visualize them.  The bad side of the system utilized is that there are a lot of tips and tricks and little things to know about the whole process that can be annoying even for someone who knows HTML pretty well.  For someone who just wants to write stuff and not worry about it, and who perhaps is not very familiar with HTML, the whole thing can be a huge mess and very frustrating.

Which of course looks like an interesting challenge.  I set out to work on LiberWriter.com several weeks ago, and it should be ready within the next week or two.  In short, it's a system that lets you concentrate on writing and, as much as possible, tries to get out of your way in order to let you concentrate on your content.  It is also targeted very specifically at the Kindle (for the time being at least), so as to really focus on making things work on that platform.  For instance, it can automatically generate a table of contents, a noted pain point in writing for the Kindle.  I have a number of other ideas up my sleeve too, that I'm excited to work on.

I'm also definitely abandoning the "let's release it for free, for fun, and see if I can find a way to make money later" model of many past projects, and treating it like a business.  I think the price I have in mind is very competitive, if you look at, for instance, conversion services that take word and spit out Kindle-specific HTML.

Anyway, have a look at the site and sign up if you're interested: as soon as it's ready, I'll email and let you know.  There'll be a somewhat limited trial version so that you can play around with it and see if you like it before buying the full version.

Syndicated 2011-03-15 20:30:04 (Updated 2011-03-15 20:59:08) from David's Computer Stuff Journal

Manipulating ckeditor data with jQuery

I'm working on a project that utilizes CKeditor and need to manipulate the data it contains.  Since I'm familiar with jQuery and it's fairly efficient at doing that sort of thing, rather than figuring out how CKeditor manipulates things internally, I wanted to, at least to get started, access things in jQuery.  There isn't a lot of information out there on the best way to do that.  Here's what I figured out - it seems to work pretty well:

    var editor = theeditor();
    var contents = $("<div id='specialwrapperthing'>" + editor.getData() + "</div>");

    .... hack away with jQuery ....
    editor.setData(contents.html());

Basically, you just wrap up what the editor hands you in terms of the data, hack away on it, and then put the HTML back into the editor.

Syndicated 2011-03-05 14:22:21 (Updated 2011-03-05 14:37:51) from David's Computer Stuff Journal

Random github idea: show pull requests on the network

Another day, another "which ^(&^%*&*^&()* version should I use?!" with github:

https://github.com/gramos/easy-fckeditor/network

Github is nice, but very, very often all the forks are the very model of a modern major paradox of choice.

Which one should I use?   Which one is best?  Do the forks exist because 1) the original author stopped bothering? 2) because the forkers just wanted to be 'cool' and have their own fork? 3) because the forkers don't have a clue about open source and don't attempt to submit their patches back?  Who the hell knows, in most cases.   This is frustrating.

I had a random idea that might help some: if the 'network' view were able to show you, at a glance, the amount of interaction between different forks: pull requests accepted and rejected.

At least we'd get an idea of what sort of community is forming around the project, and also have an idea whether the forkers and/or the authors are good open source citizens or not.

Of course, as my friend Salvatore says, "pull requests are not conversations", but it's better than nothing.

Syndicated 2011-02-17 08:55:54 (Updated 2011-02-17 09:14:50) from David's Computer Stuff Journal

410 older entries...

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!