1,275 karma · joined April 23, 2008
I also wrote http://leanpub.com/freelancedeveloperbook
[ my public key: https://keybase.io/stevejalim; my proof: https://keybase.io/stevejalim/sigs/ZE22KWshPnyhhnt5oMw5IRJfp9juGLuAs4QkrWSpovU ]
And whenever I had freelancers in who insisted that on-screen only was better/faster than on paper for them, I'd let them do it how they wanted, but they invariably spotted fewer mistakes, so not much faster in the long run. Anecdotal, sure, but paper works better in my view.
Edit: I'm 37
Hipchat's logging + API hooks are really handy
PS - thanks for the mention, soupangel
(I won't be sticking ads on it or anything lame like that - just thought it'd be a nice thing to exist).
Note: as of 8pm GMT, it's empty because I didn't want to harvest links from this thread without goodwill - but submissions are open, so please do get stuck in.
Yep, plenty. Enough, in fact, that I took the time to wrire them up in a book, which I'll also be extending as time goes on, based on feedback/requests from readers:
https://leanpub.com/freelancedeveloperbook
Use the coupon SHAMELESSPLUG before Jan 4 to get it for $9.99
For instance, the WGAC 2.0 guidelines require that HTML be valid, and if a client wants WGAC 2.0 compliance (even A level, not AA), the site's gotta validate [1].
[1] http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-pars...
One option in your situation is making a virtue of it (my other reply), another is working out what's making you skip around. Indeed, I think that's pretty important for you to try to have a handle on so that you can make better decisions as you go. Tricky thing is, the WHY is not always easy to work out.
Use the coupon MERRYCHRISTMAS at the checkout to get it for $0.
(The coupon runs out after five uses, in case other HNers get there before you.)
While that is effectively what you've been doing for the past three years, it'll come with a different mindset that might mean you're happier. (I'm assuming "help me" means you're not happy). For me, that's certainly one factor in why I prefer being an independent dev - but at the same time, I also get to enjoy working on good projects with great people for a run of time.
(Of course, being independent is for everyone, and has downsides, too)
"Hey, WTF are you doing quoting me £5000 for a full build of this app? I had the prototype done for $500 and it does almost as much as the real one I want."
Caveat/qualifier: every project was on Postgres.
1a) Why do you want it to be paper? And do you mean paper only? If so, my view is that you'd be looking at much lower revenue than if you were open to ebook versions (instead or as well). Don't overrate the prestige of paper these days. I'd rather 10,000 Kindle/PDF readers over 1000 paper-book readers.
1b) I've not dealt directly with traditional/print publishers as an on-the-books author (have never found a commission that pays enough to make the time+deadline worthwhile), but experience from dealing with them as a journalist (my previous life) is that there can be some really great people out there at publishers, but you need to find a good 'personality' match between you and the firm. What publishers whose books you have read seem most closely aligned with where your book is "at", culturally? If you can't think of any publishers because you haven't read any such books, get reading. If you can't think of any because there doesn't feel like there's a match, you've got a tougher challenge on your hands - self publishing may be the way forward.
2) The lack of a track record will make it harder to get publisher attention. Not impossible, but definitely harder. (This is partly why self-publishing is rising in popularity.) You'll need at least a couple of representative sample chapters and a solid synopsis of where this is going for them to get an idea of whether you're a) saying something worth reading and b) capable of expressing it well enough to work as a book. If you've got some kind of pedigree/relevant background/expertise/credibility that will help a lot, but only if you can write well. It may sound cynical, but these are all factors that help mitigate the publisher's risk in taking you on, and that's what really decides whether something gets published or not.
You'll also have to see whether the publisher you have in mind accepts unsolicited submissions. Not all of them do.
3) "Will such interviews be difficult for a first-time writer?" Have you interviewed anyone at all before? If not, practise on friends/family, interviewing them about anything (don't worry about writing/recording - just get used to the interplay.) Experience really helps you think on your feet and change what could be a pro-forma Q&A into a proper, interesting, interview. Doing it on the phone is good for that natural flow, but doing it over email may also work, depending on your question set and how you're planning to write it up.
If you're doing it over the phone, record it and transcribe it fully before writing it up. Keep the recordings and that paper record safe. They are your defence if someone challenges what you've written about them. Decide ahead whether you're going to let your interviewees read the resulting copy -- you don't have to, but for this kind of book I think it could be good to avoid inadvertent altered meanings during the write-up and the related fallout, if you're new to this.
4) Finding an independent editor is basically hiring a freelancer - lots of options if you google, variable quality unless you're careful [or lucky]. Look at how much money you think you might make from the book (depending on how you choose to publish), then halve that (because every writer over-estimates how much they'll really make) and then see how much of that you want to hand over to an editor, if you can still afford one.
You can save yourself some cash by doing as much prep and polish as you can: plan ahead for the structure of your book and its sections, get real friends to read it (not your parents - you need someone totally objective) and suggest changes. Be structured in your 'bug tracking' and keep polishing up to a pre-set number of revisions (else you'll go insane). If someone says your book is truly perfect, they're lying. But at least they're being nice.
5) I've bought 30-page things that call themselves books. I've also got a 600+ page hardback sitting here, waiting to be read. Don't sweat the number of words - focus on making whatever you're writing as useful and engaging as possible.
And, along with what danso says about writing a blog to get you started (which sounds like v good advice for someone who sounds relatively inexperienced in all this), check out leanpub.com, which is the most friction-free way to publish I've yet come across, with royalties that are far, far better than any print-book commission I was ever offered.
One key thing, for me, is that giving someone work requires _my_ trust in _their_ abilities. Some people might choose to base trust on a track record of projects listed on a CV, others on viewing someone's source code in a public repo, others might value personal recommendations, others might only trust people who they actually know from a not-too-distant circle of their professional network. I'm mostly in that last two camps. A cold-call email from a stranger: you'd be lucky to get a 2% genuine real-paid-work conversion rate, in my mind. A warm-call (I know that sucks as a term) email from someone I know via work or a conference or some kind of tech situation: far more likely to lead to work.
So, network. (And it's not the same as nepotism.)