Remember when I said the book was almost done? It’s done. The first full draft, anyway 😅. Every chapter written, every code sample compiling, every paragraph existing in some form that I’m not immediately embarrassed by. I think.
I sat with it for a few days after finishing the last chapter, half expecting to find a gaping hole somewhere. A missing concept, a chapter that secretly makes no sense. But no. It holds together (again: I think – I’m a bit blind at this point… And better at starting projects than finishing them). Which means I’m now in that strange phase where the writing is done but the book isn’t, because I don’t have a designated editor or a team of readers giving me feedback.
So I need feedback!
Two kinds of readers Link to heading
I’m looking for two types of people right now.
If you want to buy the book, it’s on Leanpub. You can grab it at whatever stage it’s in and you’ll get every update from here on out. Leanpub is nice that way.
If you want to review the book, that’s what I’m really after. I want people who will read it with a pen in hand (metaphorically, unless you print it out, in which case I respect the commitment). Tell me where you got confused, where I lost you, where I spent too long on something obvious or skipped past something that needed more explanation. I want the kind of feedback that makes the final version actually good, not just finished.
What’s in it for you: your name in the preface (with a quote if you want) and the chance to shape what the book becomes. If you’ve bought the book on Leanpub you already have the full manuscript – go wild. If not, I’ll send you one or more chapters to review. I don’t want the price tag to be a barrier; I’d rather have honest feedback from someone who hasn’t paid than no feedback at all.
I’m genuinely open to restructuring, cutting, and rewriting based on what reviewers tell me. The draft is done, but it’s not precious nor is it set in stone.
Who I’m looking for Link to heading
You don’t need to be an Elm expert. In fact, I’d love some reviewers who are coming from React in particular or even just TypeScript in general and have never touched Elm. That’s the audience I wrote for, and I need to know if it actually works for them.
If you are an Elm person, that’s great too – I want someone to tell me when I’ve explained something wrong or missed an idiomatic approach.
Basically: if you’re willing to read one or more 10 page ish chapters about Elm and tell me what you honestly think, I want to hear from you.
Get in touch Link to heading
Send me an email at christian.ekrem+book-review@gmail.com. Tell me a bit about your background and whether you’re interested in reviewing or just want to follow along. I’ll send you some chapters.
(And if you’ve already bought it on Leanpub and want to review, obviously that counts too, and I’m btw grateful. Just email me.)