Saturday, 24 December 2011

I’m Sticking With GoDaddy For The Right Reasons, Even If They’ve Done Wrong

Call the headline to this article overwrought, if you like, and you’ll be correct. But the way I view business is, you have partners, and the relationships you have with those partners are a balance.

If you’re a freelance coder and you’re not putting the same kind of thought and consideration you use in personal relationships into your business partners, you’re going to get burned. Because as it is with friends and lovers, you get out of customers and vendors alike exactly what you give.

I’ve put a lot into GoDaddy, and they’ve given me a lot back. That’s why, even though GoDaddy initially supported the Stop Online Piracy Act and only recanted under threat of boycott, I’m going to keep doing business with them.

For those in the dark and the benefits of post-event context, SOPA is a bill, before Congress at this writing, that would give broad censorship powers to the Department of Justice, ostensibly to block incorrigible copyright violators. It’s envisioned as a way to get the repeat scofflaws who are largely undeterred by the Digital Millennium Copyright Act (DMCA), which clearly has been almost completely ineffective at stopping brazen file sharing.

Continue reading: I’m Sticking With GoDaddy For The Right Reasons, Even If They’ve Done Wrong »

Wednesday, 12 October 2011

Hi Doug, I saw your response to a person on Yahoo answers, It was probably a couple of years ago. I’m trying toget my hands on a Sap tool to practice on it on my own. You mentioned you were doing the same at that time. Do you still have it? Thanks

Sorry, I don’t recall this. I did have a client a while back who was interested in SAP but I don’t believe I ever followed through.

If you could provide a link to the question, it might help refresh my memory.

I don’t believe I’ve ever said I use pirated software, and I’d be surprised to see anything in which I offered to share pirated software. It’s possible I noted that stealing software was an option, but I have to believe that if I said that, I also said that doing so was legally and morally wrong. Again, a link to the question you’re referencing would clear things up for me.

For the record, I have often said — and stand by the statement — that it’s everyone’s right to make personal copies of software he has legally purchased, even if a EULA forbids personal copies; but I don’t believe it’s OK to distribute copy-restricted software in violation of license terms.

Ask me anything

Friday, 5 August 2011

Review: Free: The Future of a Radical Price

Free: The Future of a Radical PriceFree: The Future of a Radical Price by Chris Anderson

My rating: 3 of 5 stars

Reading Free: The Future of a Radical Price reminded me, in many ways, of  The Grand Design.

To understand the universe on the quantum level, you have to embrace understandings and facts that seem ludicrous at human scales. That is, that we have free will; that things cannot be in the same place at the same time; that time progresses at one speed and forward only, are all convenient and explicit truths for our day-to-day existence. But at the subatomic level, that’s not how things work; not at all.

Anderson’s arguments about Free — that is, gratis and libre — are presented in the same sense, if not quite as well or explicitly.

Free does a fine job of explaining the mechanics of how things can be free on the Web: namely, per-unit / per-user costs are so low, they might as well be considered nothing.

He also does a good job of explaining the obvious money-making models applied successfully so far: advertising, freemium (basic service is free; premium service costs money) and non-monetary / indirect recompense, such as an increase in reputation / marketing of ancillary products, such as concerts and merchandise for musicians or speaking engagements and consultations for professionals.

Continue reading: Review: Free: The Future of a Radical Price »

Saturday, 16 April 2011

Good Contracts Make Good Business. Or, ‘F*ck You, Pay Me’

When I talk to new free-lance programmers about running a business, there are two core pieces of advice I offer. The first is that it‘s almost always better to have a little high-paying work than a lot of low-paying jobs. The other is the importance of a lawyer-reviewed contract that clearly defines the work to be produced, the date by which it will be completed and the cost of that work.

So I was very pleased to come across a Creative Mornings talk, given by Mike Monteiro of Mule Design and his attorney, Gabriel Levine, which reinforces and expands upon those basic ideas.

(via zeldman.com and Google Reader Play)

This is a long video (40 minutes) but worth every moment. But for the tl;dw crowd, here’s a synopsis of the salient points:

  1. Contracts protect both parties – you and your client.
  2. Don’t start work without a contract.
  3. Don’t blindly accept your client’s terms.
  4. Anticipate negotiation but don’t back down on important stuff – payment, deadlines and your intellectual property rights in the work until final payment is received.
  5. Lawyers talk to lawyers. If your client is talking to you in the presence of, or through, his lawyer, get yours or don’t talk.
  6. Be specific and confident about money. Ask for the rate you deserve and don’t back down on terms.

Continue reading: Good Contracts Make Good Business. Or, ‘F*ck You, Pay Me’ »

Tuesday, 22 March 2011

The Danger Of API Development: Making Something Too Good

On CNET, via slashdot: Lendle, a Web site that had helped facilitate the loaning of ebooks among Kindle users, was effectively destroyed when Amazon shut down Lendle’s access to its Kindle API.

Lendle first reported the news via Twitter: “Amazon has revoked Lendle’s API access. This is why the site is down. It’s sad and unfortunate that Amazon is shutting down lending sites…According to Amazon, Lendle does not ‘serve the principal purpose of driving sales of products and services on the Amazon site.’”

According to Lendle co-founder Jeff Croft, “at least two other Kindle lending services” have been terminated from the API.

The problem with Lendle and its cousins is simple: It was too good at what it did.

Amazon does allow one-time loans of an ebook for up to 14 days, but they expect such trading to be among intimates. Lendle greatly expanded the ability for one person to trade with a complete stranger, and as a result posed a serious threat to potential Kindle edition sales.

After all, if I can’t find someone to lend me an ebook, I probably have to buy it. Put me in big enough a room of Kindle owners, however, and I’m likely to find what I am after for free.

I don’t care to get into copyright, the nature of modern publishing, or the like. I’m far more interested in pointing out the problem with using third-party APIs that this illustrates: If you make something too good, there’s usually nothing stopping the API service from cutting you off and stealing your work.

Continue reading: The Danger Of API Development: Making Something Too Good »